Repository navigation
chore(contracts): backfill ModelTicketContract for 50 tickets [OMN-8637 wave 30] - #192
Conversation
…37 wave 30] Range: OMN-8494 - OMN-8571 Generated minimal contracts with keyword-enriched DoD checks.
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 9 minutes and 7 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (50)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
…37 wave 30] Range: OMN-8494 - OMN-8571 Generated minimal contracts with keyword-enriched DoD checks.
…urrent contract hash Appending the omnimarket A3 dod_evidence entries changed the OMN-12775 contract hash; every receipt under the ticket must pin the current hash or the Receipt Gate fails with contract_hash_mismatch. Re-pin all four receipts (omnidash #192, occ-evidence, omnimarket #1113 + tests) to sha256:980da6c1.
…#7169) * evidence(OMN-16549): correct pr-192 receipt to real landed squash SHA Append-only follow-up on occ#7156: a Wave-3 audit found occ#7156 (the OCC companion) merged 07:07:34Z, 28 minutes AFTER omnibase_compat#192 merged 06:39:30Z, inverting companions-merge-first. The node_occ_companion_compute autobind that wrote dod-OmniNode-ai-omnibase_compat-pr-192's receipt ran its probe while #192 was still OPEN, pinning commit_sha to the PR's then-current head 404e9a59447a7530269604c112a9e79c5fd21727. Squash-merge rewrote history: that SHA exists as a loose object but is NOT an ancestor of omnibase_compat origin/dev (verified live via git merge-base --is-ancestor, exit 1). The real landed identity is squash commit abe9095f3b55e87550e092d5e51f145739405d10 (verified live: IS an ancestor of origin/dev). Adds dod-compat-pr-192-rebind-abe9095f, superseding ONLY dod-OmniNode-ai-omnibase_compat-pr-192 -- does not edit its bytes. Two falsifiable checks: (1) omnibase_compat#192's real merge_commit_sha and merged_at via gh api, (2) occ#7156's own merged_at, documenting the actual (inverted) ordering rather than fabricating a compliant one. Cites: OMN-16549 Evidence-Source: self (this PR) * evidence(OMN-16549): merge the two rebind checks into one falsifiable probe Append-only follow-up: dod-compat-pr-192-rebind-abe9095f declared two checks, but a receipt binds one check_value per item. Merges both gh api assertions (pr-192's real merge_commit_sha/merged_at, occ#7156's merged_at) into a single command with && so the receipt has exactly one check_value to bind to. Cites: OMN-16549 Evidence-Source: self (this PR) * evidence(OMN-16549): PASS receipt for pr-192 SHA correction Real hashes computed via omnibase_core.validation.validator_receipt_gate (compute_contract_entry_sha256/_prefixed_contract_sha256) against the committed contract at 7825fff. Both gh api probes re-run live immediately before writing this receipt (probe_stdout: true/true, exit_code 0). Cites: OMN-16549 Evidence-Source: self (this PR) * evidence(OMN-16549): self-bind receipt for occ#7169 Append-only follow-up: adds occ-self-bind-pr-7169 now that this PR's number is known. Does not touch any prior dod_evidence entry. Cites: OMN-16549 Evidence-Source: self (this PR) * evidence(OMN-16549): PASS receipt for occ-self-bind-pr-7169 commit_sha anchored to 2aa8175 (already pushed) per the Receipt Hardening Gate's remote-reachability requirement (OMN-15461) -- the prior local-only commit was not yet pushed when this receipt was first written. Cites: OMN-16549 Evidence-Source: self (this PR) * evidence(OMN-16549): rename pr-192 receipt by run timestamp * fix(OMN-16549): revert receipt filename to command.yaml (validator requirement) An unexplained local commit (4956e6c, "rename pr-192 receipt by run timestamp") renamed the receipt to a <run_timestamp>.yaml shape, matching docs/RECEIPT_LOCATIONS.md's stated canonical pattern -- but that doc is stale relative to the actual code. validator_occ_merge_eligibility.py's receipt_path resolution (omnibase_core.validation) hardcodes `{evidence_item_id}/{check_type}.yaml` -- for this entry, check_type is "command", so it looks for command.yaml specifically, not a timestamp-named file. The rename broke occ-preflight/eligibility (MISSING_RECEIPT for dod-compat-pr-192-rebind-abe9095f) and the Receipt Gate on this same PR, confirmed live in CI run 32959938828/32959938799. Reverts to command.yaml, matching the ~150-file corpus convention (every other command-type receipt in drift/dod_receipts/ uses this name). Cites: OMN-16549 Evidence-Source: self (this PR)
Backfill of for tickets OMN-8494 - OMN-8571.
Part of OMN-8637: every ticket needs a contract.
Wave 30/32