[Patel230]

Unblocks omnibase_infra#3356, which fails occ-preflight with:

reason: pr_ticket_mismatch
detail: no PASS receipt for one or more tickets binds to PR #3356
        or one of its commit SHAs: OMN-18048

Every receipt OMN-18048 has on dev carries pr_number: 3351, so nothing binds to the follow-up PR.

Corrected premise

OCC#8774 is not the companion that unblocks #3356. Its supersession receipts also carry pr_number: 3351, so merging it would not clear this — the two PRs are sequential in ticket only, not in gate dependency. I had recorded the opposite and parked #3356 behind #8774; that was wrong, and this PR is the consequence of correcting it.

What this adds

Two second-consumer supersessions — the OMN-14623 merged-path pattern — neither editing a merged base receipt:

item	replacement reads	result
dod-omn-18048-qualifier-and-emphasis	the same handler file the base entry reads, at #3356's head, for _TRAILING_EMPHASIS_RE	2
dod-omn-18048-red-first-module-exists	the same PR-files surface the base entry reads, for #3356 rather than #3351	1

Both anchor to their superseded item's own declared artifact family (S2), and their check_values differ from one another (S1).

The first check is RED-derivable, and I proved it rather than asserting it

_TRAILING_EMPHASIS_RE is the marker introduced by #3356's MAJOR hostile-review fix:

at #3356 head 65a53a15e : 2   exit 0
at #3351 head 546d66164 : 0   exit 1

So it discriminates this PR from its predecessor rather than passing for both. That is the difference between evidence and a surrogate, and it is the property pr_state_surrogate findings exist to enforce.

Deliberately not included

• No .supersede.3356.yaml for dod-omn-18048-behavior-proof. That item is contested on OCC#8774 with an open S2 violation; adding a second supersession against it while that is unresolved would tangle two independent problems.
• No contract edit. The merged entries are untouched — git diff against the merge base is 2 files, 89 insertions, 0 deletions.
• Receipt hardening, yamlfmt contamination, dod-authoring and substance-floor all pass.

Ticket: OMN-18048

[Patel230]

Thank you for the merge.

Confirming the chain closed, by content rather than by the merge notice:

• drift/dod_receipts/OMN-18048/occ-self-bind-pr-8783/command.yaml — on origin/dev
• drift/dod_receipts/OMN-18048/dod-omn-18048-qualifier-and-emphasis/command.supersede.3356.yaml — on origin/dev
• control: occ-self-bind-pr-8774/command.yaml still present, so the query distinguishes rather than blanket-passing

omnibase_infra#3356 has picked it up and its CI Summary is re-running now. pr_ticket_mismatch was the single cause of all five of its reds, so this should clear them together — I will report what actually happens rather than predict it.

That matters beyond the two PRs: dev has been carrying both hostile-review defects since #3351 merged at 08:20:45Z — _TRAILING_EMPHASIS_RE and _AC_HEADING_PHRASES are still absent from origin/dev. #3356 is what removes them.

Two things this PR left behind that are worth having on the record.

The remediation text that sent #8774 into an append-only violation is filed as OMN-18082. It tells you to recompute contract_sha256 on existing receipts; against merged receipts that is the violation. It is unnecessary too — _contract_hash_violation (scripts/validation/check_receipt_hardening.py:1486) validates contract_entry_sha256 and returns before the whole-file comparison is ever reached.

Your merge proved that, on a receipt I did not author. After it, the contract's whole-file hash is a8e3cc99, while occ-self-bind-pr-8774/command.yaml still carries contract_sha256: 182b3c68 — stale — and validates anyway, because its per-entry hash 08bb20cc still matches. That is better evidence for OMN-13888 than anything I could have written myself.

Also flagged separately on OMN-18048 (5fe2a2d7): the gap_ac_unbound hold's remediation has the same shape — "add binds_ac to the dod_evidence item" is not applicable when every such item is merged. Measured: adding it moved an entry hash 8a232746 → fbeb2619 and took the hardening gate to exit 1. I built net-new binding entries instead, in #8794, which is the shape ci.yml:1446 prescribes and the one OMN-18062 already uses.