[onexbot-occ-writer]

Deterministic OCC evidence companion for OmniNode-ai/omninode_infra#795, authored by node_occ_companion_effect (RSD-3, OMN-14622) from the node_occ_companion_compute plan. Every byte is a pure function of the compute plan (attestation-oracle reproducible).

[jonahgabriel]

Forensic record — this companion merged, but only after a hand-repair, and its probes are still vacuous

Posting this because #5889 merged (dd8002664) and therefore stops looking like the incident it was.
It was hard-red on the second-companion autogen regression before being hand-repaired. Trigger
is falsifiable and worth keeping: the regression fires on the 2nd autobind companion per ticket,
never the 1st — OMN-15637 already had OCC#5880 merged 27 minutes earlier.

Gate	Failure as originally minted	Job	Producer bug
OCC Append-Only Gate	mutated the merged receipt drift/dod_receipts/OMN-15637/dod-occ-evidence-admissibility-validator/command.yaml (M, 7+/7−), landed by OCC#5880. Merged receipts are immutable.	91420368934	OMN-15485
Supersession Binding Ratchet (OMN-15459)	minted three command.supersede.795.yaml records over three DISTINCT evidence items, all sharing one generic gh pr view 795 … replacement.check_value — S1 (distinctness) + S2 (family binding) violated on all three	91420369014 / 91420414597	OMN-15477

Both were cleared by hand-stripping the three .supersede.795.yaml files and reverting the
merged-receipt edit (9d9828998), after which the diff became append-only and merged.

The defect that was NOT cleared

The evidence this PR landed for omninode_infra#795 does not bind anything:

gh pr view 795 --repo OmniNode-ai/omninode_infra --json number,state
gh pr view 795 --repo OmniNode-ai/omninode_infra --json files

That is the OMN-14443 vacuous class — both pass whenever the PR merely exists, regardless of head
OID, base branch, or the outcome being claimed. occ-self-bind-pr-5889 carries the same shape (as
does the earlier occ-self-bind-pr-5880). #795 is the PR that repins the onex-dev runtime + migrate
images across 29 merged-but-undeployed commits, and nothing in the merged evidence ties OMN-15637
to that tree.

Two further internal inconsistencies in the merged receipts, for the producer-bug record: the contract
check_value for dod-OmniNode-ai-omninode_infra-pr-795 is --json number,state while its receipt's
check_value is --json number,state,headRefName; and occ-self-bind-pr-5889's probe_command
(--json number,state) differs from its own check_value (--json number,state,headRefName).

Replacement / upgrade

OCC#5894 (branch jonah/omn-15637-occ-companion-pr795) was authored off dev as a clean-branch
replacement while this PR was red, and is retained as a strictly additive upgrade now that this
one merged. It appends — zero deletions, no merged receipt edited, no supersession record — a real
head binding:

bind="$(gh pr view 795 --repo OmniNode-ai/omninode_infra --json headRefOid,baseRefName --jq '.headRefOid + " " + .baseRefName')" && test "$bind" = "e5a1929b7dc11dd7da8575d224286f04b3894dbb dev"

plus a compound number + headRefName self-bind. Per OMN-15459 doctrine the repair primitive is a
stronger net-new sibling, never a rewrite.

Authored by session fable-drain-0801's OPUS repair lane, which did not implement #795.