[onexbot-occ-writer]

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

Advances .github/omnimarket-contract-pin.yaml from 87afb9c332151d1ef6fbb955ea71d62a1ab79b3b to f36822c59b48d8a36114891223f1041391b6ef82 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

[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.

[jonahgabriel]

Manual merge sweep claim: closing as superseded. This PR advances .github/omnimarket-contract-pin.yaml only to f36822c59b48, while #3405 has now merged the same OMN-17292 pin surface forward to 1f98554bb591. Keeping this open would reintroduce an older contract pin.

[onexbot-occ-writer]

No OCC evidence companion was minted for this PR.

product PR state is 'closed' and it did not merge — no companion is authored for a dead target (F-17, occ#4333)

Matched in the state: closed

To clear this: Nothing to do. If this PR is reopened and merged, re-trigger the born path and the companion mints normally.

Reported by node_occ_companion_effect (decline code pr_closed_unmerged, OMN-16665). This decision was made against the PR's LIVE state at compute time, not at publish time — a green publisher job only means the command reached the broker.