Skip to content

chore(OMN-17292): advance omnimarket contract pin to baf3d7880cdc - #4652

Closed
onexbot-occ-writer[bot] wants to merge 1 commit into
devfrom
bot/omnimarket-contract-pin-20261007011220
Closed

onexbot-occ-writer[bot] wants to merge 1 commit into
devfrom
bot/omnimarket-contract-pin-20261007011220

Conversation

@onexbot-occ-writer

Copy link
Copy Markdown
Contributor

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

Advances .github/omnimarket-contract-pin.yaml from bd0002cc5ed2d10435e3294dce7d5adeb0e54b86 to baf3d7880cdc6913663d0809c26fc8f9158e9701, 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

@onexbot-occ-writer

Copy link
Copy Markdown
Contributor Author

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

Copy link
Copy Markdown
Collaborator

Closing as superseded by omnibase_infra#4666, which advances .github/omnimarket-contract-pin.yaml to omnimarket e565ba5ba00c, a descendant of baf3d7880cdc (the target of #4652 from bd0002cc5ed2).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant