Repository navigation
contracts(OMN-11985): Wave 3C OCC evidence for omnimarket PRs #800 #801 #802 #803 - #1586
jonahgabriel wants to merge 2 commits into
Conversation
|
Warning Review limit reached
Your plan includes 5 reviews of capacity. Refill in 21 minutes and 48 seconds. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more review capacity refills, 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 trial, open-source, and free plans. In all cases, review capacity refills continuously over time. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (16)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
…ntracts Adds dod-deploy-readiness evidence items to the 4 Wave 3C ticket contracts (OMN-11902/11904/11905/11908) so the omnimarket deploy-gate CI check passes. Each receipt confirms contract-only YAML migration with no production mutation.
|
Superseded by the already-merged Wave 2/4/5/8 OCC evidence on main. Current main contains OMN-11902/11904/11905/11908 contracts and deploy-readiness/local-validation/OCC receipts from the successful downstream merge path; this branch now add/add conflicts on the same evidence files. Closing as redundant rather than hand-merging stale duplicate evidence. |
Pull request was closed
…and receipt bundle for 6 tickets (OmniNode-ai#999) * contract(OMN-10940,OMN-10941): add OCC contracts and receipts for infra PRs 1586 and 1587 - OMN-10940: add dod-omnibase-infra-pr-1586 evidence binding PR OmniNode-ai#1586 (E2E golden-chain task-delegated event test) to the OMN-10940 contract - OMN-10941: new contract + receipt for PR OmniNode-ai#1587 (max_tokens propagation regression tests) Both receipts are required for the receipt-gate Evidence-Source check on PRs 1586 and 1587. * contract: add OMN-10936/10942/10944 contracts + fix receipt hashes for 10940/10941/10949 - Add contracts for OMN-10936 (reviewdog-caller omniclaude), OMN-10942 (contract routing policy), OMN-10944 (dashboard projection API contract) - Update OMN-10949 contract to cover infra PR OmniNode-ai#1588 and market PR OmniNode-ai#622 in addition to market OmniNode-ai#616 - Fix contract_sha256 in OMN-10940 receipts (pr-1580, pr-1586) — contract was updated with pr-1586 evidence item, changing the hash - Add contract_sha256 to OMN-10941 pr-1587 receipt (was missing) - Update OMN-10949 pr-616 receipt contract_sha256 to reflect expanded contract - Add receipts: OMN-10936/pr-1582, OMN-10942/pr-621, OMN-10944/pr-620, OMN-10949/pr-1588, OMN-10949/pr-622 * contract(OMN-10949): add deploy evidence item + update receipt hashes - Add deploy-evidence-pricing-version dod_evidence item to satisfy deploy-gate (pricing_manifest_version is additive schema field, no runtime restart needed) - Update contract_sha256 in all OMN-10949 receipts (pr-616, pr-1588, pr-622) to reflect updated contract hash * contract: add OCC self-binding receipts (pr-999) + fix all contract_sha256 hashes - Add dod-occ-pr-999 evidence items to all 6 ticket contracts (OMN-10936/10940/10941/10942/10944/10949) - Create dod-occ-pr-999/command.yaml self-binding receipts for each ticket - Update all downstream receipt contract_sha256 fields to reflect updated contract hashes - Fixes OCC eligibility pr_ticket_mismatch failure (receipts now bind to OCC PR OmniNode-ai#999) * receipt(OMN-10949): add deploy-evidence-pricing-version receipt for deploy-gate * fix: add headRefName to probe_stdout in OMN-10942/OMN-10944 receipts (CR review) * ci(OMN-10940): suppress delegation_events migration name conflict The Migration Conflict Check on PR OmniNode-ai#999 flagged delegation_events as a NAME_CONFLICT between omnibase_infra/078_create_delegation_events.sql (Postgres projection, 22 cols, UUID PK) and omniclaude/001_create_delegation_tables.sql (SQLite hook-side capture, 15 cols, INTEGER PK). Different databases, different access patterns. The omnibase_infra side is the canonical projection consumed by HandlerProjectionDelegation from onex.evt.omniclaude.task-delegated.v1 (OMN-10526). The omniclaude side is the local hook-side store pinned to the projection contract (OMN-10604). Neither shares a Postgres instance with the other. Suppress the conflict using the existing schema_evolution reason — the same pattern already used for llm_call_metrics and savings_estimates, which have an identical infra-vs-omniclaude split. No code changes; this is a CI suppressions update only.
…try validation (OmniNode-ai#1008) * contract(OMN-10971): update skip_token_approvals schema for GHA registry validation Align allowlist field names with the validation logic in reject-deploy-gate-skip.yml: receipt_id, repo, pr_number, approved_by, expires_at, created_at, token_type, reason. Documents that approved_by != PR author is enforced by the workflow. * evidence(OMN-10971): add contract and self-binding receipt Receipt gate requires contracts/OMN-10971.yaml to exist at the PR HEAD. * evidence(OMN-10971): add omniclaude PR OmniNode-ai#1586 receipt Binds omniclaude central registry validation PR to the OMN-10971 contract.
Summary
Rebase conflict resolutions
handler_model_router.pytopic constant comments +verified_dispatch_orchestratorhandler routing formatnode_morning_handoff_generator— merged operation key from main with event_model from PRnode_golden_chain_sweep— keptsweep_golden_chainsoperation name from mainfix_handler_routing.pyscript removedTest plan
uv run pytest tests/ -v -k handler_model_router— 1 passedpre-commit run --all-files— all hooks passed on OCC filesEvidence-Ticket: OMN-11985
Evidence-Source: OCC#1585