@afokapu/atdd-bun 0.7.2 → 0.8.1

package/README.md

@@ -55,6 +55,7 @@ registerEnforcementTest({ root: import.meta.dir + "/..", profiles: ["traceabilit
 | `topology` | feature decomposition and the plan, source, test and E2E locations |
 | `planner` | schemas for every plan artifact, graph integrity, the scoped planner rules |
 | `telemetry` | the telemetry tracking plan: item shape, path-mirrored identity and versioning under `telemetry/`, wagon ownership of logical artifacts, the per-acceptance telemetry decision, metric label cardinality, source `Telemetry:` references, raw-string and forbidden-property emission, the vendor-SDK boundary around the TelemetryPort, and telemetry tests that bind the acceptance and item, assert the exact identity on a captured sink, cover every required item, and exercise declared timing semantics |
+| `delivery` | the review record of each tranche under `delivery/`: allowed author and reviewer models with recorded fallbacks, reviewer independence, every finding fixed, withdrawn after one dispute or ruled on by a human, every configured stage approved, and, at the gate, no change without a record and a merged head that contains exactly the approved commit. Inert until adopted |
 | `docs` | the documentation capability, including the generated journey view |
 | `coder`, `tester`, `security`, `architecture`, `metrics`, `runtime` | Bun source and test conventions |
 | `interlocking` | train/interlocking binding, infrastructure and route coverage |
@@ -84,7 +85,7 @@ the adoption that establishes the governed set, so a brownfield repository can d
 `profiles: [docs]` in an ordinary pull request. From then on, the integrity check reports, against
 the base branch, removing a profile from the list and removing the list itself. The second closes
 the two-step bypass `[docs, security]` → no list → `[docs]`. `init` writes a new `atdd-bun.yaml`
-with every profile listed, so a greenfield repository is governed from its first commit; trim the
+with every profile listed except the opt-in `delivery`, so a greenfield repository is governed from its first commit; trim the
 list before that commit to adopt gradually.
 
 ## Configuration
@@ -108,6 +109,45 @@ worktrees: { enabled: false }
 release: { enabled: false }
 ```
 
+### Delivery
+
+For programs delivered as tranches by a coordinator and persistent drivers, with headless authors
+and independent reviewers. Adopt it by naming `delivery` in `profiles:` (or, with no list, by adding
+a `delivery:` block); `agent init` then installs the delivery skill and its review contract. The
+adopting pull request is itself governed: it changes files outside the delivery root, so it carries
+its own tranche record, reviewed and `ready` like any other. Every key is optional; these are the
+defaults:
+
+```yaml
+delivery:
+  root: delivery                     # one <tranche>/evidence.yaml per tranche, reports beside it
+  require_record: true               # at the gate, a change outside the root needs a tranche record
+  multiplexer: herdr                 # the terminal multiplexer agents run in; any command name
+  independence: fresh-process        # or different-model; overridable per stage
+  stages:                            # models in preference order: the first, then recorded fallbacks
+    plan_review:  { authors: [codex],       reviewers: [glm, claude] }
+    test_review:  { authors: [glm, claude], reviewers: [codex, claude] }
+    code_review:  { authors: [glm, claude], reviewers: [glm, claude] }
+    final_review: { authors: [codex],       reviewers: [codex, claude] }
+  fallback: { after_failures: 3, within_minutes: 10, when_exhausted: block }   # or wait
+  commands: {}                       # per model: { author: "...", review: "..." } overriding the skill's defaults
+```
+
+The profile checks the record, never the running agents. The generated CI sets
+`ATDD_DELIVERY_GATE`: `merge` on pull requests and the merge queue, where every record the branch
+changes must be `ready`, the branch may differ from its approved SHA only under the delivery root,
+and a change outside the root needs a record (`require_record`, default true); `post-merge` on a
+push to a protected branch (the generated workflow's push branches follow `protected_branches`), where the pushed commit must contain every approved SHA it brings in. Merge tranches with a
+merge commit: a squash or rebase merge writes a commit no reviewer saw, and the post-merge check
+fails on it. Moving the root, dropping a stage, relaxing a stage from `different-model` to
+`fresh-process`, adding an author or reviewer, moving a fallback model earlier in a list, turning off
+`require_record`, making fallback easier, or adding or changing a model's `commands` loosens the policy and is reported by the integrity check.
+
+The record's model and run identifiers are the driver's claims. The profile checks that they are
+consistent and that a `ready` record retains every review's raw report (a record in progress may lag
+behind); it does not verify them
+cryptographically.
+
 The hooks enforce protected-branch blocking, micro-commit limits, mass-delete approval and
 validation of the affected area. Git can bypass them, so CI is the authority.
 
@@ -115,14 +155,15 @@ validation of the affected area. Git can bypass them, so CI is the authority.
 
 The skill gives every coding agent the lifecycle PLAN → RED → GREEN → SMOKE → REFACTOR → TRACE and
 the profile that gates each stage. The block in `AGENTS.md` and `CLAUDE.md` adds the rules: never
-modify the toolkit itself, only the configuration it offers, and enable capabilities through
-`profiles`.
+modify the toolkit itself, only the configuration it offers; turn profiles on or off in
+`profiles:` only when the user asks; and, where `delivery` is active, deliver tranches through the
+delivery skill.
 
 `atdd-bun integrity`, run by the generated test and first in CI on a clean install, fails when:
 
 - the installed package differs from its published hashes;
 - the dependency is not an npm registry version;
-- a generated file (workflow, skills, instruction block, integrity test) was edited;
+- a generated file (workflow, skills, the delivery review contract, instruction block, integrity test) was edited;
 - `atdd-bun.yaml` is looser than on the base branch (after the first explicit `profiles:` list,
   dropping a profile or the list counts).
 

package/conventions/delivery/delivery.approved-sha-resolves.convention.yaml

@@ -0,0 +1,33 @@
+schema_version: 1.1.0
+rule_id: delivery.approved-sha-resolves
+kind: rule
+status: active
+name: The approved SHA is a commit in this repository
+statement: >-
+  A ready record's approved_sha resolves to a commit in the repository's history, and every configured stage's last approval names a commit in approved_sha's history, each stage's containing the one before it in lifecycle order (REQUIRED).
+terms:
+- term_id: approved_sha
+  text: >-
+    the commit the closing review approved and the tranche asks to merge.
+content:
+  summary: >-
+    An approval of a commit nobody can find proves nothing: it may be a typo, a rewritten history, or an invention.
+  normative_text: |
+    The validator asks Git whether the commit exists. A rebase after approval changes every SHA and therefore needs a fresh review; the record cannot be updated by hand to follow it.
+  fix_hint: |
+    Record the full or abbreviated SHA the final review named. After a rebase, run the final review again on the new head.
+  exceptions:
+  - >-
+    At the gate, a record the change does not touch is not judged again: it was judged when it merged, and its tranche branch may be gone. Outside the gate every ready record is judged.
+  - >-
+    A shallow clone may lack the commit: CI must fetch full history (the generated workflow uses fetch-depth 0).
+metadata:
+  aliases:
+  - DELIVERY-APPROVED-SHA-RESOLVES-001
+  severity: 3
+  # strict: atdd-bun fails on every finding; it has no advisory mode and no ratchet baseline.
+  disposition: strict
+  introduced_in: 0.8.0
+implementation:
+  type: validator
+  ref: delivery_evidence

package/conventions/delivery/delivery.config-schema.convention.yaml

@@ -0,0 +1,43 @@
+schema_version: 1.1.0
+rule_id: delivery.config-schema
+kind: rule
+status: active
+name: The delivery policy in atdd-bun.yaml is well-formed
+statement: >-
+  The `delivery:` block of atdd-bun.yaml validates against delivery-config.schema.json: known keys only, each stage listing at least one reviewer, models named in lowercase, independence one of fresh-process or different-model, the root in canonical form (no leading, trailing or doubled slash, no dot segment) and not overlapping the plan, source, test, e2e or telemetry root (REQUIRED).
+terms:
+- term_id: policy
+  text: >-
+    the `delivery:` block: root, independence, stages (per stage: authors, reviewers, optional independence), fallback and commands. Every key is optional; an omitted key takes the package default.
+content:
+  summary: >-
+    The skill and the validators read the same policy. A misspelled key would be ignored by one and not the other, so a malformed block is a finding, and the rest of the run judges evidence against the package defaults.
+  normative_text: |
+    The policy decides which models may author and review each stage, in preference order, how independent a reviewer must be, and when a model counts as unavailable. It is read by the delivery skill when it dispatches work and by this profile when it judges the record, so both must see the same, valid document.
+  fix_hint: |
+    Correct the key the finding names. The defaults are:
+
+      delivery:
+        root: delivery
+        independence: fresh-process
+        stages:
+          plan_review:  { authors: [codex], reviewers: [glm, claude] }
+          test_review:  { authors: [glm, claude], reviewers: [codex, claude] }
+          code_review:  { authors: [glm, claude], reviewers: [glm, claude] }
+          final_review: { authors: [codex], reviewers: [codex, claude] }
+  exceptions:
+  - >-
+    Adoption is not exempt from the gate: the pull request that adopts delivery changes files outside the delivery root,
+    so it carries its own ready tranche record like any other change.
+  - >-
+    Inert until adoption: with no `delivery:` block and `delivery` absent from `profiles:`, no delivery rule emits anything.
+metadata:
+  aliases:
+  - DELIVERY-CONFIG-SCHEMA-001
+  severity: 3
+  # strict: atdd-bun fails on every finding; it has no advisory mode and no ratchet baseline.
+  disposition: strict
+  introduced_in: 0.8.0
+implementation:
+  type: validator
+  ref: delivery_evidence

package/conventions/delivery/delivery.evidence-schema.convention.yaml

@@ -0,0 +1,34 @@
+schema_version: 1.1.0
+rule_id: delivery.evidence-schema
+kind: rule
+status: active
+name: Every tranche folder holds a well-formed evidence record
+statement: >-
+  Every folder under the delivery root holds an evidence.yaml that validates against delivery-evidence.schema.json, whose tranche matches the folder name, whose reviews each name an author and a configured stage, and whose reports are data files (json, jsonl, yaml, yml, txt, md, log) inside the tranche's own folder, one per review; a ready record names one for every review (delivery.stages-complete) (REQUIRED).
+terms:
+- term_id: tranche
+  text: >-
+    one independently mergeable piece of a program, delivered on its own branch by one persistent driver through PLAN, RED, GREEN, SMOKE, REFACTOR and TRACE, with its reviews.
+- term_id: evidence
+  text: >-
+    the tranche's record of its reviews at `<root>/<tranche>/evidence.yaml`: status (open or ready), base and approved SHAs, and the chronological list of reviews, each with stage, reviewed SHA, author, reviewer, fallbacks, verdict, the checklist it went through and its findings.
+content:
+  summary: >-
+    The record is what CI can check. A review that is not written down, or written down in a shape the validator cannot read, did not happen as far as the merge gate is concerned.
+  normative_text: |
+    The profile judges the record a tranche leaves, not the agents while they work. Each review is appended, never edited, so a repair loop shows as a request-changes entry followed by a fresh review of the same stage. A review must name its author: independence is judged against the author, and without one it cannot be judged.
+  fix_hint: |
+    Create or repair `<root>/<tranche>/evidence.yaml`; the finding names the schema path at fault. A request-changes review carries at least one finding; every review carries its `checked` list.
+  exceptions:
+  - >-
+    Files other than evidence.yaml inside a tranche folder (retained raw reviewer reports) are not judged.
+metadata:
+  aliases:
+  - DELIVERY-EVIDENCE-SCHEMA-001
+  severity: 3
+  # strict: atdd-bun fails on every finding; it has no advisory mode and no ratchet baseline.
+  disposition: strict
+  introduced_in: 0.8.0
+implementation:
+  type: validator
+  ref: delivery_evidence

package/conventions/delivery/delivery.findings-resolved.convention.yaml

@@ -0,0 +1,42 @@
+schema_version: 1.1.0
+rule_id: delivery.findings-resolved
+kind: rule
+status: active
+name: Every finding is fixed, withdrawn after one dispute, or ruled on by a human
+statement: >-
+  Once a stage has a later review, or the record is ready, every finding of a request-changes review records its outcome: fixed (confirmed by a later review of the stage), withdrawn (after a written rebuttal, by a later review that does not raise it again) or human (with the decision). A finding disputed more than once goes to a human. An approving review carries no critical or high finding (REQUIRED).
+terms:
+- term_id: rebuttal
+  text: >-
+    the author's written dispute of a finding, with evidence: a test result, a rule id, a file and line. The next fresh reviewer upholds or withdraws the finding.
+- term_id: outcome
+  text: >-
+    fixed, withdrawn or human, recorded on the finding where it was raised.
+content:
+  summary: >-
+    A reviewer can be wrong and an author can be wrong. One written round, judged by a fresh reviewer, settles most disagreements; the rest go to a human instead of looping.
+  normative_text: |
+    No conversation between author and reviewer: a reviewer is stateless, and a long exchange turns it into a co-author. The author fixes a finding or disputes it once in writing; the next fresh reviewer decides. If that reviewer upholds a disputed finding, the tranche emits BLOCKED disputed-finding and a human rules.
+  fix_hint: |
+    On each finding of the request-changes review, record the outcome:
+
+      outcome: fixed
+
+      rebuttal: "handler.test.ts:31 proves the loop stops on abort"
+      outcome: withdrawn
+
+      outcome: human
+      decision: "Keep the retry; the caller owns the bound."
+  exceptions:
+  - >-
+    While a stage has no later review and the record is open, a finding without an outcome is work in progress, not a finding.
+metadata:
+  aliases:
+  - DELIVERY-FINDINGS-RESOLVED-001
+  severity: 2
+  # strict: atdd-bun fails on every finding; it has no advisory mode and no ratchet baseline.
+  disposition: strict
+  introduced_in: 0.8.0
+implementation:
+  type: validator
+  ref: delivery_evidence

package/conventions/delivery/delivery.merge-gate.convention.yaml

@@ -0,0 +1,42 @@
+schema_version: 1.1.0
+rule_id: delivery.merge-gate
+kind: rule
+status: active
+name: A tranche merges only its approved SHA
+statement: >-
+  At the gate (ATDD_DELIVERY_GATE, which the generated CI sets to merge on pull requests and the merge queue and to post-merge on pushes to the protected branches), every evidence record the change touches is ready and approves a commit the head contains; before the merge the head differs from that commit only by the record and the reports it names; no record is deleted, and no record or report already on the base branch is modified; under the delivery root only records and the reports a changed record names change; and, with require_record (the default), a change outside the delivery root comes with a tranche record (REQUIRED).
+terms:
+- term_id: merge_gate
+  text: >-
+    the CI run that decides whether a pull request may merge. It compares the branch against the base it merges into; for a merge checkout, the base is the first parent and the head the second.
+content:
+  summary: >-
+    Any commit after approval, a code change, a regenerated file, a conflict resolution or a rebase, invalidates it. The evidence commit itself is the one change allowed, since it cannot be in the SHA it records. A change with no record at all was never reviewed.
+  normative_text: |
+    This is where the profile becomes a merge rule rather than an instruction. Records that the change does not touch, earlier tranches already on the base branch, are not judged again; their approved SHAs may no longer be the head of anything.
+    After the merge, a push is judged from its previous tip (the generated CI passes it as ATDD_BASE_REF; a first push falls back to the parent): every record it brings in must approve a commit it contains. A deleted record never counts as the record that covers a change. A squash or rebase merge writes a new commit no reviewer saw and fails here, visibly, on the base branch; merge tranches with a merge commit. Drift is judged after the merge too, at the tranche's side of a merge commit or at the head of a direct push, over the files the push brings in. Only <root>/<tranche>/evidence.yaml is a record; an evidence.yaml at any other depth covers nothing. A rename is a deletion. When several tranches land in one change, a file another changed ready record approved with exactly that content is not drift.
+  fix_hint: |
+    Run the final review on the current head and record its SHA as approved_sha, or remove the change made after approval. Locally, reproduce the gate with ATDD_DELIVERY_GATE=merge ATDD_BASE_REF=origin/main bun run atdd-bun delivery.
+  exceptions:
+  - >-
+    Outside the gate (hooks, local runs) this rule emits nothing, so a tranche can push work in progress.
+  - >-
+    Before the merge, a pull request is judged at its head (the second parent of the test merge GitHub computes), not at
+    that merge commit; content only a merge commit introduces is judged after the merge, where a push is judged whole.
+    Judging GitHub's merge result instead would report the base branch's own changes to the same files as drift.
+  - >-
+    The policy governs the tree it sits in. With atdd-bun.yaml in a subfolder (a monorepo package run with --root),
+    require_record covers that subfolder, not the rest of the repository, which another policy or none governs; the
+    generated workflow runs from the repository root, and drift from an approved commit is judged repository-wide.
+  - >-
+    require_record false exempts changes with no record; turning it off is a loosening the integrity check reports.
+metadata:
+  aliases:
+  - DELIVERY-MERGE-GATE-001
+  severity: 3
+  # strict: atdd-bun fails on every finding; it has no advisory mode and no ratchet baseline.
+  disposition: strict
+  introduced_in: 0.8.0
+implementation:
+  type: validator
+  ref: delivery_evidence

package/conventions/delivery/delivery.model-allowed.convention.yaml

@@ -0,0 +1,36 @@
+schema_version: 1.1.0
+rule_id: delivery.model-allowed
+kind: rule
+status: active
+name: Authors and reviewers are allowed models, and every fallback says why
+statement: >-
+  Each review's author and reviewer model appears in that stage's authors and reviewers lists; a model after the first is used only with a recorded fallback from each model before it, stating the kind of unavailability (outage, rate_limit, no_report, timeout), the failures observed (at least delivery.fallback.after_failures) within a window no longer than delivery.fallback.within_minutes, and the reason (REQUIRED).
+terms:
+- term_id: fallback
+  text: >-
+    a recorded switch from a preferred model to the next one in the stage's list, with role (author or reviewer) and a reason: an outage, a rate limit, or no auditable report. A REQUEST CHANGES verdict is never a reason.
+content:
+  summary: >-
+    The lists are the operator's choice of who may do the work. A silent switch to another model hides an outage and can hide a reviewer chosen for being lenient.
+  normative_text: |
+    The first model in a list is used normally. When it is unavailable, the driver falls back to the next one and records it. A fallback is never triggered by a verdict: shopping for a reviewer until one approves is exactly what this rule exists to expose.
+  fix_hint: |
+    Record the fallback on the review:
+
+      fallback:
+        - { role: reviewer, from: glm, kind: rate_limit, failures: 3, window: { from: "2026-09-25T09:00:00Z", to: "2026-09-25T09:08:00Z" }, reason: "429 on 3 attempts in 10 minutes" }
+
+    or use a model the stage lists.
+  exceptions:
+  - >-
+    When a stage lists one model, no fallback is possible: an unavailable model blocks the tranche.
+metadata:
+  aliases:
+  - DELIVERY-MODEL-ALLOWED-001
+  severity: 2
+  # strict: atdd-bun fails on every finding; it has no advisory mode and no ratchet baseline.
+  disposition: strict
+  introduced_in: 0.8.0
+implementation:
+  type: validator
+  ref: delivery_evidence

package/conventions/delivery/delivery.reviewer-independent.convention.yaml

@@ -0,0 +1,34 @@
+schema_version: 1.1.0
+rule_id: delivery.reviewer-independent
+kind: rule
+status: active
+name: Every reviewer is a fresh process independent of the authors
+statement: >-
+  A reviewer's run never authored anything in the tranche and never reviewed another entry; where the stage requires different-model independence, the reviewer's model also differs from the stage author's (REQUIRED).
+terms:
+- term_id: run
+  text: >-
+    the identity of one process: a session id, a pane id with its start time, or the retained report. Two entries with the same run were produced by the same process.
+- term_id: independence
+  text: >-
+    fresh-process: the reviewer is a new process that authored nothing. different-model: additionally, its model is not the author's.
+content:
+  summary: >-
+    A reviewer that edits becomes an author, and a reviewer that already saw an earlier round is anchored to it. Independence is what makes an approval evidence.
+  normative_text: |
+    Every review is a new process. The run identifiers make that checkable: a reviewer run that appears as an author anywhere in the tranche, or on a second review, is not independent. The stricter mode is chosen per stage in the policy.
+  fix_hint: |
+    Re-run the review in a fresh process and record its own run; under different-model, use a reviewer model other than the author's.
+  exceptions:
+  - >-
+    The persistent driver authors the plan and opens the PR; its run may never review.
+metadata:
+  aliases:
+  - DELIVERY-REVIEWER-INDEPENDENT-001
+  severity: 3
+  # strict: atdd-bun fails on every finding; it has no advisory mode and no ratchet baseline.
+  disposition: strict
+  introduced_in: 0.8.0
+implementation:
+  type: validator
+  ref: delivery_evidence

package/conventions/delivery/delivery.stages-complete.convention.yaml

@@ -0,0 +1,31 @@
+schema_version: 1.1.0
+rule_id: delivery.stages-complete
+kind: rule
+status: active
+name: A ready record has every configured stage approved
+statement: >-
+  A record with status ready has, for every stage the policy configures, a last review that approves; its approved_sha is the SHA the last review of the closing stage approved; every review names its retained raw report, which exists; and, when code_review is configured and is not the closing stage, nothing outside the delivery root changed between code_review's last approval and approved_sha, since a code change goes back through code_review (REQUIRED).
+terms:
+- term_id: closing_stage
+  text: >-
+    the last configured stage in lifecycle order (plan_review, test_review, code_review, final_review); by default final_review, the review of the PR head.
+content:
+  summary: >-
+    Ready is the driver's claim that the tranche can merge. It is only true when no stage is missing and the approval covers the commit being merged.
+  normative_text: |
+    Each stage may take several rounds; only its last review counts. The closing stage's approval names the SHA the whole tranche stands on, and approved_sha must be that SHA: the merge gate compares the branch head against it.
+  fix_hint: |
+    Run the missing review, or set status back to open until it has run. Set approved_sha to the SHA the final review approved.
+  exceptions:
+  - >-
+    A stage the policy omits is not required. Omitting one loosens the policy and is reported by the integrity check until a human approves it.
+metadata:
+  aliases:
+  - DELIVERY-STAGES-COMPLETE-001
+  severity: 3
+  # strict: atdd-bun fails on every finding; it has no advisory mode and no ratchet baseline.
+  disposition: strict
+  introduced_in: 0.8.0
+implementation:
+  type: validator
+  ref: delivery_evidence

package/detectors/delivery_evidence/atdd.implementation.yaml

@@ -0,0 +1,33 @@
+schema_version: "1.0.0"
+kind: implementation
+subtype: validator
+implementation_id: delivery.evidence.impl
+targets_workspace: atdd.workspace.bun
+contract_version: "1.0.0"
+# The delivery record: one <root>/<tranche>/evidence.yaml per tranche, judged against the `delivery:` policy
+# in atdd-bun.yaml. Runs only under the delivery profile and is inert until the repository adopts it
+# (a `delivery:` block, or `delivery` named in `profiles:`).
+emits_rule_ids:
+  - delivery.config-schema
+  - delivery.evidence-schema
+  - delivery.model-allowed
+  - delivery.reviewer-independent
+  - delivery.findings-resolved
+  - delivery.stages-complete
+  - delivery.approved-sha-resolves
+# Emitted only at the merge gate (ATDD_DELIVERY_GATE=merge, set by the generated CI on pull requests and the
+# merge queue): it needs a change set against the base branch. tests/delivery.test.ts triggers it in a real
+# repository.
+api_emits_rule_ids:
+  - delivery.merge-gate
+realizes_convention:
+  - delivery.config-schema
+  - delivery.evidence-schema
+  - delivery.model-allowed
+  - delivery.reviewer-independent
+  - delivery.findings-resolved
+  - delivery.stages-complete
+  - delivery.approved-sha-resolves
+  - delivery.merge-gate
+entrypoint: detect.mjs
+report: detect.mjs

package/detectors/delivery_evidence/detect.mjs

@@ -0,0 +1,9 @@
+import { mkdir, writeFile } from "node:fs/promises";
+import { dirname } from "node:path";
+import { validateDelivery } from "../../src/delivery.ts";
+
+const roots = JSON.parse(process.env.ATDD_SCAN_ROOTS ?? "[]"), report = process.env.ATDD_VIOLATIONS_REPORT;
+if (!report) throw new Error("ATDD_VIOLATIONS_REPORT is required");
+const violations = (await Promise.all(roots.map(root => validateDelivery(root)))).flat().map(item => ({ ...item, line: 1, col: 1, source_line: "" }));
+await mkdir(dirname(report), { recursive: true });
+await writeFile(report, JSON.stringify({ violations }, null, 2));

package/detectors/delivery_evidence/fixtures/clean/atdd-bun.yaml

@@ -0,0 +1,8 @@
+profiles: [delivery]
+delivery:
+  independence: fresh-process
+  stages:
+    plan_review: { authors: [codex], reviewers: [glm, claude] }
+    test_review: { authors: [glm, claude], reviewers: [codex, claude] }
+    code_review: { authors: [glm, claude], reviewers: [glm, claude], independence: different-model }
+    final_review: { authors: [codex], reviewers: [codex, claude] }

package/detectors/delivery_evidence/fixtures/clean/delivery/api/evidence.yaml

@@ -0,0 +1,54 @@
+# In progress: every stage reviewed, the code-review dispute settled, the PR not yet marked ready.
+tranche: api
+status: open
+base_sha: 3f2a91c
+reviews:
+  - stage: plan_review
+    sha: 8b10e44
+    author: { model: codex, run: driver-api }
+    reviewer: { model: glm, run: glm-plan-1 }
+    verdict: approve
+    checked: [ACC-API-001, ACC-API-002, planner.decomposition]
+  - stage: test_review
+    sha: 91aa0b2
+    author: { model: glm, run: glm-red-1 }
+    reviewer: { model: codex, run: codex-test-1 }
+    verdict: approve
+    checked: [ACC-API-001, ACC-API-002, tester.bun.red]
+  - stage: code_review
+    sha: a4c0f11
+    author: { model: glm, run: glm-green-1 }
+    reviewer: { model: claude, run: claude-code-1 }
+    fallback:
+      - { from: glm, kind: rate_limit, failures: 3, window: { from: "2026-09-25T09:00:00Z", to: "2026-09-25T09:08:00Z" }, reason: "rate limit: 3 failures in 10 minutes" }
+    verdict: request_changes
+    checked: [ACC-API-001, ACC-API-002, src/wagons/api, coder.bun.error-response]
+    findings:
+      - id: F1
+        severity: high
+        evidence: src/wagons/api/handler.ts:42 returns a bare string
+        invariant: every error response carries a coded body
+        affects: [ui]
+        proposed_fix: return { code "API_NOT_FOUND" } instead of the bare string
+        outcome: fixed
+      - id: F2
+        severity: medium
+        evidence: src/wagons/api/handler.ts:57 retries without a bound
+        invariant: outbound calls are bounded
+        proposed_fix: cap the retry loop at three attempts
+        rebuttal: "The loop is bounded by the caller's AbortSignal; see handler.test.ts:31 which proves it stops."
+        outcome: withdrawn
+  - stage: code_review
+    sha: c77d0a2
+    author: { model: glm, run: glm-green-2 }
+    reviewer: { model: claude, run: claude-code-2 }
+    fallback:
+      - { from: glm, kind: rate_limit, failures: 3, window: { from: "2026-09-25T09:00:00Z", to: "2026-09-25T09:08:00Z" }, reason: "rate limit: 3 failures in 10 minutes" }
+    verdict: approve
+    checked: [ACC-API-001, ACC-API-002, src/wagons/api, F1, F2]
+  - stage: final_review
+    sha: c77d0a2
+    author: { model: codex, run: driver-api }
+    reviewer: { model: codex, run: codex-final-1 }
+    verdict: approve
+    checked: [src/wagons/api, contracts, ui]

package/detectors/delivery_evidence/fixtures/dirty/atdd-bun.yaml

@@ -0,0 +1,3 @@
+profiles: [delivery]
+delivery:
+  independence: loose

package/detectors/delivery_evidence/fixtures/dirty/delivery/api/evidence.yaml

@@ -0,0 +1,37 @@
+# Ready, but final_review never ran, the approved SHA exists nowhere, a reviewer is off-list, and one
+# reviewer also authored.
+tranche: api
+status: ready
+base_sha: 3f2a91c
+approved_sha: "0000000"
+reviews:
+  - stage: plan_review
+    sha: 8b10e44
+    author: { model: codex, run: driver-api }
+    reviewer: { model: gpt, run: gpt-plan-1 }
+    verdict: approve
+    checked: [ACC-API-001]
+  - stage: test_review
+    sha: 91aa0b2
+    author: { model: glm, run: glm-red-1 }
+    reviewer: { model: codex, run: driver-api }
+    verdict: approve
+    checked: [ACC-API-001]
+  - stage: code_review
+    sha: a4c0f11
+    author: { model: glm, run: glm-green-1 }
+    reviewer: { model: glm, run: glm-code-1 }
+    verdict: request_changes
+    checked: [ACC-API-001]
+    findings:
+      - id: F1
+        severity: high
+        evidence: src/wagons/api/handler.ts:42 returns a bare string
+        invariant: every error response carries a coded body
+        proposed_fix: return a coded error body
+  - stage: code_review
+    sha: "0000000"
+    author: { model: glm, run: glm-green-2 }
+    reviewer: { model: glm, run: glm-code-2 }
+    verdict: approve
+    checked: [ACC-API-001, F1]

package/detectors/delivery_evidence/fixtures/dirty/delivery/data/evidence.yaml

@@ -0,0 +1,8 @@
+# A reviewer without a verdict or a checklist.
+tranche: data
+status: open
+base_sha: 3f2a91c
+reviews:
+  - stage: plan_review
+    sha: 8b10e44
+    reviewer: { model: glm, run: glm-plan-1 }

package/detectors/delivery_evidence/fixtures/dirty/delivery/orphan/README.md

@@ -0,0 +1 @@
+The orphan tranche has a folder and no evidence.yaml.

package/detectors/delivery_evidence/fixtures/dirty/delivery/ui/evidence.yaml

@@ -0,0 +1,5 @@
+# The folder says ui, the record says web.
+tranche: web
+status: open
+base_sha: 3f2a91c
+reviews: []