codex-workflow-v2 2.0.0-beta.13.8 → 2.0.0-beta.13.9

package/docs/pdf/sources/codex-workflow-v2-architecture-ru.md

@@ -463,7 +463,7 @@ Restart Docker Desktop требует отдельного разрешения
 # 10. Operational checklist
 
 - exact package version установлен, bundled gateway соответствует release и переустановлен;
-- handshake подтверждает `packageVersion=2.0.0-beta.13.5`, protocol 2, state schema 2 и beta.13
+- handshake подтверждает `packageVersion=2.0.0-beta.13.9`, protocol 2, state schema 2 и beta.13
   capabilities;
 - routine observation начинается с компактного `status`; `status --full` запрашивается только для
   расследования, которому действительно нужна полная historical projection;

package/docs/pdf/sources/codex-workflow-v2-chat-only-guide-ru.md

@@ -57,7 +57,7 @@ AGENTS.md
 -> doctor только как дополнительная диагностика
 ```
 
-Handshake beta.13.5 должен сообщать `packageVersion=2.0.0-beta.13.5`, `protocolVersion=2`,
+Handshake beta.13.9 должен сообщать `packageVersion=2.0.0-beta.13.9`, `protocolVersion=2`,
 `stateSchemaVersion=2`, dependency DAG, initial Plan transaction, mechanical feasibility,
 Milestone autonomy, host-safe credential reference, failed-Step continuation transaction,
 cause-bound rolling refinement, structural production edge, compact status, reviewer runtime preflight,
@@ -168,8 +168,6 @@ base HEAD. Final acceptance выполняй только по exact eligible gr
 текущему MSA-code; иначе покажи полный requiredHumanGate и остановись.
 ```
 
-<!-- pagebreak -->
-
 ## 4.1. Что должно получиться до autonomy gate
 
 - Discovery без blocking unknowns;
@@ -481,8 +479,8 @@ Task/project DGR. `dependencyBinding` для standalone handoff равен null.
 
 # 14. Итоговый checklist пользователя
 
-- beta.13.1 exact package и новый bundled gateway установлены; handshake показывает
-  `packageVersion=2.0.0-beta.13.5`, protocol/state schema `2/2` и beta.13 capabilities;
+- beta.13.9 exact package и новый bundled gateway установлены; handshake показывает
+  `packageVersion=2.0.0-beta.13.9`, protocol/state schema `2/2` и beta.13 capabilities;
 - новый Coordinator chat не является fork старого Milestone;
 - bootstrap DGR, если нужен, выдан отдельным exact human confirmation;
 - Discovery не materialized при blocking unknowns;

package/docs/pdf/sources/codex-workflow-v2-technical-reference-ru.md

@@ -15,7 +15,7 @@ authority сами: mutating permission определяется runtime state
 
 | Параметр beta.13 | Значение |
 |---|---|
-| npm package | `codex-workflow-v2@2.0.0-beta.13.5` |
+| npm package | `codex-workflow-v2@2.0.0-beta.13.9` |
 | protocolVersion | 2 |
 | stateSchemaVersion | 2 |
 | lifecycle epoch | 2 |
@@ -767,7 +767,7 @@ dirty update.
 observed-route matrix/compact-status/reviewer-runtime tests, legacy compatibility regressions,
 `npm run test:signal-t10-check-support-e2e`, `npm run test:signal-remediation-e2e`,
 `npm run pack:check`, `npm run smoke:downstream`, `npm run plugin:check`, official plugin/skill validators,
-`npm run docs:pdf:check` и `npm run release:check` с exact `v2.0.0-beta.13.5` tag binding и append-only
+`npm run docs:pdf:check` и `npm run release:check` с exact `v2.0.0-beta.13.9` tag binding и append-only
 real-agent lifecycle log. Candidate проверяется из clean source checkout; missing built module не должен
 превращаться в stack trace, а обязан быть детерминированно собран или диагностирован release gate.
 

package/docs/release.md

@@ -4,6 +4,31 @@ 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.9: failed-Step planning recovery after Knowledge rebind
+
+A started Task can retain completed Steps and a failed guarded Step while a Knowledge
+rebind supersedes its execution authorization. A truthful blocking Plan Risk Audit must
+not require a false approval to reach corrective planning. This recovery uses the current
+blocking audit as planning evidence and proves its unchanged safety baseline through
+hash-checked Knowledge-only Plan history and the historical superseded authorization.
+It never treats either record as current execution authority.
+
+Fresh navigation can then advertise the existing independent corrective-decision route.
+The ordinary corrective yield, independent replacement validation and risk audit, exact
+human corrective-replan confirmation, and fresh execution authorization remain mandatory.
+An ordinary `plan-set` cannot bypass that chain. `continue-fix` is not a valid decision
+for this stopped planning posture; ordinary execution repair retains its existing choices.
+The additive upstream-remediation route remains limited to genuinely unstarted Tasks.
+
+Release evidence must exercise the complete callable recovery chain, including original
+Worker credential replacement and yield, repeated Knowledge rebind, unchanged completed
+Step and failed review evidence, and rejection of damaged Plan/audit/authorization history.
+
+The exact beta.13.9 runner retains the consumed-carryover compatibility profile from
+beta.13.6 with beta.13.9 as its pinned target. The source, ownership, lease, candidate
+Plan, provenance and transaction checks are unchanged. Historical beta.13.7 and
+beta.13.8 transcripts remain bound to their original targets.
+
 ## beta.13.8: explain changes and continue active Milestones
 
 Full autonomy can be issued during an active Milestone using an exact new human-confirmed

package/package.json

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

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

@@ -158,6 +158,11 @@ 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 exact beta.13.9 runner supports the same bounded consumed-carryover profile
+with beta.13.6 as its source and beta.13.9 as its pinned target. Require the
+returned version bindings and all the same source-recovery and transport proofs.
+Historical beta.13.8 evidence is not proof for a beta.13.9 invocation.
+
 The historical beta.13.7 runner retains its own exact beta.13.6-to-beta.13.7 profile.
 The current beta.13.8 profile does not admit a beta.13.7 source or an in-progress
 Step and cannot be used to bypass the ordinary safe update boundary.
@@ -682,6 +687,18 @@ only for membership changes; any change to outcome, success signal, acceptance,
 discovery, or base branch requires the ordinary human scope-change gate. Never self-renew or
 replace the contract.
 
+When fresh `next` advertises `task corrective-decision` with
+`planningRecovery.authority = "planning-only"`, a started failed Step has a current
+blocking audit after a Knowledge-only Plan rebind. Core proves the historical approved
+safety baseline; the stopped audit does not authorize execution. Obtain the independent
+corrective decision against the returned bindings and preserve the exact original Worker
+credential/yield prerequisites. Follow the existing human-confirmed corrective-replan
+route, then fresh replacement Plan authorization. Never approve the obstructed Plan merely
+to unlock navigation, use ordinary `plan-set` to bypass the corrective gate, or create an
+upstream remediation Task for this already-started posture. `continue-fix` is unavailable
+for this planning-only route. A package update can require another Knowledge rebind and
+fresh blocking audit; do not rewrite or silently reuse a stale audit.
+
 Repeated failed Task reviews remain on the same Task and do not require a separate corrective
 Plan audit based only on count. Follow fresh `next`: ordinary findings default to `route=fix`;
 `route=replan` is valid only with the exact Plan clause, obstruction, and minimal Plan change