Regular case · derived from the record · DevOps

ci: auto-seed client portals (projects.mjs → portal_projects) on merge

2 merges over one day on the ci surface, #1090 to #1104. Arc 102 of 136 by length.

The arc, on its own days

2026-06-13#1090#1104
1 infra1 docs

The surface's whole history, this arc's weeks in indigo

2026-03-092026-09-18

38 merges on ci in the corpus; this arc is 2 of them.

The merges, verbatim

  1. ci: auto-seed client portals (projects.mjs → portal_projects) on merge

    #1090 · 2026-06-13 · infra

  2. docs(workflow-studio): RFC + epic for a visual Workflow Designer Studio

    #1104 · 2026-06-13 · docs

What this page is

No one has written this case yet. Everything on this page is derived from the pull-request record by the same deterministic rules as the corpus: a feature or infrastructure merge opens an arc, and bug fixes, refactors, tests, and docs on the same surface within forty-five days follow it. Titles are verbatim from GitHub. Nothing here is a claim beyond the record.

Written up

No premier case cites this arc yet. It is a candidate.

Other arcs on ci

All casesThe corpus as JSONThe pull requests on GitHub

www.jakelawrence.xyz/research/case-study-library/arc/1090

Derived at build from the corpus snapshot of 2026-09-20; re-derives on every build. Base /research/case-study-library/arc.

Need something like this built?

I design and ship AI tools, full-stack apps, and data pipelines — end to end, to production. Tell me the problem in a sentence; I'll give you an honest read on fit within a day.

Work with me →