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

package/docs/validation-report.md

@@ -1,111 +1,103 @@
-# V2 beta.12.6 Validation Report
+# V2 beta.12.8 Validation Report
 
-Release candidate `2.0.0-beta.12.6` 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
 
-- The first full `npm run validate` passed typecheck and `335/335` sequential tests with no
-  failures, skips, cancellations, or todos in 1,461,147.464875 ms.
-- `npm ci` then completed from the lockfile with 0 reported vulnerabilities. The clean-install
-  `npm run validate` independently passed the same `335/335` tests with no failures, skips,
-  cancellations, or todos in 1,461,906.892 ms.
-- The exact Signal T04/downstream recovery gate passed `8/8`. The targeted dependency-provenance,
-  downstream-proof, CLI-help, and lifecycle-model suite passed `23/23`.
-- The positive beta.12.6 fixture proves the complete compatibility sequence: exact active-base and
-  Task dependency commits, history validation at `HEAD^`, candidate validation at `HEAD`, dirty
-  content binding, dependency registration, fresh navigation to `task downstream-proof-recover`,
-  unchanged product bytes, and valid recorded Task history. Negative cases cover unrelated dirty
-  files, unregistered history, and an active writer lease. Existing Signal T04 tests remain intact.
-- `npm run pack:check` built the exact beta.12.6 package: 274 files, 1.0 MB packed and 4.0 MB
-  unpacked. The first attempt could not write the user npm cache (`EPERM`); the exact retry used an
-  isolated temporary cache and passed without changing global cache ownership.
+- `npm 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.6 npm run release:check` passed. The plugin gate caught one missing
-  `HEAD^` boundary in the human-facing gateway instructions; that boundary was added and the gate
-  then passed. The bundled gateway cachebuster is `0.1.0+codex.20260829120000`.
-
-## Root cause corrected by beta.12.6
-
-- beta.12.5 correctly classified the current Signal downstream-proof conflict as recoverable, but
-  that did not make the release installable. Signal still runs beta.12.4, whose ordinary update
-  preflight rejects the running Step and dirty product work. Installing beta.12.5 would also advance
-  dependency manifests/HEAD before that new runtime could register the commit. The advertised
-  beta.12.5 recovery was therefore unreachable from the actual starting version.
-- This is an update authority deadlock, not a need for more review attempts: the old runtime cannot
-  authorize the dirty update, while the new runtime cannot be reached without an exact update.
-- beta.12.6 adds one bounded bridge rather than general dirty-update permission. The active
-  Milestone base and Task branch must each receive a separate dependency-only commit changing
-  exactly `package.json` and `package-lock.json`. A fresh beta.12.6 runtime then advertises
-  `update downstream-proof-dependency-recover` only for the active downstream-proof shape.
-- Preflight verifies recorded Task history at `HEAD^`, the exact candidate at `HEAD`, aligned
-  runtime/declared/locked/installed/current-branch/base versions, one active Step, completed
-  transitive-predecessor ownership, branch and Plan bindings, no lease, no pending/corrupt
-  transaction or Core operation, and every dirty path plus SHA-256 content.
-- Recovery registers only the dependency candidate in `systemCommits` and records the bound proof
-  in `dependencyProvenanceRecoveries.activeDownstreamProof`. It does not edit, stash, reset, commit,
-  or discard product work and does not change Step state. Fresh `next` then prioritizes
-  `task downstream-proof-recover` over manifest-induced Knowledge refresh.
-- The ordinary downstream recovery remains responsible for invalidating stale predecessor
-  completion authority and returning the same Task to a new Plan, Risk Audit, authorization,
-  execution, and strict-review cycle. beta.12.6 does not bypass that lifecycle.
-
-## Exact Signal read-only evidence
-
-- The Signal repository `/Users/home-pc/htdocs/projects/signal_v4` was re-observed read-only after
-  implementation. It remains on branch
-  `codex/task-01m0wxjad4-processing-persistence-schema` at
-  `88f8bf70d1591852ad90c976625430d4f20585ac`.
-- Its dirty set remains exactly six paths: five modified processing-migration files and one
-  untracked `tools/postgres/run-processing-integration.ts`. No Signal repository or Workflow state
-  was mutated during beta.12.6 implementation.
-- Prior read-only state inspection identified Task
-  `TASK-01M0WXJAD4GZGVNRJ284ND95C6`, revision 103, active Step
-  `STEP-002-REAL-POSTGRES-PROOF`, five files owned by completed transitive predecessor
-  `STEP-001-PROCESSING-MIGRATIONS`, and one file owned by the active proof Step. The predecessor
-  evidence commit equals the preserved HEAD.
-- The installed beta.12.4 ordinary update preflight returned `safe=false` for the running Step and
-  dirty checkout. The external beta.12.5 classifier returned `applicable=true`, `eligible=true`, and
-  no recovery blockers, proving that the product boundary itself is supported but not that the old
-  update path can reach it.
-- The beta.12.6 regression fixture mirrors all six Signal paths and the same predecessor/active-Step
-  ownership split. It proves the new update bridge and subsequent downstream recovery route under
-  controlled Git/state mutations.
-- This is strong structural and synthetic evidence, not a claim that the published package has
-  already updated live Signal. The final operational proof still requires the released exact
-  package, two exact dependency-only transport commits, the advertised preflight/recover, and a
-  fresh Signal `status -> next` readback.
+- `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 Markdown sources; `npm run docs:pdf:check`
-  reported an empty stale set.
-- All 27 pages were rendered and visually inspected: architecture is 7 pages (101,761 bytes), the
-  delegated chat-only guide is 9 pages (107,066 bytes), and the technical reference is 11 pages
-  (112,132 bytes).
-- Visual inspection found table headers rendered dark-on-dark. The shared generator now uses an
-  explicit white bold header Paragraph style; all documents were regenerated and re-inspected.
-  Titles, version headers, Cyrillic glyphs, tables, code blocks, recovery instructions, page edges,
-  and footers have no visible clipping, overlap, or unreadable content.
+- 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.6 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 compatibility bridge is limited to the proven active-downstream-proof shape. Unrelated dirty
-  paths, non-predecessor ownership, unknown history, a wider dependency commit, stale base/version
-  divergence, branch/Plan/Step mismatch, lease, transaction, or damaged sidecar fails closed.
-- Read-only preflight is an observation, not an authorization token. Recover recomputes the current
-  binding. The stored hash proves which bytes the bridge preserved; subsequent downstream recovery
-  revalidates paths, ownership, and history, while the replacement Plan and review cover current
-  content.
-- Git transport commits remain agent-executed operations on exact advertised boundaries. The
-  runtime does not create, amend, merge, reset, or push Git history.
-- Validation performed no Signal mutation, npm publication, Git commit, tag, remote push, or local
-  plugin reinstall. Those are separate release/deployment actions.
-- Confidence is high for the implemented source and tested Signal-shaped transition. Confidence in
-  the final live Signal update remains pending until the published package is installed and the
-  project-local runtime returns the expected recovery sequence.
+- 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,
+  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.6",
+  "version": "2.0.0-beta.12.8",
   "description": "Requirements-first Codex development workflow with local state and explicit Git ownership.",
   "repository": {
     "type": "git",
@@ -44,6 +44,7 @@
     "typecheck": "tsc -p tsconfig.json --noEmit",
     "test": "node scripts/with-validation-lock.mjs test",
     "test:signal-t04-recovery": "node scripts/with-validation-lock.mjs test-signal-t04",
+    "test:signal-t03-replan-e2e": "node scripts/with-validation-lock.mjs test-signal-t03-replan",
     "validate": "npm run typecheck && npm test",
     "pack:check": "npm run build && npm pack --dry-run",
     "smoke:downstream": "npm run build && node scripts/downstream-smoke.mjs",

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

@@ -1,6 +1,6 @@
 {
   "name": "codex-workflow-gateway",
-  "version": "0.1.0+codex.20260829120000",
+  "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

@@ -166,6 +166,21 @@ recovery when required). Any unrelated dirty path, unknown history, wider candid
 base, version mismatch, lease, transaction, or different route is a hard stop and never authorizes
 manual external-state edits.
 
+For the exact beta.12.6 post-recovery knowledge-rebind deadlock, an exact beta.12.7 external runner
+may execute only the read-only `update downstream-proof-replan-update-preflight` before dependency
+transport. Require `eligible=true`, source version beta.12.6 on declared/locked/installed/current/base
+surfaces, the exact Task revision/HEAD/dirty hash, no current audit for the rebound Plan, and no lease,
+transaction, or Core operation. Commit only `package.json` and `package-lock.json` on the active
+Milestone base, then only the same dependency files on the Task branch without touching product
+bytes. Install beta.12.7 and follow fresh `next` only through
+`update downstream-proof-replan-dependency-recover`, then
+`task downstream-proof-replan-recover`, and finally ordinary `task plan-set`. The recovery keeps the
+same Task, history, Knowledge binding, invalidated predecessor evidence, and dirty worktree. After
+the replacement Plan is audited and authorized, `task run` is valid only when fresh `next` reports
+`downstreamProofCarryover.state=validated` for one Step owning the complete hash-bound dirty set.
+Any wider dependency commit, dirty-byte change, current audit, extra Task revision, missing binding,
+or alternate route is a hard stop.
+
 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
@@ -211,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

package/schemas/downstream-proof-invalidation-event.schema.json

@@ -52,6 +52,7 @@
       "uniqueItems": true,
       "items": { "type": "string", "minLength": 1 }
     },
+    "dirtyWorktreeHash": { "$ref": "#/$defs/hash64" },
     "preservedHeadCommit": { "$ref": "#/$defs/gitHash" },
     "actor": { "type": "string", "minLength": 1 },
     "reason": { "type": "string", "minLength": 1 },

package/schemas/downstream-proof-replan-recovery-event.schema.json

@@ -0,0 +1,61 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "https://codex-workflow.local/schemas/downstream-proof-replan-recovery-event.schema.json",
+  "title": "Codex Workflow V2 Downstream Proof Replan Recovery Event",
+  "type": "object",
+  "additionalProperties": false,
+  "required": [
+    "eventId",
+    "taskId",
+    "previousTaskRevision",
+    "resultTaskRevision",
+    "invalidationEventId",
+    "invalidationPlanHash",
+    "reboundPlanHash",
+    "knowledgeRebindRecordedAt",
+    "dirtyFiles",
+    "dirtyWorktreeHash",
+    "preservedHeadCommit",
+    "dependencyRecoveryCommit",
+    "actor",
+    "reason",
+    "packageVersion",
+    "previousEventHash",
+    "recordedAt",
+    "eventHash"
+  ],
+  "properties": {
+    "eventId": { "type": "string", "pattern": "^DPR-[0-9A-HJKMNP-TV-Z]{26}$" },
+    "taskId": { "type": "string", "pattern": "^TASK-[0-9A-HJKMNP-TV-Z]{26}$" },
+    "previousTaskRevision": { "type": "integer", "minimum": 1 },
+    "resultTaskRevision": { "type": "integer", "minimum": 2 },
+    "invalidationEventId": { "type": "string", "pattern": "^DPI-[0-9A-HJKMNP-TV-Z]{26}$" },
+    "invalidationPlanHash": { "$ref": "#/$defs/hash64" },
+    "reboundPlanHash": { "$ref": "#/$defs/hash64" },
+    "knowledgeRebindRecordedAt": { "type": "string", "format": "date-time" },
+    "dirtyFiles": {
+      "type": "array",
+      "minItems": 1,
+      "uniqueItems": true,
+      "items": { "type": "string", "minLength": 1 }
+    },
+    "dirtyWorktreeHash": { "$ref": "#/$defs/hash64" },
+    "preservedHeadCommit": { "$ref": "#/$defs/gitHash" },
+    "dependencyRecoveryCommit": {
+      "anyOf": [
+        { "$ref": "#/$defs/gitHash" },
+        { "type": "null" }
+      ]
+    },
+    "actor": { "type": "string", "minLength": 1 },
+    "reason": { "type": "string", "minLength": 1 },
+    "packageVersion": { "type": "string", "minLength": 1 },
+    "previousEventHash": { "anyOf": [{ "$ref": "#/$defs/hash64" }, { "type": "null" }] },
+    "recordedAt": { "type": "string", "format": "date-time" },
+    "eventHash": { "$ref": "#/$defs/hash64" }
+  },
+  "$defs": {
+    "gitHash": { "type": "string", "pattern": "^[a-f0-9]{40}$" },
+    "hash64": { "type": "string", "pattern": "^[a-f0-9]{64}$" }
+  }
+}

package/schemas/task.schema.json

@@ -100,6 +100,40 @@
               }
             },
             "additionalProperties": false
+          },
+          "downstreamProofReplan": {
+            "type": "object",
+            "required": [
+              "invalidationEventId",
+              "activeStepId",
+              "sourcePlanHash",
+              "reboundPlanHash",
+              "knowledgeRebindRecordedAt",
+              "dirtyFiles",
+              "dirtyWorktreeHash",
+              "invalidatedStepIds"
+            ],
+            "properties": {
+              "invalidationEventId": { "type": "string", "pattern": "^DPI-[0-9A-HJKMNP-TV-Z]{26}$" },
+              "activeStepId": { "type": "string", "pattern": "^STEP-[A-Z0-9][A-Z0-9-]{2,63}$" },
+              "sourcePlanHash": { "type": "string", "pattern": "^[a-f0-9]{64}$" },
+              "reboundPlanHash": { "type": "string", "pattern": "^[a-f0-9]{64}$" },
+              "knowledgeRebindRecordedAt": { "type": "string", "format": "date-time" },
+              "dirtyFiles": {
+                "type": "array",
+                "minItems": 1,
+                "uniqueItems": true,
+                "items": { "type": "string", "minLength": 1 }
+              },
+              "dirtyWorktreeHash": { "type": "string", "pattern": "^[a-f0-9]{64}$" },
+              "invalidatedStepIds": {
+                "type": "array",
+                "minItems": 1,
+                "uniqueItems": true,
+                "items": { "type": "string", "pattern": "^STEP-[A-Z0-9][A-Z0-9-]{2,63}$" }
+              }
+            },
+            "additionalProperties": false
           }
         },
         "additionalProperties": false