fix(OMN-19149): advance the Receipt Gate pin so the supersede-latch fix is in force

.github/workflows/call-receipt-gate.yml

@@ -24,4 +24,4 @@ permissions:
 
 jobs:
   verify:
-    uses: OmniNode-ai/omnibase_core/.github/workflows/receipt-gate.yml@a03b10720db364575b0477003da95b46de765950 # OMN-19149: immutable SHA pin, advanced from 76532c20 (0.47.19). Provenance: the squash commit of omnibase_core#1736 on that repo's dev branch, which closes the OMN-19050 FAIL-supersede latch -- at 76532c20 the resolver's supersede-suffix pattern excludes a dot, so an attempt-scoped record is invisible to it rather than outranked, and omnimarket#2751 was blocked on a key whose merged companion already carried a PASS. NO PUBLISHED RELEASE CONTAINS THIS FIX: v0.47.20 is the latest, tagged 3afa3528 on 2026-09-20, and the fix merged 2026-09-21, so this pins the merge sha and should be re-pointed at the first release that carries it. Blast radius, measured: .github/workflows/receipt-gate.yml is BYTE-IDENTICAL across the move (blob cb0c2b547e34d664644b3faa08758ef44d245576 at both shas), so the gate's own shape does not change; the validation surface moves 18 files, and the two gate-relevant validators besides the resolver, validator_occ_append_only.py and validator_receipt_diff_consistency.py, both come from one commit, omnibase_core#1730 (OMN-18996). A 40-hex pin remains the intended long-term form here, not a placeholder for a branch ref: it is immutable, so the gate this repo runs cannot change under it without a reviewed edit to this line
+    uses: OmniNode-ai/omnibase_core/.github/workflows/receipt-gate.yml@9cc9f035465266442df542d345cde621c9c3b0d5 # OMN-19149: immutable SHA pin, advanced from a03b1072. Provenance: the squash commit of omnibase_core#1740 on that repo's dev branch. a03b1072 was the right VALIDATOR but the wrong thing to pin here: this line selects which copy of receipt-gate.yml runs, and that file carries a SECOND, separate hardcoded ref supplying the validator SOURCE, which at a03b1072 still read 37bd8519 (2026-08-24). Advancing this line alone was therefore inert -- proven live on omnimarket#2751, whose gate log shows it checking out omnibase_core at 37bd8519 after this pin had already been moved. omnibase_core#1740 advances that inner ref to a03b1072, so 9cc9f035 is the first sha at which the OMN-19050 supersede-latch fix is actually in force on this repository's gate. At 37bd8519 the supersede-suffix pattern excludes a dot, so an attempt-scoped record is invisible to the resolver rather than outranked. NO PUBLISHED RELEASE CONTAINS THIS: re-point at the first release that carries omnibase_core#1740. A 40-hex pin remains the intended long-term form here, not a placeholder for a branch ref: it is immutable, so the gate this repo runs cannot change under it without a reviewed edit to this line