codex-workflow-v2 2.0.0-beta.7 → 2.0.0-beta.8

package/docs/release.md

@@ -22,7 +22,7 @@ The downstream smoke packs the actual tarball, installs it into an empty tempora
 runs the packaged CLI handshake, and proves installation created none of `.codex`, `.tasks`,
 `.increments`, or `.memory-bank` in that project.
 
-For beta.7, the release gate also relies on `npm run release:check` to fail if:
+For beta.8, the release gate also relies on `npm run release:check` to fail if:
 
 - canonical entity schema 2 shapes drift;
 - protocol 2 is not the active public contract, or intact protocol-1 adoption evidence stops being readable through the bounded compatibility window;

package/docs/stable-release-defect-register.md

@@ -1,11 +1,11 @@
 # Stable Release Defect Register
 
 This register captures defects and operational gaps found while running the
-alpha.7 through beta.7 lines against the `signal_v4` Milestone 3 lifecycle. It is intentionally
+alpha.7 through beta.8 lines against the `signal_v4` Milestone 3 lifecycle. It is intentionally
 separate from implementation briefs: an item stays here until it is either
 verified fixed by a regression test or explicitly classified as downstream-only.
 
-Last reviewed: 2026-08-21.
+Last reviewed: 2026-08-22.
 
 ## Severity and status
 
@@ -16,6 +16,29 @@ Last reviewed: 2026-08-21.
 
 ## Post-beta.5 open findings
 
+### WF-STABLE-028 — passed guarded Step strands later final Task-review remediation
+
+- Status: Closed-regression in beta.8
+- Severity: High
+- Area: guarded remediation breaker, final Task review, navigation/mutation agreement
+- Evidence: Signal Task `TASK-01M0HVK4YDJ3W9X0N72TYNV8WK` reached a verified passing third
+  sealed Step review after two ordinary failures and one independently authorized `continue-fix`.
+  A later final Task review found two new defects and `next` correctly advertised `task plan-set`,
+  but the mutation rejected the Plan because the already-consumed `continue-fix` event still
+  matched the current Plan. The suggested current-Plan retry was impossible because the guarded
+  Step was already `completed`.
+- Risk: a valid append-only review history can leave a nonterminal Task with no executable
+  transition even though its state is clean and navigation advertises a corrective Plan update.
+- Fix: a verified passing Step-review event now closes the preceding breaker cycle for that Step.
+  Resolved `continue-fix`, remediation, and decision events remain immutable evidence but do not
+  gate a later final Task-review remediation cycle. A changed guarded Step starts a fresh bounded
+  cycle under the replacement Plan Risk Audit; unresolved and failed cycles retain the existing
+  hard-stop behavior.
+- Regression: `tests/alpha7-remediation-replay.test.ts` reproduces the full sequence through two
+  failed sealed reviews, `continue-fix`, a verified pass, failed final Task review, atomic Plan and
+  Risk Audit replacement, execution authorization, and successful `task run` of the reopened
+  guarded Step while proving the historical sidecars are retained.
+
 ### WF-STABLE-027 — Milestone coordinator stops supervising after Task-chat dispatch
 
 - Status: Closed-regression in beta.7

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "codex-workflow-v2",
-  "version": "2.0.0-beta.7",
+  "version": "2.0.0-beta.8",
   "description": "Requirements-first Codex development workflow with local state and explicit Git ownership.",
   "repository": {
     "type": "git",