Repository navigation
evidence(OMN-12243): bind core guard receipt to PR - #1724
Conversation
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (6)
📝 WalkthroughWalkthroughThis PR extends the OMN-12243 contract with a new main-target-guard workflow evidence entry and creates a corresponding evidence receipt file. The contract hash update triggers refreshes of the contract_sha256 values across four existing evidence files to maintain referential integrity. ChangesContract Evidence and Hash Update
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Possibly related PRs
Poem
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
…rving checks pinned to head SHA Unblocks omnimarket#1724, whose occ-preflight fails with reason=missing_contract (cascading into OCC Preflight Dependency + 4 gates that then refuse to start). Both substantive check_values are CONTENT READS pinned to #1724's head SHA (dbfc5d6bc72b0bddd83c3d6313ac03fff6165d28). They observe the product source, not this receipt corpus. A CI-outcome check would be circular: #1724's CI is red BECAUSE this contract is missing. RED direction proven by execution for both checks: emitter compute_contract_entry_sha256 #1724 -> exit 0 | dev -> exit 1 | bogus SHA -> exit 1 stamp CONTRACT_ENTRY_SHA_LINE_RE #1724 -> exit 0 | dev -> exit 1 | bogus SHA -> exit 1 Bare existence (--jq .sha) rejected for occ_evidence_stamp.py: the file exists on dev too, so existence does not discriminate.
…rving checks pinned to head SHA (#4008) * evidence(OMN-14418): OCC companion for omnimarket#1724 — product-observing checks pinned to head SHA Unblocks omnimarket#1724, whose occ-preflight fails with reason=missing_contract (cascading into OCC Preflight Dependency + 4 gates that then refuse to start). Both substantive check_values are CONTENT READS pinned to #1724's head SHA (dbfc5d6bc72b0bddd83c3d6313ac03fff6165d28). They observe the product source, not this receipt corpus. A CI-outcome check would be circular: #1724's CI is red BECAUSE this contract is missing. RED direction proven by execution for both checks: emitter compute_contract_entry_sha256 #1724 -> exit 0 | dev -> exit 1 | bogus SHA -> exit 1 stamp CONTRACT_ENTRY_SHA_LINE_RE #1724 -> exit 0 | dev -> exit 1 | bogus SHA -> exit 1 Bare existence (--jq .sha) rejected for occ_evidence_stamp.py: the file exists on dev too, so existence does not discriminate. * evidence(OMN-14418): normalize OCC receipt bindings * evidence(OMN-14418): bind companion to OCC PR
occ-preflight failed #4012 with reason=pr_ticket_mismatch: every existing OMN-14418 receipt binds to the source (#1724) or to the earlier companion (#4008), and none to #4012. Per validator_occ_merge_eligibility._receipt_bound_to_pr a receipt binds when pr_number == the PR under check, or commit_sha is one of that PR's commits. The merged dod-occ-self-commit receipt binds #4008 and is immutable under the Append-Only Gate, so the binding for THIS PR is APPENDED as a net-new self-bind item (dod-occ-self-commit-4012, pr_number: 4012) rather than edited into the existing one. All three already-merged receipts re-verified: still bind after the append (contract_entry_sha256 is immune to contract appends). Substantive check unchanged and re-proven from the committed YAML: pulls/1724/files -> exit 0 GREEN (0 deploy surfaces) pulls/4/files -> exit 1 RED (Dockerfile.projection + docker-compose)
Summary
Adds PR-bound OCC evidence for omnibase_core#1171 so Receipt Gate can validate the OMN-12243 main-target-guard hotfix.
Verification
uv run validate-yaml contracts/OMN-12243.yamluv run pre-commit run --files contracts/OMN-12243.yaml drift/dod_receipts/OMN-12243/.../command.yamlSummary by CodeRabbit
New Features
Chores