diff --git a/.context/codex-reviews/gate-b-quality-al2i9s67y7-pass-1.md b/.context/codex-reviews/gate-b-quality-al2i9s67y7-pass-1.md new file mode 100644 index 0000000..8d781f4 --- /dev/null +++ b/.context/codex-reviews/gate-b-quality-al2i9s67y7-pass-1.md @@ -0,0 +1,2 @@ +NO FINDINGS +END OF FINDINGS (0 total) diff --git a/.context/codex-reviews/gate-b-spec-al2i9s67y7-pass-1.md b/.context/codex-reviews/gate-b-spec-al2i9s67y7-pass-1.md new file mode 100644 index 0000000..8d781f4 --- /dev/null +++ b/.context/codex-reviews/gate-b-spec-al2i9s67y7-pass-1.md @@ -0,0 +1,2 @@ +NO FINDINGS +END OF FINDINGS (0 total) diff --git a/CLAUDE.md b/CLAUDE.md index 7696d1f..b9cec66 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -153,7 +153,7 @@ Mechanics · Severity requires. What a clean final pass and the zero-finding ear closure ordering. Codex is advisory — validate before applying; dismissed finding → one-line why. **Named residual:** the hook's messages state its own threshold as an obligation, so at a -floor of 1 they report a shortfall the cycle does not owe. **That particular overstatement is out of scope here by decision, and it is not a blanket exemption for hook text** — a reminder this change's own rules falsify is corrected in the same change, as the standing sentences above require. +floor of 1 they report a shortfall the cycle does not owe. **That particular overstatement is out of scope here by decision, and it is not a blanket exemption for hook text** — a reminder this change's own rules falsify is corrected in the same change. What makes that tolerable is the precedence rule above plus the hook exiting 0 on every branch, not the reminder being harmless. diff --git a/plugins/dev-workflow/.claude-plugin/plugin.json b/plugins/dev-workflow/.claude-plugin/plugin.json index 7b628ec..e6e4238 100644 --- a/plugins/dev-workflow/.claude-plugin/plugin.json +++ b/plugins/dev-workflow/.claude-plugin/plugin.json @@ -1,7 +1,7 @@ { "name": "dev-workflow", "displayName": "Cross-Model Review Workflow", - "version": "0.13.0", + "version": "0.13.1", "description": "Spec-driven workflow with two independent cross-model review gates, an append-only hardening ledger with an escalation ladder, and repo-enforced quality. Requires the superpowers plugin.", "author": { "name": "Daniel Sänger", diff --git a/plugins/dev-workflow/CHANGELOG.md b/plugins/dev-workflow/CHANGELOG.md index 3289350..47c492a 100644 --- a/plugins/dev-workflow/CHANGELOG.md +++ b/plugins/dev-workflow/CHANGELOG.md @@ -22,6 +22,13 @@ unambiguously, still fails. Deleting only a plugin's *manifest* while the direct keeps shipping fails too. AGENTS.md invariant 12 carries the complete list. +## 0.13.1 + +- **The Named residual loses a dangling reference.** Its closing clause, "as the standing + sentences above require", pointed at a list that exists only in the loop-rule target text, not + above it in `CLAUDE.md` or in `/dev-workflow:workflow-init`'s template. The clause is removed + from both copies; the sentence before it states the rule on its own. No rule changed. + ## 0.13.0 - **One closure ordering for §5**, installed in `CLAUDE.md`'s gate section and in diff --git a/plugins/dev-workflow/commands/workflow-init.md b/plugins/dev-workflow/commands/workflow-init.md index b7ef2ca..8c480f1 100644 --- a/plugins/dev-workflow/commands/workflow-init.md +++ b/plugins/dev-workflow/commands/workflow-init.md @@ -360,7 +360,7 @@ Mechanics · Severity requires. What a clean final pass and the zero-finding ear closure ordering. Codex is advisory — validate before applying; dismissed finding → one-line why. **Named residual:** the hook's messages state its own threshold as an obligation, so at a -floor of 1 they report a shortfall the cycle does not owe. **That particular overstatement is out of scope here by decision, and it is not a blanket exemption for hook text** — a reminder this change's own rules falsify is corrected in the same change, as the standing sentences above require. +floor of 1 they report a shortfall the cycle does not owe. **That particular overstatement is out of scope here by decision, and it is not a blanket exemption for hook text** — a reminder this change's own rules falsify is corrected in the same change. What makes that tolerable is the precedence rule above plus the hook exiting 0 on every branch, not the reminder being harmless.