baldart 5.0.0 → 5.0.1

package/CHANGELOG.md

@@ -5,6 +5,45 @@ All notable changes to BALDART will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [5.0.1] - 2026-07-03
+
+**Adversarial-verification fixes on the 5.0.0 wave.** A full release verification
+(distribution machine dogfooded end-to-end on 4 configs — all green; normative-loss audit
+over 4 core agents; pipeline-coherence audit) found the headline mechanisms inert on the
+happy path plus a handful of slot-boundary and consistency defects. All fixed; no gate
+removed, no H2 moved (consumer overlays unaffected), no `baldart.config.yml` change.
+
+- **FIXED (HIGH) — `/new` step 11b clean branch now proceeds to 11c**: previously only the
+  violation branch reached the review-bundle/doc-invariants build, leaving the v5.0.0
+  anti-re-read + PASS-fast machinery unused on every clean card (`implement.md`).
+- **FIXED (HIGH) — `/codexreview` consumes the full lean contract**: Step -0.5 now parses +
+  forwards `review_bundle_path` (anti-re-read phrase in every Step-2 prompt) and
+  `specialist_dispatch` (orchestrated-mode suppression, `dispatch_deferred:<agent>`) — both
+  were produced by `codex-gate.md` but dead-wired on the `/new`→`/codexreview` hop. Optional
+  keys: pre-5.0 contracts keep working unchanged.
+- **FIXED (HIGH) — coder slot boundaries**: `vercel-react-best-practices` un-slotted (no
+  config flag can express React-non-Next → structural normative loss); the NEVER-ad-hoc
+  browser-scripts rule hoisted out of `{{#e2e_playwright}}` (universal pre-5.0). Agents
+  CHANGELOG: coder/doc-reviewer/qa-sentinel v2.0.1.
+- **FIXED (MEDIUM)** — doc-reviewer per-card cited exceptions (`topological-generation`,
+  `schema-drift`) restored + `doc-audit-protocol.md` Contract no longer contradicts the agent
+  core; qa-sentinel bundle `gate_logs` demoted to context-only (own-tier gates always re-run);
+  `build-review-bundle.mjs` diff scoped to `--may-edit` (multi-card batches no longer leak
+  prior cards into card N's bundle/docinv; `new2.js` implement brief mirrors the scoping);
+  `new-card-review.js` + the 2.5x delegation thread `reviewBundlePath` into every brief;
+  Phase 2.55 pre-5.0 fallback uses `git diff "$TRUNK...HEAD"` (bare `git diff` post-commit is
+  vacuous); cap-and-handoff checkpoint-missing branch defined; `/ui-implement`-delegated cards
+  explicitly run 7c–11c; PASS-fast Own-Doc Closure claim corrected; "rule 8" pointers
+  re-anchored to the renumbered Post-Intervention Coherence rule 7 (prd-card-writer, upgrade
+  doc, new2-resolve comment).
+- **FIXED (LOW)** — `doc-invariants.mjs` evaluates `documentation_impact` and `canonical_docs`
+  independently; deferral KEEP list re-includes `balanced`; stale `coding-standards.md`
+  cross-refs to the removed coder H2 updated; `${paths.references_dir}` literals in
+  `doc-audit-protocol.md`.
+- Skills: `new` 2.0.1, `new2` 1.4.1 (per-skill CHANGELOGs). Codex parity: portable — prose +
+  pure-Node scripts, no Claude-only primitive added; the `/codexreview` contract keys are
+  optional and ignored by pre-5.0 readers.
+
 ## [5.0.0] - 2026-07-03
 
 **The agent-spine major.** Measured driver (1,934 subagent runs / 191 sessions on the

package/VERSION

@@ -1 +1 @@
-5.0.0
+5.0.1

package/framework/.claude/agents/CHANGELOG.md

@@ -7,6 +7,29 @@ per-item agent merge, the doctor probes, and the discovery hooks — like
 
 Formato: [Keep a Changelog](https://keepachangelog.com/) · per-agent SemVer.
 
+## [coder v2.0.1] · [doc-reviewer v2.0.1] · [qa-sentinel v2.0.1] — 2026-07-03 (framework v5.0.1)
+
+Adversarial-verification fixes on the 3-layer restructuring (no H2 moved — overlays unaffected):
+
+- **coder**: `vercel-react-best-practices` un-slotted (it applies to ANY React stack, and no
+  config flag can express "React non-Next" — a structural normative loss for those consumers;
+  "skill absent → skip silently"). The NEVER-ad-hoc-browser-scripts rule hoisted OUT of
+  `{{#e2e_playwright}}` as an unconditional line (it was universal pre-5.0; a Playwright
+  consumer with a stale `stack.testing.e2e` silently lost it); the `playwright-skill` link
+  itself stays slotted.
+- **doc-reviewer**: two per-card cited exceptions restored from the audit module —
+  `SECTION=topological-generation` (multi-file doc passes generate leaf→root; was per-card in
+  v4.99.0 but unreachable behind the module's "per-card NEVER" contract) and
+  `SECTION=schema-drift` (changed field SET on a documented payload → `SCHEMA_DRIFT`/
+  `ORPHAN_FIELD`, diff-driven as in v4.99.0). `doc-audit-protocol.md` Contract reworded to
+  name the cited exceptions instead of contradicting the agent core.
+- **qa-sentinel**: review-bundle `gate_logs` demoted to CONTEXT ONLY (`files_changed` stays
+  authoritative for scope) — own-tier gates are always re-executed, never cited from a stale
+  Phase-2 log; restored the v4.99.0 one-liners "never claim a gate ran when it did not" and
+  "never invent your own classification".
+- (pointer-only, no version bump) **prd-card-writer**: "code-reviewer rule 8" re-anchored to
+  the renumbered rule 7 (Post-Intervention Coherence Check), by name.
+
 ## [coder v2.0.0] · [code-reviewer v2.0.0] · [doc-reviewer v2.0.0] · [plan-auditor v2.0.0] · [qa-sentinel v2.0.0] · [codebase-architect v2.0.0] · [ui-expert v2.0.0] · [skill-improver v2.0.0] — 2026-07-03 (framework v5.0.0)
 
 **The 3-layer restructuring** (core inline + shared modules + install-time slots).

package/framework/.claude/agents/coder.md

@@ -4,7 +4,7 @@ description: "Write, modify, or refactor production code. For features, bugs, an
 model: opus
 effort: high
 color: red
-version: 2.0.0
+version: 2.0.1
 ---
 
 > **YOLO MODE**: All agents spawned via the Task tool MUST use `mode: "bypassPermissions"`. No exceptions.
@@ -219,17 +219,16 @@ Keep it simple. Write good code. Ask if unsure. Write it clean the first time.
 
 You MUST use these skills when applicable:
 
-{{#fw_nextjs}}
 ### `vercel-react-best-practices`
-React/Next.js performance patterns. When: writing React components, optimizing renders, async data, bundle size.
-{{/fw_nextjs}}
+React performance patterns (any React stack, Next.js included). When: writing React components, optimizing renders, async data, bundle size. Skill not installed (non-React stack / no plugin) → skip silently.
 ### `frontend-design`
 Production-grade frontend code with high design quality. When: building new UI components or complex layouts.
 {{#deploy_vercel}}
 ### `vercel:deploy`
 Deploying to Vercel. When: the user requests deployment.
 {{/deploy_vercel}}
+**Browser testing (unconditional)**: NEVER ad-hoc browser scripts or one-off `run.js` drivers — always the project's E2E test runner.
 {{#e2e_playwright}}
 ### `playwright-skill`
-E2E browser testing via Playwright Test CLI (`.spec.ts` in `tests/e2e/`, run via `npm run test:e2e`). When: testing new UI features, user flows, form submissions. NEVER ad-hoc scripts or `run.js` — always `npx playwright test`.
+E2E browser testing via Playwright Test CLI (`.spec.ts` in `tests/e2e/`, run via `npm run test:e2e`). When: testing new UI features, user flows, form submissions — always `npx playwright test`.
 {{/e2e_playwright}}

package/framework/.claude/agents/doc-reviewer.md

@@ -3,7 +3,7 @@ name: doc-reviewer
 description: "Audit, review, and write project documentation. Use after feature implementation, bug-fix waves, or documentation cleanup. Owns documentation completeness and drift control."
 model: sonnet
 color: green
-version: 2.0.0
+version: 2.0.1
 ---
 > **YOLO MODE**: All agents spawned via the Task tool MUST use `mode: "bypassPermissions"`. No exceptions.
 
@@ -163,11 +163,12 @@ When a SSOT exists, update it before any derived doc:
    - card DONE → `ssot-registry.md`
    - architecture/provider/auth/schema/contract decision → ADR
    - **changed validation constraint on a public contract** (`.max()`/`.min()`/length/regex/enum/default changed in a route handler, server action, or API schema) → the API reference **BODY** for that endpoint: verify the documented value EQUALS the code value — frontmatter freshness alone does not catch this. Mismatch = `API_BODY_CONSTRAINT_DRIFT`; you are the canonical writer, fix the body directly.
+   - **changed field SET on a documented payload** (field added/removed/renamed in a request/response schema whose endpoint doc exists) → update that doc's field table; a documented field gone from code = `SCHEMA_DRIFT`, a code field absent from the doc = `ORPHAN_FIELD`. Procedure: `agents/doc-audit-protocol.md SECTION=schema-drift` (per-card cited exception).
 {{#has_wiki_overlay}}
    - diff matches a synthesis page's `update_triggers` frontmatter (pages under `${paths.wiki_dir}/syntheses/`) → that synthesis page must be updated in the same change, or flagged `WIKI_SYNTH_STALE`. Pages without the field are exempt. See `agents/llm-wiki-methodology.md § Update triggers`.
 {{/has_wiki_overlay}}
 6. Check completeness of: data model docs, collection docs, API docs, UI docs, `product-scope.md` (business-scope changes only), `project-status.md`, ADRs when architecture changed, backlog notes, macro-feature SSOT cross-links.
-7. **Write missing docs directly.** Prefer extending existing reference docs over new files unless the feature justifies a standalone doc. Type-specific checklists: `doc-reviewer-support/references/doc-checklists.md` **if it exists**, else the invariant table + the `doc-writing-for-rag` templates.
+7. **Write missing docs directly.** Prefer extending existing reference docs over new files unless the feature justifies a standalone doc. Type-specific checklists: `doc-reviewer-support/references/doc-checklists.md` **if it exists**, else the invariant table + the `doc-writing-for-rag` templates. Writing/updating MORE than one doc file in this pass → generate in dependency order, leaf→root (schemas/data-model before endpoints before UI/index), so no doc cites a sibling not yet updated — full procedure: `agents/doc-audit-protocol.md SECTION=topological-generation` (per-card cited exception).
 8. Update indexes when new docs are added.
 9. {{#has_wiki_overlay}}Assess wiki-overlay sync need (deliverable section H): new cross-cutting concept, renamed canonical, deprecated doc — note the need, do not dispatch any sync agent here.{{/has_wiki_overlay}} Wiki assessment is a no-op when `features.has_wiki_overlay: false` — skip section H with a one-line note.
 10. Report what was checked, added, fixed, and deferred — but see Own-Documentation Closure: an own-doc may NOT appear in the "deferred" bucket.

package/framework/.claude/agents/prd-card-writer.md

@@ -264,7 +264,7 @@ exception**: the LIGHT branch (b) above, a strictly UI-presentational card (`are
 logic/ui split pair (e.g. a `…-submit-ui` card whose logic lives in its `…-submit-logic`
 sibling): reviewing a pixels-only diff at Codex-`full` depth is waste, and the design-system
 safety net still fires regardless of profile (a `light` card keeps its per-card code-review —
-since v4.18.0 a per-card Codex finder + `code-reviewer` FP-gate — plus `code-reviewer` rule 8 /
+since v4.18.0 a per-card Codex finder + `code-reviewer` FP-gate — plus `code-reviewer`'s Post-Intervention Coherence check (DS rule 7) /
 the registry-first DS cascade, and is covered by the batch-wide Final FULL gate). Any
 doubt — a hint of logic, state, data binding, a new/modified primitive, or `areas` beyond
 `[ui]` — disqualifies branch (b): the card stays `balanced`. When in doubt between `balanced`

package/framework/.claude/agents/qa-sentinel.md

@@ -4,7 +4,7 @@ description: "RUN the mechanical quality gates on a change set and return a PASS
 model: sonnet
 color: pink
 memory: project
-version: 2.0.0
+version: 2.0.1
 ---
 
 > **YOLO MODE**: All agents spawned via the Task tool MUST use `mode: "bypassPermissions"`. No exceptions.
@@ -23,10 +23,10 @@ Run mechanical quality gates fast, return a PASS/FAIL verdict, and get out of th
 ## Step 0: Always Start Here
 
 0. **Resolve the working directory.** A `Worktree path` in your prompt → `cd` into it FIRST; all git/lint/test/build commands run there. Field present but empty → HALT: `QA DONE — <CARD-ID> / Verdict: FAIL / worktree path provided but empty`. No field → current directory.
-1. `git diff --name-only HEAD` for the actual change set (you read uncommitted work pre-commit). When the briefing carries a review bundle, its `files_changed` + `gate_logs` are authoritative — don't re-derive.
-2. Read the authoritative `QA profile` from your prompt (`balanced` | `deep`) and map it via **Operating Modes**. The profile — NOT file count — selects the tier. Only allowed adjustment: `balanced → FULL` on risk drift (below). No profile in the prompt → default SCOPED and note it.
+1. `git diff --name-only HEAD` for the actual change set (you read uncommitted work pre-commit). When the briefing carries a review bundle, its `files_changed` is authoritative for SCOPE — don't re-derive it. Its `gate_logs` are CONTEXT ONLY (Phase-2 logs, possibly stale after later mutations): the gates YOUR tier owns you always execute yourself, and you never cite a bundle log as if it were your own run.
+2. Read the authoritative `QA profile` from your prompt (`balanced` | `deep`) and map it via **Operating Modes**. The profile — NOT file count — selects the tier. Only allowed adjustment: `balanced → FULL` on risk drift (below). No profile in the prompt → default SCOPED and note it — never invent your own classification.
 
-Never fabricate test results. Never assume what changed — read the diff. Do NOT read changed files to "understand scope" — that's code-reviewer's job. The ONLY files you read are the backlog card YAML and the git diff output.
+Never fabricate test results — and never claim a gate ran when it did not (a SKIP is reported as SKIP). Never assume what changed — read the diff. Do NOT read changed files to "understand scope" — that's code-reviewer's job. The ONLY files you read are the backlog card YAML and the git diff output.
 
 ## Gate Command Resolution
 

package/framework/.claude/commands/codexreview.md

@@ -48,11 +48,19 @@ For the (single) card in scope, check for `/tmp/codexreview-lean-<CARD-ID>.json`
     "profile": "light" | "full",
     "arch_baseline_path": "/tmp/arch-baseline-<CARD-ID>.md",
     "diff_summary_path": "<completion-report or git-diff path>",
+    "review_bundle_path": "/tmp/review-bundle-<CARD-ID>.json",
     "skip_doc_reviewer": true,
-    "skip_api_perf_auditor": true
+    "skip_api_perf_auditor": true,
+    "specialist_dispatch": {
+      "suppress": ["doc-reviewer", "plan-auditor", "api-perf-cost-auditor", "security-reviewer"],
+      "owner": "/new phases 3 / 3.5 / 3.7 + Final F.3"
+    }
   }
   ```
 
+  (`review_bundle_path` and `specialist_dispatch` since v5.0.1 — producer: `codex-gate.md` § lean
+  contract. Both OPTIONAL: absent on pre-5.0 contracts; unknown keys are ignored.)
+
   Apply:
   - `arch_baseline_path` readable → **skip Step 1** (do NOT re-spawn `codebase-architect`); load the
     baseline from that file and ALSO attach the `diff_summary_path` contents to every review agent so
@@ -77,6 +85,17 @@ For the (single) card in scope, check for `/tmp/codexreview-lean-<CARD-ID>.json`
     its own findings as before. Any high-risk diff trigger escalates the card to `full` (both finders)
     per the Review Profile Selector; the Final-review FULL gate re-runs Codex batch-wide regardless. *(B1)*
   - `profile: "full"` (or missing) → full agent set incl. Codex adversarial, minus #3 if `skip_doc_reviewer`.
+  - `review_bundle_path` present AND readable (since v5.0.1) → append to EVERY Step-2 reviewer prompt
+    the binding anti-re-read phrase: *"Review bundle: `<review_bundle_path>` — Read it FIRST. It lists
+    the diff, the changed files, the arch baseline and the completion report. Do NOT re-Read source
+    files to rebuild context you can get from those paths; for any file in `hot_files`, Read ONLY the
+    symbol ranges listed."* Absent/unreadable → no phrase (reviewers derive scope as before). *(A4)*
+  - `specialist_dispatch` present (since v5.0.1) → append its verbatim JSON to EVERY Step-2 reviewer
+    prompt, prefixed: *"ORCHESTRATED run — do NOT spawn any of the suppressed specialists yourself
+    (owner: `<owner>`); record what you would have routed as findings tagged
+    `dispatch_deferred: <agent>`."* (SSOT semantics: `agents/review-protocol.md § SECTION:
+    specialist-spawn`; the block WINS over the legacy `skip_*` flags where both are present.)
+    Absent → the reviewers' own spawn matrices apply (standalone behavior, unchanged). *(A5)*
 
 **Invariant**: lean mode NEVER suppresses the run itself — at minimum a **finder + the Step 3 FP-gate**
 execute on every card. At `light` the finder is **Codex** (or `code-reviewer` on the Codex-unavailable
@@ -85,8 +104,9 @@ malformed/unreadable, fall back to **full mode** and note it. **Consume-once**:
 `/tmp/codexreview-lean-<CARD-ID>.json` immediately after parsing it, so a later standalone
 `/codexreview <CARD-ID>` on the same card never inherits a stale lean contract from a prior `/new` run.
 Record the resolved mode in the Step 4 report `Method` section, e.g.
-`lean: profile=light, architect=reused, doc-reviewer=skipped(Phase 3), codex=finder(light), code-reviewer=fp-gate, cove=skipped`
-(or `codex=unavailable→code-reviewer finder(light)` when the fallback fired).
+`lean: profile=light, architect=reused, doc-reviewer=skipped(Phase 3), codex=finder(light), code-reviewer=fp-gate, cove=skipped, bundle=forwarded, dispatch=suppressed`
+(or `codex=unavailable→code-reviewer finder(light)` when the fallback fired; `bundle=absent` /
+`dispatch=none` on pre-5.0 contracts).
 
 ---
 
@@ -175,7 +195,9 @@ Launch these agents in parallel for each card:
 > the finder instead (the Step 3 FP-gate validates its findings). At `full` with `skip_api_perf_auditor`,
 > launch #1 + #4 (Codex) (+ #3 unless `skip_doc_reviewer`). At `full` with no skips (and in full mode
 > with no contract file), launch all four. The standalone `/codexreview <CARD-ID>` invocation (no
-> contract) is always full with the complete set.
+> contract) is always full with the complete set. When the contract carried `review_bundle_path` /
+> `specialist_dispatch` (Step -0.5 A4/A5), every prompt built here carries the anti-re-read phrase
+> and the suppression block respectively.
 
 **Codex invocation rules (agent #4):**
 

package/framework/.claude/skills/new/CHANGELOG.md

@@ -2,6 +2,34 @@
 
 Formato: [Keep a Changelog](https://keepachangelog.com/) · [SemVer](https://semver.org/).
 
+## 2.0.1 — 2026-07-03
+
+Adversarial-verification fixes on the v5.0.0 pipeline wave (framework v5.0.1):
+
+- **implement.md 11b→11c (HIGH)**: the clean branch of the file-diff gate now proceeds to 11c
+  (review bundle + doc-invariants) — previously it jumped straight to Phase 2.5, leaving the
+  bundle/PASS-fast machinery inert on the happy path. 11c now ends with an explicit "proceed
+  to Phase 2.5".
+- **implement.md 7d**: explicit branch for `[CAP-HANDOFF]` marker present but checkpoint file
+  missing (rebuild `items_remaining` from the completion report, else `[CAP-EXHAUSTED]`); the
+  continuation briefing cites the review bundle only "when it already exists".
+- **implement.md 6a**: delegated `/ui-implement` cards explicitly still run steps 7c–11c
+  (i18n fill, gates, ownership gate, bundle) — the delegation replaces only the build + 2.6.
+- **review-cycle.md**: Phase 2.55 pre-5.0 diff fallback is now `git diff "$TRUNK...HEAD"`
+  (a bare `git diff` post-commit is vacuous); the 2.5x delegation passes `reviewBundlePath`
+  to `new-card-review.js`; the deferral KEEP list re-includes `balanced`; the PASS-fast
+  Own-Doc Closure claim corrected (modified-primitive obligations ride the serializer gate +
+  Final F.3, R1/R3 fire on new files only); the QA briefing marks bundle `gate_logs` as
+  CONTEXT ONLY (own-tier gates always re-run).
+- **scripts/build-review-bundle.mjs**: the diff/files_changed are now SCOPED to `--may-edit`
+  when passed — in a sequential multi-card batch the unscoped `trunk...HEAD` accumulated
+  prior cards' commits into card N's bundle/docinv.
+- **scripts/doc-invariants.mjs**: `card_declares_docs` evaluates `documentation_impact` and
+  `canonical_docs` independently (a populated `canonical_docs` with `documentation_impact: []`
+  no longer PASS-fasts).
+- Companion consumer fix (command, not this skill): `/codexreview` Step -0.5 now parses +
+  forwards `review_bundle_path` and `specialist_dispatch` from the lean contract.
+
 ## 2.0.0 — 2026-07-03
 
 - **BALDART 5.0 pipeline wave (framework v5.0.0).** Six additive mechanisms, all with pre-5.0 graceful degradation:

package/framework/.claude/skills/new/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: new
 effort: medium
-version: 2.0.0
+version: 2.0.1
 description: >
   Orchestrate a team of specialized agents to implement one or more backlog cards
   end-to-end inside a dedicated worktree, with code review, doc review, QA, and

package/framework/.claude/skills/new/references/implement.md

@@ -62,7 +62,10 @@
            in programmatic mode (contract: ui-implement/references/integration.md).
            Consume its COMPACT JSON (status mirrors /e2e-review — review-cycle.md Phase 2.6
            gating table). SKIP step 6b (owner_agent router), the step-7 coarse briefing,
-           AND Phase 2.6 (the skill already ran /e2e-review). Then resume the per-card
+           AND Phase 2.6 (the skill already ran /e2e-review). Steps 7c–11c still run HERE
+           for the delegated card (i18n fill, gates 8–9, file diff gate 11b, review bundle
+           11c) — the delegation replaces ONLY the build steps and Phase 2.6, never the
+           gates or the bundle. Then resume the per-card
            review cluster (Phase 2.55 Simplify → Phase 3 doc → 3.5 QA → 3.7 Codex) per the
            card's review_profile — for a MIXED UI+logic card /new KEEPS that cluster
            (integration.md § "What /new KEEPS"); it is fidelity-only that the skill owns.
@@ -505,8 +508,9 @@
    If > 0 new keys → spawn **`i18n-translator`** BY NAME (never `general-purpose`, never a generic agent — the context-aware fill is its exclusive domain per `agents/i18n-protocol.md`), passing: the registry path (`${paths.i18n_registry}`), the diff path, and the instruction "fill the missing target locales for the new source keys — source stays untouched". This runs AFTER the coder commit and BEFORE the step-8 gates, so locale-parity holds first-try (the fail-then-fix round-trip measured ~2M tokens on FEAT-0042). Log `i18n-fill: RAN (<n> keys)` or `i18n-fill: SKIP (no new source keys)` in the tracker. A locale-parity failure later in step 8/9 despite this pass → route back to `i18n-translator`, NEVER retry the coder on it (the coder is source-only by design).
 
 7d. **Cap-and-handoff continuation loop (v5.0.0).** If the implementer returned `partial` with a `[CAP-HANDOFF]` marker and `/tmp/checkpoint-<CARD-ID>.json` exists:
-   - Respawn a FRESH instance of the SAME owner agent with a minimal continuation briefing: the review-bundle/arch-baseline paths + the checkpoint path + "continue from `items_remaining`; the checkpoint + baseline are your context — do NOT re-explore, do NOT re-read files already listed as done". Same card, same worktree, same ownership map.
+   - Respawn a FRESH instance of the SAME owner agent with a minimal continuation briefing: the arch-baseline path (+ the review-bundle path only when it already exists — it is normally built later, at 11c) + the checkpoint path + "continue from `items_remaining`; the checkpoint + baseline are your context — do NOT re-explore, do NOT re-read files already listed as done". Same card, same worktree, same ownership map.
    - **Max 2 continuations.** Still `partial` after the 2nd → do NOT keep respawning: log `[CAP-EXHAUSTED]` in `## Issues & Flags`, treat the unfinished items as `not_implemented` rows, and route through the normal gap path (AC-Closure Gate / follow-up card — the card is NOT auto-DONE). Log each continuation in the tracker: `cap-handoff: CONTINUED n=<i> (items_remaining=<k>)`.
+   - `[CAP-HANDOFF]` marker present but the checkpoint file MISSING → do NOT respawn blind: rebuild `items_remaining` from the completion report's `not_implemented` rows and persist it to `/tmp/checkpoint-<CARD-ID>.json` yourself, then run the continuation as above (it counts toward the max-2). If the completion report is also missing, treat as `[CAP-EXHAUSTED]` directly (gap path) — never guess what remains.
    - No `[CAP-HANDOFF]` marker → this step is a no-op.
 
 8. **Run the verification gates and CAPTURE their output to disk** (so step 9 can pass it to a fix agent) — **redirect, never `tee`/stream inline** (per § "Context economy" → Gate-output discipline). Each is its own gate:
@@ -556,7 +560,7 @@
    ```
    (`$TRUNK` is the trunk branch resolved in Phase 0; if the worktree branched from a different base, the `HEAD~1..HEAD` fallback covers the last commit.)
    Compare against this card's allowed files in `## File Ownership Map`.
-   - **All within allowed set** → proceed to Phase 2.5.
+   - **All within allowed set** → proceed to 11c (the bundle build runs on EVERY card, not only after a violation).
    - **Any file outside allowed set** → log the violation in `## Issues & Flags` (`"unauthorized file: <path>"`), then run the **deterministic file-scoped revert SCRIPT** (a file-scoped revert is mechanical git plumbing, not code authoring — a script cannot fabricate or over-reach, and it runs IDENTICALLY on Claude and Codex with no dependency on a `model` param or a `general-purpose` agent Codex lacks). Resolve + run it (opt-in-with-fallback):
      ```bash
      REVERT_SH="$(ls .framework/framework/.claude/skills/new/scripts/revert-files.sh .claude/skills/new/scripts/revert-files.sh 2>/dev/null | head -1)"
@@ -577,4 +581,4 @@
    DOCINV_MJS="$(ls .framework/framework/.claude/skills/new/scripts/doc-invariants.mjs .claude/skills/new/scripts/doc-invariants.mjs 2>/dev/null | head -1)"
    [ -n "$DOCINV_MJS" ] && node "$DOCINV_MJS" --diff /tmp/diff-<CARD-ID>.txt --card <card yaml path> --config baldart.config.yml
    ```
-   The bundle (`/tmp/review-bundle-<CARD-ID>.json`) unifies the diff dump (it writes `/tmp/diff-<CARD-ID>.txt` if missing — Phase 2.55 step 2 and the Phase 3.7 dump become consumers, not producers), the arch-baseline pointer + parsed Hot-File Map, the completion report path (backstop: if the implementer did not write `/tmp/completion-<CARD-ID>.md`, persist its returned `completion-report` block there YOURSELF before running the script), the ownership map, and the gate-log paths. **Every reviewer briefing from here on carries the binding phrase**: *"Review bundle: `/tmp/review-bundle-<CARD-ID>.json` — Read it FIRST. It lists the diff, the changed files, the arch baseline and the completion report. Do NOT re-Read source files to rebuild context you can get from those paths; for any file in `hot_files`, Read ONLY the symbol ranges listed."* Scripts missing (pre-5.0 install) → skip both, log `review-bundle: unavailable (pre-5.0 scripts)` — the reviewers derive scope themselves as before (graceful degradation, Codex-portable either way).
+   The bundle (`/tmp/review-bundle-<CARD-ID>.json`) unifies the diff dump (it writes `/tmp/diff-<CARD-ID>.txt` if missing — Phase 2.55 step 2 and the Phase 3.7 dump become consumers, not producers), the arch-baseline pointer + parsed Hot-File Map, the completion report path (backstop: if the implementer did not write `/tmp/completion-<CARD-ID>.md`, persist its returned `completion-report` block there YOURSELF before running the script), the ownership map, and the gate-log paths. **Every reviewer briefing from here on carries the binding phrase**: *"Review bundle: `/tmp/review-bundle-<CARD-ID>.json` — Read it FIRST. It lists the diff, the changed files, the arch baseline and the completion report. Do NOT re-Read source files to rebuild context you can get from those paths; for any file in `hot_files`, Read ONLY the symbol ranges listed."* Scripts missing (pre-5.0 install) → skip both, log `review-bundle: unavailable (pre-5.0 scripts)` — the reviewers derive scope themselves as before (graceful degradation, Codex-portable either way). Then proceed to Phase 2.5.

package/framework/.claude/skills/new/references/review-cycle.md

@@ -47,12 +47,13 @@ so it surfaces in telemetry.
   - `scopeFiles` ← this card's committed diff (`git diff --name-only "$TRUNK...HEAD"`, fallback `HEAD~1..HEAD`). **Diffs to disk (context economy, v4.43.0):** write the card's full diff to `/tmp/diff-<CARD-ID>.txt` once and derive BOTH the Step-A grep (above) and this `--name-only` list from it — never read the raw diff inline (mirrors the team-mode D.1.5 batching discipline, so the two paths stay symmetric).
   - `editableFiles` ← this card's **File Ownership Map** entries (the coder's write scope; `setup.md` step 3b).
   - `archBaselinePath` ← `/tmp/arch-baseline-<CARD-ID>.md` (persisted at `implement.md` step 5b).
+  - `reviewBundlePath` ← `/tmp/review-bundle-<CARD-ID>.json` when it exists (implement.md step 11c), else omit — the workflow threads it into every agent brief as the anti-re-read phrase (v5.0.1; absent → briefs unchanged, pre-5.0 behavior).
   - `hasSecurityFiles` ← any `scopeFiles` path matches `paths.high_risk_modules`.
   - `runSimplify` ← `true` (a non-trivial card always simplifies).
 
   ```
   Workflow({ name: 'new-card-review', args: {
-    cards: [{ cardId, cardPath, scopeFiles, editableFiles, qaTier, hasSecurityFiles, runSimplify, archBaselinePath }],
+    cards: [{ cardId, cardPath, scopeFiles, editableFiles, qaTier, hasSecurityFiles, runSimplify, archBaselinePath, reviewBundlePath }],
     worktreePath, baseBranch, config, codexScriptPath   // from Phase 0 / tracker
   }})
   ```
@@ -135,7 +136,7 @@ After completeness is verified, clean up the implementation before it reaches re
 **Step-by-step**:
 
 1. **Enter Phase 2.55 (simplify)** — **no standalone tracker write** for phase entry (§ "Context Tracking" allowlist; the tracker records only `2.55-simplify DONE` at step 6, co-emitted). Proceed directly to step 2.
-2. Ensure the card diff is on disk — implement.md step 11c's review bundle already wrote `/tmp/diff-<CARD-ID>.txt` (this phase is a CONSUMER, not a producer). Only if the bundle step did not run (pre-5.0 install): `git diff > /tmp/diff-<CARD-ID>.txt` in the worktree (**redirect, not inline** — per § "Context economy" → Diffs to disk).
+2. Ensure the card diff is on disk — implement.md step 11c's review bundle already wrote `/tmp/diff-<CARD-ID>.txt` (this phase is a CONSUMER, not a producer). Only if the bundle step did not run (pre-5.0 install): `git diff "$TRUNK...HEAD" > /tmp/diff-<CARD-ID>.txt 2>/dev/null || git diff HEAD~1..HEAD > /tmp/diff-<CARD-ID>.txt` in the worktree — the coder already committed, so a bare `git diff` would be vacuous (**redirect, not inline** — per § "Context economy" → Diffs to disk).
 3. Launch **three agents in parallel** (single message). Each receives the **path** `/tmp/diff-<CARD-ID>.txt` and Reads the diff itself — do NOT paste the full diff into the prompts. When `/tmp/review-bundle-<CARD-ID>.json` exists, each briefing ALSO carries the binding anti-re-read phrase (implement.md step 11c): *"Review bundle: `/tmp/review-bundle-<CARD-ID>.json` — Read it FIRST; do NOT re-Read source files to rebuild context you can get from its paths; for `hot_files`, Read ONLY the listed symbol ranges."*
 
    - **Reuse agent** — search the codebase for existing utilities/helpers that could replace newly written code. Flag duplicated functionality, inline logic that could use existing utils.
@@ -304,9 +305,9 @@ skill's Phase 1 falls back to deriving Gherkin scenarios from
 
 > **Note**: Code review is NOT performed in this phase — it is handled by the **mandatory unconditional `/codexreview` gate in Phase 3.7**, which runs per-card BEFORE the Phase 4 commit. The post-batch `/codexreview` in the Final review remains as a final FULL-diff sweep over the entire batch (since v3.37.0 — the guaranteed full-depth merge gate). This Phase 3 focuses exclusively on documentation sync, which must happen per-card (tied to the specific commit).
 
-> **Deferral gate (since v4.7.0 — enumerated, `review_profile`-driven)**: SKIP per-card doc-review and defer it to the **Final Review F.3 doc-reviewer** (which runs over the entire batch) when the card is **`review_profile == light` AND its committed diff touches NO documentation file** (no `.md`, no path under `${paths.references_dir}`, no data-model/ssot/api doc). These are small code changes with no doc surface of their own; their only doc concern is drift, which the batch-wide Final doc-reviewer catches. Log `doc-review: DEFERRED to Final FULL gate (light, no doc files in diff)` and proceed to Phase 3.5. **KEEP per-card doc-review** for: `deep` cards, ANY card whose diff touches a doc file (the change IS doc-relevant), and trivial cards (doc-review is their primary gate — § "Trivial-card fast-lane", unchanged). Never defer "for time" — the only enumerated reasons are `light + non-doc diff` and the deterministic PASS-fast below.
+> **Deferral gate (since v4.7.0 — enumerated, `review_profile`-driven)**: SKIP per-card doc-review and defer it to the **Final Review F.3 doc-reviewer** (which runs over the entire batch) when the card is **`review_profile == light` AND its committed diff touches NO documentation file** (no `.md`, no path under `${paths.references_dir}`, no data-model/ssot/api doc). These are small code changes with no doc surface of their own; their only doc concern is drift, which the batch-wide Final doc-reviewer catches. Log `doc-review: DEFERRED to Final FULL gate (light, no doc files in diff)` and proceed to Phase 3.5. **KEEP per-card doc-review** for: `deep` cards, `balanced` cards (they may still PASS-fast via the deterministic gate below — that gate, not this deferral, is their only skip lane), ANY card whose diff touches a doc file (the change IS doc-relevant), and trivial cards (doc-review is their primary gate — § "Trivial-card fast-lane", unchanged). Never defer "for time" — the only enumerated reasons are `light + non-doc diff` and the deterministic PASS-fast below.
 >
-> **Deterministic PASS-fast (v5.0.0 — measured: 84/127 per-card doc reviews returned PASS)**: when implement.md step 11c produced `/tmp/docinv-<CARD-ID>.json` AND it says `pass_fast_eligible: true` (zero non-advisory invariant rows triggered + no doc file in the diff + the card declares no `documentation_impact`/`canonical_docs`) AND the card is NOT `deep` → log `doc-review: PASS-fast (doc-invariants: 0 blocking rows) — Final doc-reviewer backstop stands` and **skip the per-card spawn** (proceed to Phase 3.5). No gate is removed: the batch-Final F.3 doc-reviewer still sees this card's diff, and the Own-Doc Closure obligations are definitionally empty when no invariant row fired and the card declared no docs. `deep` cards always spawn. Missing docinv JSON → no PASS-fast (fall through to the normal path).
+> **Deterministic PASS-fast (v5.0.0 — measured: 84/127 per-card doc reviews returned PASS)**: when implement.md step 11c produced `/tmp/docinv-<CARD-ID>.json` AND it says `pass_fast_eligible: true` (zero non-advisory invariant rows triggered + no doc file in the diff + the card declares no `documentation_impact`/`canonical_docs`) AND the card is NOT `deep` → log `doc-review: PASS-fast (doc-invariants: 0 blocking rows) — Final doc-reviewer backstop stands` and **skip the per-card spawn** (proceed to Phase 3.5). No gate is removed: the batch-Final F.3 doc-reviewer still sees this card's diff. Own-Doc Closure: NEW-file obligations are definitionally empty (no invariant row fired, no docs declared); obligations on MODIFIED primitives/routes are covered by the automatic spec resync (`DS_COMPONENT_STALE` serializer gate, v4.70.0) plus the Final F.3 backstop — the invariant table's R1/R3 fire on new files only, by design. `deep` cards always spawn. Missing docinv JSON → no PASS-fast (fall through to the normal path).
 
 12. **Enter Phase 3 (doc-review)** — **no standalone tracker write** for phase entry (§ "Context Tracking" allowlist; the tracker records only `3-doc-review DONE` at step 17, co-emitted). Proceed directly to the next step.
 13. Build a **Doc Sync Context** block. The coder committed in Phase 2, so detect the card's changed files against the trunk (a bare `HEAD` diff would be empty post-commit):
@@ -396,7 +397,9 @@ skill's Phase 1 falls back to deriving Gherkin scenarios from
     - Branch: <branch-name>
     - Changed files: <list from implementation phase>
     - Review bundle: /tmp/review-bundle-<CARD-ID>.json (when present) — its `files_changed`
-      and `gate_logs` are authoritative; do not re-derive them
+      is authoritative for scope (do not re-derive); its `gate_logs` are CONTEXT ONLY
+      (Phase-2 logs, possibly stale after Simplify/doc mutations) — the gates your tier
+      owns you execute yourself, never cite a bundle log as your own run
     - QA profile: [deep | balanced-escalated]
 
     Tier contract: deep → FULL suite. A BALANCED card only reaches this step when risk drift

package/framework/.claude/skills/new/scripts/build-review-bundle.mjs

@@ -37,16 +37,24 @@ const git = (argv) => {
   catch { return null; }
 };
 
+// Ownership scope (v5.0.1): in a sequential multi-card batch the worktree's
+// `trunk...HEAD` accumulates PRIOR cards' commits — an unscoped diff would make
+// card N's bundle/docinv classify other cards' files. When --may-edit is passed
+// (implement.md step 11c always passes it), scope the diff to this card's
+// allowed files; standalone invocations without it keep the full diff.
+const mayEdit = args['may-edit'] ? args['may-edit'].split(',').map((s) => s.trim()).filter(Boolean) : null;
+const scopeArgs = mayEdit && mayEdit.length ? ['--', ...mayEdit] : [];
+
 // diff: reuse the per-card dump when present, else write it now (same command
 // as implement.md step 8 / codex-gate — this script UNIFIES the dumps).
 const diffPath = `/tmp/diff-${card}.txt`;
 if (!exists(diffPath)) {
-  const diff = git(['diff', `${trunk}...HEAD`]) ?? git(['diff', 'HEAD~1..HEAD']);
+  const diff = git(['diff', `${trunk}...HEAD`, ...scopeArgs]) ?? git(['diff', 'HEAD~1..HEAD', ...scopeArgs]);
   if (diff != null) fs.writeFileSync(diffPath, diff + '\n');
 }
 
-// files changed (trunk-relative, uncommitted fallback)
-const filesChanged = (git(['diff', '--name-only', `${trunk}...HEAD`]) ?? git(['diff', '--name-only', 'HEAD~1..HEAD']) ?? '')
+// files changed (trunk-relative, uncommitted fallback; card-scoped when possible)
+const filesChanged = (git(['diff', '--name-only', `${trunk}...HEAD`, ...scopeArgs]) ?? git(['diff', '--name-only', 'HEAD~1..HEAD', ...scopeArgs]) ?? '')
   .split('\n').filter(Boolean);
 
 // arch baseline + Hot-File Map (deterministic parse of the architect's block:
@@ -95,9 +103,9 @@ const bundle = {
   hot_files: hotFiles,
   completion_report_path: exists(completionPath) ? completionPath : null,
   doc_invariants_path: exists(docinvPath) ? docinvPath : null,
-  ownership_may_edit: args['may-edit'] ? args['may-edit'].split(',').map((s) => s.trim()).filter(Boolean) : null,
+  ownership_may_edit: mayEdit,
   gate_logs: gateLogs,
-  generated_by: 'build-review-bundle.mjs v5.0.0',
+  generated_by: 'build-review-bundle.mjs v5.0.1',
 };
 
 fs.writeFileSync(out, JSON.stringify(bundle, null, 2) + '\n');

package/framework/.claude/skills/new/scripts/doc-invariants.mjs

@@ -139,8 +139,11 @@ if (hasWiki) {
 
 // doc signals the PASS-fast gate also needs (computed here so the orchestrator has one source)
 const docFilesChanged = touched.filter((f) => f.endsWith('.md') || f.startsWith(refsDir) || f.startsWith(wikiDir));
-const cardDeclaresDocs = /documentation_impact\s*:|canonical_docs\s*:/.test(cardYaml)
-  && !/documentation_impact\s*:\s*(\[\s*\]|null|~)\s*$/m.test(cardYaml);
+// Each doc-declaration field counts independently (v5.0.1): a populated
+// `canonical_docs` declares docs even when `documentation_impact: []`.
+const declares = (key) => new RegExp(`${key}\\s*:`).test(cardYaml)
+  && !new RegExp(`${key}\\s*:\\s*(\\[\\s*\\]|null|~)\\s*$`, 'm').test(cardYaml);
+const cardDeclaresDocs = declares('documentation_impact') || declares('canonical_docs');
 
 const result = {
   card: args.card ? path.basename(args.card, '.yml') : null,
@@ -150,7 +153,7 @@ const result = {
   doc_files_changed: docFilesChanged,
   card_declares_docs: cardDeclaresDocs,
   pass_fast_eligible: triggered.filter((t) => !t.advisory).length === 0 && docFilesChanged.length === 0 && !cardDeclaresDocs,
-  generated_by: 'doc-invariants.mjs v5.0.0',
+  generated_by: 'doc-invariants.mjs v5.0.1',
 };
 emit(result);
 

package/framework/.claude/skills/new2/CHANGELOG.md

@@ -2,6 +2,15 @@
 
 Formato: [Keep a Changelog](https://keepachangelog.com/) · [SemVer](https://semver.org/).
 
+## 1.4.1 — 2026-07-03
+
+- **Multi-card diff scoping (framework v5.0.1)**: the implement brief now instructs the coder
+  to persist `/tmp/diff-<ID>.txt` SCOPED to its MAY-EDIT paths (`git diff $TRUNK...HEAD -- …`) —
+  the shared batch worktree accumulates prior cards' commits, and an unscoped dump leaked them
+  into card N's bundle/docinv. `new-card-review.js` gains the optional `reviewBundlePath` card
+  arg (anti-re-read phrase in every brief when present; absent → unchanged). `new2-resolve.js`
+  comment re-anchored to the code-reviewer DS rule renumbering (Post-Intervention = rule 7).
+
 ## 1.4.0 — 2026-07-03
 
 - **BALDART 5.0 mirrors (framework v5.0.0)**: `new2.js` gains the deterministic mirrors of the /new pipeline wave — impl brief builds the review bundle + doc-invariants JSON and declares the tool-call budget; cap-and-handoff continuation loop (max 2, `cap-handoff` ledger rows); explicit `i18n-translator` fill spawn (`i18n-fill` ledger row); reviewer briefs carry the bundle anti-re-read phrase + the specialist-dispatch suppression; `fixPassModel` arg (default `sonnet`, overlay kill-switch) threads to `new2-resolve`'s coder fixers (specialists never downgraded).

package/framework/.claude/skills/new2/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: new2
 effort: high
-version: 1.4.0
+version: 1.4.1
 description: >
   Workflow-hosted batch engine for /new. Implements one or
   more backlog cards end-to-end by delegating the WHOLE batch to a background

package/framework/.claude/workflows/new-card-review.js

@@ -14,12 +14,14 @@ export const meta = {
 // ───────────────────────────────────────────────────────────────────────────
 // args contract — supplied by the /new skill (it owns git + tracker + human gates):
 //   cards         [{ cardId, cardPath, scopeFiles[], editableFiles[], qaTier,
-//                    hasSecurityFiles, runSimplify, archBaselinePath }]
+//                    hasSecurityFiles, runSimplify, archBaselinePath, reviewBundlePath }]
 //                 sequential → length 1; team-mode → the whole group/wave.
 //                   scopeFiles    files the card's committed diff touched (review surface)
 //                   editableFiles ownership-map files the coder MAY write (fix scope)
 //                   qaTier        'light' | 'full'  (qa-sentinel runs only at 'full'; else deferred to Final)
 //                   archBaselinePath  /tmp/arch-baseline-<id>.md  (or null)
+//                   reviewBundlePath  /tmp/review-bundle-<id>.json (v5.0.1, or null — briefs gain the
+//                                     anti-re-read phrase when present; absent → unchanged, fail-open)
 //   worktreePath  string   the batch worktree (agents cd into it)
 //   baseBranch    string   trunk the diff is taken against
 //   config        object   resolved baldart.config.yml (paths.* … )
@@ -252,15 +254,27 @@ const FIX_SCHEMA = {
 }
 
 // ---- Shared brief fragments -------------------------------------------------
+// Review bundles (v5.0.1 — anti-re-read handoff, implement.md step 11c): when the
+// orchestrator passed reviewBundlePath, every brief carries the binding phrase.
+// Absent → briefs unchanged (pre-5.0 orchestrator / standalone), fail-open.
+const bundlePaths = dedupe(cards.map((c) => c.reviewBundlePath).filter(Boolean))
+const waveBundleBrief = bundlePaths.length
+  ? `Review bundle(s): ${bundlePaths.join(', ')} — Read them FIRST; do NOT re-Read source files to rebuild context you can get from their paths; for hot_files, Read ONLY the listed symbol ranges.`
+  : null
+
 const waveBrief = [
   `Worktree: ${a.worktreePath || '(cwd)'}`,
   `Base branch for the diff: ${a.baseBranch || '(trunk)'}`,
   `Cards under review (Read each YAML for acceptance_criteria + entrypoints):\n${cards.map((c) => `${c.cardId} — ${c.cardPath || '(no path)'}`).join('\n')}`,
   `ALL changed files in this wave (review every one):\n${unionScope.join('\n')}`,
+  ...(waveBundleBrief ? [waveBundleBrief] : []),
 ].join('\n\n')
 
 function cardScopeBrief(c) {
-  return `Card ${c.cardId} — files changed (review surface):\n${asArr(c.scopeFiles).join('\n') || '(none)'}`
+  const bundle = c.reviewBundlePath
+    ? `\nReview bundle: ${c.reviewBundlePath} — Read it FIRST; do NOT re-Read source files to rebuild context you can get from its paths; for hot_files, Read ONLY the listed symbol ranges.`
+    : ''
+  return `Card ${c.cardId} — files changed (review surface):\n${asArr(c.scopeFiles).join('\n') || '(none)'}${bundle}`
 }
 
 // ───────────────────────────────────────────────────────────────────────────

package/framework/.claude/workflows/new2-resolve.js

@@ -116,7 +116,7 @@ const fixerOpts = fixerAgent === 'coder' ? { model: fixPassModel } : {}
 // finding's domain: doc fixes judged by doc-reviewer (code-reviewer judging prose was
 // cross-domain), test fixes by qa-sentinel (THE test specialist). `ui` and `code` stay with
 // code-reviewer: the judge verifies a CODE change, which is code-reviewer's charter
-// (including DS-coherence rule 8 for UI). Fixer and judge of the same type are still two
+// (including the DS Post-Intervention Coherence check — code-reviewer DS rule 7 — for UI). Fixer and judge of the same type are still two
 // independent instances — the judge prompt is adversarial and greps the files itself.
 const judgeAgent = (domain === 'security' || domain === 'migration') ? 'security-reviewer'
   : domain === 'perf' ? 'api-perf-cost-auditor'

package/framework/.claude/workflows/new2.js

@@ -618,7 +618,7 @@ async function runCard(cardId, cardPath) {
     impl = await agentSafe(
       `Implement card ${cardId} per ${REF}/implement.md Phase 2 — you ARE the owner_agent '${ownerAgent}' — and ${REF}/completeness.md (Phase 2.5 + 2.5b AC-closure ledger). Run all gates/bash yourself.\n${bindingBit}\n${phase1Brief}\n\n${cardBrief}\n\n` +
         `TOOL-CALL BUDGET (v5.0.0 cap-and-handoff — implement.md step 7 briefing section): soft ~80 tool calls, hard 100. Crossing the soft cap (or re-reading the same files): commit WIP ([${cardId}] WIP checkpoint), write /tmp/checkpoint-${cardId}.json per coder.md § Tool-Call Budget & Checkpoint, and return partial:true + checkpointPath + the [CAP-HANDOFF] marker in note. At the hard cap STOP even mid-task — a fresh continuation finishes cheaper than 100 more calls on a bloated context.\n\n` +
-        `POLICIES: G26 Phase-2 lint/tsc/test/build failing after the module's retry cap → buildBlocked:true + blockedGate. Build the AC Closure Ledger (one row per AC: implemented|unmet|policy-deferred). DO NOT silently defer; report unmet rows (excluding policy-deferred). Persist the diff to /tmp/diff-${cardId}.txt AND your completion-report block to /tmp/completion-${cardId}.md. LAST STEP (v5.0.0 review bundle — implement.md step 11c): run \`node "$(ls .claude/skills/new/scripts/build-review-bundle.mjs .framework/framework/.claude/skills/new/scripts/build-review-bundle.mjs 2>/dev/null | head -1)" --card ${cardId} --worktree "$(pwd)" --trunk ${JSON.stringify(TRUNK)} --may-edit "<your mayEditPaths, comma-separated>"\` then \`node "$(ls .claude/skills/new/scripts/doc-invariants.mjs .framework/framework/.claude/skills/new/scripts/doc-invariants.mjs 2>/dev/null | head -1)" --diff /tmp/diff-${cardId}.txt --card <card yaml path> --config baldart.config.yml\` (both scripts missing → skip, note 'bundle-unavailable').\n\n` +
+        `POLICIES: G26 Phase-2 lint/tsc/test/build failing after the module's retry cap → buildBlocked:true + blockedGate. Build the AC Closure Ledger (one row per AC: implemented|unmet|policy-deferred). DO NOT silently defer; report unmet rows (excluding policy-deferred). Persist the diff SCOPED to your MAY-EDIT paths (\`git diff ${JSON.stringify(TRUNK)}...HEAD -- <mayEditPaths>\` — the shared worktree accumulates prior cards' commits, an unscoped dump would include them; v5.0.1) to /tmp/diff-${cardId}.txt AND your completion-report block to /tmp/completion-${cardId}.md. LAST STEP (v5.0.0 review bundle — implement.md step 11c): run \`node "$(ls .claude/skills/new/scripts/build-review-bundle.mjs .framework/framework/.claude/skills/new/scripts/build-review-bundle.mjs 2>/dev/null | head -1)" --card ${cardId} --worktree "$(pwd)" --trunk ${JSON.stringify(TRUNK)} --may-edit "<your mayEditPaths, comma-separated>"\` then \`node "$(ls .claude/skills/new/scripts/doc-invariants.mjs .framework/framework/.claude/skills/new/scripts/doc-invariants.mjs 2>/dev/null | head -1)" --diff /tmp/diff-${cardId}.txt --card <card yaml path> --config baldart.config.yml\` (both scripts missing → skip, note 'bundle-unavailable').\n\n` +
         `E4 OWNERSHIP RECONCILE (implement.md §11b — do this BEFORE returning): the card's MAY-EDIT includes files_likely_touched ∪ paths NAMED EXPLICITLY in this card's acceptance_criteria/definition_of_done (e.g. an ADR the DoD says to update, the data-model / ER doc for a schema change). Editing THOSE is in-scope. For any OTHER dirty file outside MAY-EDIT (another card's file, or unrelated): \`git checkout -- <file>\` to revert it (NEVER leave it orphaned), list it in revertedOutOfOwnership. Set fileDiffViolation:true ONLY if such an edit genuinely could not be reverted (then say why in note) — it is no longer a silent label.\n\n` +
         `Return: { epic, buildBlocked, blockedGate, unmetACs:[{n,text}], scopeFiles, mayEditPaths, revertedOutOfOwnership:[paths], fileDiffViolation, note }`,
       { label: `implement:${cardId}`, phase: 'Implement', agentType: ownerAgent,

package/framework/agents/coding-standards.md

@@ -90,7 +90,7 @@ if (error) {
 
 > **SSOT.** This section is the canonical policy for reference-aliasing mutation
 > hazards. It is cited as the source of truth by `coder.md`
-> (§ Reference-Aliasing Mutation Hazards), `code-reviewer.md` (review checklist),
+> (§ Code Standards & Author-Time Simplicity Discipline — 1-line binding since v5.0.0), `code-reviewer.md` (review checklist),
 > and `.claude/skills/new/references/{completeness,codex-gate}.md` (Phase 2.5 step 5c
 > deterministic detector + Phase 3.7 gate). When those files cite "§ Reference-Aliasing Mutation
 > Patterns", they mean this section.
@@ -163,7 +163,7 @@ the helper's JSDoc so future editors find the contract.
 ### Enforcement layers
 
 - **This section** — full policy + JSDoc contract + remediation menu.
-- `coder.md § Reference-Aliasing Mutation Hazards` — pre-implementation check.
+- `coder.md § Code Standards & Author-Time Simplicity Discipline` (1-line binding) — pre-implementation check.
 - `code-reviewer.md` review checklist — flags un-guarded patterns at review time.
 - `.claude/skills/new/references/completeness.md § Phase 2.5 step 5c` — deterministic
   detector that flags un-guarded patterns as `[ALIAS-MUTATION] BLOCKER` in

package/framework/agents/doc-audit-protocol.md

@@ -18,8 +18,13 @@ audits), `wiki-curator` (coverage signals), the `full-sweep` routine.
 - **Dispatch**: `agents/doc-audit-protocol.md SECTION=<audit-process|drift-validators|topological-generation|epistemic-metadata|scip-refs|schema-drift|coverage-gauges>`.
   Grep for `### SECTION: <name>` and Read ONLY the sections your run needs.
 - **When**: audit mode = invoked WITHOUT card context (general audit, nightly
-  run, cleanup) or explicitly told "full audit". A per-card invocation NEVER
-  needs this module.
+  run, cleanup) or explicitly told "full audit". A per-card invocation does NOT
+  read this module wholesale — the ONLY exceptions are the sections the agent
+  core CITES explicitly (v5.0.1): `epistemic-metadata` + `scip-refs` (ADR
+  quantitative claims), `topological-generation` (a per-card pass writing MORE
+  than one doc file), `schema-drift` (a documented payload's field SET changed
+  in the diff). Everything else (audit-process, drift-validators,
+  coverage-gauges) stays audit-only.
 - **Graceful degradation (MANDATORY)**: every `npm run validate:*` /
   `scripts/*.mjs` referenced here is a project-specific example — check the
   project's `package.json` first, run only what exists, and skip each absent
@@ -147,7 +152,7 @@ model) · `external-reference` (vendor docs, public benchmark).
 4. Is `confidence` calibrated (a vendor cost quote is rarely `high`)?
 
 Run `node scripts/validate-frontmatter.mjs --evidence-only` before finalizing
-(advisory, exit 0). See `docs/references/frontmatter-standard.md § Optional
+(advisory, exit 0). See `${paths.references_dir}/frontmatter-standard.md § Optional
 epistemic metadata`.
 
 ### SECTION: scip-refs
@@ -162,7 +167,7 @@ SCIP symbol IDs survive moves/renames as long as the index is rebuilt —
 F1=80.4% link survival vs ~66% with path-only refs (arXiv 2506.16440).
 
 **Frontmatter contract** (full spec:
-`docs/references/frontmatter-standard.md § Code References`):
+`${paths.references_dir}/frontmatter-standard.md § Code References`):
 ```yaml
 code_refs:
   - symbol: 'src/lib/permissions/middleware.ts#checkPermission()'

package/framework/docs/UPGRADE-3.12-UI-COHERENCE.md

@@ -258,7 +258,7 @@ After update, these files exist locally and are authoritative:
 | Numeric reference tables (type / contrast / spacing / density) | `.framework/framework/agents/design-system-protocol.md` § "Reference Tables (embed)" |
 | Token cascade primitive → semantic → component | `.framework/framework/agents/design-system-protocol.md` § "Token Cascade" |
 | Upgraded `ui-expert` (states taxonomy, red flags, gates) | `.framework/framework/.claude/agents/ui-expert.md` |
-| Code-reviewer rule 8 (merge gate) | `.framework/framework/.claude/agents/code-reviewer.md` § "Design System Compliance" rule 8 |
+| Code-reviewer Post-Intervention Coherence (merge gate) | `.framework/framework/.claude/agents/code-reviewer.md` § "Design System Compliance" rule 7 (Post-Intervention Coherence Check) |
 | `ui-design` Step H (design-time gate) | `.framework/framework/.claude/skills/ui-design/SKILL.md` |
 | Performance Gates (CWV 2026, LCP/INP/CLS) | `.framework/framework/.claude/skills/frontend-design/SKILL.md` § "Performance Gates" |
 | Motion + reduced-motion + View Transitions | `.framework/framework/.claude/skills/motion-design/reference/accessibility-and-modern-apis.md` |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "baldart",
-  "version": "5.0.0",
+  "version": "5.0.1",
   "description": "Claude Agent Framework - Reusable framework for coordinating AI agents and humans in software projects",
   "bin": {
     "baldart": "./bin/baldart.js"