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

package/docs/autonomy-guardrails.md

@@ -55,39 +55,26 @@ into the mutation actor slot.
 Invalid or stale review sidecars fail closed. The workflow blocks downstream acceptance and
 normal continuation when review evidence is malformed, unverified, or commit-mismatched.
 
-## Repeated failed review and remediation breaker
-
-The first failed independent review returns the Task to `needs_fix` and requires a changed or
-new remediation Step. After two distinct failed-review attempts, `next` returns
-`task plan-set with independent corrective audit`. Another Plan requires a JSON audit:
-
-```json
-{
-  "auditor": "corrective-auditor",
-  "summary": "The corrective Step covers the latest findings without changing the Brief.",
-  "decision": "continue-fix",
-  "reviewedFindingIds": ["REV-001", "REV-002"]
-}
-```
-
-Apply it with `task plan-set --corrective-audit-file <file>` only for the `continue-fix`
-path. The Auditor must differ from the failed-review author and cover every latest finding.
-`replan-required`, `split-required`, and `stop-escalate` are stop decisions: Core does not
-start another implementation loop.
-
-For guarded Steps, remediation attempts are also tracked in
-`remediation-events.jsonl`. Two ordinary remediation attempts are allowed. A third ordinary
-retry is blocked until `task corrective-decision` records a current corrective decision in
-`corrective-decisions.jsonl`. The corrective gate is derived from the guarded Step, current
-Plan Risk Audit, remediation history, and corrective-decision history, so it remains visible
-after content-only context refresh, Task Knowledge rebind, and reauthorization. `continue-fix`
-allows bounded continuation; `replan-required` requires an actual new Plan posture before
-execution; the other decisions stop or redirect ordinary execution. If that third, corrective
-remediation review also fails, Core enters a hard stop: `next` must report the stop without
-throwing, a fourth run and another `continue-fix`/`replan-required` decision are rejected,
-and only `split-required` or `stop-escalate` may be recorded. At the corrective boundary,
-`next` derives a distinct `agent:corrective-auditor:<task-id>` actor; selecting that actor is
-not a human approval, while auditor independence remains mandatory.
+## Repeated failed review and continuable remediation
+
+A failed final Task review returns the same Task to `needs_fix` and requires a changed or new
+remediation Step. The failed-review count is diagnostic evidence, not a lifecycle limit: another
+Plan does not require a separate corrective Plan Auditor merely because two or more reviews failed.
+Every replacement Plan must preserve the Task objective, requirements, and acceptance; changing
+those commitments requires an explicit scope decision outside ordinary remediation.
+
+For guarded Steps, every failed review is recorded in `remediation-events.jsonl`. Attempts one and
+two retain mode `ordinary`; later attempts use mode `corrective`, but the mode does not impose a
+maximum attempt ordinal. `next` continues to return `task run` for the same failed Step, and every
+new completion still requires a fresh strict review bound to its exact commit. Therefore repeated
+fixes cannot create an approval, while a fourth, tenth, or later reviewed attempt remains possible.
+
+Each failed review finding may carry `route: fix` or `route: replan`. `fix` is the backward-compatible
+default. `replan` is accepted only with `planConflict.planClause`, `whyFixCannotFit`, and
+`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.
 
 ### First-failure Plan-integrity recovery
 
@@ -108,7 +95,8 @@ The recovery appends one hash-bound `replan-required` decision for attempt ordin
 the worktree and does not edit the Plan. A claimed C1 Task must present its current writer token and
 then follow `task corrective-yield`; the replacement Plan still requires the existing independent
 validation, Risk Audit, Human confirmation, journaled execution, readback, and renewed execution
-authorization. Other check failures retain the ordinary two-attempt breaker.
+authorization. Other check failures use the normal continuable remediation route; they do not
+receive the narrow Plan-integrity shortcut, but attempt count alone never stops them.
 
 ## Atomic context refresh
 

package/docs/decisions.md

@@ -64,10 +64,11 @@ This document closes the requirement gaps identified during the V2 design review
     fails closed without changing persisted Task state. This changes navigation and
     diagnostics only; state schema 2 and protocol 1 remain unchanged.
 12. **Autonomous correction guardrail.** The initial Plan must make migration,
-    concurrency, restart/replay, crash-window, and provider risks visible. After two failed
-    independent reviews, another corrective Plan requires a distinct Auditor covering every
-    latest finding. The audit is append-only artifact evidence; no Task state field or schema
-    change is required.
+    concurrency, restart/replay, crash-window, and provider risks visible. Repeated failed reviews
+    do not impose an attempt-count stop: findings default to a same-Task fix and may request replan
+    only with exact Plan-conflict evidence. Attempts after the second are marked corrective for
+    diagnosis, remain executable, and require another strict review. Explicit split/stop decisions
+    remain append-only authority and are never inferred from the counter.
 13. **Content-only context refresh.** A delegate may compose reconcile, approval, knowledge
     rebind, and execution reauthorization only when the approved source classification is
     identical and only content hashes changed. Core validates both delegated transitions

package/docs/delegated-approval.md

@@ -191,10 +191,11 @@ Plan-declared supporting additions допустимы только когда и
 изменении source set, category/authority, gaps или conflicts используй обычный видимый процесс.
 
 После submit запусти отдельный Independent Reviewer; Reviewer не использует
-grant и не исправляет код. После второго failed review не запускай очередной
-патч: получи отдельный corrective Plan audit, охватывающий все последние findings,
-и передай его через `--corrective-audit-file`. Продолжай только при
-`decision=continue-fix`; остальные решения верни пользователю/координатору.
+grant и не исправляет код. Failed review возвращает ту же Task в remediation: добавь или измени
+remediation Step и снова проведи review. Количество failed reviews не требует отдельного
+corrective Plan audit. Для каждого finding Reviewer использует `route=fix` по умолчанию;
+`route=replan` допустим только с точным Plan clause, доказательством невозможности обычного fix и
+минимальным изменением Plan. Objective, requirements и acceptance через remediation не меняются.
 Final acceptance делай
 только при exact task.final_accept option для DGR-ID, затем штатный merge.
 Если option отсутствует, grant истёк, scope не совпал или требуется смысловое

package/docs/development-flow.md

@@ -83,12 +83,13 @@ to be repeated before merge.
 The Technical Planner performs a risk review before authorization. Migration work includes a
 populated forward-upgrade check; concurrent state includes deterministic races; restart,
 replay, and crash claims include restart/crash-window evidence; provider work includes
-failure injection and hidden-default verification. After two failed independent reviews,
-another Plan requires a distinct corrective Auditor and `--corrective-audit-file`. Only a
-`continue-fix` audit may continue; replan, split, and stop decisions return to coordination.
-For guarded remediation, a third ordinary retry is blocked until a current
-`task corrective-decision` exists for the same Step and Plan binding. If that corrective
-attempt fails review, the third failure is a hard stop and no fourth run is permitted.
+failure injection and hidden-default verification. Repeated failed reviews remain on the same
+Task. They require a new remediation Step for final Task review, or another implementation and
+fresh strict review for a failed guarded Step; they do not require a separate corrective Auditor
+based only on attempt count. Guarded attempts above two are recorded as `corrective` and remain
+executable. A reviewer routes to `replan` only with an exact Plan obstruction and minimal Plan
+change; ordinary findings default to `fix`. Remediation cannot change the Task objective,
+requirements, or acceptance.
 
 One bounded exception avoids a deliberately repeated failure for an older authorization without
 P01-A evidence or a contradiction that becomes observable only after execution starts. If the first guarded check failure

package/docs/lifecycle/state-machine-stabilization.md

@@ -266,7 +266,7 @@ The explorer must be exhaustive over semantic classes, bounded over cardinality,
 | Actor | human, valid delegate, claimant, other |
 | Lease | none, valid-owned, valid-other, stale |
 | Attempts | 0, 1, 2, 3+ |
-| Corrective posture | none, decision-needed, continue-fix, replan, split, stop, hard-stop, recovery-needed |
+| Corrective posture | none, automatic-continue, explicit continue-fix, replan, split, stop, recovery-needed |
 | Knowledge binding | active, stale, awaiting approval, conflicting |
 | Git | clean-bound, clean-diverged, dirty, malformed |
 | Authorization | absent, current, stale, superseded |

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

@@ -1,10 +1,10 @@
 ---
-title: Codex Workflow V2: архитектура beta.11
+title: Codex Workflow V2: архитектура beta.12
 subtitle: Источники истины, lifecycle, роли, delegation, зависимости Tasks и границы доверия
 part: Часть 1 из 3 | Архитектура
 document_version: 2.0
-date: 24 августа 2026
-subject: Архитектура и границы Codex Workflow V2 beta.11
+date: 27 августа 2026
+subject: Архитектура и границы Codex Workflow V2 beta.12
 ---
 
 # 1. Назначение и граница системы
@@ -18,7 +18,7 @@ Codex Workflow V2 - локальный state machine поверх Codex App, Git
 Система рассчитана на одного пользователя и одну машину. Она не предоставляет distributed locking,
 криптографическую идентификацию actor string или безопасную синхронизацию state между компьютерами.
 
-## 1.1. Что beta.11 гарантирует
+## 1.1. Что beta.12 гарантирует
 
 - 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.11 не гарантирует
+## 1.2. Что beta.12 не гарантирует
 
 - правильность продуктовой идеи или автоматически выбранного provider Task;
 - semantic sufficiency Plan, если точные факты нельзя доказать поддерживаемым analyzer;
@@ -213,9 +213,10 @@ execution-authorized Plan и покрытое тем же Milestone Autonomy Con
 3. Reviewer возвращает закрытый schema-valid result без mutations.
 4. Core записывает его только если packet и seals не изменились.
 
-После двух failed review отдельный Corrective Auditor выбирает `continue-fix`, `replan-required`,
-`split-required` или `stop-escalate`. Continue разрешает один bounded corrective attempt; последующий
-failure создаёт hard stop.
+Failed review не ограничивает число попыток. Попытки 1-2 имеют mode `ordinary`, последующие —
+`corrective`; все исполнимы и требуют нового strict review. `route=fix` продолжает Task, а
+`route=replan` допустим только с точным Plan conflict и меняет лишь implementation Steps, не objective,
+requirements или acceptance. Explicit `split-required` и `stop-escalate` остаются stop/redirect decisions.
 
 beta.11 `task plan-integrity-recover` существует для одного первого checks-failed legacy/late case:
 отсутствует exact root npm script и текущий Step не может изменить package.json. Recovery не меняет
@@ -226,7 +227,7 @@ worktree или Plan и не создаёт synthetic second failure; он за
 # 10. Operational checklist
 
 - exact package version установлен, bundled gateway соответствует release и переустановлен;
-- handshake подтверждает protocol 2, state schema 2 и beta.11 capabilities;
+- handshake подтверждает protocol 2, state schema 2 и beta.12 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.11 путь от нового Discovery до принятого Milestone без ручного CLI
+subtitle: Актуальный beta.12 путь от нового Discovery до принятого Milestone без ручного CLI
 part: Часть 2 из 3 | Практика
 document_version: 2.0
-date: 24 августа 2026
-subject: Практическое руководство по delegated Discovery и Milestone в Workflow V2 beta.11
+date: 27 августа 2026
+subject: Практическое руководство по delegated Discovery и Milestone в Workflow V2 beta.12
 ---
 
-# 1. Рабочая модель beta.11
+# 1. Рабочая модель beta.12
 
 Пользователь работает в одном 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.11 как точную devDependency после публикации release.
+2. Установите beta.12 как точную 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.11 должен сообщать `packageVersion=2.0.0-beta.11`, `protocolVersion=2`,
+Handshake beta.12 должен сообщать `packageVersion=2.0.0-beta.12`, `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.11 в delegated режиме.
+Проведи новый Milestone через Codex Workflow V2 beta.12 в delegated режиме.
 Repository: <ABSOLUTE-REPOSITORY-ROOT>.
 Milestone ID: AUTO.
 Delegate actor: agent:milestone-coordinator.
@@ -282,7 +282,7 @@ Knowledge Map approval path. Milestone grant не разрешает standalone
 |---|---|
 | Guarded Step review | `step-review-packet` -> новый Reviewer chat -> `step-review-record` |
 | Submitted Task review | `review-packet` -> новый Final Reviewer chat -> `review-sealed-record` |
-| Corrective audit | Отдельный read-only Corrective/Plan Audit chat |
+| Explicit corrective disposition (если выбран) | Отдельный read-only Corrective/Plan Auditor chat; не attempt-count gate |
 
 Reviewer получает неизменённый packet, проверяет exact commit/diff/evidence и возвращает closed JSON.
 Task chat записывает его только при совпадении packet и repository seal hashes. Reviewer не исправляет код,
@@ -293,11 +293,11 @@ Task chat записывает его только при совпадении p
 | Состояние | Действие |
 |---|---|
 | First proven impossible npm check после legacy/late authorization | Только рекламируемый `task plan-integrity-recover` |
-| Два failed guarded reviews | Separate Corrective Auditor и exact decision route |
-| `continue-fix` | Один bounded corrective attempt |
-| `replan-required` | Corrective yield, human-confirmed journaled replan |
+| Failed guarded review | Та же Task: исправление и новый strict review без attempt hard stop |
+| Finding `route=fix` | Продолжить тот же Step; count остаётся диагностикой |
+| Finding `route=replan` с exact Plan conflict | `task plan-set`, меняются только implementation Steps |
 | `split-required` | Stop: `STRUCTURAL_REPLACEMENT_REQUIRED`, никаких replacement writes |
-| `stop-escalate` или third corrective failure | Terminal hard stop и user attention |
+| Explicit `stop-escalate` | Terminal user attention |
 | Stale dependency binding | Новый handoff/claim только по fresh `next` |
 | Review seal drift | Discard review и создать fresh packet |
 
@@ -321,7 +321,7 @@ Task/project DGR. `dependencyBinding` для standalone handoff равен null.
 
 # 14. Итоговый checklist пользователя
 
-- beta.11 exact package и новый bundled gateway установлены;
+- beta.12 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.11
+title: Codex Workflow V2: технический справочник beta.12
 subtitle: Protocol 2, state schema 2, transactions, credentials, dependency authority, review и recovery
 part: Часть 3 из 3 | Technical reference
 document_version: 2.0
-date: 24 августа 2026
-subject: Технический контракт Codex Workflow V2 beta.11
+date: 27 августа 2026
+subject: Технический контракт Codex Workflow V2 beta.12
 ---
 
 # 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.11 | Значение |
+| Параметр beta.12 | Значение |
 |---|---|
-| npm package | `codex-workflow-v2@2.0.0-beta.11` |
+| npm package | `codex-workflow-v2@2.0.0-beta.12` |
 | 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.11 capabilities:
+Ключевые beta.12 capabilities:
 
 | Группа | Capabilities |
 |---|---|
@@ -45,7 +45,7 @@ Gateway выполняет:
 | Milestone | lifecycle, initial assembly navigation, autonomy, progress, dependency DAG, initial Plan transaction |
 | 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, corrective audit and hard stop |
+| Reviews | strict reviewer, Step strict review, continuable remediation, evidence-bound fix/replan routing |
 | Recovery | dependency provenance, plan integrity, remediation mode, corrective yield/replan journals |
 | Replacement | `structural-task-replacement-disabled-v1` |
 
@@ -281,21 +281,22 @@ local reviewer внутри Codex App sandbox.
 
 # 12. Remediation и corrective decisions
 
-Guarded Step имеет bounded remediation circuit:
+Guarded Step имеет проверяемый, но не ограниченный счётчиком remediation circuit:
 
 | Boundary | Разрешение |
 |---|---|
-| Первый failed review/check cycle | Ordinary scoped retry |
-| Два failed review cycles | Independent Corrective Auditor |
-| `continue-fix` | Один corrective attempt |
-| Corrective attempt failed | Hard stop, fourth run запрещён |
-| `replan-required` | Corrective yield и Human-confirmed journaled replan |
-| `split-required` | Structural replacement stop |
-| `stop-escalate` | Terminal user attention |
-
-Corrective replan разделён на prepare, Human confirmation, execute и recover. Candidate/receipt связывают
-Task revision, Plan/Brief/evidence, corrective decision, writer posture и repository state. Execution
-transaction supersedes old authority и публикует replacement Plan атомарно.
+| Failed cycles 1-2 | `ordinary`; та же Task и новый strict review |
+| Failed cycles 3+ | `corrective`; остаются исполнимыми и требуют нового strict review |
+| Finding `route=fix` или route отсутствует | Продолжить ту же Task/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 |
+
+Attempt count является диагностикой, а не lifecycle authority. Explicit corrective-decision journal
+сохраняется для намеренного stop/split и совместимого historical recovery, но не требуется после второй
+ошибки. Replan из review обязан назвать `planClause`, `whyFixCannotFit` и `minimalPlanChange`; objective,
+requirements и acceptance Task при remediation неизменяемы. Новый Plan проходит обычные audit и authorization.
 
 # 13. beta.11 Plan-integrity recovery
 
@@ -371,7 +372,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.11
+# 18. Public command surface beta.12
 
 | Область | Actions |
 |---|---|
@@ -398,7 +399,7 @@ Exact options берутся из fresh `next`; command help используе
 running Step и active/stale writer lease. External runner допустим только в документированной rescue
 compatibility форме.
 
-Перед beta.11 tag release repository выполняет:
+Перед beta.12 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.11, the release gate also relies on `npm run release:check` to fail if:
+For beta.12, the release gate also relies on `npm run release:check` to fail if:
 
 - canonical entity schema 2 shapes drift;
 - protocol 2 is not the active public contract, or intact protocol-1 adoption evidence stops being readable through the bounded compatibility window;
@@ -50,6 +50,8 @@ For beta.11, the release gate also relies on `npm run release:check` to fail if:
   bindings, or the no-synthetic-second-failure regression is absent.
 - the P04-A Milestone dependency/initial-Plan transaction capabilities or the P01-A mechanical
   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 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