codex-workflow-v2 2.0.0-beta.12.7 → 2.0.0-beta.12.8

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

@@ -1,10 +1,10 @@
 ---
-title: Codex Workflow V2: архитектура beta.12.7
+title: Codex Workflow V2: архитектура beta.12.8
 subtitle: Источники истины, lifecycle, роли, delegation, зависимости Tasks и границы доверия
 part: Часть 1 из 3 | Архитектура
 document_version: 2.0
 date: 29 августа 2026
-subject: Архитектура и границы Codex Workflow V2 beta.12.7
+subject: Архитектура и границы Codex Workflow V2 beta.12.8
 ---
 
 # 1. Назначение и граница системы
@@ -18,7 +18,7 @@ Codex Workflow V2 - локальный state machine поверх Codex App, Git
 Система рассчитана на одного пользователя и одну машину. Она не предоставляет distributed locking,
 криптографическую идентификацию actor string или безопасную синхронизацию state между компьютерами.
 
-## 1.1. Что beta.12.7 гарантирует
+## 1.1. Что beta.12.8 гарантирует
 
 - exact project-local npm package и совместимый handshake до lifecycle действий;
 - Discovery до materialization Task или Milestone;
@@ -26,6 +26,8 @@ Codex Workflow V2 - локальный state machine поверх Codex App, Git
 - mechanical-feasibility проверку поддерживаемых форм Plan до новой Task authorization;
 - явный Milestone dependency DAG и один общий runnable predicate для routing, handoff, claim и start;
 - один C1 writer lease, секретные one-time credentials и Core-owned Step commits;
+- lease-free Human final-acceptance gate: `task result-set` проверяет и освобождает active writer
+  lease, а после acceptance merge получает новый credential только через fresh recovery route;
 - external-sealed Step/Task review в отдельных Codex tasks;
 - state-bound human gates либо ранее выданные bounded delegation contracts;
 - journaled recovery для составных переходов и fail-closed поведение при drift/corruption.
@@ -34,7 +36,7 @@ Codex Workflow V2 - локальный state machine поверх Codex App, Git
 - bounded compatibility recovery, если beta.12.6 после этого recovery ошибочно rebind-нула отвергнутый
   Plan: exact dirty bytes сохраняются до нового consolidated Step, а Knowledge refresh не отменяет `plan-set`.
 
-## 1.2. Что beta.12.7 не гарантирует
+## 1.2. Что beta.12.8 не гарантирует
 
 - правильность продуктовой идеи или автоматически выбранного provider Task;
 - semantic sufficiency Plan, если точные факты нельзя доказать поддерживаемым analyzer;
@@ -110,6 +112,11 @@ Discovery -> materialize -> Plan -> Plan Risk Audit
 -> final acceptance -> merge
 ```
 
+`task result-set` является последним execution lease-bound переходом. Он требует рекламируемый
+writer token, освобождает lease до `awaiting_final_acceptance` и тем самым допускает неограниченную
+по времени Human pause без stale-lock блокировки repository. После acceptance прежний token не
+переиспользуется: fresh `next` выдаёт bounded `task writer-credential-replace` для merge.
+
 Fresh Task authorization записывает versioned mechanical-feasibility evidence. Analyzer может
 выдать `blocked`, `pass` или `unverified`. `unverified` не означает semantic approval; он означает,
 что поддерживаемая точная грамматика не доказала противоречие.
@@ -285,7 +292,7 @@ Restart Docker Desktop требует отдельного разрешения
 # 10. Operational checklist
 
 - exact package version установлен, bundled gateway соответствует release и переустановлен;
-- handshake подтверждает protocol 2, state schema 2 и beta.12.7 capabilities;
+- handshake подтверждает protocol 2, state schema 2 и beta.12.8 capabilities;
 - каждый mutation следует свежему `status -> next` и exact option contract;
 - Docker permission failure сначала классифицируется как sandbox boundary, а не как infra retry;
 - semantic unknowns и human gates не маскируются delegation;

package/docs/pdf/sources/codex-workflow-v2-chat-only-guide-ru.md

@@ -1,13 +1,13 @@
 ---
 title: Codex Workflow V2: delegated chat-only guide
-subtitle: Актуальный beta.12.7 путь от нового Discovery до принятого Milestone без ручного CLI
+subtitle: Актуальный beta.12.8 путь от нового Discovery до принятого Milestone без ручного CLI
 part: Часть 2 из 3 | Практика
 document_version: 2.0
 date: 29 августа 2026
-subject: Практическое руководство по delegated Discovery и Milestone в Workflow V2 beta.12.7
+subject: Практическое руководство по delegated Discovery и Milestone в Workflow V2 beta.12.8
 ---
 
-# 1. Рабочая модель beta.12.7
+# 1. Рабочая модель beta.12.8
 
 Пользователь работает в одном 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.7 как точную devDependency после публикации release.
+2. Установите beta.12.8 как точную 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.7 должен сообщать `packageVersion=2.0.0-beta.12.7`, `protocolVersion=2`,
+Handshake beta.12.8 должен сообщать `packageVersion=2.0.0-beta.12.8`, `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.7 в delegated режиме.
+Проведи новый Milestone через Codex Workflow V2 beta.12.8 в delegated режиме.
 Repository: <ABSOLUTE-REPOSITORY-ROOT>.
 Milestone ID: AUTO.
 Delegate actor: agent:milestone-coordinator.
@@ -242,6 +242,10 @@ Credential и approval grant решают разные задачи.
 4. Claim проверяет dependency binding и возвращает `writerLeaseReceipt`.
 5. `task run` принимает active writer credential согласно `next.writerTokenContract` и обновляет lease.
 6. `task step-complete`, review record и другие guarded mutations используют только рекламируемый option.
+7. После passed final review `task result-set` использует active writer token и освобождает lease до
+   `awaiting_final_acceptance`; Human gate не должен удерживать credential.
+8. После acceptance старый token не используется: fresh `next` рекламирует
+   `task writer-credential-replace`, затем разрешает merge или merge confirmation.
 
 Нельзя искать token в later payload fields, писать его в prompt/report/evidence или заменять redacted
 fingerprint. Потеря token не разрешает новый handoff либо lease acquisition вне fresh recovery route.
@@ -363,7 +367,7 @@ Task/project DGR. `dependencyBinding` для standalone handoff равен null.
 
 # 14. Итоговый checklist пользователя
 
-- beta.12.7 exact package и новый bundled gateway установлены;
+- beta.12.8 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.7
+title: Codex Workflow V2: технический справочник beta.12.8
 subtitle: Protocol 2, state schema 2, transactions, credentials, dependency authority, review и recovery
 part: Часть 3 из 3 | Technical reference
 document_version: 2.0
 date: 29 августа 2026
-subject: Технический контракт Codex Workflow V2 beta.12.7
+subject: Технический контракт Codex Workflow V2 beta.12.8
 ---
 
 # 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.7 | Значение |
+| Параметр beta.12.8 | Значение |
 |---|---|
-| npm package | `codex-workflow-v2@2.0.0-beta.12.7` |
+| npm package | `codex-workflow-v2@2.0.0-beta.12.8` |
 | protocolVersion | 2 |
 | stateSchemaVersion | 2 |
 | lifecycle epoch | 2 |
@@ -37,14 +37,14 @@ Gateway выполняет:
 5. вызов только package-local `dist/src/cli.js --repo <root>`;
 6. `gateway handshake` до lifecycle действий.
 
-Ключевые beta.12.7 capabilities:
+Ключевые beta.12.8 capabilities:
 
 | Группа | Capabilities |
 |---|---|
 | Knowledge и graph | `project-memory-v1`, `graph-binding-v1`, `task-context-refresh-v1` |
 | 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 |
+| C1 | handoff sidecar/bundle, derived Worker actor, credential replacement, Human-gate lease release |
 | Reviews | strict reviewer, Step strict review, continuable remediation, evidence-bound fix/replan routing |
 | Recovery | Task-local dependency provenance, plan integrity, downstream-proof predecessor invalidation, remediation mode, legacy stop override, append-only stop-rebind chain, corrective yield/replan journals |
 | Replacement | `structural-task-replacement-disabled-v1` |
@@ -235,7 +235,8 @@ Claim сверяет stored binding с current Milestone authority до lock acq
 3. Exact target actor вызывает `task claim` с one-time token.
 4. Claim выдаёт first-field `writerLeaseReceipt`.
 5. `task run` принимает token по `next.writerTokenContract`, heartbeats lease и возвращает refreshed receipt.
-6. Terminal handback/release уничтожает active bearer material.
+6. `task result-set` consumes active token и освобождает lease до Human final-acceptance gate.
+7. После acceptance `writer-credential-replace` создаёт merge lease; terminal transitions освобождают его.
 
 Credential нельзя логировать, сохранять в chat packet или включать в evidence. `handoff-show` возвращает
 только safe persisted binding. Recovery использует отдельные advertised replacement actions.
@@ -249,7 +250,7 @@ Credential нельзя логировать, сохранять в chat packet
 | Worker return | Изменения uncommitted и только в allowedWrites |
 | Step complete | History, scope, checks, review gate, exact writer token |
 | Commit | Один Core-owned commit с Task/Step metadata |
-| Submit | Clean tree, Steps completed/skipped, recorded commits and evidence |
+| Submit/Result | Exact evidence/review; Result освобождает lease до Human gate |
 | Merge | Fresh review/acceptance, base conditions, accepted HEAD |
 
 Local start повторно сравнивает authorized base внутри Git branch creation, закрывая TOCTOU между
@@ -442,7 +443,7 @@ Docker socket/CLI `EPERM`, `operation not permitted` или `permission denied`
 После каждой successful mutation обязателен sequential `status`, затем fresh `next`. Failed status/next
 не разрешает direct mutation. Syntax help read-only и не заменяет navigation authority.
 
-# 18. Public command surface beta.12.7
+# 18. Public command surface beta.12.8
 
 | Область | Actions |
 |---|---|
@@ -470,13 +471,7 @@ running Step и active/stale writer lease. Исключения — докуме
 active-downstream-proof bridge и beta.12.7 exact stranded-replan bridge; все они fail-closed и не дают
 общего разрешения dirty update.
 
-Перед beta.12.7 tag release repository выполняет:
-
-1. `npm ci`;
-2. `npm run validate`;
-3. `npm run pack:check`;
-4. `npm run smoke:downstream`;
-5. `npm run plugin:check` и official plugin/skill validators;
-6. `npm run docs:pdf:check`;
-7. `npm run release:check` с exact release tag binding;
-8. validation append-only real-agent lifecycle log.
+Перед beta.12.8 tag обязательны `npm ci`, `npm run validate`, `npm run pack:check`,
+`npm run smoke:downstream`, `npm run plugin:check`, official plugin/skill validators,
+`npm run docs:pdf:check`, `npm run release:check` с exact tag binding и validation
+append-only real-agent lifecycle log.

package/docs/release.md

@@ -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.7, the release gate also relies on `npm run release:check` to fail if:
+For beta.12.8, 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;
@@ -42,6 +42,8 @@ For beta.12.7, the release gate also relies on `npm run release:check` to fail i
   explicit recovery, or dual-readback capabilities are absent from the packaged surface.
 - scoped Task navigation, credential replacement recovery, or sealed external Task/Step review
   commands are absent from the packaged surface.
+- `task result-set` can enter the unbounded Human final-acceptance gate without consuming a live
+  writer credential and releasing its lease, or claimed Task E2E cannot reacquire a fresh merge credential.
 - 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,

package/docs/validation-report.md

@@ -1,110 +1,103 @@
-# V2 beta.12.7 Validation Report
+# V2 beta.12.8 Validation Report
 
-Release candidate `2.0.0-beta.12.7` was validated on 2026-08-29 (Europe/Moscow) with
+Release candidate `2.0.0-beta.12.8` was validated on 2026-08-29 (Europe/Moscow) with
 Node.js 24.17.0.
 
 ## Automated release evidence
 
-- `npm ci` completed from the lockfile with 0 reported vulnerabilities.
-- The final post-fix `npm run validate` passed typecheck and `338/338` sequential tests with no
-  failures, skips, cancellations, or todos in 1,641,977.92675 ms. The same suite also passed after
-  the clean install (`338/338` in 1,661,195.192667 ms) and before it (`338/338` in
-  1,347,257.496667 ms).
-- `npm run test:signal-t03-replan-e2e` independently passed the full Signal-shaped compatibility
-  scenario. The focused dependency-provenance, downstream-proof, and lifecycle-model suite passed
-  `23/23`.
-- The Signal-shaped E2E starts with the exact six-path ownership split and the beta.12.6 accidental
-  post-invalidation Knowledge rebind. It then proves: read-only source eligibility, two
-  dependency-only transport commits, `HEAD^`/`HEAD` provenance validation, bounded dependency
-  registration, atomic replan recovery, required Project Knowledge refresh, mandatory replacement
-  `plan-set`, one-Step dirty carryover admission, hostile concurrency and rollback/restart checks,
-  Core-owned Step commit, passed strict Step Review, and fresh navigation to `task submit`.
-- Negative regressions reject stale Plan rebind, unrelated dirty files, changed content hash,
-  unknown history, a wider dependency candidate, current legacy-Plan audit/authorization, extra Task
-  revisions, active lease, pending transaction, corrupted invalidation/recovery sidecars, and a
-  replacement Plan that does not give one Step authority over the complete dirty set.
-- `npm run pack:check` built the exact beta.12.7 package: 275 files, 1.0 MB packed and 4.1 MB
-  unpacked. The sandboxed attempt
-  could not write the user npm cache (`EPERM`); the exact authorized retry passed.
+- `npm ci` completed from the exact lockfile with 0 reported vulnerabilities.
+- `npm run validate` passed typecheck and `339/339` sequential tests with no failures, skips,
+  cancellations, or todos in 1,700,172.265375 ms.
+- The focused claimed-Task E2E passed independently. It covers sealed passed final review,
+  machine-readable `task result-set` writer-token navigation, rejection of a forged token without
+  Task/lease mutation, successful Result publication, lease-free `awaiting_final_acceptance`, Human
+  acceptance, fresh credential replacement, merge, and terminal lease release.
+- CLI help regression proves that `task result-set` requires `--writer-token` and exposes optional
+  `--actor` for the exact C1 claimant.
+- The full suite retained the Signal-shaped downstream replan E2E, Signal T04 retained-review
+  recovery, dependency provenance, Plan-integrity recovery, corrective replan, lock hostility,
+  transaction crash/recovery, Milestone dependency, strict-review, and credential-confinement gates.
+- `npm run pack:check` built the exact beta.12.8 package with 275 files, 1.0 MB packed and 4.1 MB
+  unpacked. The initial sandboxed invocation could not write the user npm cache (`EPERM`); the exact
+  authorized retry passed.
 - `npm run smoke:downstream` packed and installed the tarball in a disposable consumer project and
   returned `ok=true`. The sandboxed attempt could not resolve the npm registry (`ENOTFOUND`); the
   exact network-authorized retry passed.
-- `npm run plugin:check`, `npm run docs:pdf:check`, and exact
-  `RELEASE_TAG=v2.0.0-beta.12.7 npm run release:check` passed after the final source changes. The
-  bundled gateway cachebuster is `0.1.0+codex.20260829143747`.
-
-## Root causes corrected by beta.12.7
-
-- beta.12.6 correctly invalidated the completed migration predecessor and required a replacement
-  Plan. A later Project Knowledge approval nevertheless mechanically rebound the rejected two-Step
-  Plan and returned the Task to `awaiting_execution_authorization`. The required `plan-set` boundary
-  was therefore lost.
-- The stranded state could not be fixed by another review attempt: no Step was runnable and the
-  current Plan was the artifact whose authority had already been rejected. The defect was routing
-  and recovery authority, not insufficient implementation effort.
-- A one-transition repair was also insufficient. The full E2E exposed two additional dead ends:
-  the exact dependency-only update makes Project Knowledge stale before repair, and the ordinary
-  `task run` clean-checkout precondition rejected the deliberately preserved dirty bytes even after
-  a correct replacement Plan.
-- beta.12.7 adds a closed compatibility sequence. The external source preflight recognizes only the
-  exact beta.12.6 stranded shape. Dependency registration binds the update commit to the original
-  invalidation, rebound Plan, preserved HEAD, dirty paths, and content hash. Replan recovery returns
-  the same Task to `needs_fix` without requiring the now-stale live Knowledge Map to be active.
-- Project Knowledge can then be reconciled and approved, but refresh/rebind routing cannot replace
-  the mandatory `task plan-set`. The old Plan receives no execution authority.
-- Dirty bytes are not adopted as completed evidence. After a fresh Plan Risk Audit and execution
-  authorization, `task run` permits carryover only when one planned Step owns every bound path and
-  current HEAD/path/content hashes exactly match the recovery event. All ordinary checks, Core Git
-  ownership, and strict-review requirements remain in force.
-
-## Exact Signal project evidence
-
-- The Signal repository `/Users/home-pc/htdocs/projects/signal_v4` was inspected and exercised on
-  branch `codex/task-01m0wxjad4-processing-persistence-schema` at
-  `4606eaf98f3c5f1f0dec4c361f34e2abe9aefa66`.
-- Its Workflow remains on exact `2.0.0-beta.12.6`. Task
-  `TASK-01M0WXJAD4GZGVNRJ284ND95C6` remains revision 106 and
-  `awaiting_execution_authorization`; live Workflow state was not mutated by beta.12.7 validation.
-- The dirty set remains exactly six paths: five modified processing-migration files and untracked
-  `tools/postgres/run-processing-integration.ts`. After temporary hostile-test additions were
-  removed, the beta.12.7 source preflight returned `eligible=true`, empty blockers, the preserved
-  HEAD above, and dirty-worktree SHA-256
-  `1cbeb0ccb4883ade6f2ea751423385cf504f5c18e45473f40cb9a39ca850ece1`.
-- The real Signal PostgreSQL harness was temporarily extended with two concurrent migrators and a
-  forced mid-migration conflict followed by restart. `npm run processing:postgres:test` passed clean
-  bootstrap/repeat, advisory-lock serialization, transaction rollback with no partial ledger/schema,
-  unchanged restart convergence, tamper/order denial, catalog fingerprint, immutable evidence, and
-  least-privilege checks against the pinned PostgreSQL image.
-- Those temporary product changes were then removed exactly and the original runner bytes were
-  verified against a parallel Signal checkout before the recovery fingerprint was re-read. This
-  proves product feasibility without falsely presenting pre-authorized test bytes to Workflow.
-- This is strong live read-only entry evidence plus real product proof. It is not a claim that the
-  unpublished beta.12.7 package has already updated Signal or mutated its Task. Final live continuation
-  still requires release publication, exact dependency-only transport, and following fresh
-  project-local `next` through the tested sequence.
+- `npm run plugin:check` passed for bundled gateway
+  `0.1.0+codex.20260829181421`. The plugin-creator manifest validator and skill quick validator also
+  passed using the system Python runtime that provides PyYAML.
+- `npm run docs:pdf:check` reported an empty stale set and exact beta.12.8 package binding.
+- `RELEASE_TAG=v2.0.0-beta.12.8 npm run release:check` and `git diff --check` passed.
+
+## Root cause corrected by beta.12.8
+
+`WorkflowService.setTaskResult` previously moved a reviewed Task from `validating` to
+`awaiting_final_acceptance` without accepting the active writer credential and without releasing
+the Task writer lease. Human final acceptance is intentionally unbounded, so an otherwise successful
+Task could wait until the lease expired. Repository-level `next` then truthfully returned
+`repair-required / STALE_WRITER_LEASE` instead of `task accept`.
+
+Increasing review or implementation attempts cannot correct this condition. The implementation and
+review had already passed; the defect was ownership lifetime crossing a Human pause.
+
+## Implemented lifecycle contract
+
+- `task result-set` now requires the active `--writer-token`; claimed C1 Tasks also pass the exact
+  claimant through `--actor`.
+- Core verifies the current revision, passed/fresh review, live writer credential, and C1 mutation
+  authority before staging Result.
+- Core releases the exact presented lease before committing the transition to
+  `awaiting_final_acceptance`. Human wait time therefore cannot create a new stale lease.
+- Fresh `next` advertises the writer-token contract and bounded credential recovery for
+  `task result-set` when needed.
+- `task accept` remains a credential-free Human/delegated approval transition. After acceptance,
+  fresh `next` advertises `task writer-credential-replace`; this acquires a new lease for local merge
+  or external merge confirmation. The pre-gate token is not reusable.
+- The public handshake exposes `task-human-gate-lease-release-v1`.
+
+## Exact Signal diagnosis evidence
+
+At diagnosis time the Signal project `/Users/home-pc/htdocs/projects/signal_v4` was on exact
+beta.12.7 with Task `TASK-01M0WXJAD4GZGVNRJ284ND95C6` at revision 126 and
+`awaiting_final_acceptance`. The Task checkout was clean at
+`f7ba8533314ee27f176968a6314bf3df40285ef2`; Final Task Review was `passed` with no findings.
+The Result hash was `89bbbaaef5d2b454ed7ed0e3d9f57484d36c9d86d596e009a32613701003496e`
+and Evidence hash was `85f3cb5c16e039ebf40971f88a4388fe1812ef37be8d6b195451aa6a73640c54`.
+Repository-level `next` returned only `locks repair` for the expired lease owned by the Task worker.
+
+The release process did not mutate Signal state or product files. The legacy lease must first be
+removed through that exact advertised repair route with revision, HEAD, review, Result, and Evidence
+readback. The agent must stop before `task accept`. Only after the repository is lease-free and
+`update preflight` is safe should Signal install beta.12.8 and continue through fresh navigation.
 
 ## PDF release documentation evidence
 
-- Three tracked Russian PDFs were regenerated from current Markdown sources;
-  `npm run docs:pdf:check` reported an empty stale set.
-- All 28 pages were rendered and visually inspected: architecture is 8 pages, the delegated
-  chat-only guide is 9 pages, and the technical reference is 11 pages.
-- Titles, beta.12.7 version headers, Cyrillic glyphs, tables, code blocks, new recovery commands,
-  page edges, and footers show no visible clipping, overlap, or unreadable content.
+- All three tracked Russian PDFs were regenerated from the beta.12.8 Markdown sources.
+- Architecture is 8 pages, the delegated chat-only guide is 9 pages, and the technical reference is
+  11 pages. Every page was rendered to PNG and visually inspected.
+- Titles, version headers, Cyrillic text, tables, code blocks, Human-gate credential sequence,
+  release checklist, margins, and page footers have no visible clipping, overlap, orphaned tail page,
+  or unreadable content.
 
 ## Existing boundaries and non-claims
 
-- Structural replacement remains intentionally disabled. beta.12.7 does not implement P04-B,
+- beta.12.8 prevents new `result-set` transitions from retaining a lease. It does not silently delete
+  a stale lease created by beta.12.7 or earlier; legacy state uses explicit `locks repair`.
+- The patch does not auto-accept a Task, bypass final review, widen delegated approval, or turn an
+  expired bearer into authority.
+- Protocol version remains 2 and state schema remains 2; no semantic state migration is introduced.
+- Structural replacement remains intentionally disabled. beta.12.8 does not implement P04-B,
   topology rewiring, completed-Step adoption, or a wider delegation surface.
-- The new bridge is limited to the proven beta.12.6 invalidation-plus-accidental-rebind sequence.
-  It is not a general permission for dirty update, arbitrary Plan rollback, or manual state repair.
-- A negative Plan Risk Audit decision may truthfully return the same Task to planning, but no
-  automatic component decides product semantics or widens Task objective, requirements, acceptance,
-  or Milestone topology.
-- Git transport commits remain agent-executed operations on exact advertised boundaries. Runtime
-  does not create, amend, merge, reset, publish, tag, or push release history.
+- No append-only real-agent lifecycle log was generated for this maintainer release turn because
+  the package Workflow did not orchestrate its own repository mutation. Transcript validator
+  semantics remain covered by the complete valid/invalid fixture suite; no synthetic log is
+  presented as real evidence.
 - Validation performed no npm publication, Git commit, tag, remote push, Signal dependency update,
-  or local plugin reinstall. Those remain separate release/deployment actions.
-- Confidence is high for the implementation, package artifact, synthetic Workflow E2E, and real
-  PostgreSQL proof. Confidence in final live Signal continuation remains conditional on installing
-  the published exact package and observing the same project-local recovery sequence.
+  Signal Task acceptance, or local personal-plugin reinstall. Those are separate release/deployment
+  actions.
+
+Confidence is high for the package implementation, negative credential behavior, complete claimed
+Task continuation, tarball, downstream installation, plugin, and documentation. Confidence that the
+live Signal Milestone will continue is conditional on completing the exact legacy stale-lease repair,
+observing a safe update preflight, installing the published beta.12.8 package, and following fresh
+project-local `status -> next` without skipping the Human gate.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "codex-workflow-v2",
-  "version": "2.0.0-beta.12.7",
+  "version": "2.0.0-beta.12.8",
   "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.20260829143747",
+  "version": "0.1.0+codex.20260829181421",
   "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

@@ -300,6 +300,12 @@ working memory. In claimed C1 posture, fresh `next` exposes `writerTokenContract
 pass the receipt token through its declared `--writer-token` option on the first run call. The
 successful run returns the refreshed writer receipt for later lease-bound transitions.
 
+`task result-set` is also lease-bound. It requires the active `--writer-token` and the exact C1
+claimant in `--actor` when the Task is claimed. Success releases the lease before the Task enters
+`awaiting_final_acceptance`; the token is no longer valid. The Human gate must therefore remain
+lease-free for an arbitrary amount of time. After acceptance, obtain the new merge credential only
+through the `writerCredentialRecovery` action advertised by fresh `next`.
+
 ## Milestone assembly, autonomy, and human gate
 
 During initial planning, materialize every linked Task and then call `milestone plan-set` once

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

@@ -226,6 +226,16 @@ the fresh `next.writerTokenContract` requires it. Successful `task run` returns
 `writerLeaseReceipt`; retain it only until Core releases that lease.
 Never search later payload fields for either credential and never copy credentials into evidence.
 
+When a passed final Task review routes to `task result-set`, pass the active writer credential and,
+for claimed C1 posture, the exact claimant as `--actor`. A successful `result-set` consumes that
+execution lease before entering `awaiting_final_acceptance`; never reuse the old token and never
+leave or manufacture a lease while waiting for the Human decision. After `task accept`, follow fresh
+`next`: local merge or external merge confirmation normally advertises
+`task writer-credential-replace`, which acquires a new bounded lease for the exact recovery actor.
+If a Task created under beta.12.7 or earlier is already at the Human gate with a stale lease, use
+only the exact `locks repair` route returned by repository-level `next`, verify that Task revision,
+review, Result/Evidence hashes, and HEAD did not change, and stop before acceptance.
+
 Command discovery with `codex-workflow <noun> [action] --help` is read-only. Use it only when the
 exact invocation syntax is not already available from `next` and this protocol. Consume declared
 `requiredOptions` and `optionalOptions`; when `exactOptionContractAvailable=false`, consult the