codex-workflow-v2 2.0.0-beta.13.6 → 2.0.0-beta.13.7

package/docs/release.md

@@ -4,6 +4,38 @@ The npm package is `codex-workflow-v2` with public visibility. Consumers must pi
 an exact version. Stable compatibility covers the latest minor release of the current
 major only; older minors are unsupported unless a release note explicitly says otherwise.
 
+## beta.13.7 candidate: retire completed carryover authority
+
+After a recovered Step passed review, its recorded dirty-work permission still
+overrode the next Step's route. A later repeated mechanical failure therefore
+returned `doctor` instead of ordinary Plan replacement. The completed record is
+now retained as history and consumed only after its completion evidence, exact
+PRA, required strict review and Git history are verified. Active or damaged
+bindings continue to fail closed. A corrective claim must belong to the same
+Worker who performed the terminal corrective yield.
+
+The exact published beta.13.7 read-only compatibility preflight can guide a
+stranded beta.13.6 source through its existing Plan replacement and original-Worker
+handoff commands before transport. It does not mutate state, authorize execution,
+or waive approval gates. Task and base transport must preserve all product bytes
+and change only the exact Workflow dependency. See the packaged gateway skill for
+the stage-specific bindings and mandatory source status/next readbacks.
+
+Release evidence must include the published beta.13.6 runtime reproducing the
+later-Step blocker, source Plan/PRA/authorization/handoff recovery, dependency
+transport, target provenance/context refresh, same-Worker execution and strict
+review. A route that reaches only `plan-set` is not sufficient. Prior one-time
+release-gate exceptions do not authorize this candidate.
+
+The trusted lifecycle harness must record each compatibility invocation and its
+terminal observation. For source `task plan-set`, record `inputBinding` computed
+from the actual files passed to that command: `candidatePlanHash` is the rendered
+Plan hash, and `candidateInputHash`/`riskAuditInputHash` are SHA-256 of recursively
+key-sorted canonical JSON inputs. Do not copy these values from an approval receipt
+without checking the executed inputs. The validator checks this binding, the resulting
+Plan hash, original-Worker ownership, ordered source status/next checkpoints, live-lease
+waiting, exact stale repair, and a fresh preflight before transport.
+
 ## beta.13.6 candidate: preserve work across root-cause replan
 
 A repeated mechanical failure can legitimately yield the same Task to a replacement

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "codex-workflow-v2",
-  "version": "2.0.0-beta.13.6",
+  "version": "2.0.0-beta.13.7",
   "description": "Requirements-first Codex development workflow with local state and explicit Git ownership.",
   "repository": {
     "type": "git",
@@ -68,6 +68,7 @@
   },
   "devDependencies": {
     "@types/node": "24.10.1",
+    "codex-workflow-source-beta136": "npm:codex-workflow-v2@2.0.0-beta.13.6",
     "typescript": "5.9.3"
   },
   "license": "MIT"

package/plugins/codex-workflow-gateway/skills/codex-workflow-gateway/SKILL.md

@@ -124,7 +124,41 @@ paths and content hash. Every retained path must already be allowed by the new S
 and remain outside forbidden scope. A changed binding or blocked assessment is a hard
 stop; never clean, stash, reset, manually commit, or edit state to make it eligible.
 
-The beta.13.6 corrective-carryover update compatibility profile permits its exact
+The beta.13.7 consumed-carryover compatibility profile also permits the exact
+published external beta.13.7 runner to execute only the read-only
+`update corrective-carryover-preflight --id <TASK-ID>` against a coherent beta.13.6
+repository. A completed, verified Step's carryover remains historical evidence;
+it must not override a later Step's repeated-cause recovery route.
+
+When `sourceRecovery.eligible=true`, execute only its exact `action` with the
+repository-installed beta.13.6 CLI. This narrow compatibility response, not the
+old source `next`, authorizes the source navigation repair. It may expose only
+`task plan-set`, `task handoff-prepare`, or `task claim`, bound to the current
+Task revision, Plan, completed history, terminal failure HEAD/dirty hash and
+corrective-yield actor. For Plan replacement, prepare the exact candidate Plan
+and independent PRA files, then pass them as `--file` and `--risk-audit-file`
+to this read-only preflight. Without both inputs no source mutation is authorized.
+Require the returned candidate Plan and input hashes; execute source `task plan-set`
+with those same unchanged files and verify its resulting Plan hash. Core rejects
+candidate inputs that omit or alter any completed Step before source mutation.
+Source execution
+authorization retains its ordinary human or exact eligible delegation gate.
+Use only the returned original Worker for handoff and claim. After every source
+mutation run source `status` then `next`, and repeat the target preflight before
+another compatibility action. `sourceRecovery` never authorizes transport or
+`task run`; top-level `eligible` remains false until transport itself is proved.
+
+Once the replacement Plan is authorized and that same Worker has claimed it,
+the preflight may expose the exact expired-lease repair described below. Never
+force-release a live lease. Require a fresh top-level `eligible=true` before
+dependency transport. beta.13.7 accepts one dependency-only commit on each of
+the Task and Milestone base, with the same exact source beta.13.6 and target
+beta.13.7. After installing the target, use its ordinary advertised
+dependency provenance recovery, atomic context refresh and original-Worker
+credential recovery. This profile permits no external state mutation, installed
+code patch, wider product commit, changed dirty bytes, or approval substitution.
+
+The historical beta.13.6 corrective-carryover update compatibility profile permits its exact
 external runner to execute only the read-only
 `update corrective-carryover-preflight --id <TASK-ID>` against a repository coherently
 pinned to beta.13.5. This is an explicit compatibility inspection, not permission to