Repository navigation
evidence(OMN-14086): OCC companion for omnibase_infra PR 2263 - #3982
Conversation
…fit item #5) OMN-14086 bundles 5 independent zero-risk validator diff-scope/wiring retrofits; item #3 (omniclaude#1867) already has OCC#3679 evidence. This is item #5 (run_duplication_sweep wiring). Append-only addition of a new dod_evidence entry -- existing 4 entries/receipts untouched. Independent adversarial verification (verifier=sc-reconcile, runner= verify-14374) of omnibase_infra#2263: 12/12 focused tests green, an independent fires-on-violation proof in a CI-shaped sparse-checkout layout (real duplicate pgTable across 2 files -> FAIL/exit 1; fixed -> PASS/exit 0), plus a RED->GREEN mutation proof on the new --changed-files narrowing logic. ruff/actionlint clean.
Add-only self-binding receipt for occ-preflight eligibility, ahead of the OCC PR number existing. Distinct evidence_item_id from the existing dod-occ-pr-3679 entry.
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 10 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Summary
Net-new (append-only) OCC evidence for OMN-14086 (wire duplication_sweep as a required CI gate + pre-commit hook,
omnibase_infra#2263).Important — same ticket, different sub-scope, not a new ticket collision: OMN-14086 bundles 5 independent zero-risk validator diff-scope/wiring retrofits (see Linear description). Item #3 (omniclaude#1867, aislop-sweep diff-scoping) already has a merged OCC companion (
#3679) with 4 existing dod_evidence entries and receipts. This PR is item #5 (run_duplication_sweepwiring,omnibase_infra#2263) — a separate, independent product PR against the same ticket. This companion appends a 5thdod_evidenceentry tocontracts/OMN-14086.yamland adds 3 net-new receipt files; the 4 existing entries/receipts are untouched (confirmed viagit status --shortbefore commit — onlyM contracts/OMN-14086.yaml+ 2 newAreceipts in the first commit, then 1 moreAfor the self-bind). This satisfies the append-only invariant (evaluate_append_onlychecks per-entry-id hash identity for base IDs, not whole-file diff) and the receipt-hardening gate (both pre-commit and the CI job scopecheck_receipt_hardening.pytogit diffchanged files only, so the 4 pre-existing receipts — bound to the old whole-file hash — are never re-validated against the new one).Authored under the OMN-14055-sanctioned independent-verifier escape hatch (verifier != implementer):
sc-reconcileindependently verifiedomnibase_infra#2263— read the full diff, checked out the branch in an isolated worktree, ran the focused suite green (12/12), then went beyond the test suite with an independent fires-on-violation proof in a CI-shaped sparse-checkout layout (real duplicatepgTableacross 2 files -> FAIL/exit 1; fixed -> PASS/exit 0) plus a RED->GREEN mutation proof on the new--changed-filesnarrowing logic (3/12 dedicated tests failed as expected).runner: verify-14374(the session lane that built #2263, perdocs/tracking/ROLLING_WORK_LEDGER.md),verifier: sc-reconcile(independent).contracts/OMN-14086.yaml— appended 5thdod_evidenceentry (dod-omnibase-infra-pr-2263-head-c7b8ee81)drift/dod_receipts/OMN-14086/dod-omnibase-infra-pr-2263-head-c7b8ee81/command.yaml— product proof receiptdrift/dod_receipts/OMN-14086/dod-deploy-assessment-head-c7b8ee81/command.yaml— deploy-surface assessment (no live deploy)drift/dod_receipts/OMN-14086/dod-occ-self-commit-infra-2263/command.yaml— OCC self-binding receipt (distinct id from the existingdod-occ-pr-3679)All net-new files; no existing receipt/contract entry edited (OMN-13888 append-only).
Evidence-Ticket: OMN-14086
Test plan
uv run pre-commit run --files contracts/OMN-14086.yaml drift/dod_receipts/OMN-14086/**/*.yaml— all hooks green, including Receipt Hardening Gate and normalization-symmetry