feat: delivery-discipline rule (DoR/DoD formalized) + main runs never self-cancel

Owner-mandated framework, researched to the converged standard and
found to need NAMING, not building: Scrum 2020's DoD (a formal
artifact commitment) + Kanban University's ready-for-delivery pull
criteria are the industry vocabulary for gates this repo already runs
— consolidated into ONE always-loaded rule
(.claude/rules/delivery-discipline.md) instead of four documents.
Estimation deliberately excluded (negotiates team capacity a
solo+agent loop doesn't have); peer review already settled by
ADR-0034. Build-health becomes a ritual, not a wonder: gh pr checks
--watch after opening a goal PR; gh run list -b main -L 1 at goal
pickup. Tech debt: same queue, same DoR/DoD, never a shadow register.

Plus the real config bug the research found: cancel-in-progress
applied to main's post-merge runs too, so two quick merges cancelled
the earlier one's verification (observed live: merges #1/#10) —
now conditional per GitHub's own documented pattern; PR runs still
supersede, main runs always complete.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FYwojT8GdUbYSoggbvEFft

Author: alicoding

.claude/rules/delivery-discipline.md

@@ -0,0 +1,49 @@
+# Delivery discipline — Definition of Ready / Definition of Done
+
+No `paths` frontmatter — applies to every goal, every language. Terms
+are Scrum's (the 2020 Scrum Guide formalized DoD as an artifact
+commitment) and Kanban's (Kanban University's own "ready for delivery"
+pull criteria) — adopted as the converged NAMES for gates this repo
+already runs, consolidated here from CLAUDE.md/testing.md/ADR-0034 so
+an agent checks ONE list, not four documents (researched 2026-08-12;
+owner-mandated: "DoR should be industry standard").
+
+## Definition of Ready — before a BACKLOG.md item enters a session
+- Precedent checked, not assumed (CLAUDE.md Research→Plan→Implement).
+- A capability map exists for any schema/adopt-vs-build call with more
+  than one real future use (CLAUDE.md Plan step, SPEC §3.3's worked
+  example).
+- A goal file exists: Goal/Plan/**Acceptance stated as a checkable
+  predicate**, not a vibe.
+- No SPEC.md `OPEN` dependency is silently resolved by starting —
+  surface the choice, or name it an explicit blocker and don't start.
+- No estimate/story-point step — deliberately excluded: estimation
+  negotiates shared *team* capacity, which a solo-owner +
+  agent-execution loop doesn't have.
+
+## Definition of Done — before the checkbox flips and the file moves to archive/
+- Local lefthook suite green, never bypassed.
+- CI's `ci-gate` required check green on the **merged** PR (ADR-0034).
+- Every new capability carries a seeded example + a proof at the right
+  layer (testing.md's layering) — the seed is part of DoD, never a
+  follow-up.
+- Any bug fixed via live/manual repro is now a committed test
+  (testing.md).
+- SPEC.md updated in the same change, for anything that shifts what it
+  describes (mechanical-only changes exempted).
+- The goal file's own Acceptance criteria checked against what
+  SHIPPED, not what was planned.
+- Nothing secret-shaped staged; a real commit message.
+
+## Build-health visibility
+The ruleset (ADR-0034) already makes main unmergeable-red; confirm,
+don't re-enforce:
+- `gh pr checks <n> --watch` right after opening a goal's PR.
+- `gh run list -b main -L 1` once, when picking up the next goal.
+No richer signal is worth building — a webhook receiver is a second
+deployable, already forbidden (SPEC §1.1).
+
+## Tech debt
+A BACKLOG.md entry with the same DoR/DoD as any goal — never a second
+register, never a bare TODO as the record (a comment may point at a
+goal/ADR id, never stand alone).

.github/workflows/ci.yml

@@ -15,7 +15,14 @@ permissions:
 
 concurrency:
   group: ci-${{ github.workflow }}-${{ github.ref }}
-  cancel-in-progress: true
+  # Conditional, per GitHub's own docs pattern: a superseded PR run
+  # SHOULD die (per-PR synthetic ref), but main's post-merge runs must
+  # each complete — with `true` here, two merges landing close together
+  # cancelled the earlier merge commit's own verification run, leaving
+  # that main SHA's CI status permanently incomplete (observed live
+  # 2026-08-12: merges #1/#10 showed cancelled; the mirror image of
+  # ADR-0034's bisect-blind-spot concern).
+  cancel-in-progress: ${{ github.ref != 'refs/heads/main' }}
 
 jobs:
   # goal 0024 / ADR-0034's un-deferred path-filtering: skip the heavy