codex-workflow-v2 2.0.0-beta.12.8 → 2.0.0-beta.12.9

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

@@ -1,10 +1,10 @@
 ---
-title: Codex Workflow V2: архитектура beta.12.8
+title: Codex Workflow V2: архитектура beta.12.9
 subtitle: Источники истины, lifecycle, роли, delegation, зависимости Tasks и границы доверия
 part: Часть 1 из 3 | Архитектура
 document_version: 2.0
-date: 29 августа 2026
-subject: Архитектура и границы Codex Workflow V2 beta.12.8
+date: 30 августа 2026
+subject: Архитектура и границы Codex Workflow V2 beta.12.9
 ---
 
 # 1. Назначение и граница системы
@@ -18,7 +18,7 @@ Codex Workflow V2 - локальный state machine поверх Codex App, Git
 Система рассчитана на одного пользователя и одну машину. Она не предоставляет distributed locking,
 криптографическую идентификацию actor string или безопасную синхронизацию state между компьютерами.
 
-## 1.1. Что beta.12.8 гарантирует
+## 1.1. Что beta.12.9 гарантирует
 
 - exact project-local npm package и совместимый handshake до lifecycle действий;
 - Discovery до materialization Task или Milestone;
@@ -35,8 +35,10 @@ Codex Workflow V2 - локальный state machine поверх Codex App, Git
   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`.
+- corrective Plan сохраняет authority исключённых completed Step commits, а beta.12.9 bounded recovery
+  исправляет уже stranded state только при passed strict review и прежнем hash-bound final acceptance.
 
-## 1.2. Что beta.12.8 не гарантирует
+## 1.2. Что beta.12.9 не гарантирует
 
 - правильность продуктовой идеи или автоматически выбранного provider Task;
 - semantic sufficiency Plan, если точные факты нельзя доказать поддерживаемым analyzer;
@@ -283,6 +285,14 @@ Task в `needs_fix`; stale Knowledge можно reconciliate/approve, но fresh
 всем dirty set. `task run` принимает carryover лишь при exact HEAD/path/hash match, после чего Step
 проходит обычные checks, Core-owned commit и strict review.
 
+beta.12.9 закрывает исторический provenance gap corrective replan. Новые replan transitions автоматически
+переносят evidence commits исключённых Steps в `invalidatedStepCommits`. Для уже существующего gap Core
+требует один неожиданный commit, complete passed strict-review chain, verified reviewer attestation и
+совпадающий прежний final acceptance. Если пакет уже зарегистрирован, recovery меняет только Task state.
+Если exact beta.12.9 dependency commit ещё находится в HEAD, отдельный update compatibility route
+регистрирует dependency и historical authority одной revision. Оба пути сохраняют dirty bytes текущего
+Step, не переписывают Git и завершаются fresh обычным `step-complete` flow.
+
 Docker socket `EPERM` в sandbox не является доказательством сломанного daemon. Gateway один раз
 повторяет exact health probe или Plan check с sandbox escalation без расходования remediation attempt.
 Restart Docker Desktop требует отдельного разрешения и допустим только после escalated daemon failure.
@@ -292,7 +302,7 @@ Restart Docker Desktop требует отдельного разрешения
 # 10. Operational checklist
 
 - exact package version установлен, bundled gateway соответствует release и переустановлен;
-- handshake подтверждает protocol 2, state schema 2 и beta.12.8 capabilities;
+- handshake подтверждает protocol 2, state schema 2 и beta.12.9 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.8 путь от нового Discovery до принятого Milestone без ручного CLI
+subtitle: Актуальный beta.12.9 путь от нового Discovery до принятого Milestone без ручного CLI
 part: Часть 2 из 3 | Практика
 document_version: 2.0
-date: 29 августа 2026
-subject: Практическое руководство по delegated Discovery и Milestone в Workflow V2 beta.12.8
+date: 30 августа 2026
+subject: Практическое руководство по delegated Discovery и Milestone в Workflow V2 beta.12.9
 ---
 
-# 1. Рабочая модель beta.12.8
+# 1. Рабочая модель beta.12.9
 
 Пользователь работает в одном 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.8 как точную devDependency после публикации release.
+2. Установите beta.12.9 как точную 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.8 должен сообщать `packageVersion=2.0.0-beta.12.8`, `protocolVersion=2`,
+Handshake beta.12.9 должен сообщать `packageVersion=2.0.0-beta.12.9`, `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.8 в delegated режиме.
+Проведи новый Milestone через Codex Workflow V2 beta.12.9 в delegated режиме.
 Repository: <ABSOLUTE-REPOSITORY-ROOT>.
 Milestone ID: AUTO.
 Delegate actor: agent:milestone-coordinator.
@@ -304,6 +304,7 @@ Task chat записывает его только при совпадении p
 | `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 |
+| Corrective Plan потерял authority ранее принятого Step commit | Только advertised beta.12.9 historical-Step preflight/recovery; без rebase/reset и без новой 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` |
@@ -323,32 +324,26 @@ 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`.
+Для beta.12.9 historical-Step blocker обновите base в отдельном worktree и Task branch двумя commits
+только package/lock. После install продолжайте лишь при advertised `update historical-step-dependency-recover`
+и preflight, связавшем HEAD/parent, passed+accepted historical SHA, Plan/Step, dirty hash и отсутствие lease.
+Recover сохраняет product bytes; затем обязательны `status -> next -> task step-complete`. Если package
+уже зарегистрирован, используйте advertised `task historical-step-provenance-preflight/recover`.
+
+Для exact beta.12.6 stranded-replan shape сначала нужен eligible read-only source preflight с exact
+revision/HEAD/dirty hash. Затем два beta.12.7 dependency-only commits и advertised dependency/replan
+recoveries. После Knowledge refresh `next` обязан остаться на `task plan-set`; новый единый 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 без отдельного разрешения и подтверждённого
 escalated daemon failure.
 
-Если после применённого 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, а не ручной обход.
-
-Если advertised navigation записала dependency provenance после последнего context-refresh audit,
-продолжайте только когда fresh `next` сам вернул `task run`. Core обязан доказать, что каждый такой
-recovery объясняет ровно один дополнительный Task revision; простое `revision >=` не является
-authority.
+После stop override выполняйте только advertised context/dependency recoveries и каждый раз повторяйте
+`status -> next`; attempt 4 требует `stopOverrideContextRebind.state=validated`. Lost credential
+восстанавливает только advertised exact claimant route. Semantic drift, broken chain, необъяснённый HEAD
+или revision означают stop; продолжение разрешено только когда fresh `next` сам вернул `task run`.
 
 # 12. Milestone final acceptance
 
@@ -367,7 +362,7 @@ Task/project DGR. `dependencyBinding` для standalone handoff равен null.
 
 # 14. Итоговый checklist пользователя
 
-- beta.12.8 exact package и новый bundled gateway установлены;
+- beta.12.9 exact package и новый bundled gateway установлены;
 - новый Coordinator chat не является fork старого Milestone;
 - bootstrap DGR, если нужен, выдан отдельным exact human confirmation;
 - Discovery не materialized при blocking unknowns;
@@ -380,5 +375,6 @@ Task/project DGR. `dependencyBinding` для standalone handoff равен null.
 - downstream predecessor recovery, если рекламировался, сохранил worktree и завершился новым Plan authority;
 - active-proof package bridge, если понадобился, зарегистрировал только exact dependency HEAD перед recovery;
 - stranded-replan bridge, если понадобился, завершился новым Plan и полным Step checks/review, а не только сменой navigation;
+- historical-Step recovery, если рекламировался, сохранил exact accepted commit и довёл текущий Step до обычного `step-complete` без history rewrite;
 - 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.8
+title: Codex Workflow V2: технический справочник beta.12.9
 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.8
+date: 30 августа 2026
+subject: Технический контракт Codex Workflow V2 beta.12.9
 ---
 
 # 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.8 | Значение |
+| Параметр beta.12.9 | Значение |
 |---|---|
-| npm package | `codex-workflow-v2@2.0.0-beta.12.8` |
+| npm package | `codex-workflow-v2@2.0.0-beta.12.9` |
 | 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.8 capabilities:
+Ключевые beta.12.9 capabilities:
 
 | Группа | Capabilities |
 |---|---|
@@ -46,7 +46,7 @@ Gateway выполняет:
 | Task planning | Plan Risk Audit, proof obligations, mechanical feasibility |
 | C1 | handoff sidecar/bundle, derived Worker actor, credential replacement, Human-gate lease release |
 | Reviews | strict reviewer, Step strict review, continuable remediation, evidence-bound fix/replan routing |
-| Recovery | Task-local dependency provenance, plan integrity, downstream-proof predecessor invalidation, remediation mode, legacy stop override, append-only stop-rebind chain, corrective yield/replan journals |
+| Recovery | Task-local dependency provenance, historical Step provenance, plan integrity, downstream-proof predecessor invalidation, 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 или соседней
@@ -381,6 +381,26 @@ fresh `next` рекламирует lease-bound `task downstream-proof-recover`
 remainder и пройти fresh Plan Risk Audit и execution authorization. Unrelated/non-predecessor file,
 strict-review evidence, unregistered commit, branch mismatch или damaged sidecar возвращают `doctor`.
 
+# 13.3. beta.12.9 historical Step provenance
+
+Corrective replan теперь сохраняет evidence commits Steps, исключённых replacement Plan, в
+`invalidatedStepCommits`. Это предотвращает новый unregistered-history blocker без переноса завершённого
+Step в новый Plan.
+
+Для уже существующего stranded state fresh `next` допускает только один из двух bounded routes:
+
+- `task historical-step-provenance-preflight/recover`, если beta.12.9 dependency HEAD уже зарегистрирован;
+- `update historical-step-dependency-preflight/recover`, если dependency-only beta.12.9 commit ещё
+  является единственным unregistered HEAD.
+
+Core требует один active Step, dirty paths только в его `allowedWrites`, отсутствие leases/transactions,
+ровно один omitted product commit, полный hash-valid strict Step Review с `passed`, verified reviewer
+attestation и прежний hash-bound `final_acceptance` того же Plan. Update-route дополнительно связывает
+exact `HEAD^`/`HEAD`, package/version surfaces и SHA-256 dirty worktree. Recovery не переписывает Git,
+не меняет product bytes и не возвращает старый Step в Plan; он записывает historical authority и, для
+update-route, dependency provenance в одной Task revision. Fresh `status -> next` после transition
+должен вернуть обычный credential/`task step-complete` flow текущего Step.
+
 # 14. P04-A structural replacement boundary
 
 Command shape `task replacement-materialize` retained только для compatibility diagnostics. Любая попытка
@@ -443,12 +463,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.8
+# 18. Public command surface beta.12.9
 
 | Область | Actions |
 |---|---|
 | System | `doctor`, `status`, `next`, `gateway handshake`, `locks` |
-| Update | `preflight`, `rescue-preflight`, dependency provenance, downstream-proof dependency bridge, downstream-proof replan update/dependency bridge |
+| Update | `preflight`, `rescue-preflight`, dependency provenance, historical-Step dependency bridge, 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` |
@@ -458,7 +478,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/replan-recover, remediation-mode, stop-override prepare/apply, yield и corrective-replan actions |
+| Corrective | decision/recovery, plan-integrity, historical-step-provenance preflight/recover, 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 используется только когда
@@ -468,10 +488,10 @@ Exact options берутся из fresh `next`; command help используе
 
 Перед 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 bridge и beta.12.7 exact stranded-replan bridge; все они fail-closed и не дают
-общего разрешения dirty update.
+active-downstream-proof bridge, beta.12.7 exact stranded-replan bridge и beta.12.9 historical-Step
+dependency bridge; все они fail-closed и не дают общего разрешения dirty update.
 
-Перед beta.12.8 tag обязательны `npm ci`, `npm run validate`, `npm run pack:check`,
+Перед beta.12.9 tag обязательны `npm ci`, `npm run validate`, `npm run pack:check`,
 `npm run smoke:downstream`, `npm run plugin:check`, official plugin/skill validators,
 `npm run docs:pdf:check`, `npm run release:check` с exact tag binding и validation
 append-only real-agent lifecycle log.

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.8, the release gate also relies on `npm run release:check` to fail if:
+For beta.12.9, 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;
@@ -48,6 +48,12 @@ For beta.12.8, the release gate also relies on `npm run release:check` to fail i
   revision-26 fixture, or pending/corrupt-review rejection regressions are absent.
 - dependency recovery again requires Task-local manifest/lock fields to equal the Milestone base,
   or a candidate commit can alter any non-Workflow dependency payload.
+- corrective replan drops completed Step evidence from accepted Task history, or an already-stranded
+  Task can register arbitrary/unreviewed history instead of one exact passed and previously accepted
+  Step commit.
+- beta.12.9 cannot install through an exact dependency-only base/Task transport while preserving the
+  active Step worktree, or that compatibility route fails to bind the dependency HEAD, historical
+  commit, current Plan/Step, dirty paths/content hash, and absence of leases/transactions.
 - the read-only Milestone progress projection, replacement regression, project-monotonic chat
   registry, title fallback/readback, or long-Cyrillic multi-attempt E2E evidence is absent.
 - bounded first-failure Plan-integrity recovery, exact failed-remediation/manifest/worktree

package/docs/updating-existing-project.md

@@ -59,6 +59,36 @@ candidate: его HEAD обязан менять ровно `package.json` и `p
 dependency; любое другое поле, добавленное тем же candidate commit, неизвестный commit, stale base,
 dirty checkout, lease или transaction по-прежнему блокируют recovery.
 
+### Исключение beta.12.9 для Step commit, потерянного corrective Plan
+
+Если активный corrective Step сохраняет допустимый dirty worktree, а `task step-complete` обнаруживает
+ровно один старый product commit, beta.12.9 не требует переписывать Git. Пакет поддерживает два
+строго ограниченных входа в один и тот же recovery:
+
+- если beta.12.9 уже зарегистрирована, свежий `next` рекламирует
+  `task historical-step-provenance-recover`;
+- если для установки beta.12.9 на Milestone base и Task branch уже созданы ровно dependency-only
+  commits, свежий `next` рекламирует `update historical-step-dependency-recover`. Этот переход
+  атомарно регистрирует новый dependency HEAD и сохраняет authority старого Step commit.
+
+В обоих случаях Core сам доказывает для старого SHA полную hash-valid strict Step Review цепочку с
+решением `passed`, verified reviewer isolation и совпадающий прежний `final_acceptance`. Update-route
+дополнительно требует exact target version на declared/locked/installed/current-branch/base surfaces,
+dependency commit только из `package.json` и `package-lock.json`, а также неизменный hash активного
+dirty worktree относительно read-only assessment.
+
+Сначала выполните read-only `task historical-step-provenance-preflight --id <TASK-ID>`. Продолжайте
+только при `eligible=true`, точных Task revision, Plan/Brief/HEAD и commit SHA, отсутствии leases,
+transactions и Core operations, а также dirty paths строго внутри `allowedWrites` единственного
+активного Step. Recover принимает exact SHA, actor и содержательную reason, добавляет SHA в
+`invalidatedStepCommits` и записывает источник прежнего acceptance. Product bytes, HEAD и текущий
+Plan не меняются; старый Step не возвращается в Plan. После recovery обязательны последовательные
+`status` и `next`, затем обычный credential route и `task step-complete` текущего Step.
+
+Несколько unknown commits, pending/failed review, несовпадающий Plan прежнего acceptance,
+повреждённый sidecar, посторонний dirty path или lease являются hard stop. Запрещено заменять этот
+переход rebase/reset/amend, ручным `systemCommits` или переносом старого Step в текущий Plan.
+
 ### Исключение beta.12.6 для активного downstream proof
 
 Обычный `update preflight` по-прежнему правильно запрещает обновление при running Step и dirty

package/docs/validation-report.md

@@ -1,103 +1,104 @@
-# V2 beta.12.8 Validation Report
+# V2 beta.12.9 Validation Report
 
-Release candidate `2.0.0-beta.12.8` was validated on 2026-08-29 (Europe/Moscow) with
+Release candidate `2.0.0-beta.12.9` was validated on 2026-08-30 (Europe/Moscow) with
 Node.js 24.17.0.
 
 ## Automated release evidence
 
 - `npm ci` completed from the exact lockfile with 0 reported vulnerabilities.
-- `npm run validate` passed typecheck and `339/339` sequential tests with no failures, skips,
-  cancellations, or todos in 1,700,172.265375 ms.
-- The focused claimed-Task E2E passed independently. It covers sealed passed final review,
-  machine-readable `task result-set` writer-token navigation, rejection of a forged token without
-  Task/lease mutation, successful Result publication, lease-free `awaiting_final_acceptance`, Human
-  acceptance, fresh credential replacement, merge, and terminal lease release.
-- CLI help regression proves that `task result-set` requires `--writer-token` and exposes optional
-  `--actor` for the exact C1 claimant.
-- The full suite retained the Signal-shaped downstream replan E2E, Signal T04 retained-review
-  recovery, dependency provenance, Plan-integrity recovery, corrective replan, lock hostility,
-  transaction crash/recovery, Milestone dependency, strict-review, and credential-confinement gates.
-- `npm run pack:check` built the exact beta.12.8 package with 275 files, 1.0 MB packed and 4.1 MB
+- `npm run validate` passed typecheck and `343/343` sequential tests with no failures, skips,
+  cancellations, or todos in 1,894,344.070542 ms.
+- The focused Signal-shaped E2E proves both recovery entry points. It preserves the active dirty
+  worktree and HEAD, registers the exact historical Step commit, reaches fresh
+  `task step-complete`, completes that Step with a new Core-owned commit, and validates the resulting
+  Task history.
+- Negative cases reject pending or damaged strict review, absent final acceptance, multiple or wrong
+  commits, unrelated dirty paths, changed dirty content, active/stale leases, transactions, version
+  divergence, and a dependency candidate wider than package/lock.
+- Corrective-replan executor tests prove that future replacement Plans retain evidence commits of
+  omitted completed Steps in `invalidatedStepCommits`.
+- `npm run pack:check` built the exact beta.12.9 package with 278 files, 1.0 MB packed and 4.1 MB
   unpacked. The initial sandboxed invocation 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` passed for bundled gateway
-  `0.1.0+codex.20260829181421`. The plugin-creator manifest validator and skill quick validator also
-  passed using the system Python runtime that provides PyYAML.
-- `npm run docs:pdf:check` reported an empty stale set and exact beta.12.8 package binding.
-- `RELEASE_TAG=v2.0.0-beta.12.8 npm run release:check` and `git diff --check` passed.
+  `0.1.0+codex.20260830183000`.
+- `npm run docs:pdf:check` reported an empty stale set and exact beta.12.9 package binding.
+- `RELEASE_TAG=v2.0.0-beta.12.9 npm run release:check`, JSON parsing and `git diff --check` passed.
 
-## Root cause corrected by beta.12.8
+## Root cause corrected by beta.12.9
 
-`WorkflowService.setTaskResult` previously moved a reviewed Task from `validating` to
-`awaiting_final_acceptance` without accepting the active writer credential and without releasing
-the Task writer lease. Human final acceptance is intentionally unbounded, so an otherwise successful
-Task could wait until the lease expired. Repository-level `next` then truthfully returned
-`repair-required / STALE_WRITER_LEASE` instead of `task accept`.
+The corrective-replan paths replaced `task.steps` but did not preserve evidence commits belonging to
+completed Steps omitted from the new Plan. Git correctly retained those commits, while Task history
+authority no longer named them. A later `task step-complete` therefore rejected a legitimate,
+previously reviewed and accepted commit as unregistered history.
 
-Increasing review or implementation attempts cannot correct this condition. The implementation and
-review had already passed; the defect was ownership lifetime crossing a Human pause.
+Increasing implementation or review attempts cannot correct this condition. The historical Step had
+already passed strict review and final acceptance; the defect was loss of provenance during Plan
+replacement.
 
 ## Implemented lifecycle contract
 
-- `task result-set` now requires the active `--writer-token`; claimed C1 Tasks also pass the exact
-  claimant through `--actor`.
-- Core verifies the current revision, passed/fresh review, live writer credential, and C1 mutation
-  authority before staging Result.
-- Core releases the exact presented lease before committing the transition to
-  `awaiting_final_acceptance`. Human wait time therefore cannot create a new stale lease.
-- Fresh `next` advertises the writer-token contract and bounded credential recovery for
-  `task result-set` when needed.
-- `task accept` remains a credential-free Human/delegated approval transition. After acceptance,
-  fresh `next` advertises `task writer-credential-replace`; this acquires a new lease for local merge
-  or external merge confirmation. The pre-gate token is not reusable.
-- The public handshake exposes `task-human-gate-lease-release-v1`.
+- Both legacy `setTaskPlan` and journaled corrective-replan execution now retain omitted completed
+  Step evidence commits in `invalidatedStepCommits`.
+- `task historical-step-provenance-preflight/recover` repairs an already-installed beta.12.9 state
+  only when Core proves exactly one omitted commit, one active Step, confined dirty paths, a complete
+  hash-valid passed strict Step Review chain, verified reviewer isolation, and matching prior
+  hash-bound final acceptance.
+- `update historical-step-dependency-preflight/recover` handles installation itself when the exact
+  beta.12.9 dependency-only commit is the unregistered HEAD. It binds `HEAD^`, dependency `HEAD`, all
+  version surfaces, active Plan/Step, historical SHA, dirty paths/content hash, and the absence of
+  leases or pending operations.
+- The update transition records the dependency commit and retained historical commit in one Task
+  revision. Neither recovery rewrites Git, changes product bytes, adopts the old completed Step into
+  the current Plan, or weakens ordinary strict review.
+- Fresh `next` advertises these routes before ordinary dependency recovery and returns to the normal
+  credential/`task step-complete` flow after successful registration.
+- The public handshake exposes `historical-step-provenance-recovery-v1`.
 
 ## Exact Signal diagnosis evidence
 
-At diagnosis time the Signal project `/Users/home-pc/htdocs/projects/signal_v4` was on exact
-beta.12.7 with Task `TASK-01M0WXJAD4GZGVNRJ284ND95C6` at revision 126 and
-`awaiting_final_acceptance`. The Task checkout was clean at
-`f7ba8533314ee27f176968a6314bf3df40285ef2`; Final Task Review was `passed` with no findings.
-The Result hash was `89bbbaaef5d2b454ed7ed0e3d9f57484d36c9d86d596e009a32613701003496e`
-and Evidence hash was `85f3cb5c16e039ebf40971f88a4388fe1812ef37be8d6b195451aa6a73640c54`.
-Repository-level `next` returned only `locks repair` for the expired lease owned by the Task worker.
+At release-candidate validation time the Signal project
+`/Users/home-pc/htdocs/projects/signal_v4` was on exact beta.12.8 with Task
+`TASK-01M0WXJAD4GZGVNRJ284ND95C6` at revision 136 and status `in_progress`. Current Plan hash was
+`1ba67296f352cb67fa4d46c3ec9cd2ee2f50059903a5fffc7b0b2198f6dbae4e`; HEAD was
+`272d6258e4ce169aa9f5cf2b5a4de29970d82eb7`.
 
-The release process did not mutate Signal state or product files. The legacy lease must first be
-removed through that exact advertised repair route with revision, HEAD, review, Result, and Evidence
-readback. The agent must stop before `task accept`. Only after the repository is lease-free and
-`update preflight` is safe should Signal install beta.12.8 and continue through fresh navigation.
+The active Step `STEP-004-DIRECT-LOGIN-PRIVILEGE-DENIAL` had exactly five dirty files, all inside its
+`allowedWrites`. Historical commit `f7ba8533314ee27f176968a6314bf3df40285ef2` had a passed strict
+Step Review and prior final acceptance, but was absent from current Step evidence and retained
+history authority. No active/stale lease, pending/corrupt transaction, or Core operation remained.
+Milestone progress was `2/8` merged Tasks and T04 remained blocked by T03.
+
+The recurring Signal audit automation that had created an unrelated dirty journal was paused, and
+its latest journal was archived outside the checkout with matching SHA-256. The release process did
+not rewrite Signal history or mutate its five product files. Live package transport and recovery are
+separate post-publication actions and must follow the exact advertised beta.12.9 route.
 
 ## PDF release documentation evidence
 
-- All three tracked Russian PDFs were regenerated from the beta.12.8 Markdown sources.
+- All three tracked Russian PDFs were regenerated from the beta.12.9 Markdown sources.
 - Architecture is 8 pages, the delegated chat-only guide is 9 pages, and the technical reference is
-  11 pages. Every page was rendered to PNG and visually inspected.
-- Titles, version headers, Cyrillic text, tables, code blocks, Human-gate credential sequence,
-  release checklist, margins, and page footers have no visible clipping, overlap, orphaned tail page,
-  or unreadable content.
+  12 pages. All pages were rendered to PNG contact sheets; changed recovery/update pages were also
+  inspected at full page resolution.
+- Titles, version headers, Cyrillic text, tables, command names, margins, page footers and section
+  transitions have no visible clipping, overlap, unreadable content, or orphaned tail page.
 
 ## Existing boundaries and non-claims
 
-- beta.12.8 prevents new `result-set` transitions from retaining a lease. It does not silently delete
-  a stale lease created by beta.12.7 or earlier; legacy state uses explicit `locks repair`.
-- The patch does not auto-accept a Task, bypass final review, widen delegated approval, or turn an
-  expired bearer into authority.
-- Protocol version remains 2 and state schema remains 2; no semantic state migration is introduced.
-- Structural replacement remains intentionally disabled. beta.12.8 does not implement P04-B,
-  topology rewiring, completed-Step adoption, or a wider delegation surface.
-- No append-only real-agent lifecycle log was generated for this maintainer release turn because
-  the package Workflow did not orchestrate its own repository mutation. Transcript validator
-  semantics remain covered by the complete valid/invalid fixture suite; no synthetic log is
-  presented as real evidence.
-- Validation performed no npm publication, Git commit, tag, remote push, Signal dependency update,
-  Signal Task acceptance, or local personal-plugin reinstall. Those are separate release/deployment
-  actions.
-
-Confidence is high for the package implementation, negative credential behavior, complete claimed
-Task continuation, tarball, downstream installation, plugin, and documentation. Confidence that the
-live Signal Milestone will continue is conditional on completing the exact legacy stale-lease repair,
-observing a safe update preflight, installing the published beta.12.8 package, and following fresh
-project-local `status -> next` without skipping the Human gate.
+- Recovery is intentionally unavailable for arbitrary or multiple commits, pending/failed review,
+  missing final acceptance, post-assessment drift, unrelated dirty paths, or active ownership.
+- Protocol version remains 2 and state schema remains 2; the optional audit fields are backward
+  compatible and no semantic migration is introduced.
+- Structural replacement remains disabled. beta.12.9 does not implement P04-B, topology rewiring,
+  completed-Step adoption, or a wider delegation surface.
+- No Git commit, tag, remote push, npm publication, Signal dependency transport, or Signal Task
+  completion is claimed by this pre-publication validation report.
+
+Confidence is high for the package implementation, prevention path, bounded legacy recovery,
+dependency-install compatibility, negative evidence gates, complete Step continuation, tarball,
+downstream installation, plugin and documentation. Live Signal confidence remains conditional on
+publishing beta.12.9, transporting only package/lock commits to its active base and Task branch, and
+following fresh project-local `status -> next` without manual history or state edits.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "codex-workflow-v2",
-  "version": "2.0.0-beta.12.8",
+  "version": "2.0.0-beta.12.9",
   "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.20260829181421",
+  "version": "0.1.0+codex.20260830183000",
   "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

@@ -33,6 +33,15 @@
   `retainedHistoricalCommits`.
   Task-local manifest/lock fields from recorded history may differ from the base, but the candidate
   commit must preserve them exactly while changing only the Workflow dependency entries.
+- `task historical-step-provenance-preflight --id <TASK-ID>` is read-only. The matching
+  `task historical-step-provenance-recover` is available only for one unexpected product commit
+  with an intact passed strict-review chain, matching prior final acceptance, no lease or pending
+  operation, and dirty files confined to the current active Step. It retains historical authority
+  without changing Git, worktree bytes, or the current Plan.
+- `update historical-step-dependency-preflight/recover` handles the same proof when the beta.12.9
+  dependency-only commit is the unregistered HEAD. It binds the exact dependency candidate and the
+  reviewed historical Step commit in one recovery record, preserves active product bytes, and then
+  requires fresh `status` and `next`.
 - `task stop-override-prepare` is a read-only Human gate for the exact beta.11 attempt-four stop
   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