[onexbot-occ-writer]

Automated omnimarket contract-pin advance (OMN-17292).

Advances .github/omnimarket-contract-pin.yaml from f859c7af5e1d2a4df043bbb5d5e9d873a6c1c495 to e565ba5ba00c5a9201c9eb66c0259840960f4ea4, also moves the omnimarket entry of .github/sibling-pins.yaml and the inline workflow ref: shas that read it (OMN-20331), and regenerates the derived application-database TABLE grants and rendered catalogs in the same commit.

This PR is the surface upstream contract drift is supposed to land on. Before OMN-17292 this same drift appeared as a red required check on every open omnibase_infra PR simultaneously, with no action available to their authors (OMN-17141, OMN-16930, OMN-17290).

The advance was proven forward-only against real omnimarket history (scripts/ci/check_omnimarket_contract_pin_advance.py), so it cannot silently revert grants the way the stale pin in OMN-15701 did, and the regenerated output already passes --check --prove locally in the bot run.

Evidence-Ticket: OMN-17292

Evidence-Source: OCC#13170

[onexbot-occ-writer]

OCC autobind did not mint a companion for this PR: no changed-file candidate could be proven RED against the merge base, and emitting a PR-existence probe instead would be non-falsifiable evidence (OMN-15247). Hand-authored evidence is required.

Considered 13 changed file(s):

• .github/omnimarket-contract-pin.yaml: contract-pin file with no net-new omnimarket_contract_ref sha absent from the merge base, or the diff changes a path that is not the pin or an output derived from it
• .github/sibling-pins.yaml: no candidate grammar reads this file type (only Python declarations, uv.lock lines, release-artefact lines and contract-pin lines are proposed)
• .github/workflows/call-occ-autobind.yml: no candidate grammar reads this file type (only Python declarations, uv.lock lines, release-artefact lines and contract-pin lines are proposed)
• .github/workflows/call-occ-companion-effect.yml: no candidate grammar reads this file type (only Python declarations, uv.lock lines, release-artefact lines and contract-pin lines are proposed)
• .github/workflows/ci.yml: no candidate grammar reads this file type (only Python declarations, uv.lock lines, release-artefact lines and contract-pin lines are proposed)
• .github/workflows/contract-topic-graph.yml: no candidate grammar reads this file type (only Python declarations, uv.lock lines, release-artefact lines and contract-pin lines are proposed)
• .github/workflows/contractor-integration-note.yml: no candidate grammar reads this file type (only Python declarations, uv.lock lines, release-artefact lines and contract-pin lines are proposed)
• .github/workflows/delegation-consumer-kwarg-parity.yml: no candidate grammar reads this file type (only Python declarations, uv.lock lines, release-artefact lines and contract-pin lines are proposed)
• .github/workflows/dispatcher-route-coverage.yml: no candidate grammar reads this file type (only Python declarations, uv.lock lines, release-artefact lines and contract-pin lines are proposed)
• .github/workflows/exposure-reader-coverage.yml: no candidate grammar reads this file type (only Python declarations, uv.lock lines, release-artefact lines and contract-pin lines are proposed)
• .github/workflows/r1-front-door-probe.yml: no candidate grammar reads this file type (only Python declarations, uv.lock lines, release-artefact lines and contract-pin lines are proposed)
• .github/workflows/runtime-rebuild-trigger.yml: no candidate grammar reads this file type (only Python declarations, uv.lock lines, release-artefact lines and contract-pin lines are proposed)
• .github/workflows/skill-node-mapping-sync.yml: no candidate grammar reads this file type (only Python declarations, uv.lock lines, release-artefact lines and contract-pin lines are proposed)

This verdict is occ-autobind's, derived from this head and its merge base alone. A second producer, the occ-companion-effect backstop, consumes its own command on the lab bus and may still mint a companion under the generic binding. Whether it does depends on that consumer running, not on this diff (OMN-18876).

[jonahgabriel]

actor: fan-infra-botpins (sonnet)

Not pushed: three reds on head 9e780ac cannot be cleared from this branch.

1. exposure-reader-coverage fails for onex.snapshot.projection.delegation.correlation-trace.v1 (omnimarket node_projection_delegation): it is bus_backed: true with no reader and no consumers opt-out. It persists at omnimarket e565ba5ba00c and at omnimarket dev tip d2b0d9986ed7. Run locally against omnidash 8db004873e30, the gate clears metering-summary.v1 and usage-by-model-day.v1 but still fails on correlation-trace.v1. It needs a reader in omnidash or a consumers declaration in omnimarket, then a newer pin.
2. Application Database Domain Enforcement (OMN-15361) fails tests/ci/test_supplemental_declaration_expiry_omn18863.py::TestEachEntryExpiresWhenThePinDeclaresIt::test_no_interim_entry_is_redundant: the pinned contracts now declare delegation_budget_applied_events and delegation_routing_feedback, so their LEGACY_MIGRATION_TABLE_DECLARATIONS entries in src/omnibase_infra/topology/table_grant_derivation.py and the _INTERIM_ENTRIES keys in that test must be deleted. That fix belongs on this branch but would not turn the PR green while item 1 stands.
3. The change-control companion OCC#13170 is still OPEN, so OCC Companion Merged Gate (OMN-15214), occ-preflight / eligibility, call-reject-skip-token / occ-preflight / eligibility, Hostile Review Gate, verify / verify and CI Summary stay red until it merges.

#4652 and #4660 were closed as superseded by this PR.

[jonahgabriel]

This PR is closed as superseded by #4677, which advances the omnimarket contract pin to d2b0d9986ed7, a descendant of this PR's e565ba5ba00c.