Skip to content

evidence(OMN-13480): OCC receipt binding omnibase_core PR #1315 (SEA-generated localhost-URL COMPUTE validator) - #2971

Merged
jonahgabriel merged 7 commits into
devfrom
jonah/omn-13480-localhost-validator-receipt
Jun 23, 2026
Merged

jonahgabriel merged 7 commits into
devfrom
jonah/omn-13480-localhost-validator-receipt

Conversation

@jonahgabriel

@jonahgabriel jonahgabriel commented Jun 23, 2026 •

Copy link
Copy Markdown
Contributor

Evidence-Source: OCC#2966
Evidence-Ticket: OMN-13480

evidence(OMN-13480): OCC receipt binding omnibase_core PR #1315

Adds the dod-omnibase-core-pr-1315 DoD receipt to the OMN-13480 central evidence and re-hashes the contract + all receipts, so the downstream Receipt Gate for omnibase_core PR #1315 (the SEA-generated localhost-URL COMPUTE validator) can resolve a PASS receipt.

PR #1315 lands the dedicated SEA-generated, corpus-accepted hardcoded-localhost-URL COMPUTE validator (omnibase_core.validation.localhost_url) — the generate-first canonical path the OMN-13294 G2 DoD prescribes ("if no, generate the scanner"), matching the private_ip / pin_hygiene family. The loopback-URL scanning logic was generated by node_generation_consumer against the live local-coder model (Qwen3.6-35B-A3B @ .201), corpus-accepted on attempt 3 (corpus_checked = corpus_passed = accepted = true; 5/5 violation + 5/5 clean fixtures — the corpus, not the LLM, is the authority).

This is an ALTERNATIVE to the url-authority localhost-literal rule bound from PR #1312 (also in this contract): both close the same gap. #1315 is the dedicated COMPUTE validator with no grandfathering (all 9 pre-existing localhost sites triaged + annotated); #1312 bolts a rule onto url-authority with a burn-down baseline. Operator decides which supersedes.

Receipts (all re-hashed to the current contract sha)

No live deploy mutation: the PR adds a build-time COMPUTE-over-in-memory-bus validation gate + tests + wiring only.

References OMN-13480 (related OMN-13294).

Summary by CodeRabbit

  • Chores
    • Added a new verification record confirming validation for the SEA-generated COMPUTE localhost URL validator (including the associated PASS receipt evidence).
    • Updated contract SHA-256 references across multiple verification/receipt entries to reflect the latest contract revisions, while preserving existing check outcomes and metadata.

…generated localhost-URL COMPUTE validator)
@coderabbitai

coderabbitai Bot commented Jun 23, 2026 •

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@jonahgabriel, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 6 minutes and 18 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses rolling per-developer review limits. Reviews become available again as older review attempts age out of the rolling limit window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 11f4a30e-9448-4f37-af9b-00b2662594db

📥 Commits

Reviewing files that changed from the base of the PR and between 0114116 and 03ecacd.

📒 Files selected for processing (1)
  • drift/dod_receipts/OMN-13480/dod-occ-pr-self/command.yaml
📝 Walkthrough

Walkthrough

Adds a new dod-omnibase-core-pr-1315 evidence entry to contracts/OMN-13480.yaml documenting a SEA-generated localhost-URL COMPUTE validator, along with a new command.yaml receipt recording a PASS verification. Five existing OMN-13480 receipt files have their contract_sha256 field updated to a new digest.

Changes

OMN-13480 PR-1315 Evidence and Hash Refresh

Layer / File(s) Summary
New PR-1315 evidence entry and receipt
contracts/OMN-13480.yaml, drift/dod_receipts/OMN-13480/dod-omnibase-core-pr-1315/command.yaml
Inserts dod-omnibase-core-pr-1315 into the contract's dod_evidence list with status: verified and a command check; adds the full receipt YAML recording probe metadata, probe_stdout, actual_output assertion, and exit_code: 0.
contract_sha256 refresh in existing receipts
drift/dod_receipts/OMN-13480/dod-deploy-no-live-mutation/command.yaml, drift/dod_receipts/OMN-13480/dod-occ-pr-self/command.yaml, drift/dod_receipts/OMN-13480/dod-omnibase-core-pr-1304/command.yaml, drift/dod_receipts/OMN-13480/dod-omnibase-core-pr-1312/command.yaml, drift/dod_receipts/OMN-13480/dod-url-authority-localhost-rule/command.yaml
Updates contract_sha256 to the new digest sha256:04098c69d795d51e13f82661134a065e2485c63ea6511edcb1aefc227060bb09 in all five pre-existing receipts; no other fields change.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

  • OmniNode-ai/onex_change_control#2833: Both PRs add/update the dod-occ-pr-self receipt evidence (command.yaml) with grep-based status: PASS/pr_number validation and bound contract_sha256, so the change patterns are directly aligned.

Poem

🐇 A new receipt hops into the fold,
The localhost validator, brave and bold.
Five old hashes get a fresh new face,
All SHA-256s stamped in place.
The contract grows—tick, tick, PASS!
✅ Evidence filed with flair and class.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly summarizes the main change: adding evidence binding for omnibase_core PR #1315 (a SEA-generated localhost-URL COMPUTE validator) to the OMN-13480 OCC contract. It is specific, concise, and directly aligned with the primary purpose of the PR.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch jonah/omn-13480-localhost-validator-receipt

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@drift/dod_receipts/OMN-13480/dod-omnibase-core-pr-1315/command.yaml`:
- Line 28: The receipt attestation text contains an inconsistent SHA value. The
actual_output statement at line 28 references head SHA `813b31b0`, but the
correct SHA that is bound on lines 11 and 19 is
`e155e93da9cdd47d0a73aa9a8fd4425a51f5e1af`. Update the SHA in the receipt
binding statement to use the correct SHA value
`e155e93da9cdd47d0a73aa9a8fd4425a51f5e1af` instead of the stale `813b31b0` to
ensure internal consistency across the receipt.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 8e9a94de-9347-4b1d-8173-97b0cf5a9554

📥 Commits

Reviewing files that changed from the base of the PR and between 421da92 and 3ebeba4.

📒 Files selected for processing (7)
  • contracts/OMN-13480.yaml
  • drift/dod_receipts/OMN-13480/dod-deploy-no-live-mutation/command.yaml
  • drift/dod_receipts/OMN-13480/dod-occ-pr-self/command.yaml
  • drift/dod_receipts/OMN-13480/dod-omnibase-core-pr-1304/command.yaml
  • drift/dod_receipts/OMN-13480/dod-omnibase-core-pr-1312/command.yaml
  • drift/dod_receipts/OMN-13480/dod-omnibase-core-pr-1315/command.yaml
  • drift/dod_receipts/OMN-13480/dod-url-authority-localhost-rule/command.yaml

Comment thread drift/dod_receipts/OMN-13480/dod-omnibase-core-pr-1315/command.yaml
@jonahgabriel

Copy link
Copy Markdown
Contributor Author

Status note (landing omnibase_core #1315): This carrier is CONFLICTING against OCC dev because the OMN-13480 contract + receipts already landed on dev via #2966, and this branch (which adds the dod-omnibase-core-pr-1315 receipt + updates the contract to bind #1315) diverged from that base. The feature PR omnibase_core #1315 Receipt Gate (verify / verify) is already GREEN on its current head against the dev OMN-13480 contract, so #1315 has been armed for auto-merge to dev independently. Resolving this PR (rebase onto current dev) is an operator task tied to the #1312-vs-#1315 dedup decision — #1315 was armed and #1312 disarmed per operator direction. Not bypassed.

@jonahgabriel
jonahgabriel added this pull request to the merge queue Jun 23, 2026
Merged via the queue into dev with commit 46f7fb5 Jun 23, 2026
38 checks passed
@jonahgabriel
jonahgabriel deleted the jonah/omn-13480-localhost-validator-receipt branch June 23, 2026 19:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant