Repository navigation
docs(OMN-12738): add qwen delegation evidence - #2222
Conversation
|
Warning Review limit reached
More reviews will be available in 3 minutes and 5 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, 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 include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (5)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
… on one ticket omnimarket#2222 and omnibase_infra#3035 both carry OMN-17182, so autobind minted two independent companions that each created contracts/OMN-17182.yaml and drift/dod_receipts/OMN-17182/dod-occ-evidence-admissibility-validator/command.yaml. OCC#7703 (omnimarket) merged first, so this branch went add/add CONFLICTING. Resolved as the UNION of both evidence sets - no entry from either side dropped: - dod-OmniNode-ai-omnimarket-pr-2222 (from dev, via OCC#7703) - dod-deploy-assessment (from dev, via OCC#7703) - dod-occ-evidence-admissibility-validator (from dev, via OCC#7703) - occ-self-bind-pr-7703 (from dev, via OCC#7703) - dod-OmniNode-ai-omnibase_infra-pr-3035 (this branch) - occ-self-bind-pr-7702 (this branch) The single admissibility-validator entry is kept once and left superseding the omnimarket item, matching the existing multi-PR precedent in contracts/OMN-17155 where later PRs append their own dod + self-bind entries without minting a second validator. Its receipt is dev's (PR #2222 probe), not this branch's duplicate. Hashes are RECOMPUTED, not copied. yamlfmt reflowed the merged contract, which moves the whole-file hash, so contract_sha256 was recomputed for all six receipts from the formatted bytes via compute_contract_sha256, and contract_entry_sha256 via compute_contract_entry_sha256 against the merged contract_data. Verified with the repo's own gate: scripts/validation/check_receipt_hardening.py exits 0.
Summary
Verification
Ticket: OMN-12738