codex-workflow-v2 2.0.0-beta.12.6 → 2.0.0-beta.12.7

package/docs/autonomy-guardrails.md

@@ -152,6 +152,13 @@ evidence, supersedes execution authority, yields C1, and routes the same Task to
 The route grants no authority to change Task objective, requirements, acceptance, or Milestone
 topology.
 
+The beta.12.7 compatibility repair for an accidental post-invalidation Knowledge rebind is similarly
+non-semantic. It may restore `needs_fix` and preserve an exact dirty-worktree binding, but it cannot
+approve a replacement Plan, infer new requirements, or treat preserved bytes as completed evidence.
+After any required Knowledge refresh, the full unfinished remainder is planned again. Carryover into
+execution is valid only when one newly authorized Step owns every bound path and the current
+HEAD/path/content hashes still match; checks and strict review retain their ordinary authority.
+
 Docker permission diagnostics are classified before consuming retry authority. Sandbox `EPERM` or
 permission denial gets one exact escalated rerun of the health probe/Plan check. It is not an infra
 failure and cannot authorize a Docker Desktop restart or image substitution. Only an escalated

package/docs/development-flow.md

@@ -113,6 +113,15 @@ candidate parent, binds the active proof dirty set by content hash, and register
 dependency commit. Product bytes and Step state remain unchanged; fresh `next` must then advertise
 the ordinary `task downstream-proof-recover`. This is not a general dirty-update permission.
 
+If beta.12.6 already performed that recovery but a subsequent Knowledge approval mechanically
+rebound its rejected Plan, use only the beta.12.7 stranded-replan bridge advertised by fresh `next`.
+The source preflight runs before dependency transport and binds the exact beta.12.6 Task revision,
+HEAD, dirty paths, and content hash. After dependency-only base/Task commits and provenance recovery,
+`task downstream-proof-replan-recover` restores `needs_fix`. Reconcile/approve stale Project Knowledge,
+then replace the full unfinished Plan. The preserved dirty set may enter execution only through one
+new Step whose `allowedWrites` owns every path and whose fresh `next` reports validated carryover.
+Completing that Step still requires its checks, Core-owned commit, and any guarded strict review.
+
 A sandboxed Docker `EPERM`, `operation not permitted`, or `permission denied` result is not a failed
 daemon check. Re-run the exact probe/check once with sandbox escalation without consuming a retry.
 Restart Docker Desktop only with separate authorization after the escalated call reaches Docker and

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

@@ -1,10 +1,10 @@
 ---
-title: Codex Workflow V2: архитектура beta.12.6
+title: Codex Workflow V2: архитектура beta.12.7
 subtitle: Источники истины, lifecycle, роли, delegation, зависимости Tasks и границы доверия
 part: Часть 1 из 3 | Архитектура
 document_version: 2.0
 date: 29 августа 2026
-subject: Архитектура и границы Codex Workflow V2 beta.12.6
+subject: Архитектура и границы Codex Workflow V2 beta.12.7
 ---
 
 # 1. Назначение и граница системы
@@ -18,7 +18,7 @@ Codex Workflow V2 - локальный state machine поверх Codex App, Git
 Система рассчитана на одного пользователя и одну машину. Она не предоставляет distributed locking,
 криптографическую идентификацию actor string или безопасную синхронизацию state между компьютерами.
 
-## 1.1. Что beta.12.6 гарантирует
+## 1.1. Что beta.12.7 гарантирует
 
 - exact project-local npm package и совместимый handshake до lifecycle действий;
 - Discovery до materialization Task или Milestone;
@@ -31,8 +31,10 @@ Codex Workflow V2 - локальный state machine поверх Codex App, Git
 - journaled recovery для составных переходов и fail-closed поведение при drift/corruption.
 - bounded recovery, когда downstream proof требует изменить уже завершённый predecessor Step:
   worktree и HEAD сохраняются, stale completion authority снимается, та же Task возвращается в planning.
+- bounded compatibility recovery, если beta.12.6 после этого recovery ошибочно rebind-нула отвергнутый
+  Plan: exact dirty bytes сохраняются до нового consolidated Step, а Knowledge refresh не отменяет `plan-set`.
 
-## 1.2. Что beta.12.6 не гарантирует
+## 1.2. Что beta.12.7 не гарантирует
 
 - правильность продуктовой идеи или автоматически выбранного provider Task;
 - semantic sufficiency Plan, если точные факты нельзя доказать поддерживаемым analyzer;
@@ -263,6 +265,17 @@ leases/transactions, predecessor ownership и content hash dirty set. Перех
 dependency commit, не меняет product bytes/Step и делает обычный `task downstream-proof-recover`
 достижимым до manifest-induced Knowledge refresh. Это не общее разрешение dirty update.
 
+beta.12.7 закрывает следующий доказанный Signal case: beta.12.6 уже выполнила downstream-proof
+invalidation, но последующее Project Knowledge approval механически вернуло старый двух-Step Plan в
+`awaiting_execution_authorization`. Read-only `update downstream-proof-replan-update-preflight`
+сначала связывает exact beta.12.6 revision, HEAD, шесть dirty paths и content hash. После двух
+dependency-only commits `update downstream-proof-replan-dependency-preflight/recover` регистрирует
+только новый Workflow HEAD. `task downstream-proof-replan-recover` затем атомарно возвращает ту же
+Task в `needs_fix`; stale Knowledge можно reconciliate/approve, но fresh `next` всё равно требует
+новый `task plan-set`. Новый Plan может передать сохранённые bytes только одному Step, который владеет
+всем dirty set. `task run` принимает carryover лишь при exact HEAD/path/hash match, после чего Step
+проходит обычные checks, Core-owned commit и strict review.
+
 Docker socket `EPERM` в sandbox не является доказательством сломанного daemon. Gateway один раз
 повторяет exact health probe или Plan check с sandbox escalation без расходования remediation attempt.
 Restart Docker Desktop требует отдельного разрешения и допустим только после escalated daemon failure.
@@ -272,7 +285,7 @@ Restart Docker Desktop требует отдельного разрешения
 # 10. Operational checklist
 
 - exact package version установлен, bundled gateway соответствует release и переустановлен;
-- handshake подтверждает protocol 2, state schema 2 и beta.12.6 capabilities;
+- handshake подтверждает protocol 2, state schema 2 и beta.12.7 capabilities;
 - каждый mutation следует свежему `status -> next` и exact option contract;
 - Docker permission failure сначала классифицируется как sandbox boundary, а не как infra retry;
 - semantic unknowns и human gates не маскируются delegation;

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.6 путь от нового Discovery до принятого Milestone без ручного CLI
+subtitle: Актуальный beta.12.7 путь от нового Discovery до принятого Milestone без ручного CLI
 part: Часть 2 из 3 | Практика
 document_version: 2.0
 date: 29 августа 2026
-subject: Практическое руководство по delegated Discovery и Milestone в Workflow V2 beta.12.6
+subject: Практическое руководство по delegated Discovery и Milestone в Workflow V2 beta.12.7
 ---
 
-# 1. Рабочая модель beta.12.6
+# 1. Рабочая модель beta.12.7
 
 Пользователь работает в одном 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.6 как точную devDependency после публикации release.
+2. Установите beta.12.7 как точную 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.6 должен сообщать `packageVersion=2.0.0-beta.12.6`, `protocolVersion=2`,
+Handshake beta.12.7 должен сообщать `packageVersion=2.0.0-beta.12.7`, `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.6 в delegated режиме.
+Проведи новый Milestone через Codex Workflow V2 beta.12.7 в delegated режиме.
 Repository: <ABSOLUTE-REPOSITORY-ROOT>.
 Milestone ID: AUTO.
 Delegate actor: agent:milestone-coordinator.
@@ -299,6 +299,7 @@ Task chat записывает его только при совпадении p
 | Finding `route=replan` с exact Plan conflict | `task plan-set`, меняются только implementation Steps |
 | `split-required` | Stop: `STRUCTURAL_REPLACEMENT_REQUIRED`, никаких replacement writes |
 | Старая версия + active downstream proof блокируют update | Только beta.12.6 exact dependency commits и advertised `update downstream-proof-dependency-recover` |
+| После downstream recovery beta.12.6 вернула отвергнутый Plan через Knowledge rebind | Только beta.12.7 replan update bridge, затем recovery и новый consolidated Plan той же Task |
 | Exact beta.11 attempt-four `stop-escalate` | Только advertised prepare, затем отдельный Human-confirmed apply; исходный stop сохраняется |
 | Любой другой explicit `stop-escalate` | Terminal user attention |
 | Stale dependency binding | Новый handoff/claim только по fresh `next` |
@@ -318,6 +319,15 @@ beta.12.6 и требуйте от fresh `next` `update downstream-proof-depende
 binding dirty set. Recover регистрирует только dependency HEAD; следующий fresh `next` должен вернуть
 обычный `task downstream-proof-recover`. Любой иной diff/history/dirty path/lease означает stop.
 
+Для exact stranded shape после уже выполненного beta.12.6 recovery сначала запустите новой версией
+read-only `update downstream-proof-replan-update-preflight`. Продолжайте только при `eligible=true`,
+source `2.0.0-beta.12.6`, exact revision/HEAD, ожидаемых dirty paths/hash и пустых blockers. Затем
+перенесите beta.12.7 двумя dependency-only commits на base и Task branch, установите пакет и следуйте
+fresh `next` через `update downstream-proof-replan-dependency-recover` и
+`task downstream-proof-replan-recover`. После обязательного Knowledge reconcile/approve fresh `next`
+должен остаться на `task plan-set`, а не resurrect старый Plan. Новый Step обязан один владеть всем
+сохранённым dirty set; `task run` допустим только при `downstreamProofCarryover.state=validated`.
+
 Ошибка Docker socket/CLI `EPERM`, `operation not permitted` или `permission denied` в sandbox не считается
 падением daemon и не расходует retry. Повторите exact read-only probe или Plan check один раз с sandbox
 escalation. Не перезапускайте Docker Desktop и не меняйте image без отдельного разрешения и подтверждённого
@@ -353,7 +363,7 @@ Task/project DGR. `dependencyBinding` для standalone handoff равен null.
 
 # 14. Итоговый checklist пользователя
 
-- beta.12.6 exact package и новый bundled gateway установлены;
+- beta.12.7 exact package и новый bundled gateway установлены;
 - новый Coordinator chat не является fork старого Milestone;
 - bootstrap DGR, если нужен, выдан отдельным exact human confirmation;
 - Discovery не materialized при blocking unknowns;
@@ -365,5 +375,6 @@ Task/project DGR. `dependencyBinding` для standalone handoff равен null.
 - beta.11 stop override, если рекламировался, прошёл отдельные prepare и user-confirmed apply без journal rewrite;
 - downstream predecessor recovery, если рекламировался, сохранил worktree и завершился новым Plan authority;
 - active-proof package bridge, если понадобился, зарегистрировал только exact dependency HEAD перед recovery;
+- stranded-replan bridge, если понадобился, завершился новым Plan и полным Step checks/review, а не только сменой navigation;
 - split-required остановился без replacement mutations;
 - Milestone validation и final acceptance связаны с текущим clean base HEAD.

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

@@ -1,10 +1,10 @@
 ---
-title: Codex Workflow V2: технический справочник beta.12.6
+title: Codex Workflow V2: технический справочник beta.12.7
 subtitle: Protocol 2, state schema 2, transactions, credentials, dependency authority, review и recovery
 part: Часть 3 из 3 | Technical reference
 document_version: 2.0
 date: 29 августа 2026
-subject: Технический контракт Codex Workflow V2 beta.12.6
+subject: Технический контракт Codex Workflow V2 beta.12.7
 ---
 
 # 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.6 | Значение |
+| Параметр beta.12.7 | Значение |
 |---|---|
-| npm package | `codex-workflow-v2@2.0.0-beta.12.6` |
+| npm package | `codex-workflow-v2@2.0.0-beta.12.7` |
 | 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.6 capabilities:
+Ключевые beta.12.7 capabilities:
 
 | Группа | Capabilities |
 |---|---|
@@ -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.6 compatibility transitions
+# 13.1. beta.12.7 compatibility transitions
 
 `update dependency-provenance-recover` больше не требует полного равенства Task manifest/lock с base.
 Base остаётся version authority, а parent/HEAD candidate сравниваются без единственных Workflow
@@ -332,6 +332,18 @@ aligned runtime/declared/locked/installed/current/base versions, отсутст
 `dependencyProvenanceRecoveries.activeDownstreamProof`; product work и Step state не меняются.
 Fresh `next` затем приоритетно рекламирует `task downstream-proof-recover` до Knowledge refresh.
 
+`update downstream-proof-replan-update-preflight` — read-only source gate для одного exact
+beta.12.6 stranded shape после predecessor invalidation и ошибочного Knowledge rebind старого Plan.
+Он требует точные source version surfaces, Task revision/status/rebind, preserved HEAD, dirty paths/hash
+и отсутствие lease/transactions. После dependency-only transport
+`update downstream-proof-replan-dependency-preflight/recover` валидирует parent на `HEAD^`, candidate
+на `HEAD` и записывает `dependencyProvenanceRecoveries.downstreamProofReplan` без изменения product
+bytes. `task downstream-proof-replan-recover` атомарно добавляет
+`downstream-proof-replan-recoveries.jsonl`, supersede-ит execution authorization и возвращает Task в
+`needs_fix`. Stale Knowledge refresh разрешён после repair, но не может заменить обязательный
+`task plan-set`. Dirty carryover принимается `task run` только если один replacement Step владеет всем
+set, а HEAD, paths и SHA-256 совпадают с recovery event.
+
 `task stop-override-prepare/apply` обслуживает только exact beta.11 attempt-four policy stop. Prepare
 не пишет state и создаёт binding по Task revision, Step, attempt-3 continue, attempt-4 stop, трём
 remediation events, Plan, HEAD, package, human actor и reason. Apply в отдельном user turn добавляет
@@ -430,12 +442,12 @@ Docker socket/CLI `EPERM`, `operation not permitted` или `permission denied`
 После каждой successful mutation обязателен sequential `status`, затем fresh `next`. Failed status/next
 не разрешает direct mutation. Syntax help read-only и не заменяет navigation authority.
 
-# 18. Public command surface beta.12.6
+# 18. Public command surface beta.12.7
 
 | Область | Actions |
 |---|---|
 | System | `doctor`, `status`, `next`, `gateway handshake`, `locks` |
-| Update | `preflight`, `rescue-preflight`, `dependency-provenance-preflight/recover`, `downstream-proof-dependency-preflight/recover` |
+| Update | `preflight`, `rescue-preflight`, dependency provenance, downstream-proof dependency bridge, downstream-proof replan update/dependency bridge |
 | Project memory | `scan`, `show`, `status`, `approve`, `reconcile` |
 | Delegation | `prepare`, `grant`, `list`, `show`, `revoke` |
 | Graph | `prepare`, `status`, `refresh-request`, `bind`, `fallback` |
@@ -445,7 +457,7 @@ Docker socket/CLI `EPERM`, `operation not permitted` или `permission denied`
 | Task execution | `start`, `run`, `step-complete`, `submit`, `result-set`, `accept`, `sync-base`, `merge`, `merge-confirm` |
 | C1 | `handoff[-prepare/-replace/-show]`, `claim`, `writer-credential-replace`, `handback[-create]` |
 | Review | review/step-review packet, launch, sealed record и record actions |
-| Corrective | decision/recovery, plan-integrity, downstream-proof-recover, remediation-mode, stop-override prepare/apply, yield и corrective-replan actions |
+| Corrective | decision/recovery, plan-integrity, downstream-proof-recover/replan-recover, remediation-mode, stop-override prepare/apply, yield и corrective-replan actions |
 | Replacement | `replacement-materialize` retained, но всегда disabled в P04-A |
 
 Exact options берутся из fresh `next`; command help используется только когда
@@ -454,10 +466,11 @@ Exact options берутся из fresh `next`; command help используе
 # 19. Release и package update gates
 
 Перед package update project-local `update preflight` должен вернуть `safe=true`: clean checkout, нет
-running Step и active/stale writer lease. Исключения — документированный alpha.7 rescue и beta.12.6
-active-downstream-proof dependency bridge; оба fail-closed и не дают общего разрешения dirty update.
+running Step и active/stale writer lease. Исключения — документированный alpha.7 rescue, beta.12.6
+active-downstream-proof bridge и beta.12.7 exact stranded-replan bridge; все они fail-closed и не дают
+общего разрешения dirty update.
 
-Перед beta.12.6 tag release repository выполняет:
+Перед beta.12.7 tag release repository выполняет:
 
 1. `npm ci`;
 2. `npm run validate`;

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.6, the release gate also relies on `npm run release:check` to fail if:
+For beta.12.7, 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,12 @@ For beta.12.6, the release gate also relies on `npm run release:check` to fail i
   aligned base/Task commits while preserving product bytes; or unknown history, unrelated dirty
   scope, content drift within an observation, leases, transactions, and wider candidates do not
   fail closed before provenance registration and ordinary downstream recovery.
+- the exact beta.12.6 post-invalidation Knowledge-rebind shape cannot pass a read-only source gate,
+  transport beta.12.7 through dependency-only commits, register provenance, restore `needs_fix`,
+  survive required Knowledge refresh, and reach a fresh replacement Plan;
+- preserved dirty bytes can execute without one Step owning the complete bound set, or HEAD/path/hash
+  drift is accepted; or the Signal-shaped E2E stops before checks, Core commit, strict Step review,
+  and fresh navigation to Task submission.
 - bundled gateway guidance treats Docker socket `EPERM` as daemon failure, consumes a remediation
   attempt before one exact escalated probe, or recommends restarting Docker Desktop without separate
   authority.

package/docs/updating-existing-project.md

@@ -93,6 +93,30 @@ ownership и history, а новый Plan и review оценивают текущ
 version divergence, branch/Plan/Step mismatch, lease или transaction. В этом случае не правьте
 `systemCommits` или внешний state вручную.
 
+### Исключение beta.12.7 для stranded downstream replan
+
+Это исключение применимо только если beta.12.6 уже записала downstream-proof invalidation, а затем
+Project Knowledge approval ошибочно rebound-нул отвергнутый Plan и вернул Task в
+`awaiting_execution_authorization`. До изменения dependency запустите beta.12.7 source/runtime
+read-only `update downstream-proof-replan-update-preflight --id <TASK-ID>`. Требуются
+`eligible=true`, source version `2.0.0-beta.12.6`, exact Task revision/branch/base/HEAD, неизменные
+dirty paths/content hash и пустые blockers.
+
+Затем тем же двухкоммитным способом обновите active base и Task branch только в `package.json` и
+`package-lock.json`, установите exact beta.12.7 и следуйте fresh `next`. Допустимая цепочка:
+`update downstream-proof-replan-dependency-preflight` ->
+`update downstream-proof-replan-dependency-recover` ->
+`task downstream-proof-replan-recover`. После repair manifest change обычно делает Project Knowledge
+stale: выполните рекламируемые reconcile/approve, но не `task knowledge-rebind` старого Plan. Fresh
+`next` обязан вернуть `task plan-set`.
+
+Новый Plan должен заново классифицировать весь unfinished remainder. Сохранённые dirty bytes не
+становятся completed evidence и не коммитятся административным recovery. Они могут быть приняты
+только одним planned Step, `allowedWrites` которого точно покрывает весь dirty set. Перед `task run`
+fresh `next` обязан показать `downstreamProofCarryover.state=validated`; после run обязательны checks,
+Core-owned Step commit и strict review, если Step guarded. Изменение content/path/HEAD, дополнительная
+Task revision, audit/authorization старого Plan, lease или transaction блокируют исключение.
+
 ### Исключение beta.12.1 для beta.11 attempt-four stop
 
 Если beta.11 записал `stop-escalate` перед четвёртой попыткой только после последовательности

package/docs/validation-report.md

@@ -1,111 +1,110 @@
-# V2 beta.12.6 Validation Report
+# V2 beta.12.7 Validation Report
 
-Release candidate `2.0.0-beta.12.6` was validated on 2026-08-29 (Europe/Moscow) with
+Release candidate `2.0.0-beta.12.7` was validated on 2026-08-29 (Europe/Moscow) with
 Node.js 24.17.0.
 
 ## Automated release evidence
 
-- The first full `npm run validate` passed typecheck and `335/335` sequential tests with no
-  failures, skips, cancellations, or todos in 1,461,147.464875 ms.
-- `npm ci` then completed from the lockfile with 0 reported vulnerabilities. The clean-install
-  `npm run validate` independently passed the same `335/335` tests with no failures, skips,
-  cancellations, or todos in 1,461,906.892 ms.
-- The exact Signal T04/downstream recovery gate passed `8/8`. The targeted dependency-provenance,
-  downstream-proof, CLI-help, and lifecycle-model suite passed `23/23`.
-- The positive beta.12.6 fixture proves the complete compatibility sequence: exact active-base and
-  Task dependency commits, history validation at `HEAD^`, candidate validation at `HEAD`, dirty
-  content binding, dependency registration, fresh navigation to `task downstream-proof-recover`,
-  unchanged product bytes, and valid recorded Task history. Negative cases cover unrelated dirty
-  files, unregistered history, and an active writer lease. Existing Signal T04 tests remain intact.
-- `npm run pack:check` built the exact beta.12.6 package: 274 files, 1.0 MB packed and 4.0 MB
-  unpacked. The first attempt could not write the user npm cache (`EPERM`); the exact retry used an
-  isolated temporary cache and passed without changing global cache ownership.
+- `npm ci` completed from the lockfile with 0 reported vulnerabilities.
+- The final post-fix `npm run validate` passed typecheck and `338/338` sequential tests with no
+  failures, skips, cancellations, or todos in 1,641,977.92675 ms. The same suite also passed after
+  the clean install (`338/338` in 1,661,195.192667 ms) and before it (`338/338` in
+  1,347,257.496667 ms).
+- `npm run test:signal-t03-replan-e2e` independently passed the full Signal-shaped compatibility
+  scenario. The focused dependency-provenance, downstream-proof, and lifecycle-model suite passed
+  `23/23`.
+- The Signal-shaped E2E starts with the exact six-path ownership split and the beta.12.6 accidental
+  post-invalidation Knowledge rebind. It then proves: read-only source eligibility, two
+  dependency-only transport commits, `HEAD^`/`HEAD` provenance validation, bounded dependency
+  registration, atomic replan recovery, required Project Knowledge refresh, mandatory replacement
+  `plan-set`, one-Step dirty carryover admission, hostile concurrency and rollback/restart checks,
+  Core-owned Step commit, passed strict Step Review, and fresh navigation to `task submit`.
+- Negative regressions reject stale Plan rebind, unrelated dirty files, changed content hash,
+  unknown history, a wider dependency candidate, current legacy-Plan audit/authorization, extra Task
+  revisions, active lease, pending transaction, corrupted invalidation/recovery sidecars, and a
+  replacement Plan that does not give one Step authority over the complete dirty set.
+- `npm run pack:check` built the exact beta.12.7 package: 275 files, 1.0 MB packed and 4.1 MB
+  unpacked. The sandboxed attempt
+  could not write the user npm cache (`EPERM`); the exact authorized retry passed.
 - `npm run smoke:downstream` packed and installed the tarball in a disposable consumer project and
   returned `ok=true`. The sandboxed attempt could not resolve the npm registry (`ENOTFOUND`); the
   exact network-authorized retry passed.
 - `npm run plugin:check`, `npm run docs:pdf:check`, and exact
-  `RELEASE_TAG=v2.0.0-beta.12.6 npm run release:check` passed. The plugin gate caught one missing
-  `HEAD^` boundary in the human-facing gateway instructions; that boundary was added and the gate
-  then passed. The bundled gateway cachebuster is `0.1.0+codex.20260829120000`.
+  `RELEASE_TAG=v2.0.0-beta.12.7 npm run release:check` passed after the final source changes. The
+  bundled gateway cachebuster is `0.1.0+codex.20260829143747`.
 
-## Root cause corrected by beta.12.6
+## Root causes corrected by beta.12.7
 
-- beta.12.5 correctly classified the current Signal downstream-proof conflict as recoverable, but
-  that did not make the release installable. Signal still runs beta.12.4, whose ordinary update
-  preflight rejects the running Step and dirty product work. Installing beta.12.5 would also advance
-  dependency manifests/HEAD before that new runtime could register the commit. The advertised
-  beta.12.5 recovery was therefore unreachable from the actual starting version.
-- This is an update authority deadlock, not a need for more review attempts: the old runtime cannot
-  authorize the dirty update, while the new runtime cannot be reached without an exact update.
-- beta.12.6 adds one bounded bridge rather than general dirty-update permission. The active
-  Milestone base and Task branch must each receive a separate dependency-only commit changing
-  exactly `package.json` and `package-lock.json`. A fresh beta.12.6 runtime then advertises
-  `update downstream-proof-dependency-recover` only for the active downstream-proof shape.
-- Preflight verifies recorded Task history at `HEAD^`, the exact candidate at `HEAD`, aligned
-  runtime/declared/locked/installed/current-branch/base versions, one active Step, completed
-  transitive-predecessor ownership, branch and Plan bindings, no lease, no pending/corrupt
-  transaction or Core operation, and every dirty path plus SHA-256 content.
-- Recovery registers only the dependency candidate in `systemCommits` and records the bound proof
-  in `dependencyProvenanceRecoveries.activeDownstreamProof`. It does not edit, stash, reset, commit,
-  or discard product work and does not change Step state. Fresh `next` then prioritizes
-  `task downstream-proof-recover` over manifest-induced Knowledge refresh.
-- The ordinary downstream recovery remains responsible for invalidating stale predecessor
-  completion authority and returning the same Task to a new Plan, Risk Audit, authorization,
-  execution, and strict-review cycle. beta.12.6 does not bypass that lifecycle.
+- beta.12.6 correctly invalidated the completed migration predecessor and required a replacement
+  Plan. A later Project Knowledge approval nevertheless mechanically rebound the rejected two-Step
+  Plan and returned the Task to `awaiting_execution_authorization`. The required `plan-set` boundary
+  was therefore lost.
+- The stranded state could not be fixed by another review attempt: no Step was runnable and the
+  current Plan was the artifact whose authority had already been rejected. The defect was routing
+  and recovery authority, not insufficient implementation effort.
+- A one-transition repair was also insufficient. The full E2E exposed two additional dead ends:
+  the exact dependency-only update makes Project Knowledge stale before repair, and the ordinary
+  `task run` clean-checkout precondition rejected the deliberately preserved dirty bytes even after
+  a correct replacement Plan.
+- beta.12.7 adds a closed compatibility sequence. The external source preflight recognizes only the
+  exact beta.12.6 stranded shape. Dependency registration binds the update commit to the original
+  invalidation, rebound Plan, preserved HEAD, dirty paths, and content hash. Replan recovery returns
+  the same Task to `needs_fix` without requiring the now-stale live Knowledge Map to be active.
+- Project Knowledge can then be reconciled and approved, but refresh/rebind routing cannot replace
+  the mandatory `task plan-set`. The old Plan receives no execution authority.
+- Dirty bytes are not adopted as completed evidence. After a fresh Plan Risk Audit and execution
+  authorization, `task run` permits carryover only when one planned Step owns every bound path and
+  current HEAD/path/content hashes exactly match the recovery event. All ordinary checks, Core Git
+  ownership, and strict-review requirements remain in force.
 
-## Exact Signal read-only evidence
+## Exact Signal project evidence
 
-- The Signal repository `/Users/home-pc/htdocs/projects/signal_v4` was re-observed read-only after
-  implementation. It remains on branch
-  `codex/task-01m0wxjad4-processing-persistence-schema` at
-  `88f8bf70d1591852ad90c976625430d4f20585ac`.
-- Its dirty set remains exactly six paths: five modified processing-migration files and one
-  untracked `tools/postgres/run-processing-integration.ts`. No Signal repository or Workflow state
-  was mutated during beta.12.6 implementation.
-- Prior read-only state inspection identified Task
-  `TASK-01M0WXJAD4GZGVNRJ284ND95C6`, revision 103, active Step
-  `STEP-002-REAL-POSTGRES-PROOF`, five files owned by completed transitive predecessor
-  `STEP-001-PROCESSING-MIGRATIONS`, and one file owned by the active proof Step. The predecessor
-  evidence commit equals the preserved HEAD.
-- The installed beta.12.4 ordinary update preflight returned `safe=false` for the running Step and
-  dirty checkout. The external beta.12.5 classifier returned `applicable=true`, `eligible=true`, and
-  no recovery blockers, proving that the product boundary itself is supported but not that the old
-  update path can reach it.
-- The beta.12.6 regression fixture mirrors all six Signal paths and the same predecessor/active-Step
-  ownership split. It proves the new update bridge and subsequent downstream recovery route under
-  controlled Git/state mutations.
-- This is strong structural and synthetic evidence, not a claim that the published package has
-  already updated live Signal. The final operational proof still requires the released exact
-  package, two exact dependency-only transport commits, the advertised preflight/recover, and a
-  fresh Signal `status -> next` readback.
+- The Signal repository `/Users/home-pc/htdocs/projects/signal_v4` was inspected and exercised on
+  branch `codex/task-01m0wxjad4-processing-persistence-schema` at
+  `4606eaf98f3c5f1f0dec4c361f34e2abe9aefa66`.
+- Its Workflow remains on exact `2.0.0-beta.12.6`. Task
+  `TASK-01M0WXJAD4GZGVNRJ284ND95C6` remains revision 106 and
+  `awaiting_execution_authorization`; live Workflow state was not mutated by beta.12.7 validation.
+- The dirty set remains exactly six paths: five modified processing-migration files and untracked
+  `tools/postgres/run-processing-integration.ts`. After temporary hostile-test additions were
+  removed, the beta.12.7 source preflight returned `eligible=true`, empty blockers, the preserved
+  HEAD above, and dirty-worktree SHA-256
+  `1cbeb0ccb4883ade6f2ea751423385cf504f5c18e45473f40cb9a39ca850ece1`.
+- The real Signal PostgreSQL harness was temporarily extended with two concurrent migrators and a
+  forced mid-migration conflict followed by restart. `npm run processing:postgres:test` passed clean
+  bootstrap/repeat, advisory-lock serialization, transaction rollback with no partial ledger/schema,
+  unchanged restart convergence, tamper/order denial, catalog fingerprint, immutable evidence, and
+  least-privilege checks against the pinned PostgreSQL image.
+- Those temporary product changes were then removed exactly and the original runner bytes were
+  verified against a parallel Signal checkout before the recovery fingerprint was re-read. This
+  proves product feasibility without falsely presenting pre-authorized test bytes to Workflow.
+- This is strong live read-only entry evidence plus real product proof. It is not a claim that the
+  unpublished beta.12.7 package has already updated Signal or mutated its Task. Final live continuation
+  still requires release publication, exact dependency-only transport, and following fresh
+  project-local `next` through the tested sequence.
 
 ## PDF release documentation evidence
 
-- Three tracked Russian PDFs were regenerated from Markdown sources; `npm run docs:pdf:check`
-  reported an empty stale set.
-- All 27 pages were rendered and visually inspected: architecture is 7 pages (101,761 bytes), the
-  delegated chat-only guide is 9 pages (107,066 bytes), and the technical reference is 11 pages
-  (112,132 bytes).
-- Visual inspection found table headers rendered dark-on-dark. The shared generator now uses an
-  explicit white bold header Paragraph style; all documents were regenerated and re-inspected.
-  Titles, version headers, Cyrillic glyphs, tables, code blocks, recovery instructions, page edges,
-  and footers have no visible clipping, overlap, or unreadable content.
+- Three tracked Russian PDFs were regenerated from current Markdown sources;
+  `npm run docs:pdf:check` reported an empty stale set.
+- All 28 pages were rendered and visually inspected: architecture is 8 pages, the delegated
+  chat-only guide is 9 pages, and the technical reference is 11 pages.
+- Titles, beta.12.7 version headers, Cyrillic glyphs, tables, code blocks, new recovery commands,
+  page edges, and footers show no visible clipping, overlap, or unreadable content.
 
 ## Existing boundaries and non-claims
 
-- Structural replacement remains intentionally disabled. beta.12.6 does not implement P04-B,
+- Structural replacement remains intentionally disabled. beta.12.7 does not implement P04-B,
   topology rewiring, completed-Step adoption, or a wider delegation surface.
-- The compatibility bridge is limited to the proven active-downstream-proof shape. Unrelated dirty
-  paths, non-predecessor ownership, unknown history, a wider dependency commit, stale base/version
-  divergence, branch/Plan/Step mismatch, lease, transaction, or damaged sidecar fails closed.
-- Read-only preflight is an observation, not an authorization token. Recover recomputes the current
-  binding. The stored hash proves which bytes the bridge preserved; subsequent downstream recovery
-  revalidates paths, ownership, and history, while the replacement Plan and review cover current
-  content.
-- Git transport commits remain agent-executed operations on exact advertised boundaries. The
-  runtime does not create, amend, merge, reset, or push Git history.
-- Validation performed no Signal mutation, npm publication, Git commit, tag, remote push, or local
-  plugin reinstall. Those are separate release/deployment actions.
-- Confidence is high for the implemented source and tested Signal-shaped transition. Confidence in
-  the final live Signal update remains pending until the published package is installed and the
-  project-local runtime returns the expected recovery sequence.
+- The new bridge is limited to the proven beta.12.6 invalidation-plus-accidental-rebind sequence.
+  It is not a general permission for dirty update, arbitrary Plan rollback, or manual state repair.
+- A negative Plan Risk Audit decision may truthfully return the same Task to planning, but no
+  automatic component decides product semantics or widens Task objective, requirements, acceptance,
+  or Milestone topology.
+- Git transport commits remain agent-executed operations on exact advertised boundaries. Runtime
+  does not create, amend, merge, reset, publish, tag, or push release history.
+- Validation performed no npm publication, Git commit, tag, remote push, Signal dependency update,
+  or local plugin reinstall. Those remain separate release/deployment actions.
+- Confidence is high for the implementation, package artifact, synthetic Workflow E2E, and real
+  PostgreSQL proof. Confidence in final live Signal continuation remains conditional on installing
+  the published exact package and observing the same project-local recovery sequence.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "codex-workflow-v2",
-  "version": "2.0.0-beta.12.6",
+  "version": "2.0.0-beta.12.7",
   "description": "Requirements-first Codex development workflow with local state and explicit Git ownership.",
   "repository": {
     "type": "git",
@@ -44,6 +44,7 @@
     "typecheck": "tsc -p tsconfig.json --noEmit",
     "test": "node scripts/with-validation-lock.mjs test",
     "test:signal-t04-recovery": "node scripts/with-validation-lock.mjs test-signal-t04",
+    "test:signal-t03-replan-e2e": "node scripts/with-validation-lock.mjs test-signal-t03-replan",
     "validate": "npm run typecheck && npm test",
     "pack:check": "npm run build && npm pack --dry-run",
     "smoke:downstream": "npm run build && node scripts/downstream-smoke.mjs",

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

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