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

package/docs/validation-report.md

@@ -1,97 +1,101 @@
-# V2 beta.12.3 Validation Report
+# V2 beta.12.5 Validation Report
 
-Release candidate `2.0.0-beta.12.3` was validated on 2026-08-28 (Europe/Moscow) with
+Release candidate `2.0.0-beta.12.5` was validated on 2026-08-29 (Europe/Moscow) with
 Node.js 24.17.0.
 
 ## Automated release evidence
 
-- `npm ci` completed from the committed lockfile with 0 reported vulnerabilities.
-- The final `npm run validate` passed typecheck and `326/326` sequential tests with no failures,
-  skips, cancellations, or todos in 1,360,950.996834 ms.
-- The suite includes the new beta.12.3 two-update stop-override replay, the beta.12.2 direct-rebind
-  replay, unchanged-Plan stop override, five-cycle continuable remediation, generic stale-decision
-  recovery, credential safety, dependency provenance, Signal T04, P01-A, P04-A, transaction,
-  observer-purity, and transition-model regressions.
-- `npm run pack:check` produced `codex-workflow-v2-2.0.0-beta.12.3.tgz` with 270 files,
-  package size 976.2 kB, unpacked size 3.9 MB, and SHA-1
-  `ceb2ef4c7b076b9ae01a09127d05b867d101bfb1`. The sandboxed npm-cache attempt failed with
-  `EPERM`; the authorized retry using the same source passed.
-- `npm run smoke:downstream` packed and installed the beta.12.3 tarball in an empty temporary
-  project and passed the packaged handshake. The sandboxed attempt could not resolve the npm
-  registry for AJV; the authorized network retry using the same source passed.
-- `npm run plugin:check`, the official Codex plugin validator, the gateway skill validator,
-  `npm run docs:pdf:check`, exact `RELEASE_TAG=v2.0.0-beta.12.3 npm run release:check`, and
-  `git diff --check` passed. The bundled gateway cachebuster is
-  `0.1.0+codex.20260827231109`.
+- 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 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`.
 
-## beta.12.3 chained compatibility transition
+## Root cause and bounded correction
 
-- beta.12.2 handled one direct Knowledge-only Plan rebind after an already applied beta.11
-  attempt-four stop override. It did not handle the second normal update/context-refresh cycle
-  created while installing beta.12.2 into Signal. That limitation caused the next blocker.
-- Core now accepts an arbitrary contiguous append-only chain from the override-bound Plan to the
-  current Plan only when every adjacent Plan differs solely by Knowledge Map binding and every
-  adjacent Plan Risk Audit is an exact mechanical rebound. Rebind endpoints, delegated authority,
-  active grants, and event chronology must align at every hop.
-- Git HEAD may advance across that chain only through registered dependency-provenance recovery
-  records. Every intervening commit must be a single-parent commit in the exact ancestor chain,
-  must be listed in Workflow system commits, must have exactly one matching Task recovery record,
-  and may change only `package.json` and `package-lock.json` for `codex-workflow-v2`.
-- Fresh `next` returns `task run` with validated stop-override context-rebind evidence only after
-  all of those checks pass. A lost writer credential still routes through the existing exact
-  claimant `task writer-credential-replace` recovery. The fourth and later attempts remain
-  corrective and use the normal strict-review cycle.
-- The route is append-only: it rewrites no stop, override, Plan, audit, authorization, dependency,
-  or recovery evidence. Semantic Plan drift, missing or forked history, product-file changes,
-  mismatched recovery metadata, stale delegation, malformed chronology, or sidecar corruption
-  fails closed and routes to diagnostics.
+- 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.
 
-## Exact Signal compatibility proof
+## Exact Signal read-only proof
 
-- A read-only invocation of the final built beta.12.3 validator inspected the current Workflow
-  state for Signal Task `TASK-01M0WXJAD4GZGVNRJ284ND95C6`, failed Step
-  `STEP-001-PROCESSING-MIGRATIONS`, and repository
-  `/Users/home-pc/htdocs/projects/signal_v4`.
-- The validator accepted Task revision 21, the applied stop override
-  `SOO-01M127VPRC5M5F3E3K7PS4MFJY`, three Knowledge rebinds in total, the two rebinds after the
-  stop boundary, and two registered dependency-provenance recovery records. The current Plan hash
-  was `8ab0b643cbdcb045776ede231262fdaf8bd0968c2c5fe8967142bfcb8171ae79` and the stable semantic
-  Plan hash was `b99a34ec86ad6340c1abd1b5e78e10c7996aa774ef58eeb9dacbcea72fd2698f`.
-- This proves that the exact state which beta.12.2 rejected is accepted by beta.12.3 without
-  changing Signal. It does not prove future product implementation or review success.
+- 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.
 
-## Packaged and transcript evidence
+## Sandbox-boundary prevention
 
-- Downstream smoke validated exact package resolution and the packaged beta.12.3 handshake in a
-  clean disposable installation.
-- A temporary trusted-harness transcript recorded the final built `gateway handshake` invocation
-  and its successful beta.12.3 result. `node scripts/validate-lifecycle-transcript.mjs` accepted
-  both post-provenance events. The log SHA-256 is
-  `7d65fd9fc6301205094284c1fd4236665dff1876d11e01bbc63e35e3a4e3c34b`; the temporary log remains
-  outside the repository.
+- 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.
 
-The transcript proves release-time invocation/result discipline for the final CLI. It does not
-claim a product Milestone replay or lifecycle mutation. Compatibility is covered by the exact
-Signal read-only proof and deterministic integration tests above.
+## beta.12.5 PDF release documentation evidence
 
-## beta.12.3 PDF release documentation evidence
-
-- Three tracked Russian PDFs were deterministically regenerated from reviewable Markdown sources
-  under `docs/pdf/sources`; `npm run docs:pdf:check` reported an empty stale set.
-- All 25 final pages were rendered and visually inspected: architecture is 7 pages, the delegated
-  chat-only guide is 8 pages, and the technical reference is 10 pages. No blank, clipped,
-  overlapping, or orphaned final page was found.
-- Visible titles, headers, package commands, and release gates identify beta.12.3. The documents
-  distinguish a direct rebind from the new chained compatibility route and state its fail-closed
-  dependency-provenance boundary.
+- 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.
 
 ## Existing boundaries and non-claims
 
-- The generic stale `continue-fix` recovery predicate is unchanged. The compatibility route does
-  not relax semantic stop reversal or authorize arbitrary Git history.
-- Structural replacement remains intentionally disabled. beta.12.3 does not implement P04-B,
+- Structural replacement remains intentionally disabled. beta.12.5 does not implement P04-B,
   topology rewiring, completed-Step adoption, or a wider delegation surface.
-- Validation performed no Signal mutation, npm publication, Git tag, remote push, or local plugin
-  reinstall. Tagging and push are separate release actions after these gates.
-- A consumer must install the published exact beta.12.3 package, update/reinstall the bundled
-  gateway, and use fresh project-local `handshake -> doctor -> status -> next` navigation.
+- 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.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "codex-workflow-v2",
-  "version": "2.0.0-beta.12.3",
+  "version": "2.0.0-beta.12.5",
   "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.20260827231109",
+  "version": "0.1.0+codex.20260828064343",
   "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.3 compatibility transitions and continuable remediation
+## beta.12.5 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
@@ -8,6 +8,13 @@
   It records a replan posture without changing Plan or product files; corrective yield and the
   existing state-bound corrective-replan Human gate remain mandatory.
 
+- When fresh `next` advertises `task downstream-proof-recover`, Core has proved that every dirty
+  file outside the active Step belongs to a completed transitive predecessor and that recorded Git
+  history is intact. Invoke the exact lease-bound transition once. It preserves product files and
+  HEAD, invalidates stale predecessor completion authority with an append-only event, yields C1,
+  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.
+
 - `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
@@ -27,6 +34,9 @@
   intervening commit is an exact registered dependency-provenance recovery changing only
   `package.json` and `package-lock.json`. If C1 remains claimed but the lease was lost at the Human
   boundary, use only the simultaneously advertised `task writer-credential-replace` action.
+  A provenance recovery recorded after the final context-refresh audit may explain exactly one
+  additional Task revision only when it belongs to that verified Git chain. Any unexplained
+  revision remains a `doctor` boundary.
 - `milestone progress --id <MS-ID>` is a read-only projection and the sole source for Coordinator
   progress tables. It preserves cancelled/replacement Tasks as distinct membership rows.
 - `scripts/chat-registry.mjs` atomically allocates project-monotonic `#NNN`, builds all six title
@@ -66,6 +76,7 @@ Current capability set:
 - `legacy-stop-escalate-override-v1`
 - `stop-override-context-rebind-v1`
 - `stop-override-context-rebind-chain-v1`
+- `stop-override-post-audit-dependency-revision-v1`
 - `retained-reviewed-history-recovery-v1`
 - `milestone-progress-projection-v1`
 - `strict-reviewer-v1`
@@ -96,6 +107,7 @@ Current capability set:
 - `remediation-mode-recovery-v1`
 - `plan-proof-obligations-v1`
 - `bounded-plan-integrity-recovery-v1`
+- `downstream-proof-predecessor-recovery-v1`
 - `corrective-yield-journal-v1`
 - `corrective-replan-journal-v1`
 - `corrective-replan-human-gate-v1`
@@ -171,6 +183,13 @@ actor through `--actor`; reviewer identity remains internal to the route.
 An unrecorded commit is Git history drift. Stop instead of adding another commit or editing
 workflow state manually; recovery remains coordinator-controlled.
 
+If a Docker proof fails with `EPERM`, `operation not permitted`, or `permission denied` at the
+Docker socket/CLI boundary, classify it as sandbox access, not daemon failure. Re-run the exact
+read-only health probe or Plan command once with sandbox escalation; do not charge an infrastructure
+retry. Restarting Docker Desktop or pulling another image is forbidden on this evidence alone. A
+Docker infrastructure failure exists only when an escalated call reaches Docker and independently
+proves the daemon unavailable.
+
 ## Plan Risk Audit and remediation breaker
 
 Before `task authorize`, every new alpha.7 Task requires:

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

@@ -67,6 +67,20 @@ active writer token when the C1 contract requires it. The recovery records only
 `task run` merely to manufacture the second failure, and never invoke this recovery for a generic
 test failure, a writable manifest, or unconfined changes.
 
+When fresh `next` advertises `task downstream-proof-recover`, the active proof Step has produced
+uncommitted files inside its own `allowedWrites` and has also exposed required changes owned by one
+or more completed transitive predecessor Steps. Do not invoke `task step-complete`: its scope is
+known to be stale. Use only the exact returned Task revision, claimant/lease actor, writer-token
+contract, and a substantive reason. The atomic recovery preserves the worktree and HEAD, moves the
+predecessor completion commits into historical `invalidatedStepCommits`, clears only the invalidated
+completion evidence, blocks the active proof Step, supersedes execution authorization, appends
+`downstream-proof-invalidations.jsonl`, releases C1/lease authority, and returns the same Task to
+ordinary `task plan-set`. Build the replacement Plan from the full unfinished remainder, attach a
+fresh Plan Risk Audit, then obtain fresh execution authorization. Never use this route for an
+unrelated dirty file, a non-predecessor file, unregistered Git history, strict-review evidence, or
+without explicit fresh `next` eligibility. Do not reset, stash, commit, or recreate the Task or
+Milestone around this transition.
+
 If any step fails, report the concrete diagnostic. Do not load workflow
 semantics from this skill.
 
@@ -109,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.3 `next` advertises `task stop-override-prepare`, the route is limited to the exact
+When beta.12.5 `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
@@ -130,6 +144,10 @@ commit as registered dependency-only provenance. If C1 remains claimed but the l
 the Human boundary, first use the simultaneously advertised `task writer-credential-replace`
 action for the exact claimant. A doctor route, semantic Plan drift, an unregistered or non-dependency
 commit, missing delegated authority, a broken chain, or damaged chronology is a hard stop.
+When advertised navigation records dependency provenance after the final context-refresh audit,
+Core may account for exactly one Task revision per ordered verified recovery. Never infer this
+compatibility from revision arithmetic alone: continue only when fresh `next` returns the validated
+`task run` route. An unrelated extra revision remains 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
@@ -151,6 +169,17 @@ For `task start`, the policy applies only when choosing `--workspace-owner local
 `task step-complete`, `task merge`, and `task sync-base`, the advertised transition itself
 writes Git metadata.
 
+Treat Docker access diagnostics before classifying an infrastructure failure. `EPERM`,
+`operation not permitted`, or `permission denied` while opening the Docker socket or invoking the
+Docker CLI from a sandbox means the proof is unavailable at the current execution boundary; it is
+not evidence that the daemon or image is broken. Re-run the exact read-only health probe or exact
+Plan check once with the required sandbox escalation. This escalation rerun does not consume a
+Workflow remediation attempt or a local infrastructure retry. Only an escalated probe that reaches
+Docker and reports an unavailable daemon may be classified as a Docker infrastructure failure.
+Never start, stop, or restart Docker Desktop, pull a substitute image, or mutate Docker state merely
+because the sandboxed call returned a permission error; those actions require their own explicit
+authorization and evidence.
+
 When `next` includes `writerTokenContract`, treat it as an exact first-call precondition. Retain
 the active writer lease from the first-field `writerLeaseReceipt` returned by `task run` and pass it using the advertised `option` for that
 transition. The token is sensitive: never print, summarize, persist, or substitute a redacted

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

@@ -0,0 +1,70 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "https://codex-workflow.local/schemas/downstream-proof-invalidation-event.schema.json",
+  "title": "Codex Workflow V2 Downstream Proof Invalidation Event",
+  "type": "object",
+  "additionalProperties": false,
+  "required": [
+    "eventId",
+    "taskId",
+    "previousTaskRevision",
+    "resultTaskRevision",
+    "planHash",
+    "activeStepId",
+    "invalidatedSteps",
+    "dirtyFiles",
+    "preservedHeadCommit",
+    "actor",
+    "reason",
+    "packageVersion",
+    "previousEventHash",
+    "recordedAt",
+    "eventHash"
+  ],
+  "properties": {
+    "eventId": { "type": "string", "pattern": "^DPI-[0-9A-HJKMNP-TV-Z]{26}$" },
+    "taskId": { "$ref": "#/$defs/taskId" },
+    "previousTaskRevision": { "type": "integer", "minimum": 1 },
+    "resultTaskRevision": { "type": "integer", "minimum": 2 },
+    "planHash": { "$ref": "#/$defs/hash64" },
+    "activeStepId": { "$ref": "#/$defs/stepId" },
+    "invalidatedSteps": {
+      "type": "array",
+      "minItems": 1,
+      "items": {
+        "type": "object",
+        "additionalProperties": false,
+        "required": ["stepId", "evidenceCommit", "triggerFiles"],
+        "properties": {
+          "stepId": { "$ref": "#/$defs/stepId" },
+          "evidenceCommit": { "$ref": "#/$defs/gitHash" },
+          "triggerFiles": {
+            "type": "array",
+            "uniqueItems": true,
+            "items": { "type": "string", "minLength": 1 }
+          }
+        }
+      }
+    },
+    "dirtyFiles": {
+      "type": "array",
+      "minItems": 1,
+      "uniqueItems": true,
+      "items": { "type": "string", "minLength": 1 }
+    },
+    "preservedHeadCommit": { "$ref": "#/$defs/gitHash" },
+    "actor": { "type": "string", "minLength": 1 },
+    "reason": { "type": "string", "minLength": 1 },
+    "packageVersion": { "type": "string", "minLength": 1 },
+    "previousEventHash": { "$ref": "#/$defs/nullableHash64" },
+    "recordedAt": { "type": "string", "format": "date-time" },
+    "eventHash": { "$ref": "#/$defs/hash64" }
+  },
+  "$defs": {
+    "taskId": { "type": "string", "pattern": "^TASK-[0-9A-HJKMNP-TV-Z]{26}$" },
+    "stepId": { "type": "string", "pattern": "^STEP-[0-9]{3}(?:-[A-Z0-9-]+)?$" },
+    "gitHash": { "type": "string", "pattern": "^[a-f0-9]{40}$" },
+    "hash64": { "type": "string", "pattern": "^[a-f0-9]{64}$" },
+    "nullableHash64": { "type": ["string", "null"], "pattern": "^[a-f0-9]{64}$" }
+  }
+}

package/schemas/task.schema.json

@@ -55,6 +55,11 @@
     },
     "replacementForTaskId": { "type": ["string", "null"], "pattern": "^TASK-[0-9A-HJKMNP-TV-Z]{26}$" },
     "replacedByTaskId": { "type": ["string", "null"], "pattern": "^TASK-[0-9A-HJKMNP-TV-Z]{26}$" },
+    "invalidatedStepCommits": {
+      "type": "array",
+      "uniqueItems": true,
+      "items": { "type": "string", "pattern": "^[a-f0-9]{40}$" }
+    },
     "dependencyProvenanceRecoveries": {
       "type": "array",
       "items": {