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

package/docs/validation-report.md

@@ -1,85 +1,124 @@
-# V2 beta.10 Validation Report
+# V2 beta.11 Validation Report
 
-Release candidate `2.0.0-beta.10` was validated on 2026-08-22 with Node.js 24.17.0.
+Release candidate `2.0.0-beta.11` was validated on 2026-08-24 with Node.js 24.17.0.
 
 ## Automated release evidence
 
-- `npm run validate` passed `297/297` sequential tests with no failures, skips,
-  cancellations, or todos. The exact Signal recovery tests also passed independently through
-  `npm run test:signal-t04-recovery` (`5/5`).
-- `npm run pack:check` passed with an isolated temporary npm cache. The tarball contains 247 files;
-  package size is 1.0 MB and unpacked size is 3.6 MB.
-- `npm run smoke:downstream` packed and installed the actual beta.10 tarball in an empty project,
-  then passed the packaged CLI handshake. The first sandboxed attempt was network-blocked while
-  fetching `ajv`; the authorized network retry passed.
+- `npm ci` completed from the committed lockfile with 0 reported vulnerabilities.
+- The final `npm run validate` passed `319/319` sequential tests with no failures, skips,
+  cancellations, or todos. The focused Signal recovery suite passed independently (`5/5`).
+- `npm run pack:check` passed. The beta.11 tarball contains 269 files; package size is approximately
+  951 kB and unpacked size is 3.7 MB.
+- `npm run smoke:downstream` packed and installed the actual beta.11 tarball in an empty temporary
+  project, then passed the packaged CLI handshake. The first sandboxed attempt was network-blocked
+  while fetching `ajv`; the authorized network retry and the final post-`npm ci` run passed.
 - `npm run plugin:check`, the plugin-creator structural validator, the skill validator,
-  `npm run release:check`, and `git diff --check` passed. The bundled plugin source cachebuster is
-  `0.1.0+codex.20260822140058`; the packaged installer produced and read back personal installation
-  `0.1.0+codex.20260822140239` with the beta.10 recovery instructions present in source and cache.
-
-## beta.10 retained-review recovery evidence
-
-- Recovery still requires one clean local Task branch whose final unregistered HEAD changes exactly
-  `package.json` and `package-lock.json`, with runtime, manifest, lock, installed package, current
-  branch, and Task base branch all aligned to beta.10. Running Steps, leases, transactions, Core
-  operations, product changes in the candidate, and base payload drift fail closed.
-- A product commit removed from the current Step by corrective replan is now admissible only when
-  Core derives it from the globally validated strict-review sidecars: an intact
-  `pending → review-recorded → attestation-verified` chain, `passed` decision, exact completion
-  commit, and verified reviewer isolation. Pending review and a corrupted event-hash chain fail
-  closed in dedicated regressions.
-- The dependency candidate is recorded in `systemCommits`. Historical reviewed product commits are
-  recorded separately in `dependencyProvenanceRecoveries[].retainedHistoricalCommits`; they are not
-  relabelled as Workflow system commits. Normal Git-history validation consumes both provenance
-  classes after recovery.
-- The release check pins the exact sanitized Signal fixture: project
-  `b06d0f18f790f4521a23c770`, Milestone `MS-01M0HVCBC9DM3XQAR82T4550DA`, Task
-  `TASK-01M0HVK4YDJ3W9X0N72TYNV8WK` revision 26, status
-  `awaiting_execution_authorization`, planned Step with null current evidence, recorded system
-  commits `d6cce722…` and `198de88…`, and retained passed-review commit `acdfc803…`.
-
-## Isolated exact Signal replay
-
-- The real Signal Git branch and Workflow state were copied to temporary isolated state plus two
-  temporary Git worktrees. The replay modelled the actual installed transition
-  `2.0.0-beta.7 → 2.0.0-beta.10`; it did not assume beta.9.
-- With an exact dependency-only candidate over `acdfc803…`, read-only preflight returned
-  `eligible=true`, no blockers, Task revision 26, and exactly one retained historical commit:
-  `acdfc80345d2d4cd9d42af17da246701c42f0969`.
-- Fresh `next` advertised only `update dependency-provenance-recover`. Recovery advanced the copied
-  Task `26 → 27`, preserved current corrective Plan/Step posture, appended the dependency candidate
-  to `systemCommits`, and persisted `acdfc803…` under `retainedHistoricalCommits`.
-- Sequential post-recovery `status → next` returned the normal actionable route
-  `task context-refresh`, because manifest/lock changed the derived Knowledge inputs. It did not
-  return `doctor` or another dependency recovery.
-- Temporary worktrees, branches, tarball, and copied Workflow state were deleted. Direct readback
-  then confirmed the real Signal repository remained clean at `acdfc803…` and the real Task remained
-  revision 26 with no dependency-provenance recovery record.
-
-## Progress, replacement, and chat evidence
-
-- The full suite retains the read-only Milestone progress projection and exact regression
-  `T03 cancelled → T08 replacement`, including stable membership/Step ordinals.
-- Automated chat-registry coverage still proves project-monotonic `#NNN`, all compact title
-  families, long Cyrillic readback/fallback, multiple review attempts, and atomic allocation.
-- The beta.9 live App E2E evidence remains valid for the unchanged title/registry implementation:
-  Tasks `01a02928-0436-7af2-a1b9-a969226d50d9`,
-  `01a02928-3d39-7673-8e08-6d4ed0f8d554`, and
-  `01a02928-58a0-7e03-b487-f8877b7f76d8` exercised Task, Step Review A1, and Step Review A2 with
-  exact deterministic fallback and readback before archival.
-
-## External App-runtime limitation retained
-
-Plugin CLI installation and cache readback passed. A currently open Codex task can still retain the
-skill path injected when that task started; loading the new personal plugin version requires a new
-Codex task. This is an App runtime/catalog lifetime boundary, not a package or Workflow-state
-failure.
+  `npm run docs:pdf:check`, `npm run release:check`, and `git diff --check` passed. The bundled
+  gateway cachebuster is `0.1.0+codex.20260824113210`.
+
+## Bounded Plan-integrity recovery evidence
+
+- Recovery becomes applicable only after the first ordinary `checks-failed` remediation for a
+  guarded failed Step when at least one Plan check is an exact root `npm run[-script] <name>`
+  command whose named script is absent from the root `package.json`, and that manifest is outside
+  the Step's exact `allowedWrites` boundary.
+- Fresh evidence binds the Task revision, first remediation event ID/hash, current Plan and Step
+  definition, root manifest path/hash, Git HEAD, exact check commands, missing script names, and
+  current dirty-file set into one canonical conflict hash.
+- An eligible `next` advertises only `task plan-integrity-recover`. The mutation appends one
+  schema-validated `replan-required` corrective decision and does not modify the worktree or invent
+  a second failed execution attempt.
+- Existing C1 ownership remains authoritative. A claimed Worker must execute the advertised
+  recovery and then yield its claim before the existing journaled, Human-gated corrective-replan
+  transition can prepare replacement Plan authority.
+- The route fails closed when `package.json` is writable by the Step, no missing-script check
+  matches the bounded npm-script grammar, unrelated dirty files exist, bindings drift, or
+  persisted evidence is malformed or tampered.
+
+## Regression coverage
+
+- Four dedicated beta.11 regressions cover the exact happy path, the in-scope-manifest exclusion,
+  dirty-worktree rejection, and sidecar evidence tampering.
+- Existing remediation-mode recovery retains higher navigation priority than the new assessment;
+  the legacy malformed-third-attempt regression passes unchanged.
+- The corrective-replan serialized definition SHA moved to
+  `c601cc100790a19e6ece2a1d60fb46d1e1d52e6922e6104d84f4b6ffe7ba0225` because the decision event
+  schema now admits the bounded ordinal-2 recovery record. Its runtime semantic fingerprint remains
+  `bd4e7a0ddfcb6abc0c5eb107775e6aea7e08c4606dda4d945d77af8a4520710d`, and the runtime catalog hash
+  remains `fa1d11860d4f07978c3b8e85d1f91cd3d15b17284b05f41e05d462d3bb092aed`.
+- The beta.10 dependency-provenance and exact Signal T04 revision-26 regressions remain green.
+- The read-only Milestone projection still preserves `T03 cancelled → T08 replacement`, and the
+  monotonic chat registry/title fallback regressions remain green.
+
+## Trusted-harness release replay
+
+- A fresh disposable project installed the actual current beta.11 tarball, declared the exact
+  `2.0.0-beta.11` dependency, and passed package handshake plus `doctor` with protocol 2 and state
+  schema 2. Its Git checkout remained clean.
+- The automatic trusted harness invoked the real packaged CLI and append-only recorded Discovery
+  bootstrap, sequential `status → next` checkpoints, Project Knowledge scan/approval, and
+  Discovery-to-Task materialization through the resulting `task plan-set` boundary.
+- The semantic lifecycle log validated `24/24` events with no failed or unadvertised mutation and
+  no missing checkpoint. Its SHA-256 is
+  `5c1d666aa3bc27c4b6687b836a565823a1f567227e93f76b2c3285217fb9a0b7`.
+- The matched raw result log contains 12 successful CLI results, no C1 credential fields, and has
+  SHA-256 `a51bae7221fa0ff30bd571ca3800bf8ac44911d7746f68e5e86987b6c357ccf6`.
+  The exercised tarball SHA-256 is
+  `3b7ed19961ba8394625d3a481fafb196dd80be5b138635a0bd1ce084a47fc06e`.
+- This targeted real-agent replay validates release navigation discipline and package integration;
+  it does not claim a second full product Milestone. Deeper P01/P04 lifecycle behavior is covered
+  by the deterministic and integration suites listed below.
 
 ## Not claimed
 
-- No npm publication, Git tag, push, or release commit was performed by validation.
-- No real Signal Workflow mutation, package update, branch change, or manual external-state edit was
-  performed.
-- The isolated replay proves the exact recovery path before publication; a real Signal update must
-  still install the published beta.10 package and follow fresh project-local `handshake → doctor →
-  status → next → preflight → advertised recovery`.
+- Validation itself performs no npm publication, Git tag, push, Signal Workflow mutation, or local
+  plugin reinstall.
+- The implementation and package gates prove the bounded route. A real blocked project must still
+  install the published beta.11 package and follow its fresh project-local `handshake → doctor →
+  status → next → advertised recovery` navigation.
+
+## Post-beta.11 combined P04-A/P01-A candidate evidence
+
+This later evidence was recorded on 2026-08-24 on branch `codex/p04-task-dependencies` and was
+incorporated into the final beta.11 candidate.
+
+- P04-A adds the canonical Milestone dependency DAG, atomic initial Plan transaction/recovery,
+  dependency-bound handoff/claim/start, legacy fail-closed policy, and unconditional pre-write
+  structural replacement shutdown.
+- P01-A adds 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.
+- After final source review added a pre-Git-mutation start race guard, `npm test` passed the exact
+  final sequential `319/319` suite with zero failures, skips, cancellations, or todos. The 13/13
+  focused P01-A suite, 84/84 affected P01/P04/Task lifecycle selection, and 4/4 beta.11
+  late-recovery compatibility tests also passed.
+- `npm run typecheck`, `npm run plugin:check`, `npm run release:check`, schema validation inside
+  the full suite, the focused packaged-handshake capability test, and `git diff --check` passed.
+- The changed bundled gateway uses cachebuster `0.1.0+codex.20260824113210`; it was validated but
+  not reinstalled.
+- No merge, package install, tag, publication, plugin reinstall, Signal mutation, or brief status
+  transition to `implemented` is claimed by this candidate evidence.
+
+## beta.11 PDF release documentation evidence
+
+The Russian PDF set was regenerated and revalidated on 2026-08-24 against the combined beta.11
+candidate described above.
+
+- The three tracked PDF binaries now have reviewable Markdown authorities under
+  `docs/pdf/sources/` and one deterministic ReportLab generator. `npm run docs:pdf:check`
+  regenerated all outputs and 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. Text extraction found no
+  empty pages. The architecture orphan-page defect found during inspection was removed, and the
+  complete delegated Discovery prompt no longer splits its readiness checklist across pages.
+- The content documents beta.11 delegated Discovery, the Milestone Autonomy Contract, explicit
+  `dependsOnTaskIds`, P04-A runnable routing and structural-replacement stop, P01-A mechanical
+  feasibility, C1 credential boundaries, external-sealed review, Plan-integrity recovery, and the
+  limited derived-graph role of `codebase-memory-mcp`.
+- `npm run pack:check` passed with an isolated writable npm cache. The 269-file dry-run tarball
+  contains all three PDFs, all three Markdown sources, the PDF README and pinned requirement, and
+  both generator/check scripts.
+- On the same beta.11 code tree, `npm run validate` passed `319/319`; `npm run typecheck`,
+  `npm run plugin:check`, `npm run release:check`, and `git diff --check` also passed.
+
+This evidence makes the documentation package-ready for beta.11. The release action remains a
+separate Git/tag operation after all final gates pass on the exact candidate tree.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "codex-workflow-v2",
-  "version": "2.0.0-beta.10",
+  "version": "2.0.0-beta.11",
   "description": "Requirements-first Codex development workflow with local state and explicit Git ownership.",
   "repository": {
     "type": "git",
@@ -34,6 +34,8 @@
     "references",
     "plugins",
     "docs",
+    "scripts/generate-pdf-docs.py",
+    "scripts/run-pdf-docs.mjs",
     "README.md"
   ],
   "scripts": {
@@ -46,6 +48,8 @@
     "pack:check": "npm run build && npm pack --dry-run",
     "smoke:downstream": "npm run build && node scripts/downstream-smoke.mjs",
     "plugin:check": "node scripts/validate-plugin.mjs",
+    "docs:pdf": "node scripts/run-pdf-docs.mjs",
+    "docs:pdf:check": "node scripts/run-pdf-docs.mjs --check",
     "release:check": "node scripts/release-check.mjs",
     "publish:release": "node scripts/publish.mjs"
   },

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

@@ -1,6 +1,6 @@
 {
   "name": "codex-workflow-gateway",
-  "version": "0.1.0+codex.20260822140058",
+  "version": "0.1.0+codex.20260824113210",
   "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,12 @@
 # Gateway Protocol V2
 
-## beta.10 coordinator projections, retained review provenance, and chat registry
+## beta.11 coordinator projections, retained review provenance, chat registry, and Plan-integrity recovery
+
+- 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
+  first-failure missing-root-npm-script evidence and must be followed by fresh `status -> next`.
+  It records a replan posture without changing Plan or product files; corrective yield and the
+  existing state-bound corrective-replan Human gate remain mandatory.
 
 - `update dependency-provenance-preflight --id <TASK-ID>` is read-only. The matching
   `update dependency-provenance-recover --id <TASK-ID> --expected-revision <N> --actor <ACTOR>
@@ -38,7 +44,7 @@ Current capability set:
 - `delegated-approval-v1`
 - `task-knowledge-rebind-v1`
 - `task-context-refresh-v1`
-- `terminal-task-replacement-transaction-v1`
+- `structural-task-replacement-disabled-v1`
 - `project-composite-transaction-journal-v1`
 - `corrective-plan-audit-v1`
 - `safe-update-preflight-v1`
@@ -52,7 +58,10 @@ Current capability set:
 - `step-remediation-circuit-breaker-sidecar-v1`
 - `milestone-scope-change-sidecar-v1`
 - `milestone-membership-integrity-v1`
+- `milestone-task-dependency-dag-v1`
+- `milestone-initial-plan-transaction-v1`
 - `task-c1-handoff-sidecar-v1`
+- `task-mechanical-feasibility-v1`
 - `semantic-plan-risk-audit-v2`
 - `guarded-remediation-hard-stop-v1`
 - `milestone-reverse-membership-integrity-v1`
@@ -62,10 +71,18 @@ Current capability set:
 - `milestone-initial-assembly-v1`
 - `milestone-initial-assembly-navigation-v2`
 - `milestone-autonomy-contract-v1`
+- `milestone-autonomy-content-refresh-v1`
 - `milestone-autonomous-membership-evolution-v1`
 - `task-c1-derived-worker-actor-v1`
 - `guarded-corrective-auditor-routing-v1`
+- `corrective-decision-context-recovery-v1`
+- `remediation-mode-recovery-v1`
 - `plan-proof-obligations-v1`
+- `bounded-plan-integrity-recovery-v1`
+- `corrective-yield-journal-v1`
+- `corrective-replan-journal-v1`
+- `corrective-replan-human-gate-v1`
+- `corrective-replan-protocol-v2`
 
 Protocol `1` and schema `2` remain valid only because alpha.7 is additive. The gateway must
 not claim compatibility if canonical entity shapes or non-additive command semantics change.

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

@@ -50,6 +50,17 @@ 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.
 
+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
+`checks-failed` remediation, an exact missing root npm script, `package.json` outside the Step's
+`allowedWrites`, and a dirty-file set confined to that Step. Pass the exact returned actor and the
+active writer token when the C1 contract requires it. The recovery records only a bound early
+`replan-required` decision: it does not edit the Plan or worktree. Then follow fresh `next` through
+`task corrective-yield` and the existing Human-confirmed corrective-replan flow. Never repeat
+`task run` merely to manufacture the second failure, and never invoke this recovery for a generic
+test failure, a writable manifest, or unconfined changes.
+
 If any step fails, report the concrete diagnostic. Do not load workflow
 semantics from this skill.
 
@@ -85,9 +96,12 @@ Autonomy Grant. Never infer eligibility from the Plan yourself; if Core returns
 `contextRefreshBlocked.unsafeDifferences`, use the ordinary visible Knowledge Map flow.
 
 When `next` reports terminal `split-required`, follow `docs/split-required-recovery.md` from the
-installed package. The only valid continuation is the exact `task replacement-materialize`
-transition (or creation of its one ready Discovery when requested). Never rebind, refresh, replan,
-authorize, or resume the historical Task, and never emulate the membership changes manually.
+installed package. P04-A returns `doctor` with blocked action `task replacement-materialize`,
+diagnostic `STRUCTURAL_REPLACEMENT_REQUIRED`, and
+`replacementGate.structuralReplacementAvailable=false`. Stop without invoking the retained
+command shape or consuming a replacement Discovery. Never rebind, refresh, replan, authorize,
+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 `next` returns `milestone initial-assembly`, execution is unavailable. Follow only the
 advertised `linked-task-assembly.commands` (`discovery start` and `discovery materialize`) until all

package/references/state-machine.md

@@ -78,20 +78,24 @@ the grant's Milestone. Every added source must match the Plan, and removals, can
 wildcard or directory targets, existing source category/scope/authority changes, gaps, and
 conflicts fail closed before any state write. `next` exposes the composite option only when the
 full predicate passes and otherwise reports concrete unsafe differences. Both update paths journal
-`state.json`, `plan.json`, and `scope-change-events.jsonl` together. Membership integrity is validated
-before scheduling, Task start, Milestone validation, scope change, and repository `next`.
+`state.json`, `plan.json`, and `scope-change-events.jsonl` together. Initial Plan publication uses
+the same recovery journal for `state.json` and `plan.json`. Membership and dependency integrity is
+validated before scheduling, handoff, claim (before lease acquisition), Task start, Milestone
+validation, scope change, and repository `next`.
 The same guard scans in reverse and blocks every live Task whose `milestoneId` is absent from
 the Milestone's required/waived/cancelled classification.
 
 `C1` coordination is machine-bound but local: `task handoff-prepare` returns a one-time claim
 token and prompt bound to a stable handoff ID, revision, context hashes, Milestone positions,
-delegate/grant, expected next action, and expiry. `task claim` validates those bindings and
+Milestone revision, membership revision, Milestone Plan hash, delegate/grant, expected next action,
+and expiry. `task claim` validates those bindings and
 activates claimant-only mutation; terminal `task handback-create` returns result, evidence,
 review, knowledge, limitation, and recommended-next bindings. Milestone Tasks must be claimed
 before start. If no target is supplied, Core derives `agent:worker:<task-id>`. No part of this
 contract requires or proves a physically separate Codex thread.
 
-Repository-level scheduling respects current Milestone membership. An unstarted linked Task
-is eligible only for an `active` Milestone with `required` disposition. Historical unstarted
+Repository-level scheduling respects current Milestone membership and its canonical dependency
+DAG. A linked Task is eligible only for an `active` Milestone with `required` disposition after
+all required predecessors are `merged`. Historical unstarted
 Tasks from `waived`, `cancelled`, accepted, or cancelled Milestone paths cannot shadow the
 Milestone/repository transition returned by `next`.

package/schemas/authorization-event.schema.json

@@ -20,7 +20,8 @@
     "headCommit": { "$ref": "#/$defs/nullableHash" },
     "reason": { "type": "string" },
     "authorizationMode": { "enum": ["human", "delegated"] },
-    "delegation": { "$ref": "#/$defs/delegation" }
+    "delegation": { "$ref": "#/$defs/delegation" },
+    "mechanicalFeasibility": { "$ref": "#/$defs/mechanicalFeasibility" }
   },
   "allOf": [
     {
@@ -50,6 +51,68 @@
           ]
         }
       }
+    },
+    "mechanicalFeasibility": {
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "schemaVersion", "taskId", "evaluatedTaskRevision", "briefHash", "planHash",
+        "sourceKind", "sourceBranch", "evaluatedHead", "baseCommit", "analyzerSetHash",
+        "analyzerInputHash", "analyzers", "findings", "decision"
+      ],
+      "properties": {
+        "schemaVersion": { "const": 1 },
+        "taskId": { "type": "string", "pattern": "^TASK-[0-9A-HJKMNP-TV-Z]{26}$" },
+        "evaluatedTaskRevision": { "type": "integer", "minimum": 1 },
+        "briefHash": { "type": "string", "pattern": "^[a-f0-9]{64}$" },
+        "planHash": { "type": "string", "pattern": "^[a-f0-9]{64}$" },
+        "sourceKind": { "enum": ["pre-start-base", "corrective-task-workspace"] },
+        "sourceBranch": { "type": "string", "minLength": 1 },
+        "evaluatedHead": { "type": "string", "pattern": "^[a-f0-9]{40,64}$" },
+        "baseCommit": { "$ref": "#/$defs/nullableHash" },
+        "analyzerSetHash": { "type": "string", "pattern": "^[a-f0-9]{64}$" },
+        "analyzerInputHash": { "type": "string", "pattern": "^[a-f0-9]{64}$" },
+        "analyzers": {
+          "type": "array",
+          "minItems": 3,
+          "maxItems": 3,
+          "items": { "$ref": "#/$defs/mechanicalAnalyzer" }
+        },
+        "findings": {
+          "type": "array",
+          "items": { "$ref": "#/$defs/mechanicalFinding" }
+        },
+        "decision": { "enum": ["clear", "blocked"] }
+      }
+    },
+    "mechanicalAnalyzer": {
+      "type": "object",
+      "additionalProperties": false,
+      "required": ["analyzerId", "analyzerVersion"],
+      "properties": {
+        "analyzerId": {
+          "enum": ["wf2.root-npm-script", "wf2.exact-output-path", "wf2.exact-predecessor-path"]
+        },
+        "analyzerVersion": { "const": 1 }
+      }
+    },
+    "mechanicalFinding": {
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "analyzerId", "analyzerVersion", "result", "stepId", "subject", "evidence", "reasonCode"
+      ],
+      "properties": {
+        "analyzerId": {
+          "enum": ["wf2.root-npm-script", "wf2.exact-output-path", "wf2.exact-predecessor-path"]
+        },
+        "analyzerVersion": { "const": 1 },
+        "result": { "enum": ["pass", "blocked", "unverified"] },
+        "stepId": { "type": "string", "pattern": "^STEP-[0-9]{3}(?:-[A-Z0-9-]+)?$" },
+        "subject": { "type": "string" },
+        "evidence": { "type": "string", "minLength": 1 },
+        "reasonCode": { "type": "string", "pattern": "^[A-Z0-9_]+$" }
+      }
     }
   }
 }

package/schemas/corrective-decision-event.schema.json

@@ -22,7 +22,7 @@
     "eventId": { "type": "string", "minLength": 1 },
     "taskId": { "$ref": "#/$defs/taskId" },
     "stepId": { "$ref": "#/$defs/stepId" },
-    "triggeringAttemptCount": { "type": "integer", "minimum": 3 },
+    "triggeringAttemptCount": { "type": "integer", "minimum": 2 },
     "decision": {
       "enum": ["continue-fix", "replan-required", "split-required", "stop-escalate"]
     },
@@ -38,18 +38,63 @@
       "items": { "type": "string", "minLength": 1 }
     },
     "planHash": { "$ref": "#/$defs/hash64" },
+    "recoveryBasis": { "const": "plan-integrity" },
+    "planIntegrityEvidence": { "$ref": "#/$defs/planIntegrityEvidence" },
     "previousEventHash": { "$ref": "#/$defs/nullableHash64" },
     "recordedAt": { "type": "string", "format": "date-time" },
     "eventHash": { "$ref": "#/$defs/hash64" }
   },
-  "anyOf": [
+  "allOf": [
+    {
+      "if": { "properties": { "triggeringAttemptCount": { "const": 2 } }, "required": ["triggeringAttemptCount"] },
+      "then": {
+        "required": ["recoveryBasis", "planIntegrityEvidence"],
+        "properties": { "decision": { "const": "replan-required" } }
+      },
+      "else": {
+        "not": { "anyOf": [{ "required": ["recoveryBasis"] }, { "required": ["planIntegrityEvidence"] }] }
+      }
+    },
+    {
+      "anyOf": [
     { "properties": { "coveredFindingIds": { "minItems": 1 } } },
     { "properties": { "coveredEventIds": { "minItems": 1 } } }
+      ]
+    }
   ],
   "$defs": {
     "taskId": { "type": "string", "pattern": "^TASK-[0-9A-HJKMNP-TV-Z]{26}$" },
     "stepId": { "type": "string", "pattern": "^STEP-[0-9]{3}(?:-[A-Z0-9-]+)?$" },
     "hash64": { "type": "string", "pattern": "^[a-f0-9]{64}$" },
-    "nullableHash64": { "type": ["string", "null"], "pattern": "^[a-f0-9]{64}$" }
+    "nullableHash64": { "type": ["string", "null"], "pattern": "^[a-f0-9]{64}$" },
+    "gitOid": { "type": "string", "pattern": "^[a-f0-9]{40,64}$" },
+    "stringList": {
+      "type": "array",
+      "uniqueItems": true,
+      "items": { "type": "string", "minLength": 1 }
+    },
+    "planIntegrityEvidence": {
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "kind", "taskRevision", "remediationEventId", "remediationEventHash",
+        "manifestPath", "manifestHash", "gitHead", "stepDefinitionHash",
+        "missingScripts", "checkCommands", "changedFiles", "conflictHash"
+      ],
+      "properties": {
+        "kind": { "const": "missing-npm-script-outside-allowed-writes" },
+        "taskRevision": { "type": "integer", "minimum": 1 },
+        "remediationEventId": { "type": "string", "minLength": 1 },
+        "remediationEventHash": { "$ref": "#/$defs/hash64" },
+        "manifestPath": { "const": "package.json" },
+        "manifestHash": { "$ref": "#/$defs/nullableHash64" },
+        "gitHead": { "$ref": "#/$defs/gitOid" },
+        "stepDefinitionHash": { "$ref": "#/$defs/hash64" },
+        "missingScripts": { "$ref": "#/$defs/stringList", "minItems": 1 },
+        "checkCommands": { "$ref": "#/$defs/stringList", "minItems": 1 },
+        "changedFiles": { "$ref": "#/$defs/stringList" },
+        "conflictHash": { "$ref": "#/$defs/hash64" }
+      }
+    }
   }
 }

package/schemas/milestone-scope-change-event.schema.json

@@ -50,7 +50,12 @@
       "properties": {
         "taskId": { "$ref": "#/$defs/taskId" },
         "disposition": { "enum": ["required", "waived", "cancelled"] },
-        "reason": { "type": "string" }
+        "reason": { "type": "string" },
+        "dependsOnTaskIds": {
+          "type": "array",
+          "uniqueItems": true,
+          "items": { "$ref": "#/$defs/taskId" }
+        }
       }
     },
     "scopeSnapshot": {

package/schemas/milestone.schema.json

@@ -51,7 +51,12 @@
       "properties": {
         "taskId": { "$ref": "#/$defs/taskId" },
         "disposition": { "enum": ["required", "waived", "cancelled"] },
-        "reason": { "type": "string" }
+        "reason": { "type": "string" },
+        "dependsOnTaskIds": {
+          "type": "array",
+          "uniqueItems": true,
+          "items": { "$ref": "#/$defs/taskId" }
+        }
       }
     }
   }

package/schemas/task-handoff-event.schema.json

@@ -45,6 +45,12 @@
     "planHash": { "$ref": "#/$defs/nullableHash64" },
     "knowledgeMapRevision": { "type": ["integer", "null"], "minimum": 1 },
     "knowledgeMapHash": { "$ref": "#/$defs/nullableHash64" },
+    "dependencyBinding": {
+      "oneOf": [
+        { "type": "null" },
+        { "$ref": "#/$defs/dependencyBinding" }
+      ]
+    },
     "expectedNext": { "type": "string", "minLength": 1 },
     "delegate": { "type": "string", "minLength": 1 },
     "grantId": { "type": ["string", "null"], "minLength": 1 },
@@ -94,8 +100,18 @@
   "$defs": {
     "taskId": { "type": "string", "pattern": "^TASK-[0-9A-HJKMNP-TV-Z]{26}$" },
     "hash64": { "type": "string", "pattern": "^[a-f0-9]{64}$" },
-    "nullableHash64": { "type": ["string", "null"], "pattern": "^[a-f0-9]{64}$" }
-    ,"handback": {
+    "nullableHash64": { "type": ["string", "null"], "pattern": "^[a-f0-9]{64}$" },
+    "dependencyBinding": {
+      "type": "object",
+      "additionalProperties": false,
+      "required": ["milestoneRevision", "membershipRevision", "milestonePlanHash"],
+      "properties": {
+        "milestoneRevision": { "type": "integer", "minimum": 1 },
+        "membershipRevision": { "type": "integer", "minimum": 1 },
+        "milestonePlanHash": { "$ref": "#/$defs/hash64" }
+      }
+    },
+    "handback": {
       "type": "object",
       "additionalProperties": false,
       "required": ["status", "mergedCommit", "planHash", "resultHash", "evidenceHash", "reviewAttestationHash", "knowledgeMapRevision", "knowledgeMapHash", "limitations", "recommendedNext"],