Skip to content

evidence(OMN-13092): deploy verification receipt — emit daemon round-trip of capture event types - #2582

Closed
jonahgabriel wants to merge 1 commit into
devfrom
jonah/omn-13092-occ-deploy-receipt
Closed

jonahgabriel wants to merge 1 commit into
devfrom
jonah/omn-13092-occ-deploy-receipt

Conversation

@jonahgabriel

Copy link
Copy Markdown
Contributor

Summary

Follow-up OCC evidence PR for OMN-13092 (Phase 0c of epic OMN-13089 — capture topics + event types registration + consistency test).

The original OCC receipt PR #2575 merged to dev, which invalidated the Evidence-Source SHA cited by the omnimarket implementation PR (branch head vanished after squash-merge; commit is on dev, not main, so the Receipt-Gate's open-pr | main-ancestor resolution fails). This PR re-exposes the contract chain as an open-PR head AND adds the deploy verification evidence the omnimarket deploy-gate requires.

Contents

  • contracts/OMN-13092.yaml — adds dod-emit-daemon-standalone-deploy evidence item (deploy verification for the registry change)
  • drift/dod_receipts/OMN-13092/dod-emit-daemon-standalone-deploy/command.yaml — receipt with real probe_stdout: emit daemon started standalone from omnimarket PR evidence(OMN-9068): add omniclaude receipt gate contracts #1201 head, both new duty-critical event types (artifact.captured, tool.output.captured) accepted + queued over the real Unix socket, under-specified payload rejected with exact missing required fields
  • src/onex_change_control/boundaries/migration_inventory.yaml — registers migration 085 (db_metadata) so the OCC migration-inventory gate stays green on this branch
  • Receipt verifier corrections on the two prior receipts (carried from the prior session)

dod_evidence

Evidence-Ticket: OMN-13092

@coderabbitai

coderabbitai Bot commented Jun 12, 2026

Copy link
Copy Markdown

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 1 hour, 8 minutes, and 46 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more credits in the billing tab to continue.

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

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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: e6f3fba2-2cc1-41be-b44f-6dd45837ad9e

📥 Commits

Reviewing files that changed from the base of the PR and between 3e1ac61 and 6a7b047.

📒 Files selected for processing (4)
  • contracts/OMN-13092.yaml
  • drift/dod_receipts/OMN-13092/dod-emit-daemon-standalone-deploy/command.yaml
  • drift/dod_receipts/OMN-13092/dod-occ-pr/command.yaml
  • drift/dod_receipts/OMN-13092/dod-omnimarket-pr-1201/command.yaml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch jonah/omn-13092-occ-deploy-receipt

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

@jonahgabriel

Copy link
Copy Markdown
Contributor Author

Closing as duplicate of #2581 — parallel-lane collision. #2581 carries the same dod-emit-daemon-standalone-deploy receipt (fresher commit_sha citation, already referenced by omnimarket PR #1201's Evidence-Source). The omniclaude-side registration for OMN-13092 continues separately.

@jonahgabriel
jonahgabriel deleted the jonah/omn-13092-occ-deploy-receipt branch June 12, 2026 18:52
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