codex-workflow-v2 2.0.0-beta.12.2 → 2.0.0-beta.12.4

package/docs/autonomy-guardrails.md

@@ -97,18 +97,27 @@ different attempt ordinal, missing attempt-3 continue authority, or an agent-aut
 outside the beta.11 policy shape. After a valid append, attempt four returns to the normal `task run`
 then strict-review cycle; review quality and all later corrective decisions remain unchanged.
 
-Beta.12.2 also handles the case where the accepted third attempt changed
-approved Project Knowledge: the already-applied override may be followed by the ordinary delegated
-`task context-refresh` before attempt four starts. A fresh `next` resumes `task run` only when Core
-can prove all of the following together: the same exact
-three-event remediation history and stop override remain hash-valid; the source and rebound Plans
-differ only in their canonical Knowledge Map binding line; one direct Knowledge rebind and one
-mechanical Plan Risk Audit rebound connect those Plans; the refreshed approval and execution
-authorization share the valid delegated authority; and the override plus refreshed authorization
-bind the same Git HEAD. The proof is derived from existing append-only evidence, so this route does
-not create a second recovery journal. Missing evidence, an extra rebind, semantic Plan change,
-different HEAD, or damaged chronology routes to `doctor` rather than weakening the generic
-two-attempt corrective recovery gate.
+Beta.12.4 also handles the case where the accepted third attempt changed approved Project Knowledge
+and package self-updates added later refreshes: the already-applied override may be followed by one
+or more ordinary delegated `task context-refresh` transitions before attempt four starts. A fresh
+`next` resumes `task run` only when Core can prove all of the following together: the same exact
+three-event remediation history and stop override remain hash-valid; every adjacent Plan differs
+only in its canonical Knowledge Map binding line; the Knowledge rebinds and mechanical Plan Risk
+Audit rebounds form one contiguous source-to-current chain; and the refreshed approval plus current
+execution authorization share the valid delegated authority. If Git HEAD advanced, every
+intervening commit must have one exact registered dependency-provenance recovery, one parent, a
+`systemCommits` binding, and exactly the `package.json`/`package-lock.json` diff. The proof is derived
+from existing append-only evidence, so this route does not create a second recovery journal.
+Missing evidence, semantic Plan change, an unregistered/product commit, a broken chain, or damaged
+chronology routes to `doctor` rather than weakening the generic two-attempt corrective recovery gate.
+
+If fresh navigation performs the final content refresh before the matching dependency-provenance
+recovery, that later administrative recovery may advance the Task revision without invalidating the
+mechanical audit. Core accepts the revision only when the exact count of post-audit recovery records
+fully explains the difference: each record must belong to the already verified single-parent Git
+chain, remain ordered, bind a Workflow system commit, and preserve the exact two-file dependency
+diff. A bare greater revision, unrelated Task write, duplicate record, damaged parent, product
+commit, or unverified recovery remains blocked.
 
 ### First-failure Plan-integrity recovery
 

package/docs/decisions.md

@@ -97,3 +97,17 @@ This document closes the requirement gaps identified during the V2 design review
 19. **Derived independent actors.** Core derives stable Task Worker and corrective Auditor
     actors from Task identity. This removes name-selection pauses without weakening C1 claim,
     lease, or auditor-independence checks.
+20. **Stop-override authority survives mechanical update chains.** The exact Human-confirmed
+    beta.11 attempt-four override remains valid across any contiguous append-only sequence of
+    content-only Plan rebinds. Every adjacent immutable Plan, Knowledge rebind, and mechanical
+    Plan Risk Audit rebound must agree. Git HEAD may advance only through a contiguous chain of
+    already registered dependency-provenance commits, each single-parent and limited to
+    `package.json` plus `package-lock.json`. Semantic Plan drift, product commits, missing
+    provenance, or broken chronology still fails closed; generic corrective-decision recovery
+    remains direct and is not widened.
+21. **Administrative revision continuity is evidence-accounted.** A dependency-provenance
+    recovery recorded after the current mechanical Plan Risk Audit may explain exactly one later
+    Task revision without invalidating an already applied stop override. Core counts only ordered
+    recovery records from the independently verified override-to-authorization Git chain and
+    requires the resulting expected revision to equal the current Task revision. Unexplained
+    revisions and damaged provenance remain blocked; this is not a general `revision >=` rule.

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

@@ -1,10 +1,10 @@
 ---
-title: Codex Workflow V2: архитектура beta.12.2
+title: Codex Workflow V2: архитектура beta.12.4
 subtitle: Источники истины, lifecycle, роли, delegation, зависимости Tasks и границы доверия
 part: Часть 1 из 3 | Архитектура
 document_version: 2.0
-date: 27 августа 2026
-subject: Архитектура и границы Codex Workflow V2 beta.12.2
+date: 28 августа 2026
+subject: Архитектура и границы Codex Workflow V2 beta.12.4
 ---
 
 # 1. Назначение и граница системы
@@ -18,7 +18,7 @@ Codex Workflow V2 - локальный state machine поверх Codex App, Git
 Система рассчитана на одного пользователя и одну машину. Она не предоставляет distributed locking,
 криптографическую идентификацию actor string или безопасную синхронизацию state между компьютерами.
 
-## 1.1. Что beta.12.2 гарантирует
+## 1.1. Что beta.12.4 гарантирует
 
 - exact project-local npm package и совместимый handshake до lifecycle действий;
 - Discovery до materialization Task или Milestone;
@@ -30,7 +30,7 @@ Codex Workflow V2 - локальный state machine поверх Codex App, Git
 - state-bound human gates либо ранее выданные bounded delegation contracts;
 - journaled recovery для составных переходов и fail-closed поведение при drift/corruption.
 
-## 1.2. Что beta.12.2 не гарантирует
+## 1.2. Что beta.12.4 не гарантирует
 
 - правильность продуктовой идеи или автоматически выбранного provider Task;
 - semantic sufficiency Plan, если точные факты нельзя доказать поддерживаемым analyzer;
@@ -225,13 +225,20 @@ Beta.12.1 добавила одну append-only compatibility оговорку:
 Plan, HEAD, lease, transaction или повреждённая chain блокируют переход. Попытка 4 снова проходит
 обычный `task run` и новый strict review.
 
-Beta.12.2 сохраняет этот override при одном последующем delegated `task context-refresh`, если Plan
-изменился только в canonical Knowledge Map binding. Core требует прямой rebind, механически
-эквивалентный Plan Risk Audit, общую delegated authority, корректную chronology и тот же Git HEAD.
-При утрате claimed writer lease используется только одновременно рекламируемый
-`task writer-credential-replace`; semantic Plan drift, второй rebind или повреждённая evidence chain
+Beta.12.4 сохраняет этот override при последовательности delegated `task context-refresh`, если
+каждая версия Plan изменилась только в canonical Knowledge Map binding. Core проверяет весь
+contiguous rebind/audit chain, mechanical equivalence каждого Plan Risk Audit, общую delegated
+authority и корректную chronology. Git HEAD может продвинуться только через последовательность
+зарегистрированных dependency-provenance commits, каждый из которых меняет ровно package.json и
+package-lock.json. При утрате claimed writer lease используется только одновременно рекламируемый
+`task writer-credential-replace`; semantic Plan drift, разрыв chain или любой другой commit
 возвращают `doctor`.
 
+Если последний dependency-provenance recovery записан уже после mechanical audit, он объясняет
+ровно один дополнительный Task revision. Core требует, чтобы audit boundary плюс количество
+проверенных post-audit recoveries точно равнялись current revision; произвольное увеличение
+revision, неверный parent или повреждённая provenance остаются blocker.
+
 Dependency-provenance recovery beta.12.1 также сохраняет ранее закоммиченные Task-local поля
 manifest/lock, даже если base их не содержит. Candidate остаётся dependency-only: после удаления
 только Workflow dependency parent и HEAD обязаны совпасть по всем product-owned полям.
@@ -245,7 +252,7 @@ worktree или Plan и не создаёт synthetic second failure; он за
 # 10. Operational checklist
 
 - exact package version установлен, bundled gateway соответствует release и переустановлен;
-- handshake подтверждает protocol 2, state schema 2 и beta.12.2 capabilities;
+- handshake подтверждает protocol 2, state schema 2 и beta.12.4 capabilities;
 - каждый mutation следует свежему `status -> next` и exact option contract;
 - semantic unknowns и human gates не маскируются delegation;
 - Task chats создаёт coordinator, credentials остаются только в памяти;

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.2 путь от нового Discovery до принятого Milestone без ручного CLI
+subtitle: Актуальный beta.12.4 путь от нового Discovery до принятого Milestone без ручного CLI
 part: Часть 2 из 3 | Практика
 document_version: 2.0
-date: 27 августа 2026
-subject: Практическое руководство по delegated Discovery и Milestone в Workflow V2 beta.12.2
+date: 28 августа 2026
+subject: Практическое руководство по delegated Discovery и Milestone в Workflow V2 beta.12.4
 ---
 
-# 1. Рабочая модель beta.12.2
+# 1. Рабочая модель beta.12.4
 
 Пользователь работает в одном 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.2 как точную devDependency после публикации release.
+2. Установите beta.12.4 как точную 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.2 должен сообщать `packageVersion=2.0.0-beta.12.2`, `protocolVersion=2`,
+Handshake beta.12.4 должен сообщать `packageVersion=2.0.0-beta.12.4`, `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.2 в delegated режиме.
+Проведи новый Milestone через Codex Workflow V2 beta.12.4 в delegated режиме.
 Repository: <ABSOLUTE-REPOSITORY-ROOT>.
 Milestone ID: AUTO.
 Delegate actor: agent:milestone-coordinator.
@@ -305,12 +305,18 @@ Task chat записывает его только при совпадении p
 Plan-integrity recovery не редактирует Plan, package.json или worktree и не синтезирует второй failure.
 P04-A не переносит completed Steps и не rewires dependencies при split.
 
-Если после применённого stop override `next` рекламирует delegated `task context-refresh`, выполните
-его как обычный atomic refresh и снова запросите `status -> next`. Продолжайте attempt 4 только при
-`stopOverrideContextRebind.state=validated`. При одновременном
+Если после применённого stop override `next` рекламирует delegated `task context-refresh` или
+`update dependency-provenance-recover`, выполните только этот advertised atomic/recovery переход и
+снова запросите `status -> next`. Таких механических refresh/update циклов может быть несколько.
+Продолжайте attempt 4 только при `stopOverrideContextRebind.state=validated`. При одновременном
 `writerCredentialRecovery.action=task writer-credential-replace` сначала восстановите credential
-точного claimant-актора. `doctor`, semantic Plan change, второй rebind или другой HEAD означают stop,
-а не ручной обход.
+точного claimant-актора. `doctor`, semantic Plan change, разрыв rebind/audit chain или HEAD commit без
+точного dependency-provenance record означают stop, а не ручной обход.
+
+Если advertised navigation записала dependency provenance после последнего context-refresh audit,
+продолжайте только когда fresh `next` сам вернул `task run`. Core обязан доказать, что каждый такой
+recovery объясняет ровно один дополнительный Task revision; простое `revision >=` не является
+authority.
 
 # 12. Milestone final acceptance
 
@@ -329,7 +335,7 @@ Task/project DGR. `dependencyBinding` для standalone handoff равен null.
 
 # 14. Итоговый checklist пользователя
 
-- beta.12.2 exact package и новый bundled gateway установлены;
+- beta.12.4 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.2
+title: Codex Workflow V2: технический справочник beta.12.4
 subtitle: Protocol 2, state schema 2, transactions, credentials, dependency authority, review и recovery
 part: Часть 3 из 3 | Technical reference
 document_version: 2.0
-date: 27 августа 2026
-subject: Технический контракт Codex Workflow V2 beta.12.2
+date: 28 августа 2026
+subject: Технический контракт Codex Workflow V2 beta.12.4
 ---
 
 # 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.2 | Значение |
+| Параметр beta.12.4 | Значение |
 |---|---|
-| npm package | `codex-workflow-v2@2.0.0-beta.12.2` |
+| npm package | `codex-workflow-v2@2.0.0-beta.12.4` |
 | 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.2 capabilities:
+Ключевые beta.12.4 capabilities:
 
 | Группа | Capabilities |
 |---|---|
@@ -46,7 +46,7 @@ Gateway выполняет:
 | Task planning | Plan Risk Audit, proof obligations, mechanical feasibility |
 | C1 | handoff sidecar, handoff bundle, derived Worker actor, credential replacement |
 | Reviews | strict reviewer, Step strict review, continuable remediation, evidence-bound fix/replan routing |
-| Recovery | Task-local dependency provenance, plan integrity, remediation mode, legacy stop override, context-only stop rebind, corrective yield/replan journals |
+| Recovery | Task-local dependency provenance, plan integrity, remediation mode, legacy stop override, append-only stop-rebind chain, corrective yield/replan journals |
 | Replacement | `structural-task-replacement-disabled-v1` |
 
 Handshake incompatibility прекращает работу. Запуск global package, `latest`, mutable range или соседней
@@ -316,7 +316,7 @@ 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.2 compatibility transitions
+# 13.1. beta.12.4 compatibility transitions
 
 `update dependency-provenance-recover` больше не требует полного равенства Task manifest/lock с base.
 Base остаётся version authority, а parent/HEAD candidate сравниваются без единственных Workflow
@@ -329,12 +329,21 @@ remediation events, Plan, HEAD, package, human actor и reason. Apply в отд
 `stop-escalate-overrides.jsonl`. Original corrective decision остаётся неизменным. Split, stale binding,
 lease/transaction, дубликат с другим binding и tampering fail closed.
 
-После apply один delegated `task context-refresh` может сделать исходный stop/override Plan hash
-историческим. `task run` снова доступен только если Core доказывает context-only direct rebind:
-семантическое содержимое Plan совпадает, Plan Risk Audit rebound механический, refresh approval и
-execution authorization имеют одну действующую authority, chronology монотонна, а authorization и
-override связывают один HEAD. Projection содержит `stopOverrideContextRebind.state=validated`.
-Утерянный claimed lease восстанавливается только рекламируемым `task writer-credential-replace`.
+После apply несколько delegated `task context-refresh` могут сделать source Plan историческим.
+`task run` доступен, только если Core доказывает contiguous source-to-current chain: adjacent Plans
+различаются лишь Knowledge binding, rebinds совпадают с artifacts, audits являются mechanical
+rebounds, а current approval/authorization сохраняют одну delegated authority и chronology.
+
+HEAD может отличаться от override только через зарегистрированные single-parent
+`dependencyProvenanceRecoveries` в `systemCommits`, каждый с exact `package.json`/`package-lock.json`
+diff. Semantic drift, иной commit или разрыв chain fail closed. Projection содержит
+`stopOverrideContextRebind.state=validated`; lost lease восстанавливает только advertised
+`task writer-credential-replace`.
+
+Если recovery записан после последнего rebound audit, evidence-bound revision равен
+`audit.taskRevision + 1 + postAuditVerifiedRecoveries.length`. В зачёт входят только ordered records
+из уже проверенной override-to-authorization Git chain. Формула должна точно равняться current Task
+revision; unrelated write, duplicate, неверный parent или product commit блокируют continuation.
 
 # 14. P04-A structural replacement boundary
 
@@ -393,7 +402,7 @@ Graph является навигационным индексом, не Project
 После каждой successful mutation обязателен sequential `status`, затем fresh `next`. Failed status/next
 не разрешает direct mutation. Syntax help read-only и не заменяет navigation authority.
 
-# 18. Public command surface beta.12.2
+# 18. Public command surface beta.12.4
 
 | Область | Actions |
 |---|---|
@@ -420,7 +429,7 @@ Exact options берутся из fresh `next`; command help используе
 running Step и active/stale writer lease. External runner допустим только в документированной rescue
 compatibility форме.
 
-Перед beta.12.2 tag release repository выполняет:
+Перед beta.12.4 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.2, the release gate also relies on `npm run release:check` to fail if:
+For beta.12.4, 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,9 +57,13 @@ For beta.12.2, the release gate also relies on `npm run release:check` to fail i
 - the append-only, Human-confirmed beta.11 attempt-four stop override, its exact three-event/
   continue/stop binding, split rejection, stale-confirmation rejection, or tamper detection is
   absent from the package.
-- an already-applied beta.11 stop override cannot survive one later context-only Plan rebind with
-  exact mechanical audit, delegation, chronology, and same-HEAD evidence; or the route weakens the
-  generic stale-decision recovery gate.
+- an already-applied beta.11 stop override cannot survive a contiguous append-only chain of later
+  context-only Plan rebinds with exact mechanical audits, delegation, and chronology;
+- Git HEAD may advance between the override and current execution authorization through anything
+  except an exact chain of registered dependency-provenance commits that each change only
+  `package.json` and `package-lock.json`; or the route weakens the generic stale-decision recovery gate.
+- a dependency-provenance recovery recorded after the final mechanical audit cannot explain its
+  exact single Task revision, or an unrelated revision/damaged provenance is accepted as authority.
 
 The separate lifecycle transcript validator fails if the real-agent log contains a mutation that
 bypasses failed `status`/`next`, an unadvertised or failed mutation, an unresolved syntax-only

package/docs/updating-existing-project.md

@@ -73,20 +73,28 @@ stop decision, Plan hash, Git HEAD, все три remediation events и policy
 `SOO-*` кодом. `task stop-override-apply` добавляет одну запись в
 `stop-escalate-overrides.jsonl`, сохраняя исходный `stop-escalate`; после него выполните
 последовательные `status` и `next`. Обычно ожидаемый route — `task run` того же Step с последующим
-новым strict review. Beta.12.2 дополнительно покрывает случай, когда третья
-попытка изменила Project Knowledge: перед `task run` допустим обычный
-delegated `task context-refresh`. После него Workflow продолжит attempt 4 только при
-доказанном прямом rebind: source и current Plan отличаются исключительно canonical Knowledge Map
-binding, Plan Risk Audit rebound механический, refresh approval/authorization имеют одну валидную
-delegated authority, а override и новая execution authorization связывают тот же Git HEAD. Новая
-recovery-запись для этого не создаётся — используется уже существующая append-only цепочка.
+новым strict review. Beta.12.4 покрывает и последовательность package self-update/context-refresh
+циклов после override. Перед `task run` выполняйте только свежие advertised
+`update dependency-provenance-recover` и delegated `task context-refresh`; циклов может быть
+несколько. Workflow продолжит attempt 4 лишь когда докажет contiguous source-to-current chain:
+каждый Plan отличается только canonical Knowledge Map binding, каждый rebind совпадает с Plan
+artifacts, каждый Plan Risk Audit является mechanical rebound, а current approval/authorization
+сохраняют одну delegated authority. HEAD может продвинуться только через зарегистрированные
+single-parent dependency-provenance commits, каждый с exact `package.json`/`package-lock.json` diff.
+Новая stop-override recovery-запись не создаётся — используется существующая append-only evidence.
+Если advertised navigation сначала завершила последний `task context-refresh`, а затем разрешила
+`update dependency-provenance-recover`, административный recovery может объяснить ровно один
+post-audit Task revision. Core принимает его только как часть уже проверенной dependency-only Git
+chain; арифметика audit revision + refresh boundary + exact post-audit recoveries должна точно
+равняться current Task revision. Любой необъяснённый revision остаётся blocker.
 Если C1 остаётся claimed, но writer lease после Human boundary отсутствует, `next` вместе с
 `task run` рекламирует `task writer-credential-replace`; сначала восстановите credential exact
 claimant-актора, затем запускайте Step.
 
 Этот путь не работает для `split-required`, другого attempt ordinal, семантически изменённого
-Plan, другого HEAD, отсутствующего attempt-3 continue, более чем одного rebind, повреждённой
-chronology, active/stale lease на Human prepare/apply boundary или незавершённой Task transaction.
+Plan, отсутствующего attempt-3 continue, разорванной rebind/audit chain, незарегистрированного или
+product HEAD commit, повреждённой chronology, active/stale lease на Human prepare/apply boundary
+или незавершённой Task transaction.
 Delegated approval для самого stop override отсутствует; delegation относится только к обычному
 context refresh после уже подтверждённого Human override.
 

package/docs/validation-report.md

@@ -1,102 +1,98 @@
-# V2 beta.12.2 Validation Report
+# V2 beta.12.4 Validation Report
 
-Release candidate `2.0.0-beta.12.2` was validated across 2026-08-27/28 (Europe/Moscow) with
+Release candidate `2.0.0-beta.12.4` was validated on 2026-08-28 (Europe/Moscow) with
 Node.js 24.17.0.
 
 ## Automated release evidence
 
-- `npm ci` completed from the committed lockfile with 0 reported vulnerabilities.
-- The final `npm run validate` passed typecheck and `326/326` sequential tests with no failures,
-  skips, cancellations, or todos in 1,273,564.586583 ms.
-- The full suite includes the beta.12.2 attempt-four/context-rebind replay, the unchanged-Plan
-  stop-override suite, five-cycle continuable remediation, generic stale-decision recovery,
-  credential safety, dependency provenance, Signal T04, P01-A, P04-A, transaction, observer-purity,
-  and transition-model regressions.
-- `npm run pack:check` produced the beta.12.2 dry-run tarball with 270 files, package size 972.1 kB,
-  and unpacked size 3.8 MB. The sandboxed npm-cache attempt failed with `EPERM`; the authorized
-  retry using the same source passed.
-- `npm run smoke:downstream` packed and installed
-  `codex-workflow-v2-2.0.0-beta.12.2.tgz` in an empty temporary project and passed the packaged
-  handshake. The sandboxed attempt could not resolve the npm registry for AJV; the authorized
-  network retry using the same source passed.
+- `npm ci` completed from the lockfile with 0 reported vulnerabilities.
+- The final `npm run validate` passed typecheck and `328/328` sequential tests with no failures,
+  skips, cancellations, or todos in 1,348,269.052041 ms.
+- The suite includes the beta.12.4 real-order replay (`stop override -> context refresh -> base
+  transport -> dependency provenance recovery -> task run`) and two fail-closed controls: an
+  unexplained Task revision and damaged post-audit dependency provenance. Existing beta.12.3
+  chained rebind, Signal T04, five-cycle remediation, transaction, credential, observer-purity,
+  dependency DAG, transition-catalog, and lifecycle transcript tests also remained green.
+- `npm run pack:check` built the exact beta.12.4 package and reported a 270-file tarball. The first
+  sandboxed attempt could not write the existing npm cache (`EPERM`); the authorized retry using
+  the same source passed.
+- `npm run smoke:downstream` packed and installed the tarball in a clean temporary project and
+  passed its packaged handshake. The sandboxed attempt could not resolve the npm registry for AJV;
+  the authorized network retry using the same source passed.
 - `npm run plugin:check`, the official Codex plugin validator, the gateway skill validator,
-  `npm run docs:pdf:check`, exact `RELEASE_TAG=v2.0.0-beta.12.2 npm run release:check`, and
-  `git diff --check` passed. The official Python validators used a temporary isolated `PyYAML`
-  dependency; no project or system Python files were changed. The bundled gateway cachebuster is
-  `0.1.0+codex.20260827205000`.
+  `npm run docs:pdf:check`, exact `RELEASE_TAG=v2.0.0-beta.12.4 npm run release:check`, and
+  `git diff --check` passed. The bundled gateway cachebuster is
+  `0.1.0+codex.20260828064343`.
 
-## beta.12.2 stop-override/context-rebind compatibility
+## Root cause and bounded correction
 
-- The reproduced incompatibility is narrow: an exact beta.11 attempt-four stop was already
-  Human-overridden, then the successful third attempt changed approved Project Knowledge and the
-  ordinary delegated `task context-refresh` rebound the Plan to the new Knowledge Map. The original
-  override remained valid evidence but its Plan hash no longer equalled the current Plan hash.
-- Core now derives continuation only from existing append-only evidence. It requires exactly three
-  remediation events (`ordinary`, `ordinary`, `corrective`), the matching attempt-3 `continue-fix`,
-  matching attempt-4 `stop-escalate`, one applied stop override, one direct Knowledge rebind, a
-  mechanically equivalent Plan Risk Audit rebound, shared valid delegated authority, monotonic
-  chronology, and the same Git HEAD in the override and refreshed execution authorization.
-- Fresh `next` returns `task run` with `stopOverrideContextRebind.state=validated` only when every
-  binding above remains current. The fourth attempt remains mode `corrective` and passes through the
-  normal checks and strict-review cycle.
-- If C1 remains claimed but the writer lease was lost at the Human boundary, the same projection
-  exposes the existing `task writer-credential-replace` recovery for the exact claimant. No token is
-  persisted or reconstructed from evidence.
-- The route creates no new recovery journal and does not rewrite the stop, override, Plan, audit, or
-  authorization history. Semantic Plan drift, a second rebind, different HEAD, wrong authority,
-  malformed chronology, missing/duplicate override evidence, or sidecar corruption fails closed and
-  routes to `doctor`.
+- beta.12.3 validated the chained Knowledge-only Plan rebind and the exact Git
+  dependency-provenance chain, but retained the older Task-revision predicate
+  `reboundAudit.taskRevision + 1 === task.revision` for a failed Step.
+- Signal's actual install flow created the last mechanical Plan Risk Audit at Task revision 22,
+  wrote the atomic context-refresh result at revision 23, then registered one advertised
+  dependency-provenance recovery at revision 24. The old predicate therefore rejected valid,
+  already-verified administrative evidence at the next navigation step.
+- beta.12.4 derives the exact authorization boundary as
+  `reboundAudit.taskRevision + 1 + verifiedPostAuditRecoveries.length`. Only recovery records from
+  the already validated stop-override-to-authorization Git chain count. Each record must remain
+  ordered, single-parent, present in `systemCommits`, and an exact `package.json` plus
+  `package-lock.json` Workflow dependency commit.
+- This is not a permissive `revision >=` rule. An unrelated state write, duplicate or malformed
+  recovery, wrong parent, product-file change, semantic Plan drift, or broken chronology still
+  routes to diagnostics.
 
-## Existing compatibility and lifecycle regressions retained
+## Exact Signal read-only proof
 
-- The unchanged-Plan Human-confirmed beta.11 stop override remains append-only, idempotent, and
-  unavailable for `split-required`, stale confirmation bindings, or tampered evidence.
-- The general guarded-remediation model still has no attempt-count hard stop. Attempts 1-2 are
-  ordinary; attempts 3+ are corrective and remain executable under fresh review authority. The
-  beta.12.2 exception does not weaken the generic stale `continue-fix` recovery predicate.
-- Task-local dependency-provenance recovery still preserves product fields recorded before the
-  dependency-only candidate while rejecting candidate payload drift. The exact Signal T04
-  revision-26 replay retains only passed, attested historical Step commits and rejects pending or
-  corrupt review chains.
-- P01-A mechanical feasibility, P04-A Milestone dependency authority, atomic initial Plan and
-  project transactions, external-sealed review, corrective yield/replan, and observer byte-purity
-  remain green.
-- Structural replacement remains intentionally disabled. A `split-required` posture still returns
-  `STRUCTURAL_REPLACEMENT_REQUIRED` with no Task/Discovery/Milestone/Knowledge/lock mutation.
+- The final built beta.12.4 validator inspected Signal repository
+  `/Users/home-pc/htdocs/projects/signal_v4`, Task
+  `TASK-01M0WXJAD4GZGVNRJ284ND95C6`, and failed Step
+  `STEP-001-PROCESSING-MIGRATIONS` without mutating the repository or Workflow state.
+- The persisted state has Task revision 24, current Plan hash
+  `6a0c9b7a2a2ec11c9d6a9a24137dc17be1ecd18be42cf0188200942313776a50`, four Knowledge rebinds,
+  three dependency-provenance recoveries, applied override
+  `SOO-01M127VPRC5M5F3E3K7PS4MFJY`, and final rebound audit revision 22. Exactly one verified
+  recovery was recorded after that audit, so `22 + 1 + 1 = 24`.
+- A direct final-build `next --repo /Users/home-pc/htdocs/projects/signal_v4 --json` returned
+  `action=task run`, revision 24, the expected Step, and
+  `stopOverrideContextRebind.state=validated`. It also preserved the exact claimed C1 actor and
+  writer-credential recovery contract.
+- This proves compatibility with the currently persisted Signal M3 boundary. It does not prove
+  that future product implementation or strict reviews will pass.
 
-## Packaged and transcript evidence
+## Packaged, plugin, and transcript evidence
 
-- Downstream smoke validated exact package resolution and the packaged beta.12.2 handshake in a
-  clean disposable installation.
-- A temporary trusted harness invoked the final built CLI sequentially for `gateway handshake`,
-  `doctor`, `status`, and fresh `next` against this unregistered source repository with an isolated
-  Workflow state root. All observations completed successfully and remained read-only.
-- `node scripts/validate-lifecycle-transcript.mjs` accepted all `8/8` post-provenance events with no
-  failed invocation, mutation, or missing terminal result. The log SHA-256 is
-  `954a1c97f455ae3c8e02211b6fb63982b30cbfa1c40d92ce712f4a208d0e3a8f`; the temporary log remains
+- Downstream smoke validated exact package resolution and the packaged beta.12.4 handshake in a
+  disposable installation.
+- The bundled gateway handshake reports package beta.12.4, protocol 2, state schema 2, and the new
+  `stop-override-post-audit-dependency-revision-v1` capability.
+- A temporary trusted-harness transcript recorded the final built `gateway handshake` invocation
+  and terminal result. `node scripts/validate-lifecycle-transcript.mjs` accepted both
+  post-provenance events. The log SHA-256 is
+  `4ec7d8cb105d901e82d1049c273c4f2ec8d22ea12e0116ed70cfa8ab703ea2eb`; the temporary log remains
   outside the repository.
 
 The transcript proves release-time invocation/result discipline for the final CLI. It does not
-claim a product Milestone replay or a lifecycle mutation. The compatibility transition is covered
-by deterministic repository/sidecar integration tests above.
+claim a product Milestone replay or lifecycle mutation. Compatibility is covered by the exact
+Signal read-only proof and deterministic integration tests above.
 
-## beta.12.2 PDF release documentation evidence
+## beta.12.4 PDF release documentation evidence
 
 - Three tracked Russian PDFs were deterministically regenerated from reviewable Markdown sources
   under `docs/pdf/sources`; `npm run docs:pdf:check` reported an empty stale set.
-- All 25 final pages were rendered and visually inspected: architecture is 7 pages, the delegated
-  chat-only guide is 8 pages, and the technical reference is 10 pages. No blank, clipped,
-  overlapping, or orphaned final page was found. Visual QA removed one redundant two-line spill
-  that had created an otherwise empty eleventh technical-reference page.
-- Visible titles, headers, package commands, and release gates identify beta.12.2. The documents
-  distinguish the unchanged-Plan beta.12.1 override from beta.12.2 context-only rebind continuation,
-  exact claimant credential recovery, and all fail-closed boundaries.
+- All 26 pages were rendered and visually inspected: architecture is 7 pages, the delegated
+  chat-only guide is 8 pages, and the technical reference is 11 pages. Full-size inspection of the
+  three changed compatibility pages found no clipped, overlapping, or unreadable content.
+- Visible titles, headers, package commands, capabilities, and release gates identify beta.12.4.
+  The documents state the exact evidence-bound revision formula and its fail-closed boundary.
 
-## Not claimed
+## Existing boundaries and non-claims
 
-- Validation itself performs no npm publication, Git tag, push, Signal project mutation, or local
-  plugin reinstall. Tagging and remote push are separate release actions after these exact gates.
-- beta.12.2 does not implement P04-B, topology rewiring, completed-Step adoption, a general semantic
-  stop reversal, multi-rebind recovery, or a wider delegation surface.
-- A real project must install the published exact beta.12.2 package, update/reinstall the bundled
-  gateway, and follow fresh project-local `handshake -> doctor -> status -> next` navigation.
+- The generic stale `continue-fix` recovery predicate is unchanged. The compatibility route does
+  not reverse a semantic stop or authorize arbitrary Git/state history.
+- Structural replacement remains intentionally disabled. beta.12.4 does not implement P04-B,
+  topology rewiring, completed-Step adoption, or a wider delegation surface.
+- Validation performed no Signal mutation, npm publication, Git commit, tag, remote push, or local
+  plugin reinstall. Those are separate release actions after these gates.
+- A consumer must install the published exact beta.12.4 package, update/reinstall the bundled
+  gateway, and use fresh project-local `handshake -> doctor -> status -> next` navigation.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "codex-workflow-v2",
-  "version": "2.0.0-beta.12.2",
+  "version": "2.0.0-beta.12.4",
   "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.20260827205000",
+  "version": "0.1.0+codex.20260828064343",
   "description": "Thin personal Codex gateway for exact project-local Codex Workflow V2 packages and codebase-memory-mcp.",
   "author": {
     "name": "Codex Workflow Maintainers"