Repository navigation
evidence(OMN-15749): OCC companion for OmniNode-ai/omnibase_infra#2826 - #6819
Conversation
Hand-authored because OCC autobind formally DECLINED this PR. onexbot-occ-writer commented on omnibase_infra#2826 at 2026-08-21T04:48:24Z with marker `occ-autobind-no-red-derivable:2826`: "no changed-file candidate could be proven RED against the merge base, and emitting a PR-existence probe instead would be non-falsifiable evidence (OMN-15247). Hand-authored evidence is required." That satisfies the pr-landing-ceremony §1.3 precondition for hand-authoring. The probe is content-bound, not a PR-existence check, so it clears the evidence-admissibility gate on all three axes: - EXECUTED — `gh api` is on the allowlist; bare `gh pr view` is not. - FALSIFIABLE — verified GREEN at head cc972ae1a and RED at merge-base 2444b99f1, where the fixture still calls subprocess.run directly and _PULL_TIMEOUT_SECONDS does not exist. Both directions run before the receipt was written; the receipt records the real exit status. - OUTSIDE ITS OWN DIFF — it reads omnibase_infra, which this OCC PR does not author. Uses the OMN-15411 Rule E pipe-safe shape (capture into "$body", then pipe to grep) with the ?ref= URL single-quoted, and `grep -qF --` because the needle would otherwise be parsed as an option. Refs: OMN-15749, omnibase_infra#2826, OMN-15247 (admissibility), OMN-13888 (per-entry hash), OMN-15411 (pipe-safe probe shape)
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 54 minutes Limit details: You’ve used the included review currently available. Your 116 included PR review attempts over the past 7 days set your current allowance at 1 review per hour. Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?Wait for the limit to reset, then comment An organization admin can change what happens after included review limits in Billing. How do review limits work?CodeRabbit enforces per-developer PR review limits within each organization. For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
Comment |
jonahgabriel
added
the
ci:ready
|
OCC autobind stood down for |
occ-preflight failed post-recovery with reason=pr_ticket_mismatch:
no PASS receipt for one or more tickets binds to PR #6819
or one of its commit SHAs: OMN-15749
The product-PR receipt was found and its hashes verified clean
(missing_or_nonpass_receipts and stale_receipt_bindings were both empty) --
the gap was purely binding. That receipt carries pr_number 2826, the
omnibase_infra PR, so nothing bound OMN-15749 to this OCC PR itself, which
is what the eligibility checker resolves against.
Every other OCC companion carries such an entry (occ-self-bind-pr-6805,
-6809, -6810, -6811); I omitted it because the worked example I copied from,
OCC#6814, appends to a contract whose self-bind another PR had already
landed. A companion that CREATES its contract needs its own.
Adds occ-self-bind-pr-6819 following the established convention, with the
probe run live and the real stdout recorded. Also updates the product-PR
receipt's contract_sha256, which necessarily moved when the file gained an
entry -- both contract_entry_sha256 values are unchanged, per OMN-13888.
Refs: OMN-15749, omnibase_infra#2826, OMN-13888
1 participant
Summary
OCC companion for omnibase_infra#2826, which makes the OMN-15181 deploy-agent digest-verification fixture absorb real docker daemon/registry timeouts instead of erroring on them.
Creates
contracts/OMN-15749.yamland its PASS receipt.Why this is hand-authored
OCC autobind formally declined this PR.
onexbot-occ-writer[bot]commented on omnibase_infra#2826 at2026-08-21T04:48:24Z, markerocc-autobind-no-red-derivable:2826:That satisfies the
pr-landing-ceremony.md§1.3 precondition — autobind is confirmed declined, not merely slow, so hand-authoring here does not risk the self-companion / divergent-automation guard.Worth recording why autobind could not derive a RED candidate: #2826 changes a test fixture, so there is no product-code line whose absence at the merge base proves the defect. The RED fact lives one level up — the constant and helper the fixture gains — which is exactly what the probe below targets.
The probe is content-bound, not a PR-existence check
gh apiis on the admissibility allowlist; baregh pr viewis not (it "proves a PR exists, not that the code works").cc972ae1a2124a50acdc928cc4401b7455276b95; RED at merge-base2444b99f135406b793b6620fb9b44605ad76171a, where the fixture still callssubprocess.rundirectly and_PULL_TIMEOUT_SECONDSdoes not exist. The receipt records the real exit status.omnibase_infra, a repo this OCC PR does not author.Two shape details, both deliberate:
"$body"first, then pipe togrep, so the exit status isgrep's and not masked by the pipeline head.?ref=URL is single-quoted, and the needle usesgrep -qF --. Without the--, a needle beginning with-is parsed as an option — I hit exactly that while verifying the sibling probe for infra#2817, where--squash --automade grep exit non-zero withinvalid option. A probe that fails for that reason would have looked like a legitimate RED.Evidence
Evidence-Ticket: OMN-15749
contracts/OMN-15749.yaml— new, one entrydod-OmniNode-ai-omnibase_infra-pr-2826drift/dod_receipts/OMN-15749/dod-OmniNode-ai-omnibase_infra-pr-2826/command.yaml— PASSHashes computed with
omnibase_core.validation.validator_receipt_gateagainst the yamlfmt-stabilized contract bytes, and re-verified after the commit hooks ran so a hook-side reflow cannot have staled them.verifiernames the gh CLI against the GitHub API — re-derivable by anyone, not forgeable locally — with the executing lane recorded separately asrunner, per the OMN-13060/A-5 hardening gate.What #2826 itself proves
Its own acceptance signal is already green:
Deploy Agent Testsreports 206 passed, 0 skipped, and bothreal_containertests log PASSED (not SKIPPED) on a real self-hosted runner — so the fixture still builds a real busybox container and both assertions still execute. The skip paths the PR adds are genuinely environment-conditional.Test plan
pre-commithooks passedocc-preflight / eligibilityandverify / verifygreen on this PRRefs: OMN-15749, omnibase_infra#2826, OMN-15247, OMN-13888, OMN-15411