codex-workflow-v2 2.0.0-beta.12.17 → 2.0.0-beta.12.19

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

@@ -1,10 +1,10 @@
 ---
-title: Codex Workflow V2: архитектура beta.12.17
+title: Codex Workflow V2: архитектура beta.12.19
 subtitle: Источники истины, lifecycle, роли, delegation, зависимости Tasks и границы доверия
 part: Часть 1 из 3 | Архитектура
 document_version: 2.0
-date: 31 августа 2026
-subject: Архитектура и границы Codex Workflow V2 beta.12.17
+date: 1 сентября 2026
+subject: Архитектура и границы Codex Workflow V2 beta.12.19
 ---
 
 # 1. Назначение и граница системы
@@ -18,7 +18,7 @@ Codex Workflow V2 - локальный state machine поверх Codex App, Git
 Система рассчитана на одного пользователя и одну машину. Она не предоставляет distributed locking,
 криптографическую идентификацию actor string или безопасную синхронизацию state между компьютерами.
 
-## 1.1. Что beta.12.17 гарантирует
+## 1.1. Что beta.12.19 гарантирует
 
 - exact project-local npm package и совместимый handshake до lifecycle действий;
 - Discovery до materialization Task или Milestone;
@@ -40,8 +40,14 @@ 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 случая отсутствуют.
+- после dependency registration и Knowledge rebind один общий fail-closed assessor управляет и
+  навигацией, и `task run`: переносится только точный dirty set с тем же content hash, registered HEAD,
+  непрерывной Plan/rebind chain и явным scope текущей Step; drift переводит route в `doctor`.
 
-## 1.2. Что beta.12.17 не гарантирует
+## 1.2. Что beta.12.19 не гарантирует
 
 - правильность продуктовой идеи или автоматически выбранного provider Task;
 - semantic sufficiency Plan, если точные факты нельзя доказать поддерживаемым analyzer;
@@ -354,6 +360,19 @@ locked, installed, current Task branch и active Milestone base и допуск
 версии ниже 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 и не модифицируется задним числом.
+
+beta.12.19 закрывает оставшийся execution-boundary разрыв. Успешные transport, rebind, PRA и
+authorization больше не заканчиваются рекламируемым, но невыполнимым `task run`: `next` и `runStep`
+используют одну проверку registered recovery commit, exact dirty paths/content hash, historical
+decision, Plan/rebind ancestry и current Step ownership. Совпадение разрешает только принятие уже
+доказанных байтов; любое отличие блокирует запуск и не создаёт lease или commit.
+
 Docker socket `EPERM` в sandbox не является доказательством сломанного daemon. Gateway один раз
 повторяет exact health probe или Plan check с sandbox escalation без расходования remediation attempt.
 Restart Docker Desktop требует отдельного разрешения и допустим только после escalated daemon failure.
@@ -363,7 +382,7 @@ Restart Docker Desktop требует отдельного разрешения
 # 10. Operational checklist
 
 - exact package version установлен, bundled gateway соответствует release и переустановлен;
-- handshake подтверждает protocol 2, state schema 2 и beta.12.17 capabilities;
+- handshake подтверждает protocol 2, state schema 2 и beta.12.19 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.17 путь от нового Discovery до принятого Milestone без ручного CLI
+subtitle: Актуальный beta.12.19 путь от нового Discovery до принятого Milestone без ручного CLI
 part: Часть 2 из 3 | Практика
 document_version: 2.0
-date: 31 августа 2026
-subject: Практическое руководство по delegated Discovery и Milestone в Workflow V2 beta.12.17
+date: 1 сентября 2026
+subject: Практическое руководство по delegated Discovery и Milestone в Workflow V2 beta.12.19
 ---
 
-# 1. Рабочая модель beta.12.17
+# 1. Рабочая модель beta.12.19
 
 Пользователь работает в одном 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.17 как точную devDependency после публикации release.
+2. Установите beta.12.19 как точную 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.17 должен сообщать `packageVersion=2.0.0-beta.12.17`, `protocolVersion=2`,
+Handshake beta.12.19 должен сообщать `packageVersion=2.0.0-beta.12.19`, `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.17 в delegated режиме.
+Проведи новый Milestone через Codex Workflow V2 beta.12.19 в delegated режиме.
 Repository: <ABSOLUTE-REPOSITORY-ROOT>.
 Milestone ID: AUTO.
 Delegate actor: agent:milestone-coordinator.
@@ -299,7 +299,9 @@ 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.17 external preflight выводит coherent exact beta.12 source из пяти version surfaces; затем только dependency-only transport и advertised recovery |
+| In-flight Plan-integrity Task требует package update | beta.12.19 external preflight выводит coherent exact beta.12 source из пяти version surfaces; затем только dependency-only transport и advertised recovery |
+| Новый Plan явно принял ранее derived check-support path, но старый event выглядит corrupt | beta.12.19 external preflight требует exact post-rebind scope adoption и неизменные dirty bytes; затем dependency-only transport, Knowledge rebind, PRA и fresh authorization без Human gate |
+| После rebind и authorization `next` показывает `task run`, но checkout содержит сохранённые Step bytes | Продолжать только если beta.12.19 `next` показывает `planIntegrityDirtyCarryover.state=validated`; HEAD, Plan chain, paths и content hash уже проверены Core. При `doctor` запуск запрещён |
 | 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 остаётся диагностикой |
@@ -409,7 +411,7 @@ Task/project DGR. `dependencyBinding` для standalone handoff равен null.
 
 # 14. Итоговый checklist пользователя
 
-- beta.12.17 exact package и новый bundled gateway установлены;
+- beta.12.19 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.17
+title: Codex Workflow V2: технический справочник beta.12.19
 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.17
+date: 1 сентября 2026
+subject: Технический контракт Codex Workflow V2 beta.12.19
 ---
 
 # 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.17 | Значение |
+| Параметр beta.12.19 | Значение |
 |---|---|
-| npm package | `codex-workflow-v2@2.0.0-beta.12.17` |
+| npm package | `codex-workflow-v2@2.0.0-beta.12.19` |
 | 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.17 capabilities:
+Ключевые beta.12.19 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`, `historical-check-support-dirty-carryover-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 или соседней
@@ -527,6 +527,39 @@ repository-local runner регистрирует commit только через
 `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 не нужен.
+
+# 13.10. beta.12.19 historical check-support dirty carryover
+
+После регистрации dependency recovery current Plan может быть ещё раз mechanically rebound и
+авторизован, тогда как product bytes остаются uncommitted. Запуск разрешён только при едином
+assessment для `next` и `runStep`: latest compatible dependency record должен быть зарегистрирован на
+точной history boundary; его Plan должен совпадать с current Plan или вести к нему через непрерывную
+Knowledge-rebind chain; planned Step должна владеть каждым dirty path и каждым `scopeExtension`; full
+path set и `hashDirtyWorktree` должны совпадать; один validated historical check-support decision
+должен связывать те же conflict/remediation/scope fields.
+
+При полном совпадении `next` публикует
+`planIntegrityDirtyCarryover.state=validated`, а `task run` принимает только эти байты под current
+Step envelope. При любом расхождении `next` возвращает `doctor` с `blockedAction=task run`; lease,
+Step mutation и commit не создаются. Для обновления уже авторизованной beta.12.18 Task внешний
+beta.12.19 runner выдаёт `compatibilityMode=post-rebind-dirty-carryover`, после чего сохраняются
+обычный dependency-only transport, repository-local registration, Knowledge rebind, PRA,
+authorization, checks, Core commit и sealed review. Human approval не добавляется.
+
 # 14. P04-A structural replacement boundary
 
 Command shape `task replacement-materialize` retained только для compatibility diagnostics. Любая попытка
@@ -589,7 +622,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.17
+# 18. Public command surface beta.12.19
 
 | Область | Actions |
 |---|---|
@@ -620,7 +653,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.17 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.19 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.17, the release gate also relies on `npm run release:check` to fail if:
+For beta.12.19, 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;
@@ -68,6 +68,10 @@ For beta.12.17, the release gate also relies on `npm run release:check` to fail
   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,52 @@ state schema. Совпадение `stateSchemaVersion` до и после об
 нужна. Для alpha.6 при `stateSchemaVersion: 2` применяется не migration, а sidecar-only
 adoption posture.
 
+### beta.12.19: hash-bound check-support dirty carryover at Task run
+
+beta.12.18 could validate and transport a historical check-support recovery through a new Plan, but
+the final execution boundary still applied the ordinary clean-checkout rule. Consequently fresh
+`next` advertised `task run` after dependency registration, Knowledge rebind, Risk Audit and
+authorization, while the same `task run` rejected the preserved product bytes.
+
+beta.12.19 gives navigation and execution one shared fail-closed assessment. Carryover is valid only
+when the latest registered Plan-integrity dependency record binds the current history boundary, the
+current Plan is that record's Plan or its exact Knowledge-rebind descendant, the planned Step owns
+every dirty path, every derived support path is explicit in both `allowedWrites` and
+`expectedOutputs`, and the full dirty file list and content hash still match the validated historical
+decision. `next` then reports `planIntegrityDirtyCarryover.state=validated`; `task run` may adopt
+exactly those bytes. Any mismatch changes `next` to `doctor` and leaves execution blocked.
+
+An in-flight beta.12.18 Task already in the authorized dirty-carryover posture may use external exact
+beta.12.19 `update plan-integrity-update-preflight`. It returns
+`compatibilityMode=post-rebind-dirty-carryover` only when the existing registration and all ordinary
+version, Git, lease, transaction and Core-operation guards pass. Continue only through the reported
+dependency-only transport and fresh repository-local routes. No Human approval is introduced for
+this exact machine-proved continuation; checks, Core commit and external sealed review remain
+mandatory.
+
+### 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 с одним

package/docs/validation-report.md

@@ -1,105 +1,101 @@
-# V2 beta.12.17 Validation Report
+# V2 beta.12.19 Validation Report
 
-Release candidate `2.0.0-beta.12.17` was validated on 2026-09-01 (Europe/Moscow) with
+Release candidate `2.0.0-beta.12.19` 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 `353/353` sequential tests with no failures, skips,
-  cancellations or todos in 2,273,062.454 ms.
-- `npm run test:signal-t10-check-support-e2e` passed `7/7`. It includes the Signal-shaped
-  check-support recovery and two complete update/recovery chains whose coherent source is
-  `2.0.0-beta.12.11` and `2.0.0-beta.12.15`, respectively.
-- The `.15` case proves read-only update preflight, exact dependency-only transport, dependency
-  provenance registration, Plan-integrity recovery, retry and continuation without product-byte
-  loss or a Human replan for the machine-proved support scope.
-- Existing Signal compatibility remained green inside the full suite, including T04 retained
-  review/history recovery, T03 corrective replan, audited remediation topology, downstream proof
-  and dependency-only update recovery.
-
-## Live Signal evidence before installation
-
-The live repository was observed at:
+- `npm run validate` passed typecheck and `354/354` sequential tests with no failures, skips,
+  cancellations or todos in 2,187,446.915 ms.
+- `npm run test:signal-t10-check-support-e2e` passed `8/8` in 181,400.886 ms. Its extended
+  Signal-shaped case executes the complete beta.12.18-to-beta.12.19 sequence: historical check-
+  support recovery, explicit scope adoption, dependency-only update preflight and transport, Core
+  dependency registration, Knowledge rebind, fresh Risk Audit and authorization, dirty-byte adoption,
+  checks and Core-owned Step commit. A one-byte mutation changes fresh navigation to `doctor`.
+- `npm run test:signal-remediation-e2e` passed `2/2` in 9,136.908 ms.
+- `npm run pack:check` produced the exact `2.0.0-beta.12.19` tarball with 284 files. The first
+  sandboxed attempt could not write the user npm cache; the identical cache-enabled invocation
+  passed. This was an environment boundary, not a package failure.
+- `npm run smoke:downstream` packed the release, installed it 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.19, reported no stale outputs and were visually inspected
+  on their title and changed contract pages with no clipping, overlap or broken tables.
+- `git diff --check` passed for the release patch.
+
+## Live Signal evidence before publication
+
+The live repository was observed without changing product files, Git references or Workflow state 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`, revision 21, failed Step
-  `STEP-002-CURRENT-COMMIT`;
-- exactly eight preserved STEP-002 product paths and no pending/corrupt Core transaction.
-
-The stale writer lease was repaired only through the exact repository-level `locks repair` route.
-Fresh beta.12.15 `status -> next` then reproduced the original defect: `next` advertised only
-`task run`, although the Worker could not write the imported migration support authority.
-
-Published beta.12.16 correctly identified the check-support conflict, but its external
-`update plan-integrity-update-preflight` returned `eligible=false`: the implementation still required
-all five version surfaces to equal the hard-coded stranded source `2.0.0-beta.12.11`. Signal already
-had coherent `.15` declared, locked, installed, current-branch and Milestone-base versions. No update
-commit, package installation, Workflow-state edit or product-file mutation was performed after that
-failed preflight.
-
-The beta.12.17 runner was then built locally and invoked read-only against the same Signal state. It
-returned:
-
-- `eligible=true` and `action=update plan-integrity-transport`;
-- source `2.0.0-beta.12.15`, target `2.0.0-beta.12.17`;
-- Task revision 21 and `STEP-002-CURRENT-COMMIT`;
-- the same eight dirty paths;
-- conflict hash `44ee553355bc696861bd2e4f49c1675e39c7cf4e5be28785e2f86cd95de45383`;
-- zero blockers.
-
-## Root causes corrected
-
-beta.12.16 corrected the product-flow root cause: the Plan and retry boundary did not model the
-directly imported checksum/catalog module as authority required by the approved migration check.
-The bounded analyzer and append-only scope augmentation remain unchanged in beta.12.17.
-
-The installation blocker had a separate root cause. Plan-integrity update preflight encoded one
-historical release literal instead of deriving the source version from the repository surfaces it
-already inspected. Every compatible patch after `.11` therefore became impossible to transport
-while failed-Step product work remained dirty.
-
-## Implemented beta.12.17 contract
-
-- `planIntegrityUpdatePreflight` derives `sourceVersion` from the declared exact dependency.
-- Source must match `2.0.0-beta.12.N`, with `N >= 11` and `N` strictly less than the external
-  runner's beta.12 patch ordinal.
-- Locked, installed, current Task branch and active Milestone base must equal the declared source.
-  Missing or divergent surfaces block transport with an exact diagnostic.
-- Existing guards remain mandatory: one eligible Plan-integrity conflict, coherent observation,
-  no active/stale lease, no pending/corrupt transaction or Core operation, and an exact dirty set
-  inside the failed Step boundary.
-- The only allowed transport remains one dependency-only commit changing `package.json` and
-  `package-lock.json` on the Milestone base and in Task history. Fresh repository-local Core must
-  register it through advertised `update plan-integrity-dependency-recover`.
-- The contract is advertised as `coherent-plan-integrity-update-source-v1`. It is deliberately
-  limited to the compatible beta.12 line and does not create generic update or product-history
-  adoption authority.
-
-## Retained check-support contract
-
-- `wf2.check-support-anchor@1` blocks a future Plan whose producing migration Step does not own the
-  directly imported SHA/catalog support authority.
-- For the already-running exact first-failure shape, `task plan-integrity-recover` appends one
-  `continue-fix` decision with the derived support path; Plan hash and product bytes remain stable.
-- Worker envelope, retry boundary, Core commit, downstream proof, corrective-replan guard and sealed
-  review packet use and disclose the same effective scope.
-- Indirect/dynamic imports, unsupported syntax, forbidden paths, unrelated dirty files or absent
-  anchors remain fail-closed. Missing scripts and selector-required checks retain their ordinary
-  `replan-required` path.
+- HEAD `c9dc805911f5b1dfb026ca03411f86bd72ba259f`;
+- repository-local package `codex-workflow-v2@2.0.0-beta.12.18`, protocol/schema `2/2`;
+- Task `TASK-01M1B79C660YMNSRRZ236NTR1T`, revision 27, status `ready`;
+- current Plan hash `c9ebe850ae7504db3621442cb4a3dfa6cf7a77a421a5f61f7cbcbcde31eddc5b`;
+- planned `STEP-002-CURRENT-COMMIT`, whose current Plan directly owns all eight preserved product
+  paths plus `tools/postgres/processing-migration-files.ts` as the derived support path;
+- dirty worktree hash `a53ae309e2b79a4255b0f02e45612f8c8570f7f0a0ea91f3e761979904161277`;
+- no active writer lease.
+
+beta.12.18 fresh `next` advertised `task run`. Invoking that exact route failed before credential
+issuance with `GIT_PRECONDITION_FAILED`: the planned Step was still forced through the ordinary clean-
+checkout precondition, which listed the same eight product paths preserved by the registered recovery.
+No Task revision, Step state, lease, credential or repository byte changed on that failure.
+
+The locally built external beta.12.19 runner then performed two read-only observations against the
+same state:
+
+- `next` kept `action=task run` but added
+  `planIntegrityDirtyCarryover.state=validated`, the exact eight paths, their content hash, registered
+  recovery commit and exact support scope extension;
+- `update plan-integrity-update-preflight` returned `eligible=true`,
+  `action=update plan-integrity-transport`, source `2.0.0-beta.12.18`, target
+  `2.0.0-beta.12.19`, `compatibilityMode=post-rebind-dirty-carryover` and zero blockers.
+
+## Root cause corrected
+
+beta.12.18 repaired historical evidence validation and update transport, but did not connect that
+authority to the final execution admission. Navigation could prove the recovery sequence coherent,
+while `runStep` independently knew only ordinary clean checkout, corrective retry and downstream-
+proof carryover. The result was an advertised-but-rejected transition after every required recovery
+action had succeeded.
+
+beta.12.19 introduces one shared fail-closed check-support dirty-carryover assessment for navigation,
+external update compatibility and execution admission. This is not a generic dirty-checkout bypass.
+
+## Implemented beta.12.19 contract
+
+- The latest compatible dependency recovery record must bind the exact registered history boundary.
+- Its Plan must equal the current Plan or reach it through the recorded Knowledge-rebind chain.
+- Exactly one validated historical v3 `continue-fix` decision must bind the same conflict,
+  remediation events, dirty set and derived scope extensions.
+- The complete current dirty path set and `hashDirtyWorktree` must equal the registered binding.
+- The planned Step must have no evidence, no other Step may be running, and every dirty path must be
+  inside its current `allowedWrites`.
+- Every derived support path must be explicit in both current `allowedWrites` and `expectedOutputs`.
+- Fresh `next` reports `planIntegrityDirtyCarryover.state=validated` only when `runStep` will accept
+  the same exact bytes. Any mismatch reports `doctor` with `blockedAction=task run`.
+- An already authorized beta.12.18 Task can use the ordinary dependency-only update bridge with
+  `compatibilityMode=post-rebind-dirty-carryover`; after registration, Knowledge rebind, Risk Audit and
+  authorization remain fresh Core-advertised transitions.
+- Capability `historical-check-support-dirty-carryover-v1` exposes the contract in the packaged
+  handshake. No Human approval is added for this exact machine-proved continuation.
 
 ## Boundaries and non-claims
 
-- The patch does not bypass dependency-only Git transport or permit installation while version
-  surfaces diverge.
-- It does not edit Plan, product work, Workflow state or Git history during preflight.
-- This report does not claim beta.12.17 commit/tag/push, npm publication, live installation,
-  dependency registration, STEP-002 commit/review, Task merge or Milestone completion until each
-  operation receives its own readback.
-
-Confidence is high for source-version consensus and retained check-support recovery because the
-353-test gate, both source-version E2E chains and the read-only live Signal preflight agree. Final
-end-to-end confidence remains conditional on exact publication, dependency-only transport into
-Signal, repository-local recovery, the real approved checks and a new sealed reviewer packet.
+- The patch does not accept an arbitrary dirty file, content change, unregistered commit, unrelated
+  Plan, missing explicit scope, malformed sidecar, multiple historical match or active transaction.
+- It does not mutate historical evidence, rewrite Git, manually edit Workflow state or implicitly
+  widen Step scope.
+- It does not bypass repository-local installation, Knowledge rebind, Risk Audit, authorization,
+  approved checks, Core commit, strict Step review or external sealed review.
+- This report does not claim beta.12.19 commit/tag/push, npm publication, live installation into
+  Signal, STEP-002 review, Task merge or Milestone completion until those operations receive their
+  own readback.
+
+Confidence is high for the defect classification and package behavior: full `354/354`, focused
+`8/8`, tamper-to-doctor E2E and read-only live Signal observations agree. End-to-end confidence in
+the active Milestone remains conditional on publication, exact dependency-only installation, the
+real approved checks and the user-authorized external sealed reviewer chat.

package/package.json

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