codex-workflow-v2 2.0.0-beta.12.1 → 2.0.0-beta.12.3

package/docs/autonomy-guardrails.md

@@ -92,10 +92,24 @@ inputs and code. Apply appends `stop-escalate-overrides.jsonl`; it never deletes
 original stop. A stale binding, wrong code, duplicate/conflicting override, or damaged hash chain
 fails before continuation. Delegation is not accepted for this Human gate.
 
-This is not a general stop reversal. It does not apply to `split-required`, Plan drift, a different
-attempt ordinal, missing attempt-3 continue authority, or an agent-authored semantic stop outside
-the beta.11 policy shape. After a valid append, attempt four returns to the normal `task run` then
-strict-review cycle; review quality and all later corrective decisions remain unchanged.
+This is not a general stop reversal. It does not apply to `split-required`, semantic Plan drift, a
+different attempt ordinal, missing attempt-3 continue authority, or an agent-authored semantic stop
+outside the beta.11 policy shape. After a valid append, attempt four returns to the normal `task run`
+then strict-review cycle; review quality and all later corrective decisions remain unchanged.
+
+Beta.12.3 also handles the case where the accepted third attempt changed approved Project Knowledge
+and package self-updates added later refreshes: the already-applied override may be followed by one
+or more ordinary delegated `task context-refresh` transitions before attempt four starts. A fresh
+`next` resumes `task run` only when Core can prove all of the following together: the same exact
+three-event remediation history and stop override remain hash-valid; every adjacent Plan differs
+only in its canonical Knowledge Map binding line; the Knowledge rebinds and mechanical Plan Risk
+Audit rebounds form one contiguous source-to-current chain; and the refreshed approval plus current
+execution authorization share the valid delegated authority. If Git HEAD advanced, every
+intervening commit must have one exact registered dependency-provenance recovery, one parent, a
+`systemCommits` binding, and exactly the `package.json`/`package-lock.json` diff. The proof is derived
+from existing append-only evidence, so this route does not create a second recovery journal.
+Missing evidence, semantic Plan change, an unregistered/product commit, a broken chain, or damaged
+chronology routes to `doctor` rather than weakening the generic two-attempt corrective recovery gate.
 
 ### First-failure Plan-integrity recovery
 

package/docs/decisions.md

@@ -97,3 +97,11 @@ This document closes the requirement gaps identified during the V2 design review
 19. **Derived independent actors.** Core derives stable Task Worker and corrective Auditor
     actors from Task identity. This removes name-selection pauses without weakening C1 claim,
     lease, or auditor-independence checks.
+20. **Stop-override authority survives mechanical update chains.** The exact Human-confirmed
+    beta.11 attempt-four override remains valid across any contiguous append-only sequence of
+    content-only Plan rebinds. Every adjacent immutable Plan, Knowledge rebind, and mechanical
+    Plan Risk Audit rebound must agree. Git HEAD may advance only through a contiguous chain of
+    already registered dependency-provenance commits, each single-parent and limited to
+    `package.json` plus `package-lock.json`. Semantic Plan drift, product commits, missing
+    provenance, or broken chronology still fails closed; generic corrective-decision recovery
+    remains direct and is not widened.

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

@@ -1,10 +1,10 @@
 ---
-title: Codex Workflow V2: архитектура beta.12.1
+title: Codex Workflow V2: архитектура beta.12.3
 subtitle: Источники истины, lifecycle, роли, delegation, зависимости Tasks и границы доверия
 part: Часть 1 из 3 | Архитектура
 document_version: 2.0
-date: 27 августа 2026
-subject: Архитектура и границы Codex Workflow V2 beta.12.1
+date: 28 августа 2026
+subject: Архитектура и границы Codex Workflow V2 beta.12.3
 ---
 
 # 1. Назначение и граница системы
@@ -18,7 +18,7 @@ Codex Workflow V2 - локальный state machine поверх Codex App, Git
 Система рассчитана на одного пользователя и одну машину. Она не предоставляет distributed locking,
 криптографическую идентификацию actor string или безопасную синхронизацию state между компьютерами.
 
-## 1.1. Что beta.12.1 гарантирует
+## 1.1. Что beta.12.3 гарантирует
 
 - exact project-local npm package и совместимый handshake до lifecycle действий;
 - Discovery до materialization Task или Milestone;
@@ -30,7 +30,7 @@ Codex Workflow V2 - локальный state machine поверх Codex App, Git
 - state-bound human gates либо ранее выданные bounded delegation contracts;
 - journaled recovery для составных переходов и fail-closed поведение при drift/corruption.
 
-## 1.2. Что beta.12.1 не гарантирует
+## 1.2. Что beta.12.3 не гарантирует
 
 - правильность продуктовой идеи или автоматически выбранного provider Task;
 - semantic sufficiency Plan, если точные факты нельзя доказать поддерживаемым analyzer;
@@ -218,13 +218,22 @@ Failed review не ограничивает число попыток. Попы
 `route=replan` допустим только с точным Plan conflict и меняет лишь implementation Steps, не objective,
 requirements или acceptance. Explicit `split-required` и `stop-escalate` остаются stop/redirect decisions.
 
-Beta.12.1 добавляет только одну append-only compatibility оговорку: beta.11 attempt-four
+Beta.12.1 добавила одну append-only compatibility оговорку: beta.11 attempt-four
 `stop-escalate` после exact `ordinary, ordinary, corrective` и prior attempt-3 `continue-fix` можно
 возобновить через read-only `stop-override-prepare` и отдельный Human-confirmed
 `stop-override-apply`. Исходный stop сохраняется, `split-required` не подходит, а stale revision,
 Plan, HEAD, lease, transaction или повреждённая chain блокируют переход. Попытка 4 снова проходит
 обычный `task run` и новый strict review.
 
+Beta.12.3 сохраняет этот override при последовательности delegated `task context-refresh`, если
+каждая версия Plan изменилась только в canonical Knowledge Map binding. Core проверяет весь
+contiguous rebind/audit chain, mechanical equivalence каждого Plan Risk Audit, общую delegated
+authority и корректную chronology. Git HEAD может продвинуться только через последовательность
+зарегистрированных dependency-provenance commits, каждый из которых меняет ровно package.json и
+package-lock.json. При утрате claimed writer lease используется только одновременно рекламируемый
+`task writer-credential-replace`; semantic Plan drift, разрыв chain или любой другой commit
+возвращают `doctor`.
+
 Dependency-provenance recovery beta.12.1 также сохраняет ранее закоммиченные Task-local поля
 manifest/lock, даже если base их не содержит. Candidate остаётся dependency-only: после удаления
 только Workflow dependency parent и HEAD обязаны совпасть по всем product-owned полям.
@@ -238,7 +247,7 @@ worktree или Plan и не создаёт synthetic second failure; он за
 # 10. Operational checklist
 
 - exact package version установлен, bundled gateway соответствует release и переустановлен;
-- handshake подтверждает protocol 2, state schema 2 и beta.12.1 capabilities;
+- handshake подтверждает protocol 2, state schema 2 и beta.12.3 capabilities;
 - каждый mutation следует свежему `status -> next` и exact option contract;
 - semantic unknowns и human gates не маскируются delegation;
 - Task chats создаёт coordinator, credentials остаются только в памяти;

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

@@ -1,13 +1,13 @@
 ---
 title: Codex Workflow V2: delegated chat-only guide
-subtitle: Актуальный beta.12.1 путь от нового Discovery до принятого Milestone без ручного CLI
+subtitle: Актуальный beta.12.3 путь от нового Discovery до принятого Milestone без ручного CLI
 part: Часть 2 из 3 | Практика
 document_version: 2.0
-date: 27 августа 2026
-subject: Практическое руководство по delegated Discovery и Milestone в Workflow V2 beta.12.1
+date: 28 августа 2026
+subject: Практическое руководство по delegated Discovery и Milestone в Workflow V2 beta.12.3
 ---
 
-# 1. Рабочая модель beta.12.1
+# 1. Рабочая модель beta.12.3
 
 Пользователь работает в одном Codex Project и формулирует продуктовый outcome. Coordinator выполняет
 CLI, создаёт отдельные Task/Reviewer chats и ведёт supervision loop. Workflow Core остаётся authority
@@ -40,7 +40,7 @@ Blocking unknown, scope change, grant issuance или unrecoverable integrity co
 # 2. Подготовка проекта перед новым Discovery
 
 1. Убедитесь, что checkout чистый и выбран правильный repository root.
-2. Установите beta.12.1 как точную devDependency после публикации release.
+2. Установите beta.12.3 как точную devDependency после публикации release.
 3. Обновите и переустановите bundled `codex-workflow-gateway` этого release.
 4. Проверьте, что declared и installed package versions равны.
 5. Запустите новый Coordinator chat, не fork старого Milestone conversation.
@@ -56,7 +56,7 @@ AGENTS.md
 -> doctor только как дополнительная диагностика
 ```
 
-Handshake beta.12.1 должен сообщать `packageVersion=2.0.0-beta.12.1`, `protocolVersion=2`,
+Handshake beta.12.3 должен сообщать `packageVersion=2.0.0-beta.12.3`, `protocolVersion=2`,
 `stateSchemaVersion=2`, dependency DAG, initial Plan transaction, mechanical feasibility,
 Milestone autonomy и structural replacement disabled capabilities.
 
@@ -116,7 +116,7 @@ delegate, scope, transitions и expiry. DGR передаётся только е
 ```text
 НОВЫЙ COORDINATOR CHAT
 
-Проведи новый Milestone через Codex Workflow V2 beta.12.1 в delegated режиме.
+Проведи новый Milestone через Codex Workflow V2 beta.12.3 в delegated режиме.
 Repository: <ABSOLUTE-REPOSITORY-ROOT>.
 Milestone ID: AUTO.
 Delegate actor: agent:milestone-coordinator.
@@ -305,6 +305,14 @@ Task chat записывает его только при совпадении p
 Plan-integrity recovery не редактирует Plan, package.json или worktree и не синтезирует второй failure.
 P04-A не переносит completed Steps и не rewires dependencies при split.
 
+Если после применённого stop override `next` рекламирует delegated `task context-refresh` или
+`update dependency-provenance-recover`, выполните только этот advertised atomic/recovery переход и
+снова запросите `status -> next`. Таких механических refresh/update циклов может быть несколько.
+Продолжайте attempt 4 только при `stopOverrideContextRebind.state=validated`. При одновременном
+`writerCredentialRecovery.action=task writer-credential-replace` сначала восстановите credential
+точного claimant-актора. `doctor`, semantic Plan change, разрыв rebind/audit chain или HEAD commit без
+точного dependency-provenance record означают stop, а не ручной обход.
+
 # 12. Milestone final acceptance
 
 После merge всех required Tasks Coordinator проверяет clean base HEAD и выполняет рекламируемую
@@ -322,7 +330,7 @@ Task/project DGR. `dependencyBinding` для standalone handoff равен null.
 
 # 14. Итоговый checklist пользователя
 
-- beta.12.1 exact package и новый bundled gateway установлены;
+- beta.12.3 exact package и новый bundled gateway установлены;
 - новый Coordinator chat не является fork старого Milestone;
 - bootstrap DGR, если нужен, выдан отдельным exact human confirmation;
 - Discovery не materialized при blocking unknowns;

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

@@ -1,10 +1,10 @@
 ---
-title: Codex Workflow V2: технический справочник beta.12.1
+title: Codex Workflow V2: технический справочник beta.12.3
 subtitle: Protocol 2, state schema 2, transactions, credentials, dependency authority, review и recovery
 part: Часть 3 из 3 | Technical reference
 document_version: 2.0
-date: 27 августа 2026
-subject: Технический контракт Codex Workflow V2 beta.12.1
+date: 28 августа 2026
+subject: Технический контракт Codex Workflow V2 beta.12.3
 ---
 
 # 1. Runtime contract
@@ -13,9 +13,9 @@ Workflow V2 предоставляет локальные revisioned transitions
 и `value` либо структурированную ошибку с `code`, `message` и `details`. Chat, PDF и gateway не создают
 authority сами: mutating permission определяется runtime state и свежим `next`.
 
-| Параметр beta.12.1 | Значение |
+| Параметр beta.12.3 | Значение |
 |---|---|
-| npm package | `codex-workflow-v2@2.0.0-beta.12.1` |
+| npm package | `codex-workflow-v2@2.0.0-beta.12.3` |
 | protocolVersion | 2 |
 | stateSchemaVersion | 2 |
 | lifecycle epoch | 2 |
@@ -37,7 +37,7 @@ Gateway выполняет:
 5. вызов только package-local `dist/src/cli.js --repo <root>`;
 6. `gateway handshake` до lifecycle действий.
 
-Ключевые beta.12.1 capabilities:
+Ключевые beta.12.3 capabilities:
 
 | Группа | Capabilities |
 |---|---|
@@ -46,7 +46,7 @@ Gateway выполняет:
 | Task planning | Plan Risk Audit, proof obligations, mechanical feasibility |
 | C1 | handoff sidecar, handoff bundle, derived Worker actor, credential replacement |
 | Reviews | strict reviewer, Step strict review, continuable remediation, evidence-bound fix/replan routing |
-| Recovery | Task-local dependency provenance, plan integrity, remediation mode, legacy stop override, corrective yield/replan journals |
+| Recovery | Task-local dependency provenance, plan integrity, remediation mode, legacy stop override, append-only stop-rebind chain, corrective yield/replan journals |
 | Replacement | `structural-task-replacement-disabled-v1` |
 
 Handshake incompatibility прекращает работу. Запуск global package, `latest`, mutable range или соседней
@@ -316,7 +316,7 @@ fresh `next` через corrective yield и обычный Human-confirmed repla
 P01-A предотвращает поддерживаемые contradictions до fresh authorization. beta.11 path остаётся для
 pre-P01 authorizations и late/unsupported exact recovery cases.
 
-# 13.1. beta.12.1 compatibility transitions
+# 13.1. beta.12.3 compatibility transitions
 
 `update dependency-provenance-recover` больше не требует полного равенства Task manifest/lock с base.
 Base остаётся version authority, а parent/HEAD candidate сравниваются без единственных Workflow
@@ -329,6 +329,17 @@ remediation events, Plan, HEAD, package, human actor и reason. Apply в отд
 `stop-escalate-overrides.jsonl`. Original corrective decision остаётся неизменным. Split, stale binding,
 lease/transaction, дубликат с другим binding и tampering fail closed.
 
+После apply несколько delegated `task context-refresh` могут сделать source Plan историческим.
+`task run` доступен, только если Core доказывает contiguous source-to-current chain: adjacent Plans
+различаются лишь Knowledge binding, rebinds совпадают с artifacts, audits являются mechanical
+rebounds, а current approval/authorization сохраняют одну delegated authority и chronology.
+
+HEAD может отличаться от override только через зарегистрированные single-parent
+`dependencyProvenanceRecoveries` в `systemCommits`, каждый с exact `package.json`/`package-lock.json`
+diff. Semantic drift, иной commit или разрыв chain fail closed. Projection содержит
+`stopOverrideContextRebind.state=validated`; lost lease восстанавливает только advertised
+`task writer-credential-replace`.
+
 # 14. P04-A structural replacement boundary
 
 Command shape `task replacement-materialize` retained только для compatibility diagnostics. Любая попытка
@@ -386,7 +397,7 @@ Graph является навигационным индексом, не Project
 После каждой successful mutation обязателен sequential `status`, затем fresh `next`. Failed status/next
 не разрешает direct mutation. Syntax help read-only и не заменяет navigation authority.
 
-# 18. Public command surface beta.12.1
+# 18. Public command surface beta.12.3
 
 | Область | Actions |
 |---|---|
@@ -413,7 +424,7 @@ Exact options берутся из fresh `next`; command help используе
 running Step и active/stale writer lease. External runner допустим только в документированной rescue
 compatibility форме.
 
-Перед beta.12.1 tag release repository выполняет:
+Перед beta.12.3 tag release repository выполняет:
 
 1. `npm ci`;
 2. `npm run validate`;
@@ -423,6 +434,3 @@ compatibility форме.
 6. `npm run docs:pdf:check`;
 7. `npm run release:check` с exact release tag binding;
 8. validation append-only real-agent lifecycle log.
-
-PDF source и binaries должны совпасть детерминированно. Tag имеет форму `v<package-version>`.
-Publication не выполняется локальными validation commands.

package/docs/release.md

@@ -27,7 +27,7 @@ The PDF check deterministically regenerates all three Russian documents from
 `docs/pdf/sources`, binds the visible package version to the root manifest, and fails when any
 tracked PDF is stale. Source and binary PDFs are one release unit.
 
-For beta.12.1, the release gate also relies on `npm run release:check` to fail if:
+For beta.12.3, 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;
@@ -57,6 +57,11 @@ For beta.12.1, the release gate also relies on `npm run release:check` to fail i
 - the append-only, Human-confirmed beta.11 attempt-four stop override, its exact three-event/
   continue/stop binding, split rejection, stale-confirmation rejection, or tamper detection is
   absent from the package.
+- an already-applied beta.11 stop override cannot survive a contiguous append-only chain of later
+  context-only Plan rebinds with exact mechanical audits, delegation, and chronology;
+- Git HEAD may advance between the override and current execution authorization through anything
+  except an exact chain of registered dependency-provenance commits that each change only
+  `package.json` and `package-lock.json`; or the route weakens the generic stale-decision recovery gate.
 
 The separate lifecycle transcript validator fails if the real-agent log contains a mutation that
 bypasses failed `status`/`next`, an unadvertised or failed mutation, an unresolved syntax-only

package/docs/updating-existing-project.md

@@ -72,10 +72,26 @@ stop decision, Plan hash, Git HEAD, все три remediation events и policy
 В отдельном пользовательском сообщении разрешите apply с теми же параметрами и возвращённым
 `SOO-*` кодом. `task stop-override-apply` добавляет одну запись в
 `stop-escalate-overrides.jsonl`, сохраняя исходный `stop-escalate`; после него выполните
-последовательные `status` и `next`. Ожидаемый route — `task run` того же Step с последующим новым
-strict review. Этот путь не работает для `split-required`, другого attempt ordinal, изменённого
-Plan/HEAD/revision, отсутствующего attempt-3 continue, active/stale lease, dirty checkout или
-незавершённой Task transaction. Delegated approval для него отсутствует.
+последовательные `status` и `next`. Обычно ожидаемый route — `task run` того же Step с последующим
+новым strict review. Beta.12.3 покрывает и последовательность package self-update/context-refresh
+циклов после override. Перед `task run` выполняйте только свежие advertised
+`update dependency-provenance-recover` и delegated `task context-refresh`; циклов может быть
+несколько. Workflow продолжит attempt 4 лишь когда докажет contiguous source-to-current chain:
+каждый Plan отличается только canonical Knowledge Map binding, каждый rebind совпадает с Plan
+artifacts, каждый Plan Risk Audit является mechanical rebound, а current approval/authorization
+сохраняют одну delegated authority. HEAD может продвинуться только через зарегистрированные
+single-parent dependency-provenance commits, каждый с exact `package.json`/`package-lock.json` diff.
+Новая stop-override recovery-запись не создаётся — используется существующая append-only evidence.
+Если C1 остаётся claimed, но writer lease после Human boundary отсутствует, `next` вместе с
+`task run` рекламирует `task writer-credential-replace`; сначала восстановите credential exact
+claimant-актора, затем запускайте Step.
+
+Этот путь не работает для `split-required`, другого attempt ordinal, семантически изменённого
+Plan, отсутствующего attempt-3 continue, разорванной rebind/audit chain, незарегистрированного или
+product HEAD commit, повреждённой chronology, active/stale lease на Human prepare/apply boundary
+или незавершённой Task transaction.
+Delegated approval для самого stop override отсутствует; delegation относится только к обычному
+context refresh после уже подтверждённого Human override.
 
 ## 1. Подготовьте отдельный чат обновления
 

package/docs/validation-report.md

@@ -1,99 +1,97 @@
-# V2 beta.12.1 Validation Report
+# V2 beta.12.3 Validation Report
 
-Release candidate `2.0.0-beta.12.1` was validated on 2026-08-27 with Node.js 24.17.0.
+Release candidate `2.0.0-beta.12.3` was validated on 2026-08-28 (Europe/Moscow) with
+Node.js 24.17.0.
 
 ## Automated release evidence
 
 - `npm ci` completed from the committed lockfile with 0 reported vulnerabilities.
-- The final `npm run validate` passed typecheck and `325/325` sequential tests with no failures,
-  skips, cancellations, or todos.
-- Focused compatibility replay passed independently: dependency provenance plus Signal T04 and
-  legacy stop override tests passed `9/9`; the stop-only suite passed again after the final
-  observation-boundary hardening (`3/3`).
-- `npm run pack:check` produced the beta.12.1 dry-run tarball with 270 files, package size 967.2 kB,
-  and unpacked size 3.8 MB. The sandboxed npm-cache attempt failed with `EPERM`; the authorized
-  retry using the same source passed.
-- `npm run smoke:downstream` packed and installed the actual
-  `codex-workflow-v2-2.0.0-beta.12.1.tgz` in an empty temporary project and passed the packaged
-  handshake.
+- The final `npm run validate` passed typecheck and `326/326` sequential tests with no failures,
+  skips, cancellations, or todos in 1,360,950.996834 ms.
+- The suite includes the new beta.12.3 two-update stop-override replay, the beta.12.2 direct-rebind
+  replay, unchanged-Plan stop override, five-cycle continuable remediation, generic stale-decision
+  recovery, credential safety, dependency provenance, Signal T04, P01-A, P04-A, transaction,
+  observer-purity, and transition-model regressions.
+- `npm run pack:check` produced `codex-workflow-v2-2.0.0-beta.12.3.tgz` with 270 files,
+  package size 976.2 kB, unpacked size 3.9 MB, and SHA-1
+  `ceb2ef4c7b076b9ae01a09127d05b867d101bfb1`. The sandboxed npm-cache attempt failed with
+  `EPERM`; the authorized retry using the same source passed.
+- `npm run smoke:downstream` packed and installed the beta.12.3 tarball in an empty temporary
+  project and passed the packaged handshake. The sandboxed attempt could not resolve the npm
+  registry for AJV; the authorized network retry using the same source passed.
 - `npm run plugin:check`, the official Codex plugin validator, the gateway skill validator,
-  `npm run docs:pdf:check`, exact
-  `RELEASE_TAG=v2.0.0-beta.12.1 npm run release:check`, and `git diff --check` passed. The official
-  Python validator required a temporary, isolated `PyYAML` dependency; no project or system Python
-  files were changed. The bundled gateway cachebuster is `0.1.0+codex.20260827132414`.
-
-## Task-local dependency provenance compatibility
-
-- Recovery still requires a clean local Task branch, no Step in progress, no lease or transaction,
-  exact runtime/declared/locked/installed/current/base version alignment, and one unregistered HEAD
-  that changes exactly `package.json` and `package-lock.json`.
-- The false full-file equality check against the Milestone base was removed. Candidate parent and
-  HEAD are instead compared after removing only `codex-workflow-v2` dependency entries. Previously
-  committed Task-local manifest/lock fields therefore survive unchanged.
-- A replay with a Task-local processing script is accepted and retains its recorded product commit.
-  A script added by the dependency candidate itself is rejected as payload drift; an extra product
-  file and stale base version are also rejected.
-- The exact Signal T04 revision-26 fixture still proves that only a verified historical Step Review
-  can retain its completion commit across corrective replan. Pending review is never trusted, and a
-  corrupt strict-review hash chain is rejected.
-
-## Human-confirmed beta.11 stop compatibility
-
-- The route is available only for one historical shape under the unchanged Plan: exactly two
-  ordinary remediation events, one corrective third event, one matching attempt-3 `continue-fix`,
-  and one matching attempt-4 `stop-escalate`.
-- `task stop-override-prepare` is read-only. It binds Task revision, Step, both decisions, all three
-  remediation events, Plan hash, Git HEAD, package version, human actor, and reason to an `SOO-*`
-  code. `task stop-override-apply` accepts only the same binding in a later explicit turn.
-- Apply appends `stop-escalate-overrides.jsonl`; it does not edit the Task or delete/rewrite the
-  original corrective decision. Exact replay is idempotent.
-- After apply, fresh `next` returns `task run` for the same Step and the fourth attempt actually
-  reaches `in_progress`; subsequent strict review remains mandatory.
-- `split-required`, a stale Task revision/confirmation, conflicting duplicate, active boundary,
-  or tampered hash chain fails closed. Delegated approval is not part of this gate.
-
-## Existing lifecycle regressions retained
-
-- A guarded Task remains in the same Task/Step and can converge after five consecutive failed
-  review cycles. Attempts 1-2 are ordinary; attempts 3+ are corrective diagnostics, not limits.
-- Evidence-bound `route=fix` and `route=replan`, Plan-integrity recovery, corrective yield/replan,
-  observer byte-purity, C1 credential safety, Milestone dependency authority, atomic transactions,
-  and structural-replacement shutdown all remain green.
-- `split-required` remains terminal. The new compatibility route does not implement P04-B, rewire
-  Milestone topology, adopt completed Steps, or override a semantic stop outside the exact beta.11
-  attempt-four policy shape.
+  `npm run docs:pdf:check`, exact `RELEASE_TAG=v2.0.0-beta.12.3 npm run release:check`, and
+  `git diff --check` passed. The bundled gateway cachebuster is
+  `0.1.0+codex.20260827231109`.
+
+## beta.12.3 chained compatibility transition
+
+- beta.12.2 handled one direct Knowledge-only Plan rebind after an already applied beta.11
+  attempt-four stop override. It did not handle the second normal update/context-refresh cycle
+  created while installing beta.12.2 into Signal. That limitation caused the next blocker.
+- Core now accepts an arbitrary contiguous append-only chain from the override-bound Plan to the
+  current Plan only when every adjacent Plan differs solely by Knowledge Map binding and every
+  adjacent Plan Risk Audit is an exact mechanical rebound. Rebind endpoints, delegated authority,
+  active grants, and event chronology must align at every hop.
+- Git HEAD may advance across that chain only through registered dependency-provenance recovery
+  records. Every intervening commit must be a single-parent commit in the exact ancestor chain,
+  must be listed in Workflow system commits, must have exactly one matching Task recovery record,
+  and may change only `package.json` and `package-lock.json` for `codex-workflow-v2`.
+- Fresh `next` returns `task run` with validated stop-override context-rebind evidence only after
+  all of those checks pass. A lost writer credential still routes through the existing exact
+  claimant `task writer-credential-replace` recovery. The fourth and later attempts remain
+  corrective and use the normal strict-review cycle.
+- The route is append-only: it rewrites no stop, override, Plan, audit, authorization, dependency,
+  or recovery evidence. Semantic Plan drift, missing or forked history, product-file changes,
+  mismatched recovery metadata, stale delegation, malformed chronology, or sidecar corruption
+  fails closed and routes to diagnostics.
+
+## Exact Signal compatibility proof
+
+- A read-only invocation of the final built beta.12.3 validator inspected the current Workflow
+  state for Signal Task `TASK-01M0WXJAD4GZGVNRJ284ND95C6`, failed Step
+  `STEP-001-PROCESSING-MIGRATIONS`, and repository
+  `/Users/home-pc/htdocs/projects/signal_v4`.
+- The validator accepted Task revision 21, the applied stop override
+  `SOO-01M127VPRC5M5F3E3K7PS4MFJY`, three Knowledge rebinds in total, the two rebinds after the
+  stop boundary, and two registered dependency-provenance recovery records. The current Plan hash
+  was `8ab0b643cbdcb045776ede231262fdaf8bd0968c2c5fe8967142bfcb8171ae79` and the stable semantic
+  Plan hash was `b99a34ec86ad6340c1abd1b5e78e10c7996aa774ef58eeb9dacbcea72fd2698f`.
+- This proves that the exact state which beta.12.2 rejected is accepted by beta.12.3 without
+  changing Signal. It does not prove future product implementation or review success.
 
 ## Packaged and transcript evidence
 
-- Downstream smoke validated package resolution and the packaged beta.12.1 handshake in a clean
-  disposable installation.
-- A trusted harness then invoked the final built CLI sequentially for handshake, doctor, `status`,
-  and fresh `next` against this unregistered source repository. The observations remained read-only.
-- `node scripts/validate-lifecycle-transcript.mjs` accepted all `8/8` post-provenance events with no
-  failed invocation, mutation, or missing terminal result. The log SHA-256 is
-  `3a12f6e604bef2fe5335c6fc244b52690b06925fb50b8fd8a20acefb672ca46d`; the temporary log remains
+- Downstream smoke validated exact package resolution and the packaged beta.12.3 handshake in a
+  clean disposable installation.
+- A temporary trusted-harness transcript recorded the final built `gateway handshake` invocation
+  and its successful beta.12.3 result. `node scripts/validate-lifecycle-transcript.mjs` accepted
+  both post-provenance events. The log SHA-256 is
+  `7d65fd9fc6301205094284c1fd4236665dff1876d11e01bbc63e35e3a4e3c34b`; the temporary log remains
   outside the repository.
 
-This transcript proves release-time invocation/result discipline for the final CLI. It does not
-claim a second product Milestone replay or a lifecycle mutation. The two compatibility mechanisms
-are covered by deterministic repository/sidecar integration tests above.
+The transcript proves release-time invocation/result discipline for the final CLI. It does not
+claim a product Milestone replay or lifecycle mutation. Compatibility is covered by the exact
+Signal read-only proof and deterministic integration tests above.
 
-## beta.12.1 PDF release documentation evidence
+## beta.12.3 PDF release documentation evidence
 
 - Three tracked Russian PDFs were deterministically regenerated from reviewable Markdown sources
-  under `docs/pdf/sources/`; `npm run docs:pdf:check` reported an empty stale set.
-- All 25 pages were rendered and visually inspected: architecture is 7 pages, the delegated
+  under `docs/pdf/sources`; `npm run docs:pdf:check` reported an empty stale set.
+- All 25 final pages were rendered and visually inspected: architecture is 7 pages, the delegated
   chat-only guide is 8 pages, and the technical reference is 10 pages. No blank, clipped,
-  overlapping, or orphaned page was found.
-- Visible titles, headers, package commands, and release gates identify beta.12.1. The content
-  distinguishes general continuable remediation from the narrow Human-confirmed beta.11 stop
-  override and documents Task-local dependency preservation without weakening candidate checks.
-
-## Not claimed
-
-- Validation itself performs no npm publication, Git tag, push, Signal Workflow mutation, or local
-  plugin reinstall. Tagging and remote push are separate actions after the exact candidate gates.
-- Structural replacement remains intentionally disabled; beta.12.1 does not claim P04-B
-  materialization or completed-Step adoption.
-- A real project must install the published exact beta.12.1 package, update/reinstall the bundled
-  gateway, and follow fresh project-local `handshake -> doctor -> status -> next` navigation.
+  overlapping, or orphaned final page was found.
+- Visible titles, headers, package commands, and release gates identify beta.12.3. The documents
+  distinguish a direct rebind from the new chained compatibility route and state its fail-closed
+  dependency-provenance boundary.
+
+## Existing boundaries and non-claims
+
+- The generic stale `continue-fix` recovery predicate is unchanged. The compatibility route does
+  not relax semantic stop reversal or authorize arbitrary Git history.
+- Structural replacement remains intentionally disabled. beta.12.3 does not implement P04-B,
+  topology rewiring, completed-Step adoption, or a wider delegation surface.
+- Validation performed no Signal mutation, npm publication, Git tag, remote push, or local plugin
+  reinstall. Tagging and push are separate release actions after these gates.
+- A consumer must install the published exact beta.12.3 package, update/reinstall the bundled
+  gateway, and use fresh project-local `handshake -> doctor -> status -> next` navigation.

package/package.json

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

package/plugins/codex-workflow-gateway/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "codex-workflow-gateway",
-  "version": "0.1.0+codex.20260827132414",
+  "version": "0.1.0+codex.20260827231109",
   "description": "Thin personal Codex gateway for exact project-local Codex Workflow V2 packages and codebase-memory-mcp.",
   "author": {
     "name": "Codex Workflow Maintainers"

package/plugins/codex-workflow-gateway/references/protocol.md

@@ -1,6 +1,6 @@
 # Gateway Protocol V2
 
-## beta.12.1 compatibility transitions and continuable remediation
+## beta.12.3 compatibility transitions and continuable remediation
 
 - When fresh `next` advertises `task plan-integrity-recover`, consume its exact Task revision,
   Step, actor, and writer-token contract. This route is valid only for the Core-derived
@@ -20,6 +20,13 @@
   shape. `task stop-override-apply` requires the same Task revision, Step, actor, reason, Plan, HEAD,
   evidence binding, and returned `SOO-*` code in a later user turn. It appends evidence without
   deleting `stop-escalate`; it never applies to `split-required`.
+- After an applied stop override, one or more ordinary delegated `task context-refresh` transitions
+  may rebind the Plan before attempt four. Fresh `next` returns `task run` only when Core validates
+  the complete contiguous Plan/rebind/audit chain, mechanical equivalence at every hop, shared
+  delegated authority, and append-only chronology. HEAD may differ from the override only when every
+  intervening commit is an exact registered dependency-provenance recovery changing only
+  `package.json` and `package-lock.json`. If C1 remains claimed but the lease was lost at the Human
+  boundary, use only the simultaneously advertised `task writer-credential-replace` action.
 - `milestone progress --id <MS-ID>` is a read-only projection and the sole source for Coordinator
   progress tables. It preserves cancelled/replacement Tasks as distinct membership rows.
 - `scripts/chat-registry.mjs` atomically allocates project-monotonic `#NNN`, builds all six title
@@ -57,6 +64,8 @@ Current capability set:
 - `bounded-dependency-provenance-recovery-v1`
 - `task-local-dependency-provenance-recovery-v1`
 - `legacy-stop-escalate-override-v1`
+- `stop-override-context-rebind-v1`
+- `stop-override-context-rebind-chain-v1`
 - `retained-reviewed-history-recovery-v1`
 - `milestone-progress-projection-v1`
 - `strict-reviewer-v1`

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

@@ -109,7 +109,7 @@ command shape or consuming a replacement Discovery. Never rebind, refresh, repla
 resume, cancel, or manually replace the historical Task. Continue only after a later P04-B/P05
 package explicitly advertises a topology-preserving replacement capability.
 
-When beta.12.1 `next` advertises `task stop-override-prepare`, the route is limited to the exact
+When beta.12.3 `next` advertises `task stop-override-prepare`, the route is limited to the exact
 beta.11 attempt-four policy stop: two ordinary failures, one corrective failure, a matching
 attempt-3 `continue-fix`, and a matching attempt-4 `stop-escalate` under the unchanged Plan. Invoke
 prepare with the exact Task/Step/revision, explicit human actor, and user-supplied reason. It is
@@ -120,6 +120,17 @@ evidence changes. Successful apply preserves the original stop, appends
 `stop-escalate-overrides.jsonl`, and requires fresh sequential `status` then `next` before attempt
 four runs through the normal strict-review cycle.
 
+After an applied override, one or more ordinary delegated `task context-refresh` transitions may
+change only the Plan's canonical Knowledge Map binding. A package update may also advance HEAD, but
+only through the exact `update dependency-provenance-recover` route advertised by fresh `next`.
+Continue only when fresh `next` advertises `task run` with
+`stopOverrideContextRebind.state=validated` for the exact override and stop decision. Core verifies
+the complete source-to-current Plan/audit/rebind chain and, when HEAD changed, every intervening Git
+commit as registered dependency-only provenance. If C1 remains claimed but the lease was lost at
+the Human boundary, first use the simultaneously advertised `task writer-credential-replace`
+action for the exact claimant. A doctor route, semantic Plan drift, an unregistered or non-dependency
+commit, missing delegated authority, a broken chain, or damaged chronology is a hard stop.
+
 When `next` returns `milestone initial-assembly`, execution is unavailable. Follow only the
 advertised `linked-task-assembly.commands` (`discovery start` and `discovery materialize`) until all
 intended linked Tasks exist. The closing `milestone plan-set` option appears only after at least one