Repository navigation
receipt(OMN-10865): update infra PR 1591 binding to post-enum-fix head - #1004
Merged
Merged
Conversation
jonahgabriel
enabled auto-merge (squash)
May 14, 2026 14:17
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (8)
✅ Files skipped from review due to trivial changes (7)
📝 WalkthroughWalkthroughReplaced the ChangesChecksum update for OMN-10865 evidence
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Rebind the dod-omnibase-infra-pr-1591 receipt to commit 96be34674fb2d76a7a233ce8d2653034984644d1 — the head after the topic enum regeneration fix was pushed to address the Topic Enum Drift CI failure.
Receipt gate requires a PASS receipt that binds to this PR number.
jonahgabriel
force-pushed
the
jonah/omn-10958-occ-receipt-pr1591-v2
branch
from
May 14, 2026 22:12
34c60b0 to
eda58f2
Compare
…_sha256 bindings Adding a new dod_evidence item changes the contract hash, breaking all existing receipts that embedded the original contract_sha256.
…_sha256 The receipt gate requires each OCC PR to have a matching receipt. Adding the evidence item changes the contract hash, so all existing receipts with contract_sha256 must be updated to the new hash.
jonahgabriel
added a commit
that referenced
this pull request
Aug 26, 2026
#7150) * evidence(OMN-16574): OCC companion for OmniNode-ai/omninode_infra#1006 Hand-scaffolded via scripts/auto_scaffold_contract.py because the per-PR OCC autobind publisher (call-occ-autobind.yml) ran and published successfully but the .201 effects-runtime consumer (node_pr_lifecycle_fix_effect) had not minted a companion or PATCHed Evidence-Source onto omninode_infra#1006 after ~10 minutes -- well outside the ~30s turnaround observed on this same ticket family's other PRs tonight (#1001, #1002, #1004, #1005). Evidence-Ticket: OMN-16574 * fix(OMN-16574): fill real ModelDodReceipt fields, scope commands to what was actually run The scaffold-generated stub receipts were missing required ModelDodReceipt fields (run_timestamp, commit_sha, runner, verifier, probe_command, probe_stdout) -- occ-preflight rejected them as "nonpass_receipt" with 6 pydantic validation errors. Replaces the generic stub check_values (uv run pytest tests/ -v / pre-commit run --all-files) with the exact commands actually run against omninode_infra#1006's head commit, fills every required field with real captured output, and rebinds contract_entry_sha256 via the real compute_contract_entry_sha256() after the contract edit (verified: both receipts validate against ModelDodReceipt and hash-match their contract entries). commit_sha is a cross-repo (omninode_infra) SHA; embedded a real "gh pr view 1006 --repo OmniNode-ai/omninode_infra" probe into probe_command/probe_stdout so the Evidence-Commit SHA Existence Gate (OMN-15461/OMN-15111) can resolve it against the correct repo instead of defaulting to onex_change_control. Evidence-Ticket: OMN-16574 * fix(OMN-16574): add OCC self-bind entry for PR #7150 occ-preflight identified the specific remaining gap on its own: no receipt bound this OCC PR itself (#7150), so eligibility could not resolve a PASS receipt for the in-repo evidence PR carrying the OMN-16574 contract. Adds the occ-self-bind-pr-7150 dod_evidence entry and its receipt (real "gh pr view 7150" probe output), and recomputes contract_sha256 on the two existing dod-001/dod-002 receipts -- the whole-file hash moves when the contract gains an entry, per-entry contract_entry_sha256 does not (OMN-13888), and both are verified unchanged/consistent against the live contract file. Evidence-Ticket: OMN-16574
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Rebinds
dod-omnibase-infra-pr-1591receipt to the new head SHA after the topic enum regeneration fix (commit96be34674fb2d76a7a233ce8d2653034984644d1) was pushed to omnibase_infra PR #1591.The original receipt bound to
2b0f1597which predated the CI fix commit. This updates it to the current head so the Receipt Gate passes.Evidence-Ticket: OMN-10865
Evidence-Source: 7b6e353
Summary by CodeRabbit