[onexbot-occ-writer]

Summary

Append-only successor for OMN-19978's evidence item dod-occ-diff-derived-behavior-proof-pr-4301. The last evidence sweep (2026-10-05T16:49Z) failed that item: it runs four pytest files that need Postgres (initdb), a git checkout and .proof-dependencies, which the closer host lacks, and it pins no commit. The new item proves what omnibase_infra#4301 delivered without Postgres and pinned to its merge commit.

What changed

• contracts/OMN-19978.yaml: one appended item, dod-omn19978-pr4301-proof-no-postgres, source manual, evidence_artifact: supersedes_dod_evidence:dod-occ-diff-derived-behavior-proof-pr-4301. Like the item it replaces, it binds no AC. Every existing item is byte-identical (61 insertions, 0 deletions over two files).
• The check is a pinned gh api command that needs no database and no checkout. It asserts that:
  • at omnibase_infra 6b97547573 (evidence(OMN-14696): OCC Evidence-Source autobind for OmniNode-ai/omnibase_infra#2321 #4301's merge), the two vendored node_projection_usage_by_model_day migrations (0000_create…, 0001_grant…) hash to the sha256 values the shipped vendor test pins;
  • both hashes equal the omnimarket source files at 02acdb34b9 (omnimarket#3073's merge), the byte-identity evidence(OMN-14696): OCC Evidence-Source autobind for OmniNode-ai/omnibase_infra#2321 #4301 promised;
  • application-migrations.tsv at 6b97547573 carries both tenant rows with those hashes.
• drift/dod_receipts/OMN-19978/dod-omn19978-pr4301-proof-no-postgres/command.yaml: the captured receipt (verifier occ-probe-capture-v1).

How it was verified

• Captured with check_receipt_hardening.py --capture-probe --red-ref 0607e9c383d03d7765bf74c9a17da111b8a70722 (the merge's parent): {"green_exit":0,"red_exit":1}. At the parent the vendored files answer HTTP 404, so the probe exits 1.
• Mutation: changing one digit of a pinned hash makes the probe exit 1.
• OCC pre-commit with GITHUB_BASE_REF=dev passes in full, including check_value lint, Receipt Honesty and Receipt Hardening. The commit is signed.

Failure paths

• No answer: if gh api can't reach GitHub, the command exits non-zero, so the item fails rather than passing.
• Incomplete verdict: a missing file, a hash mismatch or a missing ledger row each exit non-zero.
• Size: n/a. The output is one short JSON line.

Open defects

none

Local gates

• No gate was bypassed — no --no-verify, no SKIP=, no --no-gpg-sign, no core.hooksPath override. Every pre-commit and pre-push hook ran.
• Any hook that failed was fixed at the input, not worked around.

Not in this change

• It doesn't re-run evidence(OMN-14696): OCC Evidence-Source autobind for OmniNode-ai/omnibase_infra#2321 #4301's four pytest files. The new item is a content and hash proof of what evidence(OMN-14696): OCC Evidence-Source autobind for OmniNode-ai/omnibase_infra#2321 #4301 vendored, which is what lets it run without Postgres.
• OMN-19978's AC2 (the Usage page figures) still waits on OMN-20006 (omnimarket#3378).
• The sweep host needs gh authenticated, sha256sum and grep -F. The receipt was captured on the lakshman lane's laptop.

Evidence-Ticket: OMN-19978

[Patel230]

Close-out for OMN-19978: merged 2026-10-06 as cd20247f49.

• Landed: a Postgres-free proof of what omnibase_infra#4301 vendored, pinned to its merge.
• Found after merge: the closer refused the item (INVALID_CHECK_VALUE_NOT_A_COMMAND), because its check_value opens with a shell function, R().
• Successor: onex_change_control#13133 appends dod-omn19978-pr4301-proof-no-postgres-v2, the same proof behind a first token the closer resolves; its receipt passes the PROBE_CAPTURE gate, and a one-byte tamper fails it.

Thank you!