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

package/docs/autonomy-guardrails.md

@@ -92,10 +92,23 @@ 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.2 also handles the case where the accepted third attempt changed
+approved Project Knowledge: the already-applied override may be followed by the ordinary delegated
+`task context-refresh` 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; the source and rebound Plans
+differ only in their canonical Knowledge Map binding line; one direct Knowledge rebind and one
+mechanical Plan Risk Audit rebound connect those Plans; the refreshed approval and execution
+authorization share the valid delegated authority; and the override plus refreshed authorization
+bind the same Git HEAD. The proof is derived from existing append-only evidence, so this route does
+not create a second recovery journal. Missing evidence, an extra rebind, semantic Plan change,
+different HEAD, or damaged chronology routes to `doctor` rather than weakening the generic
+two-attempt corrective recovery gate.
 
 ### First-failure Plan-integrity recovery
 

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.2
 subtitle: Источники истины, lifecycle, роли, delegation, зависимости Tasks и границы доверия
 part: Часть 1 из 3 | Архитектура
 document_version: 2.0
 date: 27 августа 2026
-subject: Архитектура и границы Codex Workflow V2 beta.12.1
+subject: Архитектура и границы Codex Workflow V2 beta.12.2
 ---
 
 # 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.2 гарантирует
 
 - 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.2 не гарантирует
 
 - правильность продуктовой идеи или автоматически выбранного provider Task;
 - semantic sufficiency Plan, если точные факты нельзя доказать поддерживаемым analyzer;
@@ -218,13 +218,20 @@ 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.2 сохраняет этот override при одном последующем delegated `task context-refresh`, если Plan
+изменился только в canonical Knowledge Map binding. Core требует прямой rebind, механически
+эквивалентный Plan Risk Audit, общую delegated authority, корректную chronology и тот же Git HEAD.
+При утрате claimed writer lease используется только одновременно рекламируемый
+`task writer-credential-replace`; semantic Plan drift, второй rebind или повреждённая evidence chain
+возвращают `doctor`.
+
 Dependency-provenance recovery beta.12.1 также сохраняет ранее закоммиченные Task-local поля
 manifest/lock, даже если base их не содержит. Candidate остаётся dependency-only: после удаления
 только Workflow dependency parent и HEAD обязаны совпасть по всем product-owned полям.
@@ -238,7 +245,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.2 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.2 путь от нового Discovery до принятого Milestone без ручного CLI
 part: Часть 2 из 3 | Практика
 document_version: 2.0
 date: 27 августа 2026
-subject: Практическое руководство по delegated Discovery и Milestone в Workflow V2 beta.12.1
+subject: Практическое руководство по delegated Discovery и Milestone в Workflow V2 beta.12.2
 ---
 
-# 1. Рабочая модель beta.12.1
+# 1. Рабочая модель beta.12.2
 
 Пользователь работает в одном 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.2 как точную 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.2 должен сообщать `packageVersion=2.0.0-beta.12.2`, `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.2 в delegated режиме.
 Repository: <ABSOLUTE-REPOSITORY-ROOT>.
 Milestone ID: AUTO.
 Delegate actor: agent:milestone-coordinator.
@@ -305,6 +305,13 @@ 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`, выполните
+его как обычный atomic refresh и снова запросите `status -> next`. Продолжайте attempt 4 только при
+`stopOverrideContextRebind.state=validated`. При одновременном
+`writerCredentialRecovery.action=task writer-credential-replace` сначала восстановите credential
+точного claimant-актора. `doctor`, semantic Plan change, второй rebind или другой HEAD означают stop,
+а не ручной обход.
+
 # 12. Milestone final acceptance
 
 После merge всех required Tasks Coordinator проверяет clean base HEAD и выполняет рекламируемую
@@ -322,7 +329,7 @@ Task/project DGR. `dependencyBinding` для standalone handoff равен null.
 
 # 14. Итоговый checklist пользователя
 
-- beta.12.1 exact package и новый bundled gateway установлены;
+- beta.12.2 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.2
 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
+subject: Технический контракт Codex Workflow V2 beta.12.2
 ---
 
 # 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.2 | Значение |
 |---|---|
-| npm package | `codex-workflow-v2@2.0.0-beta.12.1` |
+| npm package | `codex-workflow-v2@2.0.0-beta.12.2` |
 | 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.2 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, context-only stop rebind, 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.2 compatibility transitions
 
 `update dependency-provenance-recover` больше не требует полного равенства Task manifest/lock с base.
 Base остаётся version authority, а parent/HEAD candidate сравниваются без единственных Workflow
@@ -329,6 +329,13 @@ 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` может сделать исходный stop/override Plan hash
+историческим. `task run` снова доступен только если Core доказывает context-only direct rebind:
+семантическое содержимое Plan совпадает, Plan Risk Audit rebound механический, refresh approval и
+execution authorization имеют одну действующую authority, chronology монотонна, а authorization и
+override связывают один HEAD. Projection содержит `stopOverrideContextRebind.state=validated`.
+Утерянный claimed lease восстанавливается только рекламируемым `task writer-credential-replace`.
+
 # 14. P04-A structural replacement boundary
 
 Command shape `task replacement-materialize` retained только для compatibility diagnostics. Любая попытка
@@ -386,7 +393,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.2
 
 | Область | Actions |
 |---|---|
@@ -413,7 +420,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.2 tag release repository выполняет:
 
 1. `npm ci`;
 2. `npm run validate`;
@@ -423,6 +430,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.2, 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,9 @@ 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 one later context-only Plan rebind with
+  exact mechanical audit, delegation, chronology, and same-HEAD evidence; 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,23 @@ 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.2 дополнительно покрывает случай, когда третья
+попытка изменила Project Knowledge: перед `task run` допустим обычный
+delegated `task context-refresh`. После него Workflow продолжит attempt 4 только при
+доказанном прямом rebind: source и current Plan отличаются исключительно canonical Knowledge Map
+binding, Plan Risk Audit rebound механический, refresh approval/authorization имеют одну валидную
+delegated authority, а override и новая execution authorization связывают тот же Git HEAD. Новая
+recovery-запись для этого не создаётся — используется уже существующая append-only цепочка.
+Если C1 остаётся claimed, но writer lease после Human boundary отсутствует, `next` вместе с
+`task run` рекламирует `task writer-credential-replace`; сначала восстановите credential exact
+claimant-актора, затем запускайте Step.
+
+Этот путь не работает для `split-required`, другого attempt ordinal, семантически изменённого
+Plan, другого HEAD, отсутствующего attempt-3 continue, более чем одного rebind, повреждённой
+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,102 @@
-# V2 beta.12.1 Validation Report
+# V2 beta.12.2 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.2` was validated across 2026-08-27/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,
+- The final `npm run validate` passed typecheck and `326/326` sequential tests with no failures,
+  skips, cancellations, or todos in 1,273,564.586583 ms.
+- The full suite includes the beta.12.2 attempt-four/context-rebind replay, the unchanged-Plan
+  stop-override suite, 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 the beta.12.2 dry-run tarball with 270 files, package size 972.1 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.
+- `npm run smoke:downstream` packed and installed
+  `codex-workflow-v2-2.0.0-beta.12.2.tgz` 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.2 npm run release:check`, and
+  `git diff --check` passed. The official Python validators used a temporary isolated `PyYAML`
+  dependency; no project or system Python files were changed. The bundled gateway cachebuster is
+  `0.1.0+codex.20260827205000`.
+
+## beta.12.2 stop-override/context-rebind compatibility
+
+- The reproduced incompatibility is narrow: an exact beta.11 attempt-four stop was already
+  Human-overridden, then the successful third attempt changed approved Project Knowledge and the
+  ordinary delegated `task context-refresh` rebound the Plan to the new Knowledge Map. The original
+  override remained valid evidence but its Plan hash no longer equalled the current Plan hash.
+- Core now derives continuation only from existing append-only evidence. It requires exactly three
+  remediation events (`ordinary`, `ordinary`, `corrective`), the matching attempt-3 `continue-fix`,
+  matching attempt-4 `stop-escalate`, one applied stop override, one direct Knowledge rebind, a
+  mechanically equivalent Plan Risk Audit rebound, shared valid delegated authority, monotonic
+  chronology, and the same Git HEAD in the override and refreshed execution authorization.
+- Fresh `next` returns `task run` with `stopOverrideContextRebind.state=validated` only when every
+  binding above remains current. The fourth attempt remains mode `corrective` and passes through the
+  normal checks and strict-review cycle.
+- If C1 remains claimed but the writer lease was lost at the Human boundary, the same projection
+  exposes the existing `task writer-credential-replace` recovery for the exact claimant. No token is
+  persisted or reconstructed from evidence.
+- The route creates no new recovery journal and does not rewrite the stop, override, Plan, audit, or
+  authorization history. Semantic Plan drift, a second rebind, different HEAD, wrong authority,
+  malformed chronology, missing/duplicate override evidence, or sidecar corruption fails closed and
+  routes to `doctor`.
+
+## Existing compatibility and lifecycle regressions retained
+
+- The unchanged-Plan Human-confirmed beta.11 stop override remains append-only, idempotent, and
+  unavailable for `split-required`, stale confirmation bindings, or tampered evidence.
+- The general guarded-remediation model still has no attempt-count hard stop. Attempts 1-2 are
+  ordinary; attempts 3+ are corrective and remain executable under fresh review authority. The
+  beta.12.2 exception does not weaken the generic stale `continue-fix` recovery predicate.
+- Task-local dependency-provenance recovery still preserves product fields recorded before the
+  dependency-only candidate while rejecting candidate payload drift. The exact Signal T04
+  revision-26 replay retains only passed, attested historical Step commits and rejects pending or
+  corrupt review chains.
+- P01-A mechanical feasibility, P04-A Milestone dependency authority, atomic initial Plan and
+  project transactions, external-sealed review, corrective yield/replan, and observer byte-purity
+  remain green.
+- Structural replacement remains intentionally disabled. A `split-required` posture still returns
+  `STRUCTURAL_REPLACEMENT_REQUIRED` with no Task/Discovery/Milestone/Knowledge/lock mutation.
 
 ## 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.
+- Downstream smoke validated exact package resolution and the packaged beta.12.2 handshake in a
+  clean disposable installation.
+- A temporary trusted harness invoked the final built CLI sequentially for `gateway handshake`,
+  `doctor`, `status`, and fresh `next` against this unregistered source repository with an isolated
+  Workflow state root. All observations completed successfully and 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
+  `954a1c97f455ae3c8e02211b6fb63982b30cbfa1c40d92ce712f4a208d0e3a8f`; 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 a lifecycle mutation. The compatibility transition is covered
+by deterministic repository/sidecar integration tests above.
 
-## beta.12.1 PDF release documentation evidence
+## beta.12.2 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.
+  overlapping, or orphaned final page was found. Visual QA removed one redundant two-line spill
+  that had created an otherwise empty eleventh technical-reference page.
+- Visible titles, headers, package commands, and release gates identify beta.12.2. The documents
+  distinguish the unchanged-Plan beta.12.1 override from beta.12.2 context-only rebind continuation,
+  exact claimant credential recovery, and all fail-closed boundaries.
 
 ## 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
+- Validation itself performs no npm publication, Git tag, push, Signal project mutation, or local
+  plugin reinstall. Tagging and remote push are separate release actions after these exact gates.
+- beta.12.2 does not implement P04-B, topology rewiring, completed-Step adoption, a general semantic
+  stop reversal, multi-rebind recovery, or a wider delegation surface.
+- A real project must install the published exact beta.12.2 package, update/reinstall the bundled
   gateway, and follow 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.2",
   "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.20260827205000",
   "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.2 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,11 @@
   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 ordinary delegated `task context-refresh` may rebind the Plan
+  before attempt four. Fresh `next` returns `task run` only when Core validates an exact direct
+  Knowledge rebind, a mechanically equivalent Plan Risk Audit rebound, shared delegated authority,
+  append-only chronology, and the same Git HEAD. 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 +62,7 @@ Current capability set:
 - `bounded-dependency-provenance-recovery-v1`
 - `task-local-dependency-provenance-recovery-v1`
 - `legacy-stop-escalate-override-v1`
+- `stop-override-context-rebind-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.2 `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,13 @@ 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 ordinary delegated `task context-refresh` may change only the Plan's
+canonical Knowledge Map binding. Continue only when fresh `next` advertises `task run` with
+`stopOverrideContextRebind.state=validated` for the exact override and stop decision. 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,
+second rebind, different HEAD, missing delegated authority, 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