codex-workflow-v2 2.0.0-beta.12.11 → 2.0.0-beta.12.13

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

@@ -1,10 +1,10 @@
 ---
-title: Codex Workflow V2: архитектура beta.12.11
+title: Codex Workflow V2: архитектура beta.12.13
 subtitle: Источники истины, lifecycle, роли, delegation, зависимости Tasks и границы доверия
 part: Часть 1 из 3 | Архитектура
 document_version: 2.0
 date: 31 августа 2026
-subject: Архитектура и границы Codex Workflow V2 beta.12.11
+subject: Архитектура и границы Codex Workflow V2 beta.12.13
 ---
 
 # 1. Назначение и граница системы
@@ -18,7 +18,7 @@ Codex Workflow V2 - локальный state machine поверх Codex App, Git
 Система рассчитана на одного пользователя и одну машину. Она не предоставляет distributed locking,
 криптографическую идентификацию actor string или безопасную синхронизацию state между компьютерами.
 
-## 1.1. Что beta.12.11 гарантирует
+## 1.1. Что beta.12.13 гарантирует
 
 - 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.11 не гарантирует
+## 1.2. Что beta.12.13 не гарантирует
 
 - правильность продуктовой идеи или автоматически выбранного provider Task;
 - semantic sufficiency Plan, если точные факты нельзя доказать поддерживаемым analyzer;
@@ -314,6 +314,23 @@ Workflow pin, Core переносит reconcile и `corrective-derived` approval
 transaction. Изменение любого другого Knowledge source, classification, gap или conflict fail-closed
 остаётся в обычном явном approval flow.
 
+beta.12.12 закрывает доказанный runtime Plan-integrity gap. Mechanical feasibility теперь статически
+распознаёт repository-local `node <runner> affected`, когда исходник runner явно требует selector,
+и блокирует authorization для `npm run <script>` без `--base`, `--head` или `--files`. Для уже начатой
+Task recovery связывает не только первую, а всю последовательную checks-failed history, точный Plan,
+manifest/runner hashes, HEAD и dirty allowlist. Exact beta.12.11 update bridge сохраняет product bytes,
+регистрирует только dependency commit и атомарно обновляет Knowledge, если изменился только Workflow pin.
+Результат — один `replan-required` decision и обычный corrective replan с исполняемой check command;
+повтор старой команды, ручной commit product files и state editing не допускаются.
+
+beta.12.13 устраняет следующий доказанный разрыв этого пути. Corrective-replan credential раздельно
+связывает исходную Knowledge revision/hash Task и целевую active Knowledge revision/hash replacement
+Plan. Различие разрешено только при exact Plan-integrity dependency recovery: текущий system commit,
+package version, failed Step, Plan, полная remediation history, dirty file set и их bytes должны
+совпасть. Следующее dependency-only обновление после corrective yield может перенести ту же compatibility
+на новый HEAD только при точном parent commit и неизменном worktree. Completed corrective-yield journal
+остаётся историческим prefix-доказательством и не блокирует последующие append-only handoff events.
+
 Docker socket `EPERM` в sandbox не является доказательством сломанного daemon. Gateway один раз
 повторяет exact health probe или Plan check с sandbox escalation без расходования remediation attempt.
 Restart Docker Desktop требует отдельного разрешения и допустим только после escalated daemon failure.
@@ -323,7 +340,7 @@ Restart Docker Desktop требует отдельного разрешения
 # 10. Operational checklist
 
 - exact package version установлен, bundled gateway соответствует release и переустановлен;
-- handshake подтверждает protocol 2, state schema 2 и beta.12.11 capabilities;
+- handshake подтверждает protocol 2, state schema 2 и beta.12.13 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.11 путь от нового Discovery до принятого Milestone без ручного CLI
+subtitle: Актуальный beta.12.13 путь от нового Discovery до принятого Milestone без ручного CLI
 part: Часть 2 из 3 | Практика
 document_version: 2.0
 date: 31 августа 2026
-subject: Практическое руководство по delegated Discovery и Milestone в Workflow V2 beta.12.11
+subject: Практическое руководство по delegated Discovery и Milestone в Workflow V2 beta.12.13
 ---
 
-# 1. Рабочая модель beta.12.11
+# 1. Рабочая модель beta.12.13
 
 Пользователь работает в одном 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.11 как точную devDependency после публикации release.
+2. Установите beta.12.13 как точную 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.11 должен сообщать `packageVersion=2.0.0-beta.12.11`, `protocolVersion=2`,
+Handshake beta.12.13 должен сообщать `packageVersion=2.0.0-beta.12.13`, `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.11 в delegated режиме.
+Проведи новый Milestone через Codex Workflow V2 beta.12.13 в delegated режиме.
 Repository: <ABSOLUTE-REPOSITORY-ROOT>.
 Milestone ID: AUTO.
 Delegate actor: agent:milestone-coordinator.
@@ -350,6 +350,21 @@ binding dirty set. Recover регистрирует только dependency HEAD
 Recover сохраняет product bytes; затем обязательны `status -> next -> task step-complete`. Если package
 уже зарегистрирован, используйте advertised `task historical-step-provenance-preflight/recover`.
 
+Для beta.12.11 Task, застрявшей на selector-required `npm run validate:affected` без selector, сначала
+остановите Worker и дождитесь отсутствия active/stale lease. Внешний exact beta.12.12 runner допускается
+только для read-only `update plan-integrity-update-preflight`; требуйте `eligible=true`, exact failed Step,
+полную remediation history и неизменённый dirty allowlist. После единственного dependency-only commit
+на base и Task branch fresh repository-local `next` должен рекламировать
+`update plan-integrity-dependency-recover`. Recovery атомарно регистрирует commit и dependency-only
+Knowledge refresh. Затем выполните advertised credential recovery, `task plan-integrity-recover` и
+`task corrective-yield`. Replacement Plan меняет только неисполняемую check на
+`npm run validate:affected -- --files=<Step allowedWrites>` и проходит fresh Plan Risk Audit до нового run.
+
+Если update произошёл уже после `task corrective-yield`, beta.12.13 допускает только advertised
+`update plan-integrity-dependency-recover`: parent должен быть предыдущим зарегистрированным recovery
+commit, а failed Step, Plan, remediation IDs, dirty paths и dirty SHA-256 — полностью совпадать. После
+recovery снова запросите `status -> next`; ожидаемый route остаётся `task corrective-replan-prepare`.
+
 Для exact beta.12.6 stranded-replan shape сначала нужен eligible read-only source preflight с exact
 revision/HEAD/dirty hash. Затем два beta.12.7 dependency-only commits и advertised dependency/replan
 recoveries. После Knowledge refresh `next` обязан остаться на `task plan-set`; новый единый Step должен
@@ -382,7 +397,7 @@ Task/project DGR. `dependencyBinding` для standalone handoff равен null.
 
 # 14. Итоговый checklist пользователя
 
-- beta.12.11 exact package и новый bundled gateway установлены;
+- beta.12.13 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.11
+title: Codex Workflow V2: технический справочник beta.12.13
 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.11
+subject: Технический контракт Codex Workflow V2 beta.12.13
 ---
 
 # 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.11 | Значение |
+| Параметр beta.12.13 | Значение |
 |---|---|
-| npm package | `codex-workflow-v2@2.0.0-beta.12.11` |
+| npm package | `codex-workflow-v2@2.0.0-beta.12.13` |
 | 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.11 capabilities:
+Ключевые beta.12.13 capabilities:
 
 | Группа | Capabilities |
 |---|---|
@@ -445,6 +445,47 @@ Materialization тогда дополнительно пишет active Knowledg
 `corrective-derived` в той же Project transaction. Это не разрешает автоматически принимать README,
 docs, commands, classification, authority, gaps или conflicts.
 
+# 13.5. beta.12.12 selector-contract Plan-integrity recovery
+
+Analyzer `wf2.root-npm-script-arguments@1` читает root `package.json` и только repository-local runner
+из evaluated Git HEAD. Узкий доказуемый contract — script `node <safe-relative-path> affected`, исходник
+которого использует `process.argv.slice(3)`, содержит selector literals `--base`, `--head`, `--files` и
+явный `Affected mode requires` guard. Для такого script check без forwarded selector получает
+`ROOT_NPM_SCRIPT_REQUIRED_SELECTOR_MISSING` и блокирует execution authorization. Произвольный shell или
+нераспознанный runner остаётся `unverified`, а не объявляется ошибочным по догадке.
+
+Legacy recovery принимает последовательную append-only history из одного или нескольких
+`checks-failed` events при отсутствии corrective decision. Evidence v2 связывает каждый event ID/hash/
+ordinal, Task revision, Plan/Step definition, manifest и runner hashes, Git HEAD, conflicts и SHA-256
+dirty worktree. `task plan-integrity-recover` записывает один `replan-required` decision с
+`triggeringAttemptCount = failures + 1` и полным `coveredEventIds`.
+
+Если exact beta.12.12 package ещё не установлен, `update plan-integrity-update-preflight` проверяет
+source beta.12.11, отсутствие leases/transactions и exact dirty allowlist. После dependency-only
+transport `update plan-integrity-dependency-preflight/recover` регистрирует единственный HEAD как system
+commit. Когда Knowledge drift объясняется только Workflow pin, та же Project transaction выполняет
+corrective-derived reconcile/approval; прочий drift fail-closed. Product bytes не коммитятся и не
+переносятся. Fresh route продолжается через credential replacement, `plan-integrity-recover`, yield и
+corrective replan с selector-bearing check.
+
+# 13.6. beta.12.13 source/target Knowledge binding
+
+Corrective-replan receipt теперь включает две разные пары. `knowledgeRevision/knowledgeHash` связывает
+исходное состояние Task; `targetKnowledgeRevision/targetKnowledgeHash` связывает active Project
+Knowledge Map и replacement Plan. Executor проверяет source под Task lock, candidate Plan — по target,
+а Risk Audit и materialized Task получают target binding.
+
+Source и target могут различаться только при exact `dependencyProvenanceRecoveries.planIntegrity` для
+текущего HEAD и package version. Record обязан совпасть по Plan, failed Step, всей remediation event ID
+последовательности, dirty paths и повторно вычисленному dirty SHA-256. Для последовательного package
+update после corrective yield Core переносит compatibility лишь с зарегистрированного `HEAD^`; любое
+изменение product bytes, Step status, Plan, decision или C1 posture отключает route.
+
+Completed corrective-yield transaction проверяет неизменный canonical yield event как prefix текущей
+append-only handoff history. Это сохраняет tamper detection, но разрешает новый handoff после успешного
+corrective replan. E2E release gate проходит prepare/confirm/execute, authorization, handoff/claim,
+selector-bearing Step completion commit и strict Step review.
+
 # 14. P04-A structural replacement boundary
 
 Command shape `task replacement-materialize` retained только для compatibility diagnostics. Любая попытка
@@ -507,12 +548,12 @@ Docker socket/CLI `EPERM`, `operation not permitted` или `permission denied`
 После каждой successful mutation обязателен sequential `status`, затем fresh `next`. Failed status/next
 не разрешает direct mutation. Syntax help read-only и не заменяет navigation authority.
 
-# 18. Public command surface beta.12.11
+# 18. Public command surface beta.12.13
 
 | Область | Actions |
 |---|---|
 | System | `doctor`, `status`, `next`, `gateway handshake`, `locks` |
-| Update | `preflight`, `rescue-preflight`, dependency provenance, historical-Step dependency bridge, downstream-proof dependency bridge, downstream-proof replan update/dependency bridge |
+| Update | `preflight`, `rescue-preflight`, dependency provenance, historical-Step dependency bridge, downstream-proof bridges, Plan-integrity update/dependency bridge |
 | Project memory | `scan`, `show`, `status`, `approve`, `reconcile` |
 | Delegation | `prepare`, `grant`, `list`, `show`, `revoke` |
 | Graph | `prepare`, `status`, `refresh-request`, `bind`, `fallback` |
@@ -532,10 +573,11 @@ Exact options берутся из fresh `next`; command help используе
 
 Перед package update project-local `update preflight` должен вернуть `safe=true`: clean checkout, нет
 running Step и active/stale writer lease. Исключения — документированный alpha.7 rescue, beta.12.6
-active-downstream-proof bridge, beta.12.7 exact stranded-replan bridge и beta.12.9 historical-Step
-dependency bridge; все они fail-closed и не дают общего разрешения dirty update.
+active-downstream-proof bridge, beta.12.7 exact stranded-replan bridge, beta.12.9 historical-Step
+dependency bridge и beta.12.13 Plan-integrity bridge; все они fail-closed и не дают общего разрешения
+dirty update.
 
-Перед beta.12.11 tag обязательны `npm ci`, `npm run validate`, `npm run test:signal-remediation-e2e`, `npm run pack:check`,
+Перед beta.12.13 tag обязательны `npm ci`, `npm run validate`, `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

@@ -28,7 +28,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.11, the release gate also relies on `npm run release:check` to fail if:
+For beta.12.12, the release gate also relies on `npm run release:check` to fail if:
 
 - canonical entity schema 2 shapes drift;
 - protocol 2 is not the active public contract, or intact protocol-1 adoption evidence stops being readable through the bounded compatibility window;
@@ -57,7 +57,8 @@ For beta.12.11, the release gate also relies on `npm run release:check` to fail
   commit, current Plan/Step, dirty paths/content hash, and absence of leases/transactions.
 - the read-only Milestone progress projection, replacement regression, project-monotonic chat
   registry, title fallback/readback, or long-Cyrillic multi-attempt E2E evidence is absent.
-- bounded first-failure Plan-integrity recovery, exact failed-remediation/manifest/worktree
+- 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.
 - 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

package/docs/updating-existing-project.md

@@ -22,6 +22,31 @@ state schema. Совпадение `stateSchemaVersion` до и после об
 нужна. Для alpha.6 при `stateSchemaVersion: 2` применяется не migration, а sidecar-only
 adoption posture.
 
+### beta.12.12: неисполняемая Step check и сохранение текущей реализации
+
+Новые Plans больше не могут получить execution authorization, если root npm script запускает
+repository-local `affected` validator, сам validator явно требует `--base`, `--head` или `--files`,
+а Step check не передаёт ни одного selector. Исправьте check в Plan, например
+`npm run validate:affected -- --files=<allowedWrites>`; Worker и remediation attempt до этого не
+запускаются.
+
+Для Task, уже застрявшей на beta.12.11 после одного или нескольких одинаковых `checks-failed`,
+используется только bounded bridge. Внешний exact beta.12.12 runner выполняет read-only
+`update plan-integrity-update-preflight`; продолжение допустимо лишь при `eligible=true`, отсутствии
+lease/transaction и точном dirty set внутри failed Step `allowedWrites`. Затем один dependency-only
+commit (`package.json` и `package-lock.json`) должен оказаться и на Milestone base, и в Task history
+без изменения product bytes. Fresh repository-local `next` рекламирует
+`update plan-integrity-dependency-recover`; этот переход регистрирует dependency commit и, если
+Knowledge drift вызван только Workflow pin в `package.json`, атомарно выполняет corrective-derived
+Knowledge refresh без Human approval.
+
+После регистрации Core связывает всю append-only цепочку failed attempts, текущий Plan, HEAD,
+manifest, validator и SHA-256 dirty worktree. `task plan-integrity-recover` записывает один
+`replan-required` decision для следующего ordinal. Затем следуйте fresh
+`task corrective-yield -> task corrective-replan-*`; replacement Plan обязан сохранить Step и dirty
+allowlist, но заменить check на исполняемую selector-bearing команду. Не коммитьте product files,
+не редактируйте state и не повторяйте старую неисполняемую проверку.
+
 ### beta.12.11: audited remediation и dependency-only Knowledge refresh
 
 После безопасного обновления существующий active Milestone может продолжить работу без пересоздания,

package/docs/validation-report.md

@@ -1,113 +1,134 @@
-# V2 beta.12.11 Validation Report
+# V2 beta.12.13 Validation Report
 
-Release candidate `2.0.0-beta.12.11` was validated on 2026-08-31 (Europe/Moscow) with
+Release candidate `2.0.0-beta.12.13` was validated on 2026-08-31 (Europe/Moscow) with
 Node.js 24.17.0.
 
 ## Automated release evidence
 
-- `npm ci` completed from the exact lockfile. No dependency version changed outside the release pin.
-- `npm run validate` passed typecheck and `345/345` sequential tests with no failures, skips,
-  cancellations, or todos in 1,974,837.33 ms.
-- `npm run test:signal-remediation-e2e` passed two focused scenarios. The positive E2E starts with an
-  approved Knowledge Map bound to beta.12.9, commits an exact dependency-only update to beta.12.11,
-  proves the stale map from Git and all version surfaces, materializes an audited upstream remediation
-  Task, completes its Plan/audit/C1/Step/review/accept/merge lifecycle, replans the original Task, and
-  completes a later Step there. The negative E2E changes README and proves that unrelated Knowledge
-  drift is not auto-approved while standalone reconcile remains executable.
-- Existing negative coverage still rejects non-exact predecessor frontiers, duplicate remediation,
-  stale revisions, non-required or non-active Milestone posture, topology drift, reused audit evidence,
-  unsafe Knowledge paths, classification/gap/conflict drift, dirty checkouts, unaligned package
-  surfaces and wider Git commits.
-- Package dry-run produced `codex-workflow-v2-2.0.0-beta.12.11.tgz` with 278 files, 1,057,906 bytes
-  packed and 4,224,300 bytes unpacked. The tarball excludes repository-local `docs/quality`. The first
-  invocation encountered a root-owned user npm cache (`EPERM`); the exact retry passed with an isolated
-  temporary cache.
-- `npm run smoke:downstream` built and installed the tarball in a disposable consumer project and
-  returned `ok=true`. The sandboxed attempt could not resolve npm (`ENOTFOUND`); the same command passed
-  with network access.
+- `npm ci` completed from the exact lockfile; the audit reported zero vulnerabilities.
+- The first full `npm run validate` passed 346 of 348 tests. The only two failures were exact
+  transition-definition identity pins intentionally changed by the two new Knowledge fields: the
+  serialized definition SHA-256 and the binding-manifest row count. The derived serialized digest,
+  runtime fingerprint, runtime catalog hash, and row count were recorded from the actual compiled
+  model; the focused authority suite then passed `4/4`.
+- The mandatory clean rerun of `npm run validate` passed typecheck and `348/348` sequential tests
+  with no failures, skips, cancellations, or todos in 2,131,076.63 ms.
+- The full suite includes a beta.12.13 Signal-shaped E2E: repeated selector-contract failures,
+  beta.12.12-like dependency recovery, a second package-only update, carried exact compatibility,
+  corrective replan against the active Knowledge Map, fresh authorization/C1, selector-bearing
+  validation, a Core Step commit, and strict Step review. It also proves that changed dirty bytes
+  make the carry preflight fail closed.
+- `npm run test:signal-remediation-e2e` passed `2/2`; `npm run
+  test:signal-t03-replan-e2e` passed `1/1`; and `npm run test:signal-t04-recovery` passed `11/11`.
+  Together they independently cover audited upstream remediation through a later Step, the
+  Signal-shaped accidental-rebind/replan path, bounded dependency recovery, and retained reviewed
+  Step provenance.
+- Package dry-run produced `codex-workflow-v2-2.0.0-beta.12.13.tgz` with 281 files (approximately
+  1.1 MB packed and 4.3 MB unpacked). The first invocation encountered the known root-owned user npm
+  cache (`EPERM`); the exact retry passed with an isolated temporary cache and no system permission
+  changes.
+- `npm run smoke:downstream` built and installed that tarball in a disposable consumer project and
+  returned `ok=true`. The sandboxed attempt could not resolve npm (`ENOTFOUND`); the same command
+  passed with approved network access.
 - `npm run plugin:check` passed for bundled gateway `0.1.0+codex.20260830183000`.
-- `npm run docs:pdf:check` reported an empty stale set and exact beta.12.11 package binding.
-- `RELEASE_TAG=v2.0.0-beta.12.11 npm run release:check` and `git diff --check` passed.
+- `npm run docs:pdf:check` reported an empty stale set and exact beta.12.13 package binding.
+- `RELEASE_TAG=v2.0.0-beta.12.13 npm run release:check` and `git diff --check` passed.
 
-## Root causes corrected
+## Root cause corrected
 
-beta.12.10 added the bounded audited-remediation topology for a required pre-execution Task whose
-current Plan Risk Audit truthfully returned `stop-escalate` because an upstream capability was absent.
-Real installation in Signal exposed a second deadlock before that route could run:
+Signal Task `TASK-01M1B79C660YMNSRRZ236NTR1T` retained its three allowlisted Worker files and reached
+a legitimate `corrective-replan-prepare` route after beta.12.12 recovery. Preparation still failed:
+the Task source Plan remained bound to the older Project Knowledge Map, while the only admissible
+replacement Plan correctly bound the newer active map created by the package-only Knowledge refresh.
+The public corrective-replan path required those two bindings to be identical, so no candidate could
+satisfy both constraints.
 
-1. the dependency-only package commit changed the approved `package.json` content hash;
-2. repository `next` correctly observed stale Project Knowledge and advertised standalone reconcile;
-3. standalone reconcile tried to discover a delegated Task context owner;
-4. the same blocking Plan Risk Audit rejected that inspection, so the advertised transition could not
-   execute; and
-5. even an ordinary reconcile would have required a Human approval and Task rebind that invalidated the
-   exact audit binding needed by remediation.
+A further release update exposed two related continuity gaps:
 
-The primary defect was incomplete composition between package update, Knowledge authority and audited
-remediation, not an insufficient retry count. A one-command bypass or broad auto-approval would have
-hidden unreviewed product/documentation changes.
+1. Plan-integrity dependency recovery could derive compatibility only from a currently detectable
+   invalid-check assessment. After the first recovery and `replan-required` decision, a second
+   package-only update could no longer reconstruct the already registered exact compatibility.
+2. A completed corrective-yield journal required the whole current handoff sidecar to equal the
+   yield-owned bytes forever. A later valid append-only handoff therefore made historical readback
+   fail even though the original yielded entry was intact.
+
+The defect was not insufficient Worker effort, an invalid product implementation, or a need to
+increase attempts. It was an over-constrained source/target Knowledge identity plus incomplete
+append-only continuity across consecutive Workflow updates.
 
 ## Implemented lifecycle contract
 
-- Fresh `next` advertises audited remediation only for an unstarted
-  `awaiting_execution_authorization` required Task of an active Milestone with a current
-  `stop-escalate` Plan Risk Audit.
-- When Project Knowledge is stale, the route continues without a Human gate only if Core proves all of
-  the following: the previously stored map is active and approved; the sole changed Knowledge path is
-  `package.json`; checkout is clean; runtime, declared, locked, installed, HEAD and Milestone-base
-  versions equal; the approved manifest bytes exist in current Git ancestry; and every subsequent
-  commit that touched `package.json` changed exactly `package.json` and `package-lock.json` with no
-  structural difference after removing the Workflow dependency.
-- `next.auditedRemediation.dependencyKnowledgeRefresh` exposes the evidence and blockers without writes.
-  Discovery start/update stays available only when this assessment is eligible.
-- `milestone remediation-materialize` atomically writes the consumed Discovery, one required remediation
-  Task, additive Milestone topology, scope-change evidence and—when required—the reconciled active
-  Knowledge Map at revision +2 with `corrective-derived` approval. No actor, confirmation code,
-  delegation grant or Human approval is accepted.
-- The new Task inherits the blocked Task exact direct predecessor frontier. Milestone outcome, success
-  signal, acceptance, checks, base, old memberships and unrelated dependency edges remain unchanged.
-- The corrective-derived actor remains `agent:milestone-remediation:<MS-ID>` and authorizes only the
-  advertised required Task execution/final-acceptance transitions. Final Milestone acceptance remains
-  an ordinary Human/delegated gate.
-- After remediation merge, the original Task returns to `task plan-set`, receives a fresh Knowledge
-  binding, Plan and Risk Audit, then proceeds through ordinary C1, checks, commits and reviews.
-- Unsafe or unrelated Knowledge drift never enters this route. Standalone reconcile now remains
-  executable instead of throwing while it checks whether a blocked Task can own delegated refresh;
-  subsequent explicit approval semantics are unchanged.
-- Handshake adds `audited-remediation-dependency-knowledge-refresh-v1` while protocol and state schema
-  remain `2/2`.
-
-## Signal-shaped evidence
-
-The focused E2E reproduces the real post-install boundary, including an older approved manifest hash,
-an exact package/lock update commit, a stale Knowledge observation, an active Milestone, one blocked
-required consumer and the later ordinary Step. It proves the complete continuation rather than only
-the Knowledge assessment or materialization command.
-
-Live Signal installation and mutation remain post-publication actions. They must install exact
-repository-local beta.12.11, commit only package/lock, run sequential handshake/status/next, follow the
-advertised audited-remediation route and confirm Core readback. No manual state edit, Git history
-rewrite, Task cancellation or duplicate Milestone is part of the recovery.
+- Corrective-replan credentials now bind two distinct pairs. `knowledgeRevision`/`knowledgeHash`
+  identify the unchanged source Task/Plan state under the Core lock;
+  `targetKnowledgeRevision`/`targetKnowledgeHash` identify the active Project Knowledge Map that the
+  candidate Plan, new Plan Risk Audit, and materialized Task state must bind.
+- Source and target Knowledge may differ only when the Task contains one exact current
+  Plan-integrity dependency-provenance recovery. It must match the current HEAD and package version,
+  a Workflow-owned system commit, current Plan and failed Step, the complete remediation-event list,
+  exact dirty paths, and a freshly recomputed dirty-worktree hash. Otherwise preparation remains
+  fail closed.
+- A consecutive package-only update may carry compatibility from exactly one prior registered
+  recovery on `HEAD^`. Carry is admitted only when the current Task still has the same Plan, failed
+  Step, full remediation history, dirty paths and bytes, one `replan-required` decision, and no C1
+  posture. It cannot infer compatibility from prose or widen the product boundary.
+- The corrective-replan private credential schema and binding manifest contain 30 exact fields.
+  Their serialized definition digest, runtime semantic fingerprint, and runtime catalog hash are
+  pinned by the authority-model suite.
+- A completed corrective-yield journal now proves that its owned handoff bytes remain an exact prefix
+  of the current canonical append-only history and validates the entire current JSONL chain. Pending
+  and in-flight phases retain exact-byte equality. Truncation, prefix mutation, or malformed appended
+  history still fails closed.
+- Protocol and state schema remain `2/2`; no lifecycle-state migration is required.
+
+## Signal-shaped and negative evidence
+
+The new synthetic E2E reproduces the live boundary instead of testing a helper in isolation:
+
+- an active failed guarded Step with repeated selector-contract failures and three allowlisted dirty
+  product files;
+- an existing beta.12.12 Plan-integrity recovery and `replan-required` decision;
+- a subsequent exact package-only beta.12.13 update while the Task source Knowledge remains older
+  than the active Project Knowledge Map;
+- reconstruction of exact compatibility from `HEAD^` without modifying product bytes;
+- corrective replan whose source binding remains old and whose candidate target binding is current;
+- new execution authorization and C1 cycle;
+- the selector-bearing `validate:affected -- --files=...` check;
+- successful Step completion through a Workflow-owned Core commit and strict Step review.
+
+Negative coverage rejects changed dirty bytes, wider dirty scope, the wrong parent/system commit,
+stale Plan or Step, incomplete remediation history, a non-`replan-required` decision, active C1,
+unregistered Knowledge drift, truncated historical handoff bytes, mutated historical bytes, and
+malformed appended handoff history.
+
+Live Signal mutation remains post-publication work. Installation must preserve the three current
+Worker files, transport only package/lock through the advertised update compatibility route, use a
+fresh repository-local handshake/status/next before each mutation, and follow only Core-advertised
+actions. No manual Workflow-state edit, history rewrite, Task cancellation, duplicate Task, or
+replacement Milestone is authorized by this release.
 
 ## PDF release documentation evidence
 
-- All three tracked Russian PDFs were regenerated from beta.12.11 Markdown sources.
-- Architecture is 8 pages, the delegated chat-only guide is 10 pages, and the technical reference is
-  13 pages. All 31 pages were rendered to PNG and visually inspected.
-- Titles, package bindings, Cyrillic text, tables, code blocks, margins, footers and the new
-  dependency-Knowledge sections have no visible clipping, overlap or unreadable content.
+- All three tracked Russian PDFs were regenerated from beta.12.13 Markdown sources.
+- Architecture remains 9 pages, the delegated chat-only guide 10 pages, and the technical reference
+  13 pages. All 32 pages were rendered and visually inspected; changed source/target Knowledge,
+  consecutive-update, and append-only yield sections were additionally checked at full resolution.
+- Titles, version bindings, Cyrillic text, tables, code blocks, margins and footers show no clipping,
+  overlap, or unreadable content.
 
 ## Existing boundaries and non-claims
 
-- The route does not permit arbitrary Task insertion, Task removal, semantic Milestone scope change,
-  arbitrary dependency rewiring, completed-Step adoption or `split-required` replacement.
-- It does not auto-approve README, documentation, commands, classifications, authorities, gaps,
-  conflicts, dirty files or package commits containing any non-Workflow change.
-- Protocol version remains 2 and state schema remains 2; no state migration is required.
-- This report does not claim Git tag/push, npm publication or live Signal recovery before those
-  post-gate operations are read back separately.
-
-Confidence is high for the package implementation, bounded no-Human dependency Knowledge refresh,
-transaction atomicity, regression compatibility, tarball composition, downstream installation,
-gateway and documentation. Live Signal confidence remains conditional on exact publication,
-installation and fresh Core/Coordinator readback.
+- Compatibility is exact recovery authority, not general permission to rebind Knowledge, edit a
+  Plan, change product files, alter Milestone topology, adopt unrelated commits, or skip review.
+- The carry route supports a consecutive package-only update only when the previous recovery record
+  remains fully reproducible from current Git, Task and worktree evidence.
+- Historical corrective-yield readback accepts append-only continuation, not arbitrary sidecar drift.
+- The release does not make failing product logic pass, approve a broken check, increase retry limits,
+  or infer an executable selector. The replacement Plan must supply the exact selector-bearing command.
+- This report does not claim Git commit/tag/push, npm publication, live Signal installation, or Task
+  completion before those operations receive their own readbacks.
+
+Confidence is high for source/target Knowledge separation, consecutive-update compatibility,
+append-only yield continuity, Core authority closure, transaction recovery, package composition,
+downstream installation, gateway validation and documentation. Live Signal confidence remains
+conditional on exact publication, installation, fresh Core readback, and completion of the blocked
+Step through the advertised route.

package/package.json

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