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

package/docs/autonomy-guardrails.md

@@ -145,25 +145,28 @@ commit, or unverified recovery remains blocked.
 
 ### First-failure Plan-integrity recovery
 
-A mechanically impossible Plan check must not consume the second ordinary remediation attempt
-only to unlock corrective replan. After the first guarded `checks-failed` event, Core performs a
-read-only bounded assessment. `next` advertises `task plan-integrity-recover` only when all of the
-following are true:
-
-- the failed Step contains an exact root `npm run <script>` or `npm run-script <script>` check;
-- the named script is absent from the current root `package.json`;
-- `package.json` is outside the failed Step's `allowedWrites`;
+A mechanically impossible Plan check must not consume another attempt merely to unlock its known
+correction. After the first guarded `checks-failed` event, Core performs a read-only bounded
+assessment. Existing missing-script and required-selector conflicts route to corrective replan.
+beta.12.16 additionally recognizes one exact check-support conflict when all of the following hold:
+
+- the failed Step contains an exact root `npm run <script>` check and declares an absent migration
+  output path that is inside its original `allowedWrites`;
+- the root script resolves to a repository-local runner whose direct static import resolves to a
+  tracked checksum/catalog support module;
+- that support module has SHA-256 anchors and names an existing migration in the same file family,
+  but is outside the Step's `allowedWrites` and `forbiddenScope`;
 - exactly one ordinary `checks-failed` remediation event exists for the Step;
 - no corrective decision exists for its second-attempt binding;
 - every dirty file remains inside the Step's current `allowedWrites` and outside its
   `forbiddenScope`.
 
-The recovery appends one hash-bound `replan-required` decision for attempt ordinal 2. It preserves
-the worktree and does not edit the Plan. A claimed C1 Task must present its current writer token and
-then follow `task corrective-yield`; the replacement Plan still requires the existing independent
-validation, Risk Audit, Human confirmation, journaled execution, readback, and renewed execution
-authorization. Other check failures use the normal continuable remediation route; they do not
-receive the narrow Plan-integrity shortcut, but attempt count alone never stops them.
+The recovery appends one hash-bound `continue-fix` decision for attempt ordinal 2 and the exact
+support path. It preserves the worktree and Plan hash; it does not alter source or Git. The current
+C1 actor presents the existing writer token and fresh `task run` exposes the effective scope.
+`task step-complete` remains the only commit owner, all checks rerun, and strict review packets name
+the derived scope. Missing-script/selector conflicts still use `replan-required` plus the normal
+Human-confirmed corrective replan. Unproved or broader scope changes never receive this authority.
 
 ### Downstream-proof predecessor recovery
 

package/docs/development-flow.md

@@ -93,13 +93,13 @@ executable. A reviewer routes to `replan` only with an exact Plan obstruction an
 change; ordinary findings default to `fix`. Remediation cannot change the Task objective,
 requirements, or acceptance.
 
-One bounded exception avoids a deliberately repeated failure for an older authorization without
-P01-A evidence or a contradiction that becomes observable only after execution starts. If the first guarded check failure
-is caused by an absent root npm script that the Step cannot add because `package.json` is outside
-its `allowedWrites`, fresh `next` advertises `task plan-integrity-recover`. The command records only
-the exact evidence-bound early `replan-required` posture; it never edits source, Plan, or Git.
-Continue through the advertised corrective yield and corrective replan rather than calling
-`task run` again.
+One bounded exception avoids deliberately repeating an already-proved Plan-integrity failure.
+Missing root scripts and missing mandatory selectors use the advertised evidence-bound
+`replan-required` path. For beta.12.16's exact direct check-support case, fresh `next` instead binds
+the imported SHA/catalog support module and records a machine-derived `continue-fix` scope. Continue
+with fresh `task run`; its envelope contains the original Step paths plus that one support path.
+Core still owns the commit and review packet. Do not add adjacent files or treat this as generic
+permission to change the Plan.
 
 If a later proof Step leaves changes both in its own scope and in files owned by a completed
 transitive predecessor, fresh `next` advertises `task downstream-proof-recover` instead of

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

@@ -1,10 +1,10 @@
 ---
-title: Codex Workflow V2: архитектура beta.12.15
+title: Codex Workflow V2: архитектура beta.12.17
 subtitle: Источники истины, lifecycle, роли, delegation, зависимости Tasks и границы доверия
 part: Часть 1 из 3 | Архитектура
 document_version: 2.0
 date: 31 августа 2026
-subject: Архитектура и границы Codex Workflow V2 beta.12.15
+subject: Архитектура и границы Codex Workflow V2 beta.12.17
 ---
 
 # 1. Назначение и граница системы
@@ -18,7 +18,7 @@ Codex Workflow V2 - локальный state machine поверх Codex App, Git
 Система рассчитана на одного пользователя и одну машину. Она не предоставляет distributed locking,
 криптографическую идентификацию actor string или безопасную синхронизацию state между компьютерами.
 
-## 1.1. Что beta.12.15 гарантирует
+## 1.1. Что beta.12.17 гарантирует
 
 - exact project-local npm package и совместимый handshake до lifecycle действий;
 - Discovery до materialization Task или Milestone;
@@ -41,7 +41,7 @@ Codex Workflow V2 - локальный state machine поверх Codex App, Git
   один additive remediation Task без нового Human gate; Core сохраняет Milestone semantics и выводит
   authority из текущей Milestone authorization и exact audit evidence.
 
-## 1.2. Что beta.12.15 не гарантирует
+## 1.2. Что beta.12.17 не гарантирует
 
 - правильность продуктовой идеи или автоматически выбранного provider Task;
 - semantic sufficiency Plan, если точные факты нельзя доказать поддерживаемым analyzer;
@@ -337,6 +337,23 @@ Completed corrective-replan journal также остаётся читаемым
 если его завершённый manifest/runtime/catalog tuple есть в append-only historical registry. Pending и
 неизвестные identity по-прежнему fail-closed, поэтому compatibility не выдаёт новую authority.
 
+beta.12.16 закрывает следующий доказанный разрыв: migration Step мог владеть новой SQL migration,
+manifest и bootstrap, но не владеть TypeScript-модулем, который direct import из обязательного check
+использовал как независимую SHA/catalog authority. Новый `wf2.check-support-anchor@1` блокирует такой
+Plan до execution authorization. Для уже выполняемой Task после первого `checks-failed` Core связывает
+Plan/Step/HEAD, полный dirty set, runner/support hashes, direct import, отсутствующий declared output и
+существующие anchors. Если доказательство однозначно, append-only decision `continue-fix` выдаёт только
+один exact support path как effective Step scope. Human replan не нужен, Plan hash и product bytes не
+меняются, а Worker envelope, Core commit и sealed review packet явно используют и раскрывают derived
+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 вручную не изменяются.
+
 Docker socket `EPERM` в sandbox не является доказательством сломанного daemon. Gateway один раз
 повторяет exact health probe или Plan check с sandbox escalation без расходования remediation attempt.
 Restart Docker Desktop требует отдельного разрешения и допустим только после escalated daemon failure.
@@ -346,7 +363,7 @@ Restart Docker Desktop требует отдельного разрешения
 # 10. Operational checklist
 
 - exact package version установлен, bundled gateway соответствует release и переустановлен;
-- handshake подтверждает protocol 2, state schema 2 и beta.12.15 capabilities;
+- handshake подтверждает protocol 2, state schema 2 и beta.12.17 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.15 путь от нового Discovery до принятого Milestone без ручного CLI
+subtitle: Актуальный beta.12.17 путь от нового Discovery до принятого Milestone без ручного CLI
 part: Часть 2 из 3 | Практика
 document_version: 2.0
 date: 31 августа 2026
-subject: Практическое руководство по delegated Discovery и Milestone в Workflow V2 beta.12.15
+subject: Практическое руководство по delegated Discovery и Milestone в Workflow V2 beta.12.17
 ---
 
-# 1. Рабочая модель beta.12.15
+# 1. Рабочая модель beta.12.17
 
 Пользователь работает в одном 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.15 как точную devDependency после публикации release.
+2. Установите beta.12.17 как точную 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.15 должен сообщать `packageVersion=2.0.0-beta.12.15`, `protocolVersion=2`,
+Handshake beta.12.17 должен сообщать `packageVersion=2.0.0-beta.12.17`, `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.15 в delegated режиме.
+Проведи новый Milestone через Codex Workflow V2 beta.12.17 в delegated режиме.
 Repository: <ABSOLUTE-REPOSITORY-ROOT>.
 Milestone ID: AUTO.
 Delegate actor: agent:milestone-coordinator.
@@ -298,6 +298,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.17 external preflight выводит coherent exact beta.12 source из пяти version surfaces; затем только dependency-only transport и advertised recovery |
 | 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 остаётся диагностикой |
@@ -313,6 +315,9 @@ Task chat записывает его только при совпадении p
 | Review seal drift | Discard review и создать fresh packet |
 
 Plan-integrity recovery не редактирует Plan, package.json или worktree и не синтезирует второй failure.
+Для beta.12.16 check-support evidence fresh `task run` обязан показать `boundedEffect=record-machine-derived-check-support-scope`
+и добавить ровно рекламируемый support path в Worker `allowedWrites`. Для иных Plan-integrity видов
+сохраняется `replan-required` route.
 P04-A не переносит completed Steps и не rewires dependencies при split.
 
 Audited remediation beta.12.11 не является generic scope-change. Coordinator использует только exact
@@ -404,7 +409,7 @@ Task/project DGR. `dependencyBinding` для standalone handoff равен null.
 
 # 14. Итоговый checklist пользователя
 
-- beta.12.15 exact package и новый bundled gateway установлены;
+- beta.12.17 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.15
+title: Codex Workflow V2: технический справочник beta.12.17
 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.15
+subject: Технический контракт Codex Workflow V2 beta.12.17
 ---
 
 # 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.15 | Значение |
+| Параметр beta.12.17 | Значение |
 |---|---|
-| npm package | `codex-workflow-v2@2.0.0-beta.12.15` |
+| npm package | `codex-workflow-v2@2.0.0-beta.12.17` |
 | 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.15 capabilities:
+Ключевые beta.12.17 capabilities:
 
 | Группа | Capabilities |
 |---|---|
@@ -496,6 +496,37 @@ legacy tuple у незавершённой transaction, повреждённый
 `journal-invalid`. Это позволяет читать terminal beta.12.12 history после расширения binding manifest,
 не превращая legacy identity в новую execution authority.
 
+# 13.7. beta.12.16 check-support scope authority
+
+Analyzer `wf2.check-support-anchor@1` рассматривает только root `npm run` check, repository-local
+`node`/`tsx` runner и его direct relative static import. Блокировка допустима, когда Step создаёт
+отсутствующий exact migration output, импортированный support-модуль содержит SHA-256 и approved/
+expected/manifest/catalog anchors той же `.sql` family, но Step не владеет support path. Это machine
+evidence, а не вывод из текста ошибки.
+
+Для pre-execution Plan finding `CHECK_SUPPORT_ANCHOR_OUTSIDE_ALLOWED_WRITES` блокирует authorization.
+Для уже выполняемой guarded Step первый `checks-failed` может рекламировать тот же
+`task plan-integrity-recover`, но evidence v3 записывает `continue-fix`, а не `replan-required`.
+`scopeExtensions` равно отсортированному exact набору support paths из conflict evidence; dirty files
+до recovery обязаны оставаться в original allowedWrites, support path не может пересекать
+forbiddenScope. Plan hash не меняется. Effective scope используется retry precondition, Worker envelope,
+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.
+
 # 14. P04-A structural replacement boundary
 
 Command shape `task replacement-materialize` retained только для compatibility diagnostics. Любая попытка
@@ -558,7 +589,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.15
+# 18. Public command surface beta.12.17
 
 | Область | Actions |
 |---|---|
@@ -589,7 +620,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.15 tag обязательны `npm ci`, `npm run validate`, `npm run test:signal-remediation-e2e`, `npm run pack:check`,
+Перед 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`,
 `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

@@ -10,14 +10,15 @@ Before tagging a release:
 
 1. `npm ci`
 2. `npm run validate`
-3. `npm run test:signal-remediation-e2e`
-4. `npm run pack:check`
-5. `npm run smoke:downstream`
-6. `npm run plugin:check`
-7. `npm run docs:pdf:check`
-8. `npm run release:check`
-9. validate `plugins/codex-workflow-gateway` with the Codex plugin validator
-10. validate the append-only real-agent log with
+3. `npm run test:signal-t10-check-support-e2e`
+4. `npm run test:signal-remediation-e2e`
+5. `npm run pack:check`
+6. `npm run smoke:downstream`
+7. `npm run plugin:check`
+8. `npm run docs:pdf:check`
+9. `npm run release:check`
+10. validate `plugins/codex-workflow-gateway` with the Codex plugin validator
+11. validate the append-only real-agent log with
    `node scripts/validate-lifecycle-transcript.mjs --file <lifecycle-log.jsonl>`
 
 The downstream smoke packs the actual tarball, installs it into an empty temporary project,
@@ -28,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.17, 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;
@@ -60,6 +61,13 @@ 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.
 - 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,40 @@ state schema. Совпадение `stateSchemaVersion` до и после об
 нужна. Для alpha.6 при `stateSchemaVersion: 2` применяется не migration, а sidecar-only
 adoption posture.
 
+### 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,
+repository-local `node`/`tsx` runner и его direct static relative imports. Если Step создаёт новую
+SQL migration, а импортированный TypeScript/JavaScript support-модуль закрепляет approved SHA-256,
+manifest или expected catalog той же migration family, этот support path должен входить в
+`allowedWrites` той же Step. Иначе Plan возвращается к `task plan-set` до запуска Worker.
+
+Для уже выполняемой Task с первым `checks-failed` fresh beta.12.16 `next` может рекламировать
+`task plan-integrity-recover` с reason `CHECK_SUPPORT_ANCHOR_OUTSIDE_ALLOWED_WRITES` и
+`boundedEffect=record-machine-derived-check-support-scope`. Выполните только этот route под текущим
+C1 actor/writer credential, затем снова прочитайте `next` и вызовите `task run`. Worker envelope
+должен добавить ровно `evidence.scopeExtensions`; Plan hash и существующие product bytes остаются
+неизменными. Core повторяет все checks, сам создаёт commit и включает derived scope в sealed review
+packet. Human corrective-replan для этого точного scope-only случая не требуется. Если route не
+рекламируется, есть indirect/dynamic import, лишний dirty path, forbiddenScope intersection или нет
+SHA/catalog anchors — не расширяйте scope вручную.
+
 ### beta.12.12: неисполняемая Step check и сохранение текущей реализации
 
 Новые Plans больше не могут получить execution authorization, если root npm script запускает

package/docs/validation-report.md

@@ -1,107 +1,105 @@
-# V2 beta.12.15 Validation Report
+# V2 beta.12.17 Validation Report
 
-Release candidate `2.0.0-beta.12.15` was validated on 2026-08-31 (Europe/Moscow) with
+Release candidate `2.0.0-beta.12.17` 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.
-- The first full `npm run validate` run passed every behavioral assertion except two diagnostics
-  whose text still described the superseded one-commit boundary. The messages were corrected without
-  changing transition behavior. The second full run passed typecheck and `349/349` sequential tests
-  with no failures, skips, cancellations or todos in 2,169,018.255 ms.
-- The focused dependency-provenance suite passed `11/11`. It covers a two-commit unregistered
-  dependency suffix, exact oldest-to-newest recovery, per-commit package-version provenance and
-  fail-closed product/payload/ancestry drift.
-- `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 281 files (approximately 1.1 MB packed and 4.3 MB unpacked).
-- Disposable downstream installation returned `ok=true` for the exact beta.12.15 tarball. The first
-  sandboxed run failed only because registry DNS was unavailable; the exact network-enabled retry
-  passed.
-- `npm run plugin:check` and `npm run docs:pdf:check` passed. PDF freshness reported an empty stale
-  set and exact beta.12.15 package binding.
-
-## Live Signal reproduction
-
-Signal Task `TASK-01M1B79C660YMNSRRZ236NTR1T` is blocked after a completed corrective yield. Its
-three allowlisted STEP-001 product files remain uncommitted and unchanged. The repository contains
-two consecutive Workflow dependency-only commits that Core could not register:
-
-- beta.12.13: `51e5e61b39ff9a234dcc9ccb80d81da710570f55`;
-- beta.12.14: `96c3bd22e818873c1de59cd42b466efde0947d23`.
-
-Fresh beta.12.14 observation is otherwise coherent: no pending or corrupt transactions and no active
-leases. Nevertheless, `next` advertised dependency recovery while its preflight rejected the route
-because it expected the current update commit's parent to be an already registered system commit.
-The beta.12.13 parent could not be registered earlier because the beta.12.13 transaction-observation
-defect prevented all workflow commands before beta.12.14 was installed.
-
-The beta.12.15 implementation was built locally and run read-only against this exact Signal state.
-Preflight returned `eligible=true`, action `update plan-integrity-dependency-recover`, and the exact
-two-commit chain above in oldest-to-newest order. No Signal state, journal, sidecar, Git history or
-product file was modified by this reproduction.
-
-## Root cause corrected
-
-The beta.12.14 carried-compatibility and dependency-recovery logic assumed a single unregistered
-Workflow update at `HEAD`, with an already registered parent at `HEAD^`. That assumption is false
-when an earlier release was installable but its recovery route was unreachable because observation
-itself failed. Installing the observer fix then creates a bounded consecutive suffix of two
-unregistered dependency-only commits.
-
-The resulting blocker was not invalid Signal product work, a stale lease or corrupt Core state. It
-was an incomplete dependency-provenance boundary: navigation advertised a route that the route's own
-single-hop preflight could never accept.
-
-## Implemented compatibility contract
-
-- Preflight discovers the complete trailing unregistered suffix after the exact recorded Task
-  history instead of assuming one commit.
-- Every suffix element must form an uninterrupted parent chain and change exactly `package.json` and
-  `package-lock.json`, only as an exact `codex-workflow-v2` pin update. Product bytes, additional
-  dependency changes, merge ancestry and unexplained commits remain blockers.
-- The terminal suffix commit must match the declared, locked and installed package version.
-- Carried Plan-integrity compatibility is derived by walking through the bounded suffix to the last
-  registered system commit. The original recovery, failed Step, Plan, remediation history, dirty
-  allowlist, dirty SHA-256, C1 posture and completed corrective-yield history must still match.
-- Recovery atomically registers the entire chain in `systemCommits` and appends one provenance record
-  per commit using that commit's actual package version. Partial registration is not permitted.
-- A failed atomic recovery leaves all Core state unchanged. No product file, Plan, Step, lease,
-  review or Git history is edited by this route.
-- Protocol and state schema remain `2/2`; no migration or manual state repair is required.
-
-## Existing beta.12.14 contract retained
-
-- Current binding manifests remain mandatory for pending and in-flight corrective-replan
-  transactions.
-- Historical manifest/runtime/catalog identities are accepted only for exact registered completed
-  journals and cannot create new authority.
-- Corrective-replan credentials still separate source Task Knowledge from target replacement-Plan
-  Knowledge.
-- Completed corrective-yield journals still require their canonical event bytes to be an exact prefix
-  of the append-only handoff history.
-- After dependency recovery, the blocked Task must still pass normal corrective-replan preparation,
-  confirmation, execution, fresh authorization/C1, selector-bearing checks, Core-owned Step commit and
-  strict external review.
-
-## PDF release documentation evidence
-
-- All three tracked Russian PDFs were regenerated from beta.12.15 sources.
-- Architecture is 9 pages, delegated chat-only guide is 10 pages, and technical reference is 14
-  pages. All 33 rendered pages were visually inspected; no clipping, overlap or unreadable content
-  was observed.
+- `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:
+
+- 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.
 
 ## Boundaries and non-claims
 
-- The suffix scan is not generic history adoption. Only the contiguous, exact Workflow-pin-only
-  prefix between registered Task history and current HEAD is eligible.
-- The patch does not weaken dirty-worktree boundaries, Plan identity, remediation evidence, C1
-  authority, checks or review gates.
-- This report does not claim commit/tag/push, npm publication, live beta.12.15 installation,
-  dependency recovery or STEP-001 completion before each operation receives its own readback.
-
-Confidence is high for consecutive dependency-provenance recovery because the focused tests, full
-349-test gate and read-only real Signal reproduction agree. End-to-end confidence remains conditional
-on publication, exact Signal installation, fresh repository-local `status -> next`, and completion of
-the blocked STEP-001 through Core-advertised routes.
+- 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.