codex-workflow-v2 2.0.0-beta.12.5 → 2.0.0-beta.12.6

package/docs/development-flow.md

@@ -106,6 +106,13 @@ invalidated predecessor completion, yields its C1 lease, and returns the same Ta
 The replacement Plan must cover the unfinished remainder and pass a fresh Risk Audit and execution
 authorization. Do not stash, reset, commit, or recreate the Task around this route.
 
+If the repository is still on a package version that cannot advertise that route, beta.12.6 has
+one update-only bridge. After exact dependency-only commits have aligned the active Milestone base
+and Task branch, `update downstream-proof-dependency-recover` validates recorded history at the
+candidate parent, binds the active proof dirty set by content hash, and registers only the Task
+dependency commit. Product bytes and Step state remain unchanged; fresh `next` must then advertise
+the ordinary `task downstream-proof-recover`. This is not a general dirty-update permission.
+
 A sandboxed Docker `EPERM`, `operation not permitted`, or `permission denied` result is not a failed
 daemon check. Re-run the exact probe/check once with sandbox escalation without consuming a retry.
 Restart Docker Desktop only with separate authorization after the escalated call reaches Docker and

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

@@ -1,10 +1,10 @@
 ---
-title: Codex Workflow V2: архитектура beta.12.5
+title: Codex Workflow V2: архитектура beta.12.6
 subtitle: Источники истины, lifecycle, роли, delegation, зависимости Tasks и границы доверия
 part: Часть 1 из 3 | Архитектура
 document_version: 2.0
 date: 29 августа 2026
-subject: Архитектура и границы Codex Workflow V2 beta.12.5
+subject: Архитектура и границы Codex Workflow V2 beta.12.6
 ---
 
 # 1. Назначение и граница системы
@@ -18,7 +18,7 @@ Codex Workflow V2 - локальный state machine поверх Codex App, Git
 Система рассчитана на одного пользователя и одну машину. Она не предоставляет distributed locking,
 криптографическую идентификацию actor string или безопасную синхронизацию state между компьютерами.
 
-## 1.1. Что beta.12.5 гарантирует
+## 1.1. Что beta.12.6 гарантирует
 
 - exact project-local npm package и совместимый handshake до lifecycle действий;
 - Discovery до materialization Task или Milestone;
@@ -32,7 +32,7 @@ Codex Workflow V2 - локальный state machine поверх Codex App, Git
 - bounded recovery, когда downstream proof требует изменить уже завершённый predecessor Step:
   worktree и HEAD сохраняются, stale completion authority снимается, та же Task возвращается в planning.
 
-## 1.2. Что beta.12.5 не гарантирует
+## 1.2. Что beta.12.6 не гарантирует
 
 - правильность продуктовой идеи или автоматически выбранного provider Task;
 - semantic sufficiency Plan, если точные факты нельзя доказать поддерживаемым analyzer;
@@ -249,13 +249,20 @@ beta.11 `task plan-integrity-recover` существует для одного
 отсутствует exact root npm script и текущий Step не может изменить package.json. Recovery не меняет
 worktree или Plan и не создаёт synthetic second failure; он записывает bound `replan-required`.
 
-beta.12.5 различает другой случай: активный downstream proof оставил изменения в собственном scope и
+beta.12.6 различает другой случай: активный downstream proof оставил изменения в собственном scope и
 показал необходимость исправить completed transitive predecessor. Fresh `next` вместо невозможного
 `step-complete` рекламирует `task downstream-proof-recover`. Atomic transition сохраняет dirty files и
 HEAD, переносит predecessor commits в historical `invalidatedStepCommits`, очищает только stale Step evidence,
 yield C1 и возвращает ту же Task к новому Plan/risk audit/authorization. Unrelated dirty file,
 non-predecessor ownership, повреждённый journal или unregistered commit fail closed.
 
+Если старая версия не может установить этот fix из-за running Step/dirty preflight, beta.12.6
+добавляет отдельный update bridge. После двух exact dependency-only commits на active base и Task
+branch Core проверяет Task history на `HEAD^`, candidate на `HEAD`, все version surfaces, отсутствие
+leases/transactions, predecessor ownership и content hash dirty set. Переход регистрирует только
+dependency commit, не меняет product bytes/Step и делает обычный `task downstream-proof-recover`
+достижимым до manifest-induced Knowledge refresh. Это не общее разрешение dirty update.
+
 Docker socket `EPERM` в sandbox не является доказательством сломанного daemon. Gateway один раз
 повторяет exact health probe или Plan check с sandbox escalation без расходования remediation attempt.
 Restart Docker Desktop требует отдельного разрешения и допустим только после escalated daemon failure.
@@ -265,7 +272,7 @@ Restart Docker Desktop требует отдельного разрешения
 # 10. Operational checklist
 
 - exact package version установлен, bundled gateway соответствует release и переустановлен;
-- handshake подтверждает protocol 2, state schema 2 и beta.12.5 capabilities;
+- handshake подтверждает protocol 2, state schema 2 и beta.12.6 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.5 путь от нового Discovery до принятого Milestone без ручного CLI
+subtitle: Актуальный beta.12.6 путь от нового Discovery до принятого Milestone без ручного CLI
 part: Часть 2 из 3 | Практика
 document_version: 2.0
 date: 29 августа 2026
-subject: Практическое руководство по delegated Discovery и Milestone в Workflow V2 beta.12.5
+subject: Практическое руководство по delegated Discovery и Milestone в Workflow V2 beta.12.6
 ---
 
-# 1. Рабочая модель beta.12.5
+# 1. Рабочая модель beta.12.6
 
 Пользователь работает в одном 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.5 как точную devDependency после публикации release.
+2. Установите beta.12.6 как точную 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.5 должен сообщать `packageVersion=2.0.0-beta.12.5`, `protocolVersion=2`,
+Handshake beta.12.6 должен сообщать `packageVersion=2.0.0-beta.12.6`, `protocolVersion=2`,
 `stateSchemaVersion=2`, dependency DAG, initial Plan transaction, mechanical feasibility,
 Milestone autonomy и structural replacement disabled capabilities.
 
@@ -116,7 +116,7 @@ delegate, scope, transitions и expiry. DGR передаётся только е
 ```text
 НОВЫЙ COORDINATOR CHAT
 
-Проведи новый Milestone через Codex Workflow V2 beta.12.5 в delegated режиме.
+Проведи новый Milestone через Codex Workflow V2 beta.12.6 в delegated режиме.
 Repository: <ABSOLUTE-REPOSITORY-ROOT>.
 Milestone ID: AUTO.
 Delegate actor: agent:milestone-coordinator.
@@ -298,6 +298,7 @@ Task chat записывает его только при совпадении p
 | Finding `route=fix` | Продолжить тот же Step; count остаётся диагностикой |
 | Finding `route=replan` с exact Plan conflict | `task plan-set`, меняются только implementation Steps |
 | `split-required` | Stop: `STRUCTURAL_REPLACEMENT_REQUIRED`, никаких replacement writes |
+| Старая версия + active downstream proof блокируют update | Только beta.12.6 exact dependency commits и advertised `update downstream-proof-dependency-recover` |
 | Exact beta.11 attempt-four `stop-escalate` | Только advertised prepare, затем отдельный Human-confirmed apply; исходный stop сохраняется |
 | Любой другой explicit `stop-escalate` | Terminal user attention |
 | Stale dependency binding | Новый handoff/claim только по fresh `next` |
@@ -310,6 +311,13 @@ P04-A не переносит completed Steps и не rewires dependencies пр
 dirty worktree/HEAD, append-only фиксирует invalidated predecessor evidence, освобождает C1 и возвращает
 текущую Task к `task plan-set`. Если fresh `next` не рекламирует этот переход, вызывать его нельзя.
 
+Если этот переход доступен только после update, не stash/reset product work. Обновите active base в
+отдельном worktree и текущую Task branch двумя отдельными commits только `package.json`/lock, установите
+beta.12.6 и требуйте от fresh `next` `update downstream-proof-dependency-recover`. Read-only preflight
+должен вернуть `eligible=true`, exact `HEAD`/`HEAD^`, Task revision, пустые blockers и content-hash
+binding dirty set. Recover регистрирует только dependency HEAD; следующий fresh `next` должен вернуть
+обычный `task downstream-proof-recover`. Любой иной diff/history/dirty path/lease означает stop.
+
 Ошибка Docker socket/CLI `EPERM`, `operation not permitted` или `permission denied` в sandbox не считается
 падением daemon и не расходует retry. Повторите exact read-only probe или Plan check один раз с sandbox
 escalation. Не перезапускайте Docker Desktop и не меняйте image без отдельного разрешения и подтверждённого
@@ -345,7 +353,7 @@ Task/project DGR. `dependencyBinding` для standalone handoff равен null.
 
 # 14. Итоговый checklist пользователя
 
-- beta.12.5 exact package и новый bundled gateway установлены;
+- beta.12.6 exact package и новый bundled gateway установлены;
 - новый Coordinator chat не является fork старого Milestone;
 - bootstrap DGR, если нужен, выдан отдельным exact human confirmation;
 - Discovery не materialized при blocking unknowns;
@@ -356,5 +364,6 @@ Task/project DGR. `dependencyBinding` для standalone handoff равен null.
 - каждый transition пришёл из fresh `next`;
 - beta.11 stop override, если рекламировался, прошёл отдельные prepare и user-confirmed apply без journal rewrite;
 - downstream predecessor recovery, если рекламировался, сохранил worktree и завершился новым Plan authority;
+- active-proof package bridge, если понадобился, зарегистрировал только exact dependency HEAD перед recovery;
 - split-required остановился без replacement mutations;
 - Milestone validation и final acceptance связаны с текущим clean base HEAD.

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

@@ -1,10 +1,10 @@
 ---
-title: Codex Workflow V2: технический справочник beta.12.5
+title: Codex Workflow V2: технический справочник beta.12.6
 subtitle: Protocol 2, state schema 2, transactions, credentials, dependency authority, review и recovery
 part: Часть 3 из 3 | Technical reference
 document_version: 2.0
 date: 29 августа 2026
-subject: Технический контракт Codex Workflow V2 beta.12.5
+subject: Технический контракт Codex Workflow V2 beta.12.6
 ---
 
 # 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.5 | Значение |
+| Параметр beta.12.6 | Значение |
 |---|---|
-| npm package | `codex-workflow-v2@2.0.0-beta.12.5` |
+| npm package | `codex-workflow-v2@2.0.0-beta.12.6` |
 | 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.5 capabilities:
+Ключевые beta.12.6 capabilities:
 
 | Группа | Capabilities |
 |---|---|
@@ -316,13 +316,22 @@ fresh `next` через corrective yield и обычный Human-confirmed repla
 P01-A предотвращает поддерживаемые contradictions до fresh authorization. beta.11 path остаётся для
 pre-P01 authorizations и late/unsupported exact recovery cases.
 
-# 13.1. beta.12.5 compatibility transitions
+# 13.1. beta.12.6 compatibility transitions
 
 `update dependency-provenance-recover` больше не требует полного равенства Task manifest/lock с base.
 Base остаётся version authority, а parent/HEAD candidate сравниваются без единственных Workflow
 dependency entries. Поэтому recorded Task-local scripts сохраняются; payload drift того же candidate
 commit по-прежнему блокируется.
 
+`update downstream-proof-dependency-preflight/recover` — отдельная beta.12.6 совместимость для
+active proof, который делает обычный clean update недостижимым. После exact dependency-only commits
+на active base и Task branch preflight проверяет recorded history на `HEAD^`, candidate на `HEAD`,
+aligned runtime/declared/locked/installed/current/base versions, отсутствие leases/transactions,
+единственный active Step, transitive predecessor ownership и SHA-256 dirty product bytes. Recovery
+добавляет только candidate в `systemCommits` и сохраняет binding в
+`dependencyProvenanceRecoveries.activeDownstreamProof`; product work и Step state не меняются.
+Fresh `next` затем приоритетно рекламирует `task downstream-proof-recover` до Knowledge refresh.
+
 `task stop-override-prepare/apply` обслуживает только exact beta.11 attempt-four policy stop. Prepare
 не пишет state и создаёт binding по Task revision, Step, attempt-3 continue, attempt-4 stop, трём
 remediation events, Plan, HEAD, package, human actor и reason. Apply в отдельном user turn добавляет
@@ -421,12 +430,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.5
+# 18. Public command surface beta.12.6
 
 | Область | Actions |
 |---|---|
 | System | `doctor`, `status`, `next`, `gateway handshake`, `locks` |
-| Update | `preflight`, `rescue-preflight`, `dependency-provenance-preflight/recover` |
+| Update | `preflight`, `rescue-preflight`, `dependency-provenance-preflight/recover`, `downstream-proof-dependency-preflight/recover` |
 | Project memory | `scan`, `show`, `status`, `approve`, `reconcile` |
 | Delegation | `prepare`, `grant`, `list`, `show`, `revoke` |
 | Graph | `prepare`, `status`, `refresh-request`, `bind`, `fallback` |
@@ -445,10 +454,10 @@ Exact options берутся из fresh `next`; command help используе
 # 19. Release и package update gates
 
 Перед package update project-local `update preflight` должен вернуть `safe=true`: clean checkout, нет
-running Step и active/stale writer lease. External runner допустим только в документированной rescue
-compatibility форме.
+running Step и active/stale writer lease. Исключения — документированный alpha.7 rescue и beta.12.6
+active-downstream-proof dependency bridge; оба fail-closed и не дают общего разрешения dirty update.
 
-Перед beta.12.5 tag release repository выполняет:
+Перед beta.12.6 tag release repository выполняет:
 
 1. `npm ci`;
 2. `npm run validate`;

package/docs/release.md

@@ -27,7 +27,7 @@ The PDF check deterministically regenerates all three Russian documents from
 `docs/pdf/sources`, binds the visible package version to the root manifest, and fails when any
 tracked PDF is stale. Source and binary PDFs are one release unit.
 
-For beta.12.5, the release gate also relies on `npm run release:check` to fail if:
+For beta.12.6, 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;
@@ -53,6 +53,10 @@ For beta.12.5, the release gate also relies on `npm run release:check` to fail i
 - 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.
+- an eligible active downstream proof cannot transport one exact dependency-only update across
+  aligned base/Task commits while preserving product bytes; or unknown history, unrelated dirty
+  scope, content drift within an observation, leases, transactions, and wider candidates do not
+  fail closed before provenance registration and ordinary downstream recovery.
 - bundled gateway guidance treats Docker socket `EPERM` as daemon failure, consumes a remediation
   attempt before one exact escalated probe, or recommends restarting Docker Desktop without separate
   authority.

package/docs/updating-existing-project.md

@@ -59,6 +59,40 @@ candidate: его HEAD обязан менять ровно `package.json` и `p
 dependency; любое другое поле, добавленное тем же candidate commit, неизвестный commit, stale base,
 dirty checkout, lease или transaction по-прежнему блокируют recovery.
 
+### Исключение beta.12.6 для активного downstream proof
+
+Обычный `update preflight` по-прежнему правильно запрещает обновление при running Step и dirty
+checkout. Но если dirty set уже является подтверждаемым конфликтом между активным proof Step и
+completed transitive predecessor, ожидание чистой границы создаёт цикл: штатный recovery существует
+только в новой версии, а установить её до recovery нельзя. beta.12.6 разрешает только этот exact
+bootstrap и не ослабляет общий preflight.
+
+Сначала убедитесь, что нет active/stale writer lease, pending/corrupt transaction и Core operation.
+Не stash/reset/commit product files и не завершайте Step вручную. В отдельном временном worktree
+обновите active Milestone base до точной beta.12.6 и создайте commit только с `package.json` и
+`package-lock.json`. Затем в текущей Task branch установите ту же точную версию и создайте второй
+commit только из этих двух файлов, оставив существующий product dirty set неизменным. Не merge и
+не переносите product commits между ветками.
+
+Fresh project-local beta.12.6 `next` обязан вернуть
+`update downstream-proof-dependency-recover`. Выполните read-only
+`update downstream-proof-dependency-preflight --id <TASK-ID>` и продолжайте только при
+`eligible=true`, пустом `blockers`, ожидаемых `HEAD`/`HEAD^`, exact Task revision и непустом
+`activeDownstreamProof`. Binding включает current Plan, единственный active Step, все dirty paths,
+SHA-256 их содержимого и completed predecessor Steps, чья authority будет инвалидирована позже.
+После advertised recover повторите `status -> next`: ожидается `task downstream-proof-recover`,
+который имеет приоритет над Knowledge refresh, вызванным manifest/lock commit. Только после него
+выполняются новый Plan, Risk Audit, authorization и возвращённые `next` Knowledge actions.
+
+Read-only preflight является наблюдением, а не confirmation token: recover заново вычисляет и
+записывает binding текущего dirty content. Поэтому изменение допустимого product content до
+recover создаёт другой hash, который нужно сверить в ответе. После recover этот hash остаётся
+аудит-доказательством сохранённых bridge bytes; downstream-proof заново проверяет текущие paths,
+ownership и history, а новый Plan и review оценивают текущий content. Путь fail-closed при unrelated dirty path,
+неизвестном commit до candidate, candidate шире двух dependency-файлов, stale Milestone base,
+version divergence, branch/Plan/Step mismatch, lease или transaction. В этом случае не правьте
+`systemCommits` или внешний state вручную.
+
 ### Исключение beta.12.1 для beta.11 attempt-four stop
 
 Если beta.11 записал `stop-escalate` перед четвёртой попыткой только после последовательности
@@ -100,8 +134,9 @@ context refresh после уже подтверждённого Human override.
 
 ## 1. Подготовьте отдельный чат обновления
 
-Не обновляйте пакет во время выполняющегося Worker Step. Дождитесь завершения текущего ответа
-Codex и откройте в нужном проекте отдельный чат `Workflow update`.
+Не обновляйте пакет во время выполняющегося Worker Step, кроме exact beta.12.6 downstream-proof
+исключения выше. В обычном случае дождитесь завершения текущего ответа Codex и откройте в нужном
+проекте отдельный чат `Workflow update`.
 
 Передайте агенту этот промпт, заменив `<НОВАЯ_ВЕРСИЯ>` точной опубликованной версией:
 

package/docs/validation-report.md

@@ -1,101 +1,111 @@
-# V2 beta.12.5 Validation Report
+# V2 beta.12.6 Validation Report
 
-Release candidate `2.0.0-beta.12.5` was validated on 2026-08-29 (Europe/Moscow) with
+Release candidate `2.0.0-beta.12.6` was validated on 2026-08-29 (Europe/Moscow) with
 Node.js 24.17.0.
 
 ## Automated release evidence
 
-- The pre-install `npm run validate` passed typecheck and `332/332` sequential tests with no
-  failures, skips, cancellations, or todos in 1,313,147.293583 ms.
+- The first full `npm run validate` passed typecheck and `335/335` sequential tests with no
+  failures, skips, cancellations, or todos in 1,461,147.464875 ms.
 - `npm ci` then completed from the lockfile with 0 reported vulnerabilities. The clean-install
-  `npm run validate` independently passed the same `332/332` tests in 1,312,649.239333 ms.
-- A final credential-recovery review then added one mapping and one regression test for an eligible
-  claimed C1 recovery whose writer lease is absent. Post-change typecheck and the focused
-  downstream-proof, CLI-help, and lifecycle-model suite passed `15/15`; the final full
-  `npm run validate` passed `333/333` tests with no failures, skips, cancellations, or todos in
-  1,321,160.33825 ms.
-- The suite covers the beta.12.5 downstream-proof recovery, exact lifecycle inventory, C1 yield,
-  one-writer concurrency, transaction crash boundaries, tampered sidecars, unrelated dirty files,
-  ordinary active-Step completion, existing Signal T04 recovery, dependency DAG, observer purity,
-  credential secrecy, corrective replay, and Milestone validation/acceptance.
-- `npm run pack:check` built the exact beta.12.5 package: 274 files, 995.1 kB packed and 3.9 MB
-  unpacked. The first sandboxed attempt could not write the user npm cache (`EPERM`); the exact
-  authorized retry passed and included the new runtime module and public schema.
+  `npm run validate` independently passed the same `335/335` tests with no failures, skips,
+  cancellations, or todos in 1,461,906.892 ms.
+- The exact Signal T04/downstream recovery gate passed `8/8`. The targeted dependency-provenance,
+  downstream-proof, CLI-help, and lifecycle-model suite passed `23/23`.
+- The positive beta.12.6 fixture proves the complete compatibility sequence: exact active-base and
+  Task dependency commits, history validation at `HEAD^`, candidate validation at `HEAD`, dirty
+  content binding, dependency registration, fresh navigation to `task downstream-proof-recover`,
+  unchanged product bytes, and valid recorded Task history. Negative cases cover unrelated dirty
+  files, unregistered history, and an active writer lease. Existing Signal T04 tests remain intact.
+- `npm run pack:check` built the exact beta.12.6 package: 274 files, 1.0 MB packed and 4.0 MB
+  unpacked. The first attempt could not write the user npm cache (`EPERM`); the exact retry used an
+  isolated temporary cache and passed without changing global cache ownership.
 - `npm run smoke:downstream` packed and installed the tarball in a disposable consumer project and
   returned `ok=true`. The sandboxed attempt could not resolve the npm registry (`ENOTFOUND`); the
   exact network-authorized retry passed.
-- `npm run plugin:check`, `npm run docs:pdf:check`, exact
-  `RELEASE_TAG=v2.0.0-beta.12.5 npm run release:check`, and `git diff --check` passed. The bundled
-  gateway cachebuster remains `0.1.0+codex.20260828064343`.
+- `npm run plugin:check`, `npm run docs:pdf:check`, and exact
+  `RELEASE_TAG=v2.0.0-beta.12.6 npm run release:check` passed. The plugin gate caught one missing
+  `HEAD^` boundary in the human-facing gateway instructions; that boundary was added and the gate
+  then passed. The bundled gateway cachebuster is `0.1.0+codex.20260829120000`.
 
-## Root cause and bounded correction
+## Root cause corrected by beta.12.6
 
-- A downstream executable proof can demonstrate that a completed predecessor Step must change.
-  The existing navigation still advertised `task step-complete`, but that command correctly
-  rejected predecessor-owned dirty files. Repeating the command or increasing remediation attempts
-  could not solve the authority contradiction: predecessor completion evidence remained canonical
-  while the proof required changing its output.
-- beta.12.5 adds `task downstream-proof-recover`. It is advertised only when every dirty file
-  outside the active Step belongs to a completed transitive predecessor, Task branch/Plan/history
-  bindings are exact, the active Step has no completion evidence, and the Task uses a local
-  workspace. Unrelated files, damaged history, a branch mismatch, a malformed audit journal, or an
-  unregistered commit fail closed to `doctor`.
-- One crash-recoverable project transaction preserves worktree bytes and HEAD, append-only records
-  `downstream-proof-invalidations.jsonl`, moves invalidated product commits to historical
-  `invalidatedStepCommits`, clears stale Step/review/execution authority, yields claimed C1, removes
-  the writer lease, and returns the same Task to ordinary `task plan-set`.
-- No completed-Step adoption or synthetic replacement Task is performed. The replacement Plan must
-  re-cover the unfinished proof and invalidated predecessor work, then pass normal audit,
-  authorization, execution, and review again.
+- beta.12.5 correctly classified the current Signal downstream-proof conflict as recoverable, but
+  that did not make the release installable. Signal still runs beta.12.4, whose ordinary update
+  preflight rejects the running Step and dirty product work. Installing beta.12.5 would also advance
+  dependency manifests/HEAD before that new runtime could register the commit. The advertised
+  beta.12.5 recovery was therefore unreachable from the actual starting version.
+- This is an update authority deadlock, not a need for more review attempts: the old runtime cannot
+  authorize the dirty update, while the new runtime cannot be reached without an exact update.
+- beta.12.6 adds one bounded bridge rather than general dirty-update permission. The active
+  Milestone base and Task branch must each receive a separate dependency-only commit changing
+  exactly `package.json` and `package-lock.json`. A fresh beta.12.6 runtime then advertises
+  `update downstream-proof-dependency-recover` only for the active downstream-proof shape.
+- Preflight verifies recorded Task history at `HEAD^`, the exact candidate at `HEAD`, aligned
+  runtime/declared/locked/installed/current-branch/base versions, one active Step, completed
+  transitive-predecessor ownership, branch and Plan bindings, no lease, no pending/corrupt
+  transaction or Core operation, and every dirty path plus SHA-256 content.
+- Recovery registers only the dependency candidate in `systemCommits` and records the bound proof
+  in `dependencyProvenanceRecoveries.activeDownstreamProof`. It does not edit, stash, reset, commit,
+  or discard product work and does not change Step state. Fresh `next` then prioritizes
+  `task downstream-proof-recover` over manifest-induced Knowledge refresh.
+- The ordinary downstream recovery remains responsible for invalidating stale predecessor
+  completion authority and returning the same Task to a new Plan, Risk Audit, authorization,
+  execution, and strict-review cycle. beta.12.6 does not bypass that lifecycle.
 
-## Exact Signal read-only proof
+## Exact Signal read-only evidence
 
-- The final built beta.12.5 classifier inspected Signal repository
-  `/Users/home-pc/htdocs/projects/signal_v4`, project
-  `b06d0f18f790f4521a23c770`, and Task
-  `TASK-01M0WXJAD4GZGVNRJ284ND95C6` without mutating repository or Workflow state.
-- Persisted Task revision is 103 on branch
-  `codex/task-01m0wxjad4-processing-persistence-schema`; active Step is
-  `STEP-002-REAL-POSTGRES-PROOF`. HEAD is
+- The Signal repository `/Users/home-pc/htdocs/projects/signal_v4` was re-observed read-only after
+  implementation. It remains on branch
+  `codex/task-01m0wxjad4-processing-persistence-schema` at
   `88f8bf70d1591852ad90c976625430d4f20585ac`.
-- The classifier observed six dirty files. Five are outside the active Step and are owned by the
-  completed transitive predecessor `STEP-001-PROCESSING-MIGRATIONS`; the sixth,
-  `tools/postgres/run-processing-integration.ts`, belongs to the active proof Step. The predecessor
+- Its dirty set remains exactly six paths: five modified processing-migration files and one
+  untracked `tools/postgres/run-processing-integration.ts`. No Signal repository or Workflow state
+  was mutated during beta.12.6 implementation.
+- Prior read-only state inspection identified Task
+  `TASK-01M0WXJAD4GZGVNRJ284ND95C6`, revision 103, active Step
+  `STEP-002-REAL-POSTGRES-PROOF`, five files owned by completed transitive predecessor
+  `STEP-001-PROCESSING-MIGRATIONS`, and one file owned by the active proof Step. The predecessor
   evidence commit equals the preserved HEAD.
-- The result was `applicable=true`, `eligible=true`, with no blockers. This proves that the exact
-  current Signal boundary has a bounded beta.12.5 transition. It does not prove that the replacement
-  Plan, product checks, strict review, or the remainder of Milestone 3 will pass.
+- The installed beta.12.4 ordinary update preflight returned `safe=false` for the running Step and
+  dirty checkout. The external beta.12.5 classifier returned `applicable=true`, `eligible=true`, and
+  no recovery blockers, proving that the product boundary itself is supported but not that the old
+  update path can reach it.
+- The beta.12.6 regression fixture mirrors all six Signal paths and the same predecessor/active-Step
+  ownership split. It proves the new update bridge and subsequent downstream recovery route under
+  controlled Git/state mutations.
+- This is strong structural and synthetic evidence, not a claim that the published package has
+  already updated live Signal. The final operational proof still requires the released exact
+  package, two exact dependency-only transport commits, the advertised preflight/recover, and a
+  fresh Signal `status -> next` readback.
 
-## Sandbox-boundary prevention
-
-- The bundled gateway now classifies Docker socket/CLI `EPERM`, `operation not permitted`, and
-  `permission denied` from a sandbox as an execution-boundary failure, not evidence that the daemon,
-  image, or product infrastructure is broken.
-- It permits one exact escalated read-only probe or Plan check without consuming a remediation or
-  infrastructure retry. Docker Desktop restart, daemon mutation, or image substitution still
-  requires separate authority and an actual escalated daemon failure.
-- Plugin validation pins this guidance. The release gates exercised analogous npm cache/network
-  sandbox boundaries, but no live Docker daemon failure was synthesized; Docker runtime behavior is
-  therefore documentation/gateway-contract evidence, not an end-to-end Docker test claim.
-
-## beta.12.5 PDF release documentation evidence
+## PDF release documentation evidence
 
 - Three tracked Russian PDFs were regenerated from Markdown sources; `npm run docs:pdf:check`
   reported an empty stale set.
-- All 27 pages were rendered and visually inspected: architecture is 7 pages, the delegated
-  chat-only guide is 9 pages, and the technical reference is 11 pages. The changed recovery,
-  Docker-boundary, command-surface, and release pages have no visible clipping, overlap, or
-  unreadable content.
-- Visible titles, headers, commands, capabilities, and release gates identify beta.12.5.
+- All 27 pages were rendered and visually inspected: architecture is 7 pages (101,761 bytes), the
+  delegated chat-only guide is 9 pages (107,066 bytes), and the technical reference is 11 pages
+  (112,132 bytes).
+- Visual inspection found table headers rendered dark-on-dark. The shared generator now uses an
+  explicit white bold header Paragraph style; all documents were regenerated and re-inspected.
+  Titles, version headers, Cyrillic glyphs, tables, code blocks, recovery instructions, page edges,
+  and footers have no visible clipping, overlap, or unreadable content.
 
 ## Existing boundaries and non-claims
 
-- Structural replacement remains intentionally disabled. beta.12.5 does not implement P04-B,
+- Structural replacement remains intentionally disabled. beta.12.6 does not implement P04-B,
   topology rewiring, completed-Step adoption, or a wider delegation surface.
-- Recovery requires exact one-writer/C1 authority and a fresh `next`; it does not authorize manual
-  state edits, arbitrary Git history, unrelated dirty files, or automatic approval.
+- The compatibility bridge is limited to the proven active-downstream-proof shape. Unrelated dirty
+  paths, non-predecessor ownership, unknown history, a wider dependency commit, stale base/version
+  divergence, branch/Plan/Step mismatch, lease, transaction, or damaged sidecar fails closed.
+- Read-only preflight is an observation, not an authorization token. Recover recomputes the current
+  binding. The stored hash proves which bytes the bridge preserved; subsequent downstream recovery
+  revalidates paths, ownership, and history, while the replacement Plan and review cover current
+  content.
+- Git transport commits remain agent-executed operations on exact advertised boundaries. The
+  runtime does not create, amend, merge, reset, or push Git history.
 - Validation performed no Signal mutation, npm publication, Git commit, tag, remote push, or local
-  plugin reinstall. Those remain separate release actions.
-- A consumer must install the published exact beta.12.5 package, reinstall the bundled gateway, and
-  follow fresh project-local `handshake -> doctor -> status -> next` navigation before invoking the
-  advertised recovery.
+  plugin reinstall. Those are separate release/deployment actions.
+- Confidence is high for the implemented source and tested Signal-shaped transition. Confidence in
+  the final live Signal update remains pending until the published package is installed and the
+  project-local runtime returns the expected recovery sequence.

package/package.json

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

package/plugins/codex-workflow-gateway/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "codex-workflow-gateway",
-  "version": "0.1.0+codex.20260828064343",
+  "version": "0.1.0+codex.20260829120000",
   "description": "Thin personal Codex gateway for exact project-local Codex Workflow V2 packages and codebase-memory-mcp.",
   "author": {
     "name": "Codex Workflow Maintainers"

package/plugins/codex-workflow-gateway/references/protocol.md

@@ -1,6 +1,6 @@
 # Gateway Protocol V2
 
-## beta.12.5 compatibility transitions and continuable remediation
+## beta.12.6 compatibility transitions and continuable remediation
 
 - When fresh `next` advertises `task plan-integrity-recover`, consume its exact Task revision,
   Step, actor, and writer-token contract. This route is valid only for the Core-derived
@@ -15,6 +15,16 @@
   and routes the same Task to ordinary `task plan-set`. The replacement Plan, risk audit, and
   execution authorization are fresh authority; no Task or Milestone recreation is involved.
 
+- When an older installed package cannot reach that recovery because its normal update preflight
+  requires a clean checkout, beta.12.6 permits one bounded dependency transport. The active
+  Milestone base and Task branch must first receive separate exact commits changing only
+  `package.json` and `package-lock.json`; product work remains dirty and uncommitted. Fresh beta.12.6
+  `next` must then advertise `update downstream-proof-dependency-recover`. Its preflight proves the
+  Task history at `HEAD^`, the dependency candidate at `HEAD`, aligned version surfaces, no lease or
+  transaction, exact predecessor ownership, and a content hash of the dirty set. Recovery registers
+  only the dependency commit. It does not mutate product files or Step state; fresh `next` must
+  proceed to `task downstream-proof-recover`, which outranks manifest-induced Knowledge staleness.
+
 - `update dependency-provenance-preflight --id <TASK-ID>` is read-only. The matching
   `update dependency-provenance-recover --id <TASK-ID> --expected-revision <N> --actor <ACTOR>
   --reason <TEXT>` is valid only when preflight and fresh `next` both advertise it. Historical
@@ -108,6 +118,7 @@ Current capability set:
 - `plan-proof-obligations-v1`
 - `bounded-plan-integrity-recovery-v1`
 - `downstream-proof-predecessor-recovery-v1`
+- `active-downstream-proof-dependency-recovery-v1`
 - `corrective-yield-journal-v1`
 - `corrective-replan-journal-v1`
 - `corrective-replan-human-gate-v1`