codex-workflow-v2 2.0.0-beta.12.16 → 2.0.0-beta.12.18

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

@@ -1,10 +1,10 @@
 ---
-title: Codex Workflow V2: архитектура beta.12.16
+title: Codex Workflow V2: архитектура beta.12.18
 subtitle: Источники истины, lifecycle, роли, delegation, зависимости Tasks и границы доверия
 part: Часть 1 из 3 | Архитектура
 document_version: 2.0
-date: 31 августа 2026
-subject: Архитектура и границы Codex Workflow V2 beta.12.16
+date: 1 сентября 2026
+subject: Архитектура и границы Codex Workflow V2 beta.12.18
 ---
 
 # 1. Назначение и граница системы
@@ -18,7 +18,7 @@ Codex Workflow V2 - локальный state machine поверх Codex App, Git
 Система рассчитана на одного пользователя и одну машину. Она не предоставляет distributed locking,
 криптографическую идентификацию actor string или безопасную синхронизацию state между компьютерами.
 
-## 1.1. Что beta.12.16 гарантирует
+## 1.1. Что beta.12.18 гарантирует
 
 - exact project-local npm package и совместимый handshake до lifecycle действий;
 - Discovery до materialization Task или Milestone;
@@ -40,8 +40,11 @@ Codex Workflow V2 - локальный state machine поверх Codex App, Git
 - pre-execution `stop-escalate`, доказавший отсутствующую upstream capability, может materialize ровно
   один additive remediation Task без нового Human gate; Core сохраняет Milestone semantics и выводит
   authority из текущей Milestone authorization и exact audit evidence.
+- исторический check-support decision проверяется против собственного Plan hash, а новый Plan может
+  продолжить только после явного принятия каждого support path в `allowedWrites` и `expectedOutputs`;
+  implicit scope carry-over и Human approval для этого exact machine-proved случая отсутствуют.
 
-## 1.2. Что beta.12.16 не гарантирует
+## 1.2. Что beta.12.18 не гарантирует
 
 - правильность продуктовой идеи или автоматически выбранного provider Task;
 - semantic sufficiency Plan, если точные факты нельзя доказать поддерживаемым analyzer;
@@ -348,6 +351,19 @@ Plan/Step/HEAD, полный dirty set, runner/support hashes, direct import, о
 scope. Indirect import, dynamic shell, forbidden path, unrelated dirty file или отсутствие SHA anchors
 fail-closed и не расширяют authority.
 
+beta.12.17 закрывает transport-разрыв перед этим recovery: внешний runner больше не ожидает один
+зашитый source release. Он выводит exact beta.12 source из declared dependency, требует равенства
+locked, installed, current Task branch и active Milestone base и допускает только patch от .11 до
+версии ниже runner. Dirty scope, отсутствие lease/transaction и dependency-only Git transport
+остаются обязательными; product bytes и Workflow state вручную не изменяются.
+
+beta.12.18 закрывает следующий post-rebind разрыв. Исторический check-support event остаётся валиден
+по Plan hash, при котором был создан, даже если новый Plan теперь прямо владеет derived support path.
+External preflight допускает продолжение только при одном таком event, неизменных dirty bytes,
+отсутствии активного Step/lease/transaction и полном explicit scope adoption в planned Step. После
+dependency-only transport Core заново связывает Knowledge и authorization; старый event не создаёт
+скрытой authority и не модифицируется задним числом.
+
 Docker socket `EPERM` в sandbox не является доказательством сломанного daemon. Gateway один раз
 повторяет exact health probe или Plan check с sandbox escalation без расходования remediation attempt.
 Restart Docker Desktop требует отдельного разрешения и допустим только после escalated daemon failure.
@@ -357,7 +373,7 @@ Restart Docker Desktop требует отдельного разрешения
 # 10. Operational checklist
 
 - exact package version установлен, bundled gateway соответствует release и переустановлен;
-- handshake подтверждает protocol 2, state schema 2 и beta.12.16 capabilities;
+- handshake подтверждает protocol 2, state schema 2 и beta.12.18 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.16 путь от нового Discovery до принятого Milestone без ручного CLI
+subtitle: Актуальный beta.12.18 путь от нового Discovery до принятого Milestone без ручного CLI
 part: Часть 2 из 3 | Практика
 document_version: 2.0
-date: 31 августа 2026
-subject: Практическое руководство по delegated Discovery и Milestone в Workflow V2 beta.12.16
+date: 1 сентября 2026
+subject: Практическое руководство по delegated Discovery и Milestone в Workflow V2 beta.12.18
 ---
 
-# 1. Рабочая модель beta.12.16
+# 1. Рабочая модель beta.12.18
 
 Пользователь работает в одном 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.16 как точную devDependency после публикации release.
+2. Установите beta.12.18 как точную 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.16 должен сообщать `packageVersion=2.0.0-beta.12.16`, `protocolVersion=2`,
+Handshake beta.12.18 должен сообщать `packageVersion=2.0.0-beta.12.18`, `protocolVersion=2`,
 `stateSchemaVersion=2`, dependency DAG, initial Plan transaction, mechanical feasibility,
 Milestone autonomy и structural replacement disabled capabilities.
 
@@ -117,7 +117,7 @@ delegate, scope, transitions и expiry. DGR передаётся только е
 ```text
 НОВЫЙ COORDINATOR CHAT
 
-Проведи новый Milestone через Codex Workflow V2 beta.12.16 в delegated режиме.
+Проведи новый Milestone через Codex Workflow V2 beta.12.18 в delegated режиме.
 Repository: <ABSOLUTE-REPOSITORY-ROOT>.
 Milestone ID: AUTO.
 Delegate actor: agent:milestone-coordinator.
@@ -299,6 +299,8 @@ Task chat записывает его только при совпадении p
 |---|---|
 | First proven impossible npm check после legacy/late authorization | Только рекламируемый `task plan-integrity-recover` |
 | Direct imported migration checksum/catalog authority вне Step scope | beta.12.16: advertised `task plan-integrity-recover`, затем тот же Step с exact derived support path; Human replan не нужен |
+| In-flight Plan-integrity Task требует package update | beta.12.18 external preflight выводит coherent exact beta.12 source из пяти version surfaces; затем только dependency-only transport и advertised recovery |
+| Новый Plan явно принял ранее derived check-support path, но старый event выглядит corrupt | beta.12.18 external preflight требует exact post-rebind scope adoption и неизменные dirty bytes; затем dependency-only transport, Knowledge rebind, PRA и fresh authorization без Human gate |
 | Downstream proof требует изменить completed predecessor | Только `task downstream-proof-recover`, затем новый Plan/risk audit/authorization в той же Task |
 | Failed guarded review | Та же Task: исправление и новый strict review без attempt hard stop |
 | Finding `route=fix` | Продолжить тот же Step; count остаётся диагностикой |
@@ -408,7 +410,7 @@ Task/project DGR. `dependencyBinding` для standalone handoff равен null.
 
 # 14. Итоговый checklist пользователя
 
-- beta.12.16 exact package и новый bundled gateway установлены;
+- beta.12.18 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.16
+title: Codex Workflow V2: технический справочник beta.12.18
 subtitle: Protocol 2, state schema 2, transactions, credentials, dependency authority, review и recovery
 part: Часть 3 из 3 | Technical reference
 document_version: 2.0
-date: 31 августа 2026
-subject: Технический контракт Codex Workflow V2 beta.12.16
+date: 1 сентября 2026
+subject: Технический контракт Codex Workflow V2 beta.12.18
 ---
 
 # 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.16 | Значение |
+| Параметр beta.12.18 | Значение |
 |---|---|
-| npm package | `codex-workflow-v2@2.0.0-beta.12.16` |
+| npm package | `codex-workflow-v2@2.0.0-beta.12.18` |
 | 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.16 capabilities:
+Ключевые beta.12.18 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, historical Step 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, `historical-check-support-scope-adoption-v1`, 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 или соседней
@@ -513,6 +513,35 @@ forbiddenScope. Plan hash не меняется. Effective scope использ
 Core commit, downstream-proof assessment, corrective-replan worktree guard и strict review packet.
 Любое более широкое изменение остаётся в обычном corrective replan с Human gate.
 
+# 13.8. beta.12.17 coherent Plan-integrity update source
+
+Read-only `update plan-integrity-update-preflight` выводит `sourceVersion` из declared dependency, а
+не из release-specific constant. Он принимает только exact `2.0.0-beta.12.N`, где `N >= 11` и
+`N` меньше patch ordinal внешнего runner. Locked, installed, current Task branch и active Milestone
+base обязаны совпадать с declared source. Любая missing/divergent surface блокирует transport.
+
+Version consensus не заменяет остальные guards: должна существовать ровно одна eligible failed-Step
+Plan-integrity assessment, observation обязана быть coherent, lease/transaction/Core operation
+отсутствуют, а dirty bytes совпадают с доказанным Step scope. После dependency-only Git transport
+repository-local runner регистрирует commit только через advertised
+`update plan-integrity-dependency-recover`. Source consensus не усыновляет product history, не меняет
+Plan/remediation evidence и не даёт generic update authority другим beta lines.
+
+# 13.9. beta.12.18 historical check-support scope adoption
+
+Validation v3 связывает check-support event с `event.planHash`. Если поздний Knowledge rebind и новый
+Plan явно добавили derived support path, исторический event проверяется по собственным immutable
+fields, hashes и conflict evidence, а не против scope нового Plan. Только event текущего Plan может
+расширять effective Step scope; поэтому старое evidence не переносит authority неявно.
+
+Read-only `update plan-integrity-update-preflight` может вернуть
+`compatibilityMode=post-rebind-scope-adoption`, только если Task ожидает execution authorization, ни
+одна Step не выполняется, существует ровно один исторический v3 `continue-fix`, его dirty paths и
+content hash не изменились, а current planned Step напрямую владеет всеми `scopeExtensions` и
+объявляет их outputs. Обычные coherent-version, lease, transaction, Core-operation и dependency-only
+Git guards сохраняются. После регистрации update Knowledge rebind, PRA и authorization выполняются
+только по fresh routes; Human approval для exact machine-proved scope не нужен.
+
 # 14. P04-A structural replacement boundary
 
 Command shape `task replacement-materialize` retained только для compatibility diagnostics. Любая попытка
@@ -575,7 +604,7 @@ 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.16
+# 18. Public command surface beta.12.18
 
 | Область | Actions |
 |---|---|
@@ -606,7 +635,7 @@ active-downstream-proof bridge, beta.12.7 exact stranded-replan bridge, beta.12.
 dependency bridge и beta.12.15 Plan-integrity bridge; все они fail-closed и не дают общего разрешения
 dirty update.
 
-Перед beta.12.16 tag обязательны `npm ci`, `npm run validate`, `npm run test:signal-t10-check-support-e2e`, `npm run test:signal-remediation-e2e`, `npm run pack:check`,
+Перед beta.12.18 tag обязательны `npm ci`, `npm run validate`, `npm run test:signal-t10-check-support-e2e`, `npm run test:signal-remediation-e2e`, `npm run pack:check`,
 `npm run smoke:downstream`, `npm run plugin:check`, official plugin/skill validators,
 `npm run docs:pdf:check`, `npm run release:check` с exact tag binding и validation
 append-only real-agent lifecycle log.

package/docs/release.md

@@ -29,7 +29,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.12, the release gate also relies on `npm run release:check` to fail if:
+For beta.12.18, 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;
@@ -61,10 +61,17 @@ For beta.12.12, the release gate also relies on `npm run release:check` to fail
 - bounded first- or repeated-failure Plan-integrity recovery, selector-required npm-check
   feasibility, exact failed-remediation/manifest/worktree
   bindings, or the no-synthetic-second-failure regression is absent.
+- Plan-integrity update preflight again hard-codes one historical source release instead of deriving
+  a coherent exact beta.12 source from declared/locked/installed/current/base surfaces, or it accepts
+  a source before beta.12.11, a source not older than the runner, or any divergent version surface.
 - a direct migration check can import an external checksum/catalog authority without the producing
   Step owning it; or in-flight recovery can widen beyond the exact imported support path, bypass
   `forbiddenScope`, change the Plan hash, skip checks/Core commit/review disclosure, or require a
   Human approval for the machine-proved scope-only correction.
+- historical check-support evidence is reinterpreted against a later Plan instead of the Plan hash
+  recorded by the event; or a post-rebind update is accepted without one planned Step explicitly
+  owning every previously derived support path in both `allowedWrites` and `expectedOutputs`, exact
+  dirty-byte continuity, coherent versions, and an otherwise idle recovery boundary.
 - downstream proof cannot invalidate only completed transitive-predecessor authority while
   preserving worktree/HEAD, yielding C1, and returning the same Task to fresh planning; or unrelated
   dirty files and damaged invalidation evidence do not fail closed.

package/docs/updating-existing-project.md

@@ -22,6 +22,45 @@ state schema. Совпадение `stateSchemaVersion` до и после об
 нужна. Для alpha.6 при `stateSchemaVersion: 2` применяется не migration, а sidecar-only
 adoption posture.
 
+### beta.12.18: historical check-support scope adoption after Knowledge rebind
+
+beta.12.18 closes a bounded post-rebind deadlock. A Task may already contain a valid beta.12.16
+`continue-fix` decision that derived one exact check-support path, then refresh Knowledge and adopt
+that path explicitly in a new Plan. The historical event must still be validated against its own
+Plan hash; comparing it with the new Plan incorrectly reports `STATE_CORRUPT` precisely because the
+new Plan now owns the path.
+
+An external exact beta.12.18 runner recognizes only this exact shape: the Task awaits execution
+authorization, no Step is running, one historical check-support decision binds the unchanged dirty
+worktree, and one planned Step directly lists every derived support path in both `allowedWrites` and
+`expectedOutputs`. Read-only `update plan-integrity-update-preflight` reports
+`compatibilityMode=post-rebind-scope-adoption` only when all ordinary version, lease, transaction,
+Core-operation, Git-head and dirty-byte guards also pass.
+
+After `eligible=true`, use the same dependency-only base/Task transport described below. Fresh
+repository-local Core registers it only through advertised
+`update plan-integrity-dependency-recover`; Knowledge rebind and Risk Audit then follow fresh
+`status -> next`. The adopted support path comes from the current Plan, not from implicit reuse of
+the historical event. No Human approval is required for this exact machine-proved recovery. Any
+additional path, dirty-byte drift, missing explicit Plan ownership, multiple matching events, active
+lease or incoherent version surface remains blocked.
+
+### beta.12.17: coherent beta.12 Plan-integrity update transport
+
+`update plan-integrity-update-preflight` больше не связывает совместимый transport с одним
+историческим source release. Внешний exact beta.12.17 runner выводит source version из declared
+dependency и требует, чтобы locked, installed, current Task branch и active Milestone base
+совпадали с ним. Source должен быть exact `2.0.0-beta.12.N`, где `N >= 11` и `N` меньше patch
+ordinal текущего runner. Расхождение хотя бы одной поверхности блокирует transport.
+
+Остальные границы не изменены: ровно одна eligible Plan-integrity conflict, coherent observation,
+нет lease/transaction/Core operation, а dirty set полностью совпадает с уже доказанным failed Step
+scope. После `eligible=true` один dependency-only commit обновляет только `package.json` и
+`package-lock.json` на Milestone base и в Task history; fresh repository-local package затем
+регистрирует commit через advertised `update plan-integrity-dependency-recover`. Product bytes,
+Plan hash и remediation evidence не переписываются. Этот контракт разрешает текущий `.15 -> .17`
+transport и не требует нового literal для следующего совместимого beta.12 patch.
+
 ### beta.12.16: direct migration check-support authority
 
 Новый mechanical analyzer до execution authorization проверяет root `npm run` migration checks,

package/docs/validation-report.md

@@ -1,127 +1,103 @@
-# V2 beta.12.16 Validation Report
+# V2 beta.12.18 Validation Report
 
-Release candidate `2.0.0-beta.12.16` was validated on 2026-08-31 (Europe/Moscow) with
+Release candidate `2.0.0-beta.12.18` was validated on 2026-09-01 (Europe/Moscow) with
 Node.js 24.17.0.
 
 ## Automated release evidence
 
 - A clean `npm ci` completed from the exact lockfile and reported zero vulnerabilities.
-- `npm run validate` passed typecheck and `352/352` sequential tests with no failures, skips,
-  cancellations or todos in 2,166,261.797 ms.
-- The release-specific `npm run test:signal-t10-check-support-e2e` gate passed `6/6`. Its
-  Signal-shaped case reproduces the STEP-002 migration/check-support conflict, records one bounded
-  machine-derived scope extension, retries the same Step, passes checks and produces the Core-owned
-  Step commit without a Human replan.
-- Existing Signal compatibility gates remained green: `npm run test:signal-t04-recovery` passed
-  `11/11`, `npm run test:signal-t03-replan-e2e` passed `1/1`, and `npm run
-  test:signal-remediation-e2e` passed `2/2`.
-- Package dry-run passed with 284 files (approximately 1.1 MB packed and 4.4 MB unpacked). The
-  tarball contains the compiled `check-support-anchor` analyzer and its declaration/source map.
-- Disposable downstream installation returned `ok=true` for the exact beta.12.16 tarball. The first
-  sandboxed run failed only because registry DNS was unavailable; the exact network-enabled retry
-  passed.
-- `npm run plugin:check` passed. `npm run docs:pdf:check` reported `stale=[]` and the exact
-  beta.12.16 package binding.
-
-## Live Signal reproduction before installation
+- `npm run validate` passed typecheck and `354/354` sequential tests with no failures, skips,
+  cancellations or todos in 2,103,253.819 ms.
+- `npm run test:signal-t10-check-support-e2e` passed `8/8` in 148,470.477 ms. The added case
+  reproduces a historical v3 check-support decision, Knowledge rebind, explicit support-path adoption
+  by the new Plan and successful fresh navigation without `STATE_CORRUPT`.
+- `npm run test:signal-remediation-e2e` passed `2/2`.
+- `npm run pack:check` produced the exact `2.0.0-beta.12.18` tarball. The first sandboxed attempt
+  could not write npm cache; the identical escalated invocation passed. This was an environment
+  boundary, not a package failure.
+- `npm run smoke:downstream` installed the packed tarball into an empty project and returned
+  `ok=true`. The first sandboxed attempt could not resolve the npm registry; the identical network-
+  enabled invocation passed.
+- `npm run plugin:check`, `npm run docs:pdf:check` and `npm run release:check` all passed. The three
+  Russian PDFs were regenerated for beta.12.18, reported no stale outputs and were visually inspected
+  on their title and changed contract pages.
+
+## Live Signal evidence before publication
 
 The live repository was observed read-only at:
 
 - Task branch `codex/task-01m1b79c66-current-formalization-commit-and-provide`;
-- HEAD `f290d0875387283c368bedd03964fb423619db7b`;
-- repository-local package `codex-workflow-v2@2.0.0-beta.12.15`, protocol/schema `2/2`;
-- Task `TASK-01M1B79C660YMNSRRZ236NTR1T`, with the last recorded STEP-002 failure at Task revision
-  21.
-
-HEAD is the Core-owned STEP-001 commit. Its strict external review passed with sealed packet hash
-`c48658ce617bca58eddba4e11f43501eb87967d076e43bd4656f512ba256358f` and seal
-`31cfd03a8bd9f9ba21f067703db90da97102643901725718f3e88199e486d806`.
-
-The checkout still contains exactly the eight STEP-002 product paths present at the recorded
-`checks-failed` boundary:
-
-- `libs/processing-decision/ports/src/processing-persistence.ts`;
-- `libs/processing-decision/ports/src/index.ts`;
-- `libs/processing-decision/adapters/postgres/src/processing-evidence-transaction.ts`;
-- `libs/processing-decision/adapters/postgres/src/processing-evidence-transaction.spec.ts`;
-- `libs/processing-decision/adapters/postgres/src/processing-evidence-transaction.integration.spec.ts`;
-- `libs/processing-decision/adapters/postgres/migrations/0003_current_formalization_commits.sql`;
-- `libs/processing-decision/adapters/postgres/migrations/manifest.json`;
-- `libs/processing-decision/adapters/postgres/bootstrap/0000_roles_and_schema.sql`.
-
-Focused evidence and full affected validation passed for those product changes. The exact migration
-check failed because `tools/postgres/check-processing-migrations.ts` directly imports
-`tools/postgres/processing-migration-files.ts`, while the latter did not catalog the new migration
-and was outside STEP-002 `allowedWrites`. Repeating the approved check could not change that result.
-
-The beta.12.16 analyzer was then run read-only against this exact repository state. It derived one
-candidate and no broader scope:
-
-- runner: `tools/postgres/check-processing-migrations.ts`;
-- support authority: `tools/postgres/processing-migration-files.ts`;
-- expected output:
-  `libs/processing-decision/adapters/postgres/migrations/0003_current_formalization_commits.sql`;
-- reason: `CHECK_SUPPORT_ANCHOR_OUTSIDE_ALLOWED_WRITES`.
-
-Fresh beta.12.15 `status -> next` currently stops earlier at an expired writer lease and advertises
-only `locks repair`. No Signal lease, Workflow state, Git history, product file or chat was changed
-by this release-candidate reproduction. Live beta.12.16 recovery is intentionally not claimed until
-publication, installation, stale-lease repair and fresh repository-local readback.
+- HEAD `a34314d2613865767ef9adb37e7c12b4a12cd5c2`;
+- repository-local package `codex-workflow-v2@2.0.0-beta.12.17`, protocol/schema `2/2`;
+- Task `TASK-01M1B79C660YMNSRRZ236NTR1T`, revision 24, status
+  `awaiting_execution_authorization`;
+- current Plan hash `94fba18b423b795fc3b276166f9dec03a34fe3d0d2db73acf3c74dbf0e35f34b`;
+- planned `STEP-002-CURRENT-COMMIT`, which directly owns the derived check-support path;
+- exactly eight preserved STEP-002 product paths, with no support-module edit yet.
+
+beta.12.17 rejected fresh navigation with `STATE_CORRUPT`. Its v3 validator compared the historical
+check-support event against the current Plan. That event was valid under its recorded earlier Plan,
+but the current Plan now explicitly owned the same support path, so the old validation predicate
+became self-contradictory after the intended recovery sequence.
+
+The locally built external beta.12.18 runner then executed read-only
+`update plan-integrity-update-preflight` against the same state and returned:
+
+- `eligible=true` and `action=update plan-integrity-transport`;
+- `compatibilityMode=post-rebind-scope-adoption`;
+- source `2.0.0-beta.12.17`, target `2.0.0-beta.12.18`;
+- Task revision 24 and `STEP-002-CURRENT-COMMIT`;
+- the same eight dirty paths;
+- conflict hash `1bb6b0f7d1817024ff9c61a55ce3eda97169780265c3eea74f21643fcd9f487e`;
+- zero blockers.
+
+No Signal product byte, Git reference or Workflow-state artifact was changed by this live preflight.
 
 ## Root cause corrected
 
-Mechanical feasibility treated the migration, manifest and bootstrap files as the Step's complete
-output boundary, but did not model the repository-local module imported by the approved migration
-check as execution authority. That support module owns the exact migration list and SHA-256 catalog;
-therefore the new migration cannot pass its check until the support module changes as well.
-
-This is not a semantic Plan error and not evidence that the product implementation must be
-discarded. The missing path is mechanically derivable from executable code and exact file anchors.
-The old runtime nevertheless routed the first confirmed failure back to ordinary `task run`, where
-the Worker remained forbidden from editing the only file that could make the approved check pass.
-
-## Implemented contract
-
-- New analyzer `wf2.check-support-anchor@1` recognizes only a root `npm run` check, its
-  repository-local Node/tsx runner, one direct relative static import, and a support module whose
-  migration filename family plus SHA/catalog anchors bind an exact Plan-declared migration output.
-- For a future Plan, execution authorization fails closed when the producing Step does not own that
-  exact support path. This prevents the invalid scope from reaching execution.
-- For an already running guarded Step, the first exact `checks-failed` event may advertise `task
-  plan-integrity-recover`. Recovery revalidates Plan, Step, HEAD, complete dirty set, runner/support
-  hashes, direct import, missing declared output and existing evidence under the Workflow lock.
-- Recovery appends one `continue-fix` decision with the exact `scopeExtensions` path. It does not
-  change the Plan hash, product bytes, Git history or review result and does not synthesize a second
-  failed attempt.
-- Worker envelope, retry boundary, Core commit, downstream proof, corrective-replan worktree guard
-  and strict review packet all use the same effective Step scope. The original allowedWrites remain
-  canonical and the append-only decision is visible as derived authority.
-- The existing missing-script and selector-required cases retain `replan-required` and their
-  Human-confirmed corrective-replan route. Indirect imports, dynamic shell, unsupported syntax,
-  forbidden paths, unrelated dirty files, missing SHA/catalog anchors and multiple ambiguous
-  candidates remain fail-closed.
-
-## PDF release documentation evidence
-
-- All three tracked Russian PDFs were regenerated from beta.12.16 sources.
-- Architecture is 9 pages, delegated chat-only guide is 10 pages, and technical reference is 15
-  pages. All 34 rendered pages were visually inspected; no clipping, overlap or unreadable content
-  was observed.
+The defect was not the original migration check-support analyzer. beta.12.16 had already proved the
+missing imported support authority, and the new Plan correctly adopted that path. The remaining root
+cause was temporal validation: immutable evidence from Plan A was reinterpreted using Plan B's scope.
+Because Plan B intentionally fixed the scope omission, the validator classified the valid historical
+event as corrupt.
+
+beta.12.18 separates two authorities:
+
+- historical event integrity is checked against the Plan hash recorded by that event and its own
+  immutable hashes, conflicts, dirty set and remediation chain;
+- executable current scope comes only from the current Plan or a current-Plan event. Historical
+  evidence does not implicitly widen the new Step.
+
+## Implemented beta.12.18 contract
+
+- v3 check-support validation applies current Step scope predicates only when
+  `event.planHash === task.planHash`.
+- A bounded post-rebind compatibility candidate exists only while the Task awaits execution
+  authorization, no Step is running and C1 posture is empty.
+- Exactly one historical `continue-fix` check-support event must match the current unchanged dirty
+  worktree and a registered system commit.
+- The current planned Step must explicitly list every historical `scopeExtension` in both
+  `allowedWrites` and `expectedOutputs`.
+- Ordinary coherent-version, dependency-only commit, lease, transaction, Core-operation and dirty-
+  byte guards remain mandatory.
+- The route is advertised as `historical-check-support-scope-adoption-v1` and reports
+  `compatibilityMode=post-rebind-scope-adoption`.
+- Registration, Knowledge rebind, Plan Risk Audit and execution authorization remain separate fresh
+  Core-advertised transitions. The exact machine-proved recovery requires no Human approval.
 
 ## Boundaries and non-claims
 
-- The patch is not autonomous semantic replanning and does not permit a Worker to add an arbitrary
-  file after a failed check.
-- Scope augmentation is limited to one exact mechanically proved support authority for the current
-  migration-file family. A broader or ambiguous dependency remains an ordinary Plan conflict.
-- The patch does not weaken dirty-worktree, forbidden-scope, Plan identity, C1 authority, checks,
-  Core-owned commit or sealed strict-review gates.
-- This report does not claim commit/tag/push, npm publication, live beta.12.16 installation, live
-  STEP-002 recovery, STEP-002 commit/review, Task merge or Milestone completion before those
-  operations receive their own readback.
-
-Confidence is high for the bounded analyzer, preventive authorization and runtime recovery because
-the full 352-test gate, release-specific Signal E2E, legacy Signal gates and read-only live candidate
-agree. End-to-end confidence for the active Signal Task remains conditional on publication, exact
-repository-local installation, advertised stale-lease repair, fresh `status -> next`, Core recovery,
-the real approved checks and a new sealed external review packet.
+- The patch does not accept an arbitrary new Plan, extra support path, changed dirty byte, multiple
+  matching event, active lease or divergent version surface.
+- It does not mutate or rewrite the historical event and does not carry its scope into an unrelated
+  current Plan.
+- It does not bypass dependency-only Git transport, repository-local installation, Knowledge rebind,
+  Plan Risk Audit, checks, Core commit or external sealed review.
+- This report does not claim beta.12.18 commit/tag/push, npm publication, live installation into
+  Signal, STEP-002 commit/review, Task merge or Milestone completion until each operation receives its
+  own readback.
+
+Confidence is high for the defect classification and compatibility preflight: the full `354/354`
+gate, focused `8/8` Signal suite and read-only live Signal state agree. End-to-end confidence remains
+conditional on publication, exact dependency-only transport into Signal, fresh Core routing, the real
+approved checks and the user-authorized new sealed reviewer chat.

package/package.json

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