Regular case · derived from the record · Heddle

heddle: tighten DemoForm + login validation UX (#475)

6 merges over 4 days on the heddle surface, #480 to #527. Arc 2 of 136 by length.

The arc, on its own days

2026-05-202026-05-24#480#505#507#508#526#527
1 feature4 docs1 bugfix

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

2026-04-202026-09-03

135 merges on heddle in the corpus; this arc is 6 of them.

The merges, verbatim

  1. heddle: tighten DemoForm + login validation UX (#475)

    #480 · 2026-05-20 · feature

  2. docs(heddle): close 4 shipped-mitigation risks in the register

    #505 · 2026-05-24 · docs

  3. docs(heddle): add canonical master PRD (current + future state)

    #507 · 2026-05-24 · docs

  4. docs(heddle): place UX epic + agent spec, wire PRD refs, mirror epic into LAUNCH-PLAN

    #508 · 2026-05-24 · docs

  5. test(heddle): fix milestone-count assertion broken by UX epic mirror

    #526 · 2026-05-24 · bugfix

  6. build(heddle): run parse-docs test in pre-commit on heddle doc edits

    #527 · 2026-05-24 · 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 heddle

All casesThe corpus as JSONThe pull requests on GitHub

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

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 →