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

package/docs/validation-report.md

@@ -1,101 +1,110 @@
-# V2 beta.12.5 Validation Report
+# V2 beta.12.7 Validation Report
 
-Release candidate `2.0.0-beta.12.5` was validated on 2026-08-29 (Europe/Moscow) with
+Release candidate `2.0.0-beta.12.7` was validated on 2026-08-29 (Europe/Moscow) with
 Node.js 24.17.0.
 
 ## Automated release evidence
 
-- The pre-install `npm run validate` passed typecheck and `332/332` sequential tests with no
-  failures, skips, cancellations, or todos in 1,313,147.293583 ms.
-- `npm ci` then completed from the lockfile with 0 reported vulnerabilities. The clean-install
-  `npm run validate` independently passed the same `332/332` tests in 1,312,649.239333 ms.
-- A final credential-recovery review then added one mapping and one regression test for an eligible
-  claimed C1 recovery whose writer lease is absent. Post-change typecheck and the focused
-  downstream-proof, CLI-help, and lifecycle-model suite passed `15/15`; the final full
-  `npm run validate` passed `333/333` tests with no failures, skips, cancellations, or todos in
-  1,321,160.33825 ms.
-- The suite covers the beta.12.5 downstream-proof recovery, exact lifecycle inventory, C1 yield,
-  one-writer concurrency, transaction crash boundaries, tampered sidecars, unrelated dirty files,
-  ordinary active-Step completion, existing Signal T04 recovery, dependency DAG, observer purity,
-  credential secrecy, corrective replay, and Milestone validation/acceptance.
-- `npm run pack:check` built the exact beta.12.5 package: 274 files, 995.1 kB packed and 3.9 MB
-  unpacked. The first sandboxed attempt could not write the user npm cache (`EPERM`); the exact
-  authorized retry passed and included the new runtime module and public schema.
+- `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 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`, exact
-  `RELEASE_TAG=v2.0.0-beta.12.5 npm run release:check`, and `git diff --check` passed. The bundled
-  gateway cachebuster remains `0.1.0+codex.20260828064343`.
+- `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 cause and bounded correction
+## Root causes corrected by beta.12.7
 
-- A downstream executable proof can demonstrate that a completed predecessor Step must change.
-  The existing navigation still advertised `task step-complete`, but that command correctly
-  rejected predecessor-owned dirty files. Repeating the command or increasing remediation attempts
-  could not solve the authority contradiction: predecessor completion evidence remained canonical
-  while the proof required changing its output.
-- beta.12.5 adds `task downstream-proof-recover`. It is advertised only when every dirty file
-  outside the active Step belongs to a completed transitive predecessor, Task branch/Plan/history
-  bindings are exact, the active Step has no completion evidence, and the Task uses a local
-  workspace. Unrelated files, damaged history, a branch mismatch, a malformed audit journal, or an
-  unregistered commit fail closed to `doctor`.
-- One crash-recoverable project transaction preserves worktree bytes and HEAD, append-only records
-  `downstream-proof-invalidations.jsonl`, moves invalidated product commits to historical
-  `invalidatedStepCommits`, clears stale Step/review/execution authority, yields claimed C1, removes
-  the writer lease, and returns the same Task to ordinary `task plan-set`.
-- No completed-Step adoption or synthetic replacement Task is performed. The replacement Plan must
-  re-cover the unfinished proof and invalidated predecessor work, then pass normal audit,
-  authorization, execution, and review again.
+- 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 read-only proof
+## Exact Signal project evidence
 
-- The final built beta.12.5 classifier inspected Signal repository
-  `/Users/home-pc/htdocs/projects/signal_v4`, project
-  `b06d0f18f790f4521a23c770`, and Task
-  `TASK-01M0WXJAD4GZGVNRJ284ND95C6` without mutating repository or Workflow state.
-- Persisted Task revision is 103 on branch
-  `codex/task-01m0wxjad4-processing-persistence-schema`; active Step is
-  `STEP-002-REAL-POSTGRES-PROOF`. HEAD is
-  `88f8bf70d1591852ad90c976625430d4f20585ac`.
-- The classifier observed six dirty files. Five are outside the active Step and are owned by the
-  completed transitive predecessor `STEP-001-PROCESSING-MIGRATIONS`; the sixth,
-  `tools/postgres/run-processing-integration.ts`, belongs to the active proof Step. The predecessor
-  evidence commit equals the preserved HEAD.
-- The result was `applicable=true`, `eligible=true`, with no blockers. This proves that the exact
-  current Signal boundary has a bounded beta.12.5 transition. It does not prove that the replacement
-  Plan, product checks, strict review, or the remainder of Milestone 3 will pass.
+- 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.
 
-## Sandbox-boundary prevention
+## PDF release documentation evidence
 
-- The bundled gateway now classifies Docker socket/CLI `EPERM`, `operation not permitted`, and
-  `permission denied` from a sandbox as an execution-boundary failure, not evidence that the daemon,
-  image, or product infrastructure is broken.
-- It permits one exact escalated read-only probe or Plan check without consuming a remediation or
-  infrastructure retry. Docker Desktop restart, daemon mutation, or image substitution still
-  requires separate authority and an actual escalated daemon failure.
-- Plugin validation pins this guidance. The release gates exercised analogous npm cache/network
-  sandbox boundaries, but no live Docker daemon failure was synthesized; Docker runtime behavior is
-  therefore documentation/gateway-contract evidence, not an end-to-end Docker test claim.
-
-## beta.12.5 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, the delegated
-  chat-only guide is 9 pages, and the technical reference is 11 pages. The changed recovery,
-  Docker-boundary, command-surface, and release pages have no visible clipping, overlap, or
-  unreadable content.
-- Visible titles, headers, commands, capabilities, and release gates identify beta.12.5.
+- 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.
 
 ## Existing boundaries and non-claims
 
-- Structural replacement remains intentionally disabled. beta.12.5 does not implement P04-B,
+- Structural replacement remains intentionally disabled. beta.12.7 does not implement P04-B,
   topology rewiring, completed-Step adoption, or a wider delegation surface.
-- Recovery requires exact one-writer/C1 authority and a fresh `next`; it does not authorize manual
-  state edits, arbitrary Git history, unrelated dirty files, or automatic approval.
-- Validation performed no Signal mutation, npm publication, Git commit, tag, remote push, or local
-  plugin reinstall. Those remain separate release actions.
-- A consumer must install the published exact beta.12.5 package, reinstall the bundled gateway, and
-  follow fresh project-local `handshake -> doctor -> status -> next` navigation before invoking the
-  advertised recovery.
+- 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.
+- 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.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "codex-workflow-v2",
-  "version": "2.0.0-beta.12.5",
+  "version": "2.0.0-beta.12.7",
   "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.20260828064343",
+  "version": "0.1.0+codex.20260829143747",
   "description": "Thin personal Codex gateway for exact project-local Codex Workflow V2 packages and codebase-memory-mcp.",
   "author": {
     "name": "Codex Workflow Maintainers"

package/plugins/codex-workflow-gateway/references/protocol.md

@@ -1,6 +1,6 @@
 # Gateway Protocol V2
 
-## beta.12.5 compatibility transitions and continuable remediation
+## beta.12.6 compatibility transitions and continuable remediation
 
 - When fresh `next` advertises `task plan-integrity-recover`, consume its exact Task revision,
   Step, actor, and writer-token contract. This route is valid only for the Core-derived
@@ -15,6 +15,16 @@
   and routes the same Task to ordinary `task plan-set`. The replacement Plan, risk audit, and
   execution authorization are fresh authority; no Task or Milestone recreation is involved.
 
+- When an older installed package cannot reach that recovery because its normal update preflight
+  requires a clean checkout, beta.12.6 permits one bounded dependency transport. The active
+  Milestone base and Task branch must first receive separate exact commits changing only
+  `package.json` and `package-lock.json`; product work remains dirty and uncommitted. Fresh beta.12.6
+  `next` must then advertise `update downstream-proof-dependency-recover`. Its preflight proves the
+  Task history at `HEAD^`, the dependency candidate at `HEAD`, aligned version surfaces, no lease or
+  transaction, exact predecessor ownership, and a content hash of the dirty set. Recovery registers
+  only the dependency commit. It does not mutate product files or Step state; fresh `next` must
+  proceed to `task downstream-proof-recover`, which outranks manifest-induced Knowledge staleness.
+
 - `update dependency-provenance-preflight --id <TASK-ID>` is read-only. The matching
   `update dependency-provenance-recover --id <TASK-ID> --expected-revision <N> --actor <ACTOR>
   --reason <TEXT>` is valid only when preflight and fresh `next` both advertise it. Historical
@@ -108,6 +118,7 @@ Current capability set:
 - `plan-proof-obligations-v1`
 - `bounded-plan-integrity-recovery-v1`
 - `downstream-proof-predecessor-recovery-v1`
+- `active-downstream-proof-dependency-recovery-v1`
 - `corrective-yield-journal-v1`
 - `corrective-replan-journal-v1`
 - `corrective-replan-human-gate-v1`

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

@@ -123,7 +123,7 @@ command shape or consuming a replacement Discovery. Never rebind, refresh, repla
 resume, cancel, or manually replace the historical Task. Continue only after a later P04-B/P05
 package explicitly advertises a topology-preserving replacement capability.
 
-When beta.12.5 `next` advertises `task stop-override-prepare`, the route is limited to the exact
+When beta.12.6 `next` advertises `task stop-override-prepare`, the route is limited to the exact
 beta.11 attempt-four policy stop: two ordinary failures, one corrective failure, a matching
 attempt-3 `continue-fix`, and a matching attempt-4 `stop-escalate` under the unchanged Plan. Invoke
 prepare with the exact Task/Step/revision, explicit human actor, and user-supplied reason. It is
@@ -149,6 +149,38 @@ Core may account for exactly one Task revision per ordered verified recovery. Ne
 compatibility from revision arithmetic alone: continue only when fresh `next` returns the validated
 `task run` route. An unrelated extra revision remains a hard stop.
 
+For the exact beta.12.6 active-downstream-proof update deadlock, do not apply the ordinary
+clean-boundary update recipe and do not stash/reset/commit product work. This exception is available
+only when a completed transitive predecessor and the active proof Step already own the complete dirty
+set, no writer lease/transaction/Core operation exists, and the active Milestone base can be updated
+in a separate worktree. Commit only exact `package.json`/`package-lock.json` dependency changes on
+that base, then commit only the same dependency files on the current Task branch while leaving all
+product bytes untouched. Install the exact beta.12.6 package and use only a fresh advertised
+`update downstream-proof-dependency-recover`. Run its read-only preflight first and require
+`eligible=true`, empty blockers, exact Task revision and non-null `activeDownstreamProof` binding.
+Require recorded Task history to validate at `HEAD^` and the exact dependency-only candidate to be
+`HEAD`; neither boundary may contain an unrelated or unregistered commit. The mutation registers
+only the dependency HEAD. Immediately run sequential `status` then `next`;
+continue only to the returned `task downstream-proof-recover` (including advertised writer-credential
+recovery when required). Any unrelated dirty path, unknown history, wider candidate commit, stale
+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

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

@@ -78,6 +78,62 @@
             "type": "array",
             "uniqueItems": true,
             "items": { "type": "string", "pattern": "^[a-f0-9]{40}$" }
+          },
+          "activeDownstreamProof": {
+            "type": "object",
+            "required": ["activeStepId", "planHash", "dirtyFiles", "dirtyWorktreeHash", "invalidatedStepIds"],
+            "properties": {
+              "activeStepId": { "type": "string", "pattern": "^STEP-[A-Z0-9][A-Z0-9-]{2,63}$" },
+              "planHash": { "type": "string", "pattern": "^[a-f0-9]{64}$" },
+              "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
+          },
+          "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

package/scripts/generate-pdf-docs.py

@@ -200,6 +200,14 @@ def styles() -> dict[str, ParagraphStyle]:
             leading=10.3,
             textColor=TEXT,
         ),
+        "table_header": ParagraphStyle(
+            "TableHeader",
+            parent=base["BodyText"],
+            fontName="WorkflowBold",
+            fontSize=7.7,
+            leading=10.3,
+            textColor=colors.white,
+        ),
         "code": ParagraphStyle(
             "Code",
             parent=base["BodyText"],
@@ -316,8 +324,11 @@ def markdown_story(lines: list[str], style: dict[str, ParagraphStyle]) -> list:
             column_count = max(len(row) for row in rows)
             normalized = [row + [""] * (column_count - len(row)) for row in rows]
             rendered = [
-                [Paragraph(inline_markup(cell), style["small"]) for cell in row]
-                for row in normalized
+                [
+                    Paragraph(inline_markup(cell), style["table_header"] if row_index == 0 else style["small"])
+                    for cell in row
+                ]
+                for row_index, row in enumerate(normalized)
             ]
             table = LongTable(rendered, colWidths=table_widths(column_count), repeatRows=1)
             table.setStyle(TableStyle([