Repository navigation
docs(OMN-10698): add ADR canary OCC evidence - #831
Conversation
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ 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 (5)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
…lution The earlier merge-conflict resolution rewrote the shared "dod-occ-evidence-admissibility-validator" dod_evidence entry and its receipt file, both of which were already merged to dev by OCC#6234 (PR #830's companion). That trips the OCC Append-Only Gate: a merged dod_evidence entry/receipt must never be edited, only superseded via a net-new record. Per the established pattern for this exact shape (OMN-15637, PR #795 landing after PR #794's companion already merged the same shared validator-item id): leave the merged "dod-occ-evidence-admissibility- validator" entry and its receipt untouched, and add PR #831's evidence as net-new dod_evidence items (dod-OmniNode-ai-omninode_infra-pr-831, -831-ci, occ-self-bind-pr-6235) instead of duplicating the shared id. Zero merged content edited or deleted; three net-new entries appended.
…inode_infra#831 (#6235) * evidence(OMN-15769): author OCC companion for OmniNode-ai/omninode_infra#831 OCC companion by node_pr_lifecycle_fix_effect (OMN-13317 F1 / OMN-13990 / OMN-14285). Product PR head 4b103cc358600941a843f9b60da5813c06c8cb28. * evidence(OMN-15769): self-bind OCC#6235 + rebind contract_sha256 * fix(OMN-15769): repair append-only violation from merge conflict resolution The earlier merge-conflict resolution rewrote the shared "dod-occ-evidence-admissibility-validator" dod_evidence entry and its receipt file, both of which were already merged to dev by OCC#6234 (PR #830's companion). That trips the OCC Append-Only Gate: a merged dod_evidence entry/receipt must never be edited, only superseded via a net-new record. Per the established pattern for this exact shape (OMN-15637, PR #795 landing after PR #794's companion already merged the same shared validator-item id): leave the merged "dod-occ-evidence-admissibility- validator" entry and its receipt untouched, and add PR #831's evidence as net-new dod_evidence items (dod-OmniNode-ai-omninode_infra-pr-831, -831-ci, occ-self-bind-pr-6235) instead of duplicating the shared id. Zero merged content edited or deleted; three net-new entries appended. --------- Co-authored-by: omnimarket-bot <bot@omninode.ai> Co-authored-by: Jonah Gray <jonah@omninode.ai>
…enance cascade recovery) Two PASS receipts binding OmniNode-ai/omniintelligence#831 to the OMN-15604 contract, computed with the canonical per-entry hash (omnibase_core.validation.validator_receipt_gate.compute_contract_entry_sha256) against the OMN-15604.yaml committed and pushed in the prior commit (post-yamlfmt, stable bytes, remote-reachable at 32cac9b), and verified to bind via check_receipt_contract_binding before commit: - dod-OmniNode-ai-omniintelligence-pr-831: live `gh pr view 831` readback — PR exists, OPEN, correct branch. - dod-OmniNode-ai-omniintelligence-pr-831-ci: live file-scope assertion (OMN-14425) — PR #831 touches exactly pyproject.toml + uv.lock. Local admissibility validator: `uv run pytest tests/test_evidence_admissibility.py -q` — 76 passed (matches the OMN-16287/#6770 precedent baseline). Self-bind entry (occ-self-bind-pr-<this PR number>) follows in a third commit once the PR number is known, same pattern as #6770/#6862. Ticket: OMN-15604 Evidence-Ticket: OMN-15604
… (#6866) * evidence(OMN-15604): mint contract entries for OmniNode-ai/omniintelligence#831 Local CLI mint fallback (occ-autobind declined on omniintelligence#831 — "no changed-file candidate could be proven RED against the merge base"; pure lockfile/dependency-source change, no RED-then-GREEN diff to key off). Two new dod_evidence entries appended to the existing OMN-15604 contract: - dod-OmniNode-ai-omniintelligence-pr-831 (PR identity) - dod-OmniNode-ai-omniintelligence-pr-831-ci (exact file-scope: pyproject.toml,uv.lock) Committing the contract change alone first so yamlfmt reflows/stabilizes the file before contract_sha256 / contract_entry_sha256 are computed for the receipts (per-entry hash, OMN-13888 — appending an entry does not disturb prior entries' hashes). Ticket: OMN-15604 Evidence-Ticket: OMN-15604 * evidence(OMN-15604): PASS receipts for omniintelligence#831 (dep-provenance cascade recovery) Two PASS receipts binding OmniNode-ai/omniintelligence#831 to the OMN-15604 contract, computed with the canonical per-entry hash (omnibase_core.validation.validator_receipt_gate.compute_contract_entry_sha256) against the OMN-15604.yaml committed and pushed in the prior commit (post-yamlfmt, stable bytes, remote-reachable at 32cac9b), and verified to bind via check_receipt_contract_binding before commit: - dod-OmniNode-ai-omniintelligence-pr-831: live `gh pr view 831` readback — PR exists, OPEN, correct branch. - dod-OmniNode-ai-omniintelligence-pr-831-ci: live file-scope assertion (OMN-14425) — PR #831 touches exactly pyproject.toml + uv.lock. Local admissibility validator: `uv run pytest tests/test_evidence_admissibility.py -q` — 76 passed (matches the OMN-16287/#6770 precedent baseline). Self-bind entry (occ-self-bind-pr-<this PR number>) follows in a third commit once the PR number is known, same pattern as #6770/#6862. Ticket: OMN-15604 Evidence-Ticket: OMN-15604 * evidence(OMN-15604): self-bind contract entry for OCC companion #6866 Ticket: OMN-15604 Evidence-Ticket: OMN-15604 * evidence(OMN-15604): PASS receipt for OCC self-bind #6866 Ticket: OMN-15604 Evidence-Ticket: OMN-15604
Summary
Verification
Related-Source: omnimarket#565
Evidence-Source: OCC#831
Evidence-Ticket: OMN-10698