[jonahgabriel]

OMN-15472 — retire the unfalsifiable dod-deploy-assessment evidence item (append-only supersession)

Ticket: OMN-15472. This PR adds evidence only; it changes no product source, flips no Linear status, and deletes or rewrites nothing.

Finding (lane C2 adversarial verify of the OMN-15472 evidence chain)

OMN-15472's code legs are merged and independently verified — omnimarket #1990, squash 46e5364db360da5dbb72f382ddfea93488fc01fa. The evidence chain was not clean.

contracts/OMN-15472.yaml item dod-deploy-assessment (landed on OCC bot companion #5758, merged 2026-07-31T20:44:33Z) runs:

gh pr diff 1990 --repo OmniNode-ai/omnimarket --name-only | grep -ciE 'nodes/|handlers/|runtime/|services/|docker|monitor_logs|deploy'

That greps PR #1990's own file list. #1990 is MERGED, so the list is immutable and permanently contains
src/omnimarket/nodes/node_projection_registration/handlers/handler_projection_registration.py — which matches both nodes/ and handlers/. The check therefore exits 0 unconditionally. No change to the product source, the deploy surface, or the runtime can ever drive it RED. It is unfalsifiable by construction — the OMN-14443 class — and a check that can never fail is not evidence of deploy scope; it is a green light wired to nothing.

OCC #5762 (merged 2026-07-31T21:13:54Z) neutralised this additively by adding dod-deploy-source-probe, but did not retire the vacuous item. It stayed live and eligible to be read as passing evidence. This PR retires it.

Change — one appended item

contracts/OMN-15472.yaml gains exactly one new dod_evidence entry, dod-deploy-assessment-falsifiable, carrying:

evidence_artifact: "supersedes_dod_evidence:dod-deploy-assessment"

Idiom and precedent: append-only supersession, per EvidenceCollector._resolve_supersessions (shipped under OMN-15382 / OMN-15390) — the superseded item resolves to status=superseded at dod_verify runtime and stays verbatim in the file for audit. Direct precedent: lane B3's OCC #5760, which superseded dod-omn15535-pr-239-merged-at-4bae73ea on contracts/OMN-15535.yaml the same way. Append-only is not stylistic here: a merged dod_evidence entry is immutable and its receipt pins the entry hash, so an in-place rewrite is rejected by validator_occ_append_only and would invalidate the receipt binding.

Replacement semantics (falsifiable)

Immutable-ref content probe of the deploy-relevant source at PR #1990's squash merge commit 46e5364d, asserting the OMN-15472 fix symbol _preserve_service_url is present both as a definition and at the registration create-path call site the fix exists to protect:

gh api 'repos/OmniNode-ai/omnimarket/contents/src/.../handler_projection_registration.py?ref=46e5364d...' --jq .content \
  | base64 -d | grep -F 'def _preserve_service_url(existing: object) -> str:' > /dev/null \
&& gh api '...same ref...' --jq .content \
  | base64 -d | grep -F '"service_url": _preserve_service_url(base.get("service_url")),' > /dev/null

dod_evidence — proven, not asserted (executed on .200, stickybeatz-studio)

Leg	What ran	Result
GREEN	check_value verbatim under bash -euo pipefail	rc=0
GREEN	check_value verbatim under plain bash -c (no pipefail)	rc=0
RED	same probe repointed at #1990's first parent 8e27c27ab810d06386511cfada0c5b167ef445ca	rc=1
RED	same probe against a path lacking the symbol (README.md)	rc=1
Parse	yaml.safe_load(contracts/OMN-15472.yaml)	OK, 7 items
Shape	shlex.split(check_value)[0]	'gh'
Shape	'$(' in check_value	False
Gates	uv run pre-commit run --files contracts/OMN-15472.yaml	every applicable hook Passed

Falsifiability is demonstrated, not claimed — which is the entire point of the item being replaced.

Executor-shape notes

• The first shlex token is gh, a resolvable executable, and the command contains zero command substitution. node_dod_verify shape-guards a check_value before executing it by tokenizing with shlex.split, which is not $()-aware; this shape cannot mis-branch on it. (OMN-15597 caution; the OMN-15535 INVALID_CHECK_VALUE_NOT_A_COMMAND false-RED class.)
• Both legs terminate in grep -F ... > /dev/null on fully drained input — avoiding both the grep -q SIGPIPE exit-141 hazard and the grep -c | grep -qx N counting idiom that fails in both polarities under pipefail.

Authorship separation

Authored by session fable-ws0-0731/laneC3, which did not implement the OMN-15472 code legs. Implementer and evidence-author are separate for this item. A separate audit-trail disclosure is posted on #5758 and #5762 recording that #5762's author identity is not resolvable to human-vs-agent from GitHub metadata.

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 31 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: d7e71fef-c088-467b-a6a7-fa557864c542

📥 Commits

Reviewing files that changed from the base of the PR and between 3e022b2 and 5138f38.

📒 Files selected for processing (5)

• contracts/OMN-14443.yaml
• contracts/OMN-15472.yaml
• drift/dod_receipts/OMN-14443/occ-self-bind-pr-5768/command.yaml
• drift/dod_receipts/OMN-15472/dod-deploy-assessment-falsifiable/command.yaml
• drift/dod_receipts/OMN-15472/occ-self-bind-pr-5768/command.yaml

---

_{Comment @coderabbitai help to get the list of available commands.}