codex-workflow-v2 2.0.0-beta.12 → 2.0.0-beta.12.1

package/docs/autonomy-guardrails.md

@@ -74,7 +74,28 @@ default. `replan` is accepted only with `planConflict.planClause`, `whyFixCannot
 `minimalPlanChange`; Core retains that evidence in the hash-chained Step-review event and routes
 the failed Step to `task plan-set`. Replan may change implementation Steps only. Explicit historical
 `continue-fix`, `replan-required`, `split-required`, and `stop-escalate` decisions remain readable;
-an explicit split or stop still outranks ordinary execution.
+an explicit split or stop still outranks ordinary execution except for the narrow beta.11
+attempt-four stop compatibility route below.
+
+### Human-confirmed beta.11 attempt-four stop compatibility
+
+Beta.12.1 can resume one historical shape that beta.11 stopped mechanically: the same failed
+guarded Step has exactly two `ordinary` remediation events, one `corrective` third event, an exact
+attempt-3 `continue-fix` decision, and an attempt-4 `stop-escalate` decision under the unchanged
+Plan. Fresh `next` advertises `task stop-override-prepare` only for that shape and only on a clean
+local Task branch with no Step in progress, writer lease, Task transaction, or Core operation.
+
+Preparation is read-only and binds Task revision, Step, both corrective decisions, all three
+remediation events, Plan hash, Git HEAD, package version, actor, and reason to an `SOO-*`
+confirmation code. In a later explicit user turn, invoke `task stop-override-apply` with the same
+inputs and code. Apply appends `stop-escalate-overrides.jsonl`; it never deletes or rewrites the
+original stop. A stale binding, wrong code, duplicate/conflicting override, or damaged hash chain
+fails before continuation. Delegation is not accepted for this Human gate.
+
+This is not a general stop reversal. It does not apply to `split-required`, Plan drift, a different
+attempt ordinal, missing attempt-3 continue authority, or an agent-authored semantic stop 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.
 
 ### First-failure Plan-integrity recovery
 

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

@@ -1,10 +1,10 @@
 ---
-title: Codex Workflow V2: архитектура beta.12
+title: Codex Workflow V2: архитектура beta.12.1
 subtitle: Источники истины, lifecycle, роли, delegation, зависимости Tasks и границы доверия
 part: Часть 1 из 3 | Архитектура
 document_version: 2.0
 date: 27 августа 2026
-subject: Архитектура и границы Codex Workflow V2 beta.12
+subject: Архитектура и границы Codex Workflow V2 beta.12.1
 ---
 
 # 1. Назначение и граница системы
@@ -18,7 +18,7 @@ Codex Workflow V2 - локальный state machine поверх Codex App, Git
 Система рассчитана на одного пользователя и одну машину. Она не предоставляет distributed locking,
 криптографическую идентификацию actor string или безопасную синхронизацию state между компьютерами.
 
-## 1.1. Что beta.12 гарантирует
+## 1.1. Что beta.12.1 гарантирует
 
 - 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 не гарантирует
+## 1.2. Что beta.12.1 не гарантирует
 
 - правильность продуктовой идеи или автоматически выбранного provider Task;
 - semantic sufficiency Plan, если точные факты нельзя доказать поддерживаемым analyzer;
@@ -218,6 +218,17 @@ Failed review не ограничивает число попыток. Попы
 `route=replan` допустим только с точным Plan conflict и меняет лишь implementation Steps, не objective,
 requirements или acceptance. Explicit `split-required` и `stop-escalate` остаются stop/redirect decisions.
 
+Beta.12.1 добавляет только одну append-only compatibility оговорку: beta.11 attempt-four
+`stop-escalate` после exact `ordinary, ordinary, corrective` и prior attempt-3 `continue-fix` можно
+возобновить через read-only `stop-override-prepare` и отдельный Human-confirmed
+`stop-override-apply`. Исходный stop сохраняется, `split-required` не подходит, а stale revision,
+Plan, HEAD, lease, transaction или повреждённая chain блокируют переход. Попытка 4 снова проходит
+обычный `task run` и новый strict review.
+
+Dependency-provenance recovery beta.12.1 также сохраняет ранее закоммиченные Task-local поля
+manifest/lock, даже если base их не содержит. Candidate остаётся dependency-only: после удаления
+только Workflow dependency parent и HEAD обязаны совпасть по всем product-owned полям.
+
 beta.11 `task plan-integrity-recover` существует для одного первого checks-failed legacy/late case:
 отсутствует exact root npm script и текущий Step не может изменить package.json. Recovery не меняет
 worktree или Plan и не создаёт synthetic second failure; он записывает bound `replan-required`.
@@ -227,7 +238,7 @@ worktree или Plan и не создаёт synthetic second failure; он за
 # 10. Operational checklist
 
 - exact package version установлен, bundled gateway соответствует release и переустановлен;
-- handshake подтверждает protocol 2, state schema 2 и beta.12 capabilities;
+- handshake подтверждает protocol 2, state schema 2 и beta.12.1 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 путь от нового Discovery до принятого Milestone без ручного CLI
+subtitle: Актуальный beta.12.1 путь от нового Discovery до принятого Milestone без ручного CLI
 part: Часть 2 из 3 | Практика
 document_version: 2.0
 date: 27 августа 2026
-subject: Практическое руководство по delegated Discovery и Milestone в Workflow V2 beta.12
+subject: Практическое руководство по delegated Discovery и Milestone в Workflow V2 beta.12.1
 ---
 
-# 1. Рабочая модель beta.12
+# 1. Рабочая модель beta.12.1
 
 Пользователь работает в одном 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 как точную devDependency после публикации release.
+2. Установите beta.12.1 как точную 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 должен сообщать `packageVersion=2.0.0-beta.12`, `protocolVersion=2`,
+Handshake beta.12.1 должен сообщать `packageVersion=2.0.0-beta.12.1`, `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 в delegated режиме.
+Проведи новый Milestone через Codex Workflow V2 beta.12.1 в delegated режиме.
 Repository: <ABSOLUTE-REPOSITORY-ROOT>.
 Milestone ID: AUTO.
 Delegate actor: agent:milestone-coordinator.
@@ -297,7 +297,8 @@ 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 |
-| Explicit `stop-escalate` | Terminal user attention |
+| 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` |
 | Review seal drift | Discard review и создать fresh packet |
 
@@ -321,7 +322,7 @@ Task/project DGR. `dependencyBinding` для standalone handoff равен null.
 
 # 14. Итоговый checklist пользователя
 
-- beta.12 exact package и новый bundled gateway установлены;
+- beta.12.1 exact package и новый bundled gateway установлены;
 - новый Coordinator chat не является fork старого Milestone;
 - bootstrap DGR, если нужен, выдан отдельным exact human confirmation;
 - Discovery не materialized при blocking unknowns;
@@ -330,5 +331,6 @@ Task/project DGR. `dependencyBinding` для standalone handoff равен null.
 - Coordinator сам создаёт и supervises Task/Reviewer chats;
 - credentials не появились в prompts, reports или files;
 - каждый transition пришёл из fresh `next`;
+- beta.11 stop override, если рекламировался, прошёл отдельные prepare и user-confirmed apply без journal rewrite;
 - 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
+title: Codex Workflow V2: технический справочник beta.12.1
 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
+subject: Технический контракт Codex Workflow V2 beta.12.1
 ---
 
 # 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 | Значение |
+| Параметр beta.12.1 | Значение |
 |---|---|
-| npm package | `codex-workflow-v2@2.0.0-beta.12` |
+| npm package | `codex-workflow-v2@2.0.0-beta.12.1` |
 | 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 capabilities:
+Ключевые beta.12.1 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 | dependency provenance, plan integrity, remediation mode, corrective yield/replan journals |
+| Recovery | Task-local dependency provenance, plan integrity, remediation mode, legacy stop override, corrective yield/replan journals |
 | Replacement | `structural-task-replacement-disabled-v1` |
 
 Handshake incompatibility прекращает работу. Запуск global package, `latest`, mutable range или соседней
@@ -65,7 +65,7 @@ $CODEX_HOME/workflow-state/v2/projects/<project-id>/
   tasks/<TASK-ID>/
     brief.md, plan.md, result.md, evidence.json, state.json
     .versions/
-    authorization/review/remediation/corrective/handoff sidecars
+    authorization/review/remediation/corrective/stop-override/handoff sidecars
   milestones/<MS-ID>/
     plan.json, result.md, evidence.json, state.json
     .versions/ и scope/autonomy sidecars
@@ -291,7 +291,8 @@ Guarded Step имеет проверяемый, но не ограниченны
 | Finding `route=replan` с exact Plan conflict | `task plan-set`; меняются только implementation Steps |
 | `route=replan` без exact conflict | Невалидный review result, state не меняется |
 | Explicit `split-required` | Structural replacement stop |
-| Explicit `stop-escalate` | Terminal user attention |
+| Exact beta.11 attempt-four `stop-escalate` | Append-only Human-confirmed compatibility override |
+| Любой другой explicit `stop-escalate` | Terminal user attention |
 
 Attempt count является диагностикой, а не lifecycle authority. Explicit corrective-decision journal
 сохраняется для намеренного stop/split и совместимого historical recovery, но не требуется после второй
@@ -315,6 +316,19 @@ 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.1 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 по-прежнему блокируется.
+
+`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 добавляет
+`stop-escalate-overrides.jsonl`. Original corrective decision остаётся неизменным. Split, stale binding,
+lease/transaction, дубликат с другим binding и tampering fail closed.
+
 # 14. P04-A structural replacement boundary
 
 Command shape `task replacement-materialize` retained только для compatibility diagnostics. Любая попытка
@@ -372,7 +386,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
+# 18. Public command surface beta.12.1
 
 | Область | Actions |
 |---|---|
@@ -387,7 +401,7 @@ Graph является навигационным индексом, не Project
 | Task execution | `start`, `run`, `step-complete`, `submit`, `result-set`, `accept`, `sync-base`, `merge`, `merge-confirm` |
 | C1 | `handoff[-prepare/-replace/-show]`, `claim`, `writer-credential-replace`, `handback[-create]` |
 | Review | review/step-review packet, launch, sealed record и record actions |
-| Corrective | decision/recovery, plan-integrity, remediation-mode, yield и corrective-replan actions |
+| Corrective | decision/recovery, plan-integrity, remediation-mode, stop-override prepare/apply, yield и corrective-replan actions |
 | Replacement | `replacement-materialize` retained, но всегда disabled в P04-A |
 
 Exact options берутся из fresh `next`; command help используется только когда
@@ -399,7 +413,7 @@ Exact options берутся из fresh `next`; command help используе
 running Step и active/stale writer lease. External runner допустим только в документированной rescue
 compatibility форме.
 
-Перед beta.12 tag release repository выполняет:
+Перед beta.12.1 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, the release gate also relies on `npm run release:check` to fail if:
+For beta.12.1, 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;
@@ -44,6 +44,8 @@ For beta.12, the release gate also relies on `npm run release:check` to fail if:
   commands are absent from the packaged surface.
 - bounded dependency-provenance recovery, retained passed-review provenance, the exact Signal T04
   revision-26 fixture, or pending/corrupt-review rejection regressions are absent.
+- dependency recovery again requires Task-local manifest/lock fields to equal the Milestone base,
+  or a candidate commit can alter any non-Workflow dependency payload.
 - 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
@@ -52,6 +54,9 @@ For beta.12, the release gate also relies on `npm run release:check` to fail if:
   feasibility capability is absent from the packaged handshake.
 - continuable guarded remediation or evidence-bound `fix`/`replan` review routing is absent, or a
   third/later failed review is again converted into an attempt-count stop.
+- 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.
 
 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

@@ -52,6 +52,31 @@ commit остался в Git между `baseCommit` и новым dependency-on
 него обязательны последовательные `status` и `next`; выполняйте возвращённый Knowledge reconcile
 или `task context-refresh`, если manifest/lock сделали Knowledge Map stale.
 
+В beta.12.1 preflight сравнивает parent и candidate после удаления только записей зависимости
+`codex-workflow-v2`. Поэтому ранее закоммиченные Task-local scripts и другие product-owned поля
+`package.json`/lockfile могут отличаться от Milestone base и сохраняются. Это не ослабляет сам
+candidate: его HEAD обязан менять ровно `package.json` и `package-lock.json`, только точную Workflow
+dependency; любое другое поле, добавленное тем же candidate commit, неизвестный commit, stale base,
+dirty checkout, lease или transaction по-прежнему блокируют recovery.
+
+### Исключение beta.12.1 для beta.11 attempt-four stop
+
+Если beta.11 записал `stop-escalate` перед четвёртой попыткой только после последовательности
+`ordinary`, `ordinary`, `corrective`, и перед третьей попыткой уже существовал exact
+`continue-fix`, fresh `next` может вернуть `task stop-override-prepare`. Не создавайте новый
+Milestone и не редактируйте sidecar вручную. Сначала выполните только read-only prepare с exact
+Task revision, Step, human actor и содержательной причиной. Проверьте, что ответ связывает тот же
+stop decision, Plan hash, Git HEAD, все три remediation events и policy
+`beta11-attempt4-stop-compatibility-v1`, затем остановитесь перед Human gate.
+
+В отдельном пользовательском сообщении разрешите apply с теми же параметрами и возвращённым
+`SOO-*` кодом. `task stop-override-apply` добавляет одну запись в
+`stop-escalate-overrides.jsonl`, сохраняя исходный `stop-escalate`; после него выполните
+последовательные `status` и `next`. Ожидаемый route — `task run` того же Step с последующим новым
+strict review. Этот путь не работает для `split-required`, другого attempt ordinal, изменённого
+Plan/HEAD/revision, отсутствующего attempt-3 continue, active/stale lease, dirty checkout или
+незавершённой Task transaction. Delegated approval для него отсутствует.
+
 ## 1. Подготовьте отдельный чат обновления
 
 Не обновляйте пакет во время выполняющегося Worker Step. Дождитесь завершения текущего ответа

package/docs/validation-report.md

@@ -1,98 +1,99 @@
-# V2 beta.12 Validation Report
+# V2 beta.12.1 Validation Report
 
-Release candidate `2.0.0-beta.12` was validated on 2026-08-27 with Node.js 24.17.0.
+Release candidate `2.0.0-beta.12.1` was validated on 2026-08-27 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 `321/321` sequential tests with no failures, skips,
-  cancellations, or todos. The focused Signal T04 recovery suite passed independently (`5/5`).
-- `npm run pack:check` passed outside the filesystem-restricted sandbox. The beta.12 tarball
-  contains 269 files; package size is 955.6 kB and unpacked size is 3.7 MB.
-- `npm run smoke:downstream` packed and installed the actual beta.12 tarball in an empty temporary
-  project, then passed the packaged CLI handshake. The first sandboxed attempt was network-blocked
-  while fetching pinned `ajv`; the authorized network retry passed.
-- `npm run plugin:check`, the official Codex plugin validator, `npm run docs:pdf:check`, exact
-  `RELEASE_TAG=v2.0.0-beta.12 npm run release:check`, and `git diff --check` passed. The bundled
-  gateway cachebuster is `0.1.0+codex.20260827003726`.
-
-The first full post-version-bump validation exposed three failures before the Signal T04 runtime
-scenario began: a historical read-only snapshot truthfully targeted beta.11, while its replay
-assertion incorrectly required the current package version. The fix keeps the snapshot immutable at
-`2.0.0-beta.11`, binds the synthetic replay dependency to current `PACKAGE_VERSION`, and makes the
-release check verify both identities separately. The focused suite then passed `5/5`, and the final
-complete suite passed `321/321`.
-
-## Continuable remediation and review-routing evidence
-
-- A guarded Task remains in the same Task/Step and reaches a passing strict review after five
-  consecutive failed review cycles. Attempts 1–2 are ordinary; attempts 3+ are corrective
-  diagnostics but remain executable and review-gated.
-- Attempt count no longer selects a terminal lifecycle transition. It is retained as diagnostic
-  history only; explicit `split-required` and `stop-escalate` remain the stop authorities.
-- A failed review defaults to `route=fix` (or an omitted route) and continues the same Task/Step.
-  `route=replan` is valid only with exact `planClause`, `whyFixCannotFit`, and `minimalPlanChange`
-  evidence.
-- Replan returns to ordinary `task plan-set`; objective, requirements, and acceptance remain
-  immutable, while only implementation Steps may change. The replacement Plan still passes the
-  normal Plan Risk Audit and execution-authorization gates.
-- Failed-review routing evidence is hash-chained in the public Step Review event schema. Drift,
-  malformed evidence, unrelated Knowledge changes, forged actors, and corrupt chains remain
-  fail-closed.
-
-## Retained dependency, feasibility, and recovery evidence
-
-- P04-A retains the canonical Milestone dependency DAG, atomic initial Plan transaction/recovery,
-  dependency-bound handoff/claim/start, legacy fail-closed policy, and unconditional structural
-  replacement shutdown.
-- P01-A retains three versioned read-only analyzers, canonical in-event evidence/hash binding,
-  exact pre-start and corrective source selection, and phase-aware freshness before claim/start/run.
+- The final `npm run validate` passed typecheck and `325/325` sequential tests with no failures,
+  skips, cancellations, or todos.
+- Focused compatibility replay passed independently: dependency provenance plus Signal T04 and
+  legacy stop override tests passed `9/9`; the stop-only suite passed again after the final
+  observation-boundary hardening (`3/3`).
+- `npm run pack:check` produced the beta.12.1 dry-run tarball with 270 files, package size 967.2 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 the actual
+  `codex-workflow-v2-2.0.0-beta.12.1.tgz` in an empty temporary project and passed the packaged
+  handshake.
+- `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.1 npm run release:check`, and `git diff --check` passed. The official
+  Python validator required a temporary, isolated `PyYAML` dependency; no project or system Python
+  files were changed. The bundled gateway cachebuster is `0.1.0+codex.20260827132414`.
+
+## Task-local dependency provenance compatibility
+
+- Recovery still requires a clean local Task branch, no Step in progress, no lease or transaction,
+  exact runtime/declared/locked/installed/current/base version alignment, and one unregistered HEAD
+  that changes exactly `package.json` and `package-lock.json`.
+- The false full-file equality check against the Milestone base was removed. Candidate parent and
+  HEAD are instead compared after removing only `codex-workflow-v2` dependency entries. Previously
+  committed Task-local manifest/lock fields therefore survive unchanged.
+- A replay with a Task-local processing script is accepted and retains its recorded product commit.
+  A script added by the dependency candidate itself is rejected as payload drift; an extra product
+  file and stale base version are also rejected.
 - The exact Signal T04 revision-26 fixture still proves that only a verified historical Step Review
   can retain its completion commit across corrective replan. Pending review is never trusted, and a
   corrupt strict-review hash chain is rejected.
-- Bounded beta.11 `task plan-integrity-recover` compatibility remains green for its exact first
-  ordinary checks-failed case. It does not edit the Plan, package manifest, or worktree and still
-  fails closed for writable-manifest scope, unrelated dirty files, binding drift, or tampering.
-- Read-only Milestone progress still preserves `T03 cancelled → T08 replacement`; project-monotonic
-  chat allocation and deterministic long-title fallback/readback remain green.
-
-## Packaged real-agent lifecycle replay
-
-- A fresh disposable Git project installed the locally packed beta.12 tarball, declared the exact
-  `2.0.0-beta.12` dependency, and passed packaged `gateway handshake` plus `doctor` with protocol 2,
-  state schema 2, current dependency identity, and a clean checkout.
-- The trusted harness invoked the real packaged CLI sequentially for handshake, doctor, direct first
-  Discovery bootstrap, `status`, and fresh `next`. The resulting navigation advertised
-  `project-memory scan`.
-- `node scripts/validate-lifecycle-transcript.mjs` accepted all `10/10` post-provenance events with
-  no failed invocation, unadvertised mutation, or missing checkpoint. The semantic log SHA-256 is
-  `ab4ef10ad00e2fd9f54810ec5d0bbfb4106e1b211b3a185869d8a46787a5062d`; the raw packaged-result
-  log SHA-256 is `e693a839604c7ba2055f99e43c49c5ab63ac0cf6e790adc901db5dd8eb0ffae9`.
-- Credential-marker inspection found no writer, claim, delegation, bearer, or secret material, and
-  the disposable product checkout remained clean. Logs and external workflow state stayed outside
-  this repository.
-
-This replay validates package resolution, clean bootstrap, one real mutation, and mandatory
-post-mutation navigation discipline. It does not claim a second full product Milestone replay;
-deeper remediation, P01-A, and P04-A behavior is covered by deterministic and integration tests.
-
-## beta.12 PDF release documentation evidence
+
+## Human-confirmed beta.11 stop compatibility
+
+- The route is available only for one historical shape under the unchanged Plan: exactly two
+  ordinary remediation events, one corrective third event, one matching attempt-3 `continue-fix`,
+  and one matching attempt-4 `stop-escalate`.
+- `task stop-override-prepare` is read-only. It binds Task revision, Step, both decisions, all three
+  remediation events, Plan hash, Git HEAD, package version, human actor, and reason to an `SOO-*`
+  code. `task stop-override-apply` accepts only the same binding in a later explicit turn.
+- Apply appends `stop-escalate-overrides.jsonl`; it does not edit the Task or delete/rewrite the
+  original corrective decision. Exact replay is idempotent.
+- After apply, fresh `next` returns `task run` for the same Step and the fourth attempt actually
+  reaches `in_progress`; subsequent strict review remains mandatory.
+- `split-required`, a stale Task revision/confirmation, conflicting duplicate, active boundary,
+  or tampered hash chain fails closed. Delegated approval is not part of this gate.
+
+## Existing lifecycle regressions retained
+
+- A guarded Task remains in the same Task/Step and can converge after five consecutive failed
+  review cycles. Attempts 1-2 are ordinary; attempts 3+ are corrective diagnostics, not limits.
+- Evidence-bound `route=fix` and `route=replan`, Plan-integrity recovery, corrective yield/replan,
+  observer byte-purity, C1 credential safety, Milestone dependency authority, atomic transactions,
+  and structural-replacement shutdown all remain green.
+- `split-required` remains terminal. The new compatibility route does not implement P04-B, rewire
+  Milestone topology, adopt completed Steps, or override a semantic stop outside the exact beta.11
+  attempt-four policy shape.
+
+## Packaged and transcript evidence
+
+- Downstream smoke validated package resolution and the packaged beta.12.1 handshake in a clean
+  disposable installation.
+- A trusted harness then invoked the final built CLI sequentially for handshake, doctor, `status`,
+  and fresh `next` against this unregistered source repository. The observations 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
+  `3a12f6e604bef2fe5335c6fc244b52690b06925fb50b8fd8a20acefb672ca46d`; the temporary log remains
+  outside the repository.
+
+This transcript proves release-time invocation/result discipline for the final CLI. It does not
+claim a second product Milestone replay or a lifecycle mutation. The two compatibility mechanisms
+are covered by deterministic repository/sidecar integration tests above.
+
+## beta.12.1 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 24 pages were rendered and visually inspected: architecture is 6 pages, the delegated
-  chat-only guide is 8 pages, and the technical reference is 10 pages. No blank, clipped, or orphaned
-  page was found.
-- Visible titles, headers, package commands, and release gates identify beta.12. The content covers
-  continuable remediation, evidence-bound fix/replan routing, Milestone dependency authority,
-  P01-A mechanical feasibility, C1 credentials, external-sealed review, Plan-integrity compatibility,
-  structural-replacement shutdown, and the limited derived-graph role of `codebase-memory-mcp`.
+- All 25 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 page was found.
+- Visible titles, headers, package commands, and release gates identify beta.12.1. The content
+  distinguishes general continuable remediation from the narrow Human-confirmed beta.11 stop
+  override and documents Task-local dependency preservation without weakening candidate checks.
 
 ## Not claimed
 
 - Validation itself performs no npm publication, Git tag, push, Signal Workflow mutation, or local
   plugin reinstall. Tagging and remote push are separate actions after the exact candidate gates.
-- Structural replacement remains intentionally disabled; beta.12 does not claim P04-B replacement
+- Structural replacement remains intentionally disabled; beta.12.1 does not claim P04-B
   materialization or completed-Step adoption.
-- A real project must install the published exact beta.12 package, update/reinstall the bundled
-  gateway, and follow fresh project-local `handshake → doctor → status → next` navigation.
+- A real project must install the published exact beta.12.1 package, update/reinstall the bundled
+  gateway, and follow 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",
+  "version": "2.0.0-beta.12.1",
   "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.20260827003726",
+  "version": "0.1.0+codex.20260827132414",
   "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 continuable remediation, coordinator projections, and retained recovery compatibility
+## beta.12.1 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
@@ -14,6 +14,12 @@
   product commits absent from the current corrective Step are recognized only through intact passed
   strict-review plus verified reviewer-attestation chains and remain separately auditable as
   `retainedHistoricalCommits`.
+  Task-local manifest/lock fields from recorded history may differ from the base, but the candidate
+  commit must preserve them exactly while changing only the Workflow dependency entries.
+- `task stop-override-prepare` is a read-only Human gate for the exact beta.11 attempt-four stop
+  shape. `task stop-override-apply` requires the same Task revision, Step, actor, reason, Plan, HEAD,
+  evidence binding, and returned `SOO-*` code in a later user turn. It appends evidence without
+  deleting `stop-escalate`; it never applies to `split-required`.
 - `milestone progress --id <MS-ID>` is a read-only projection and the sole source for Coordinator
   progress tables. It preserves cancelled/replacement Tasks as distinct membership rows.
 - `scripts/chat-registry.mjs` atomically allocates project-monotonic `#NNN`, builds all six title
@@ -49,6 +55,8 @@ Current capability set:
 - `corrective-plan-audit-v1`
 - `safe-update-preflight-v1`
 - `bounded-dependency-provenance-recovery-v1`
+- `task-local-dependency-provenance-recovery-v1`
+- `legacy-stop-escalate-override-v1`
 - `retained-reviewed-history-recovery-v1`
 - `milestone-progress-projection-v1`
 - `strict-reviewer-v1`
@@ -187,6 +195,12 @@ explicit stop or redirection decisions. They are never inferred from attempt cou
 explicit decision, another failed strict review continues the same Task through its evidence-bound
 `fix`/`replan` route.
 
+One append-only compatibility exception exists for a beta.11 policy-created attempt-four stop.
+Fresh `next` must advertise `task stop-override-prepare`; run it with exact human inputs, present the
+complete binding, and stop. A later explicit user turn may run `task stop-override-apply` with the
+same inputs and confirmation code. Any split decision, Plan/revision/HEAD drift, missing attempt-3
+continue authority, lease, transaction, or journal damage blocks the route.
+
 ## Context refresh
 
 Before `task plan-set`, compare exact Step `allowedWrites` and expected output paths with scanner

package/plugins/codex-workflow-gateway/skills/codex-workflow-gateway/SKILL.md

@@ -50,6 +50,12 @@ pending/corrupt transaction. After success run sequential `status` then `next` a
 returned lifecycle action; Knowledge reconciliation or atomic Task context refresh may legitimately
 be next because the dependency files changed.
 
+Beta.12.1 permits product-owned manifest/lock fields already present in the exact recorded Task
+history to differ from the Milestone base. Core compares candidate parent to candidate HEAD after
+removing only the Workflow dependency entries, so the dependency commit must preserve every such
+field exactly. Do not rebase, copy the base manifest over Task-local scripts, or interpret this as
+permission for product payload in the candidate commit.
+
 The beta.11 bounded Plan-integrity route prevents a known impossible check from consuming a second
 ordinary remediation attempt. Use `task plan-integrity-recover` only when fresh `next` advertises
 it for the exact failed Task/Step/revision. Require `state=eligible`, no blockers, one first
@@ -103,6 +109,17 @@ command shape or consuming a replacement Discovery. Never rebind, refresh, repla
 resume, cancel, or manually replace the historical Task. Continue only after a later P04-B/P05
 package explicitly advertises a topology-preserving replacement capability.
 
+When beta.12.1 `next` advertises `task stop-override-prepare`, the route is limited to the exact
+beta.11 attempt-four policy stop: two ordinary failures, one corrective failure, a matching
+attempt-3 `continue-fix`, and a matching attempt-4 `stop-escalate` under the unchanged Plan. Invoke
+prepare with the exact Task/Step/revision, explicit human actor, and user-supplied reason. It is
+read-only. Show the returned binding and `SOO-*` code, then stop. Only a later explicit user turn may
+invoke `task stop-override-apply` with the identical inputs and code. Never delegate the gate,
+override `split-required`, edit either journal, or reuse a code after Task revision, Plan, HEAD, or
+evidence changes. Successful apply preserves the original stop, appends
+`stop-escalate-overrides.jsonl`, and requires fresh sequential `status` then `next` before attempt
+four runs through the normal strict-review cycle.
+
 When `next` returns `milestone initial-assembly`, execution is unavailable. Follow only the
 advertised `linked-task-assembly.commands` (`discovery start` and `discovery materialize`) until all
 intended linked Tasks exist. The closing `milestone plan-set` option appears only after at least one