[JacobStephens2]

Summary

Glossary and ADR for Spec runs, from the grilling on #28 that produced spec #139. Docs only.

 CONTEXT.md
+  Spec, Ticket               (cite Matt Pocock's AI Coding Dictionary)
~  Run                        narrowed to one issue that isn't a Spec
+  Spec run, Spec branch, Spec PR, Unready Ticket, Spec review, Failed spec run
~  Base branch                a Ticket's Run uses the Spec branch
~  Merge run                  a Ticket's Run is always one, into the Spec branch
~  Repair                     also runs on the Spec PR after the Spec review
 docs/adr/
+  0006-spec-runs-merge-tickets-into-a-spec-branch.md

ADR 0006 covers four decisions:

• Each Ticket self-merges into a Spec branch, and the day shift reviews one Spec PR.
• Tickets run in parallel, 3 at once by default.
• Each Ticket's Run is a child thirdshift process.
• Agents run only where their judgement is needed.

Evidence

• Before: CONTEXT.md had no word for a multi-Ticket issue, and no record of how one would be implemented.
  After: Spec runs: work through a Spec's Tickets in dependency order, in parallel, into one Spec PR #139 is written entirely in these terms, and ADR 0006 records the alternatives it rejects: Tickets merged straight to main, Tickets left ready for review, running them one at a time, threads instead of processes, and an agent-driven implement-spec.

Merge Danger

Door: two-way

No code changes. The only term whose meaning changes is Run, which is narrowed to issues that aren't Specs. That's accurate today, because Spec runs don't exist yet.

Blast Radius: docs

Agents reading CONTEXT.md will see the Spec run terms before the feature ships.

🤖 Generated with Claude Code