Skip to content

evidence(OMN-9413): add contract and dod receipts for registration orchestrator topic subscription regression test - #1094

Merged
jonahgabriel merged 2 commits into
mainfrom
jonah/omn-9413-occ-evidence
May 18, 2026
Merged

jonahgabriel merged 2 commits into
mainfrom
jonah/omn-9413-occ-evidence

Conversation

@jonahgabriel

@jonahgabriel jonahgabriel commented May 17, 2026 •

Copy link
Copy Markdown
Contributor

OMN-9413 — OCC Evidence: registration orchestrator all 7 topics subscribed

Adds contract YAML + dod receipts proving the OMN-9413 regression test is in place.

Evidence

  • contracts/OMN-9413.yaml — ticket contract with evidence requirements
  • drift/dod_receipts/OMN-9413/dod-001/command.yaml — regression test pass receipt (2 passed)
  • drift/dod_receipts/OMN-9413/dod-002/command.yaml — infra PR contracts(OMN-12061): add model registry evidence #1634 receipt

omnibase_infra PR

OmniNode-ai/omnibase_infra#1634

Evidence-Source: OCC#1093
Evidence-Ticket: OMN-9413

Summary by CodeRabbit

  • Tests
    • Added regression test contract and validation evidence records to verify node registration orchestrator functionality.

Review Change Stack

…chestrator topic subscription regression test

Contract OMN-9413: node_registration_orchestrator declares 7 subscribe_topics
but at runtime only 3 consumer groups were wired. Fixed in OMN-10448 (which
delegated all wiring to generic contract auto-wiring). This OCC entry records
the regression test proof via omnibase_infra PR #1634.
@coderabbitai

coderabbitai Bot commented May 17, 2026 •

Copy link
Copy Markdown

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 63819393-39df-495a-b54a-8ae70cc7b5fd

📥 Commits

Reviewing files that changed from the base of the PR and between b7b53c7 and 3f7c837.

📒 Files selected for processing (4)
  • contracts/OMN-9413.yaml
  • drift/dod_receipts/OMN-9413/dod-001/command.yaml
  • drift/dod_receipts/OMN-9413/dod-002/command.yaml
  • drift/dod_receipts/OMN-9413/dod-occ-pr-1094/command.yaml

📝 Walkthrough

Walkthrough

This PR introduces a Definition of Done (DOD) contract and evidence collection for ticket OMN-9413. It adds a contract specification file that documents regression-test requirements (node registration orchestrator auto-wiring to 7 topics) and evidence validation logic, plus three receipt files that record the passing execution status and grep-based validation outputs from those tests.

Changes

OMN-9413 Ticket Contract and Evidence

Layer / File(s) Summary
Contract specification
contracts/OMN-9413.yaml
Defines the OMN-9413 contract with schema versioning, ticket metadata, node registration orchestrator regression-test assertion, and DOD evidence items specifying integration test and CI/PR check commands along with grep assertions for expected PASS status and ticket/evidence IDs in drift receipts. Emergency bypass is disabled.
Evidence receipts
drift/dod_receipts/OMN-9413/dod-001/command.yaml, drift/dod_receipts/OMN-9413/dod-002/command.yaml, drift/dod_receipts/OMN-9413/dod-occ-pr-1094/command.yaml
Three command receipt records documenting successful execution of the contract's validation checks. Each receipt records the probe command, expected/actual output, PASS status, timestamp, commit SHA, runner/verifier identifiers, exit code, and PR number.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A contract takes shape, so clear and true,
With evidence receipts to see it through,
Seven topics wired, regression blessed—
The orchestrator passes every test! ✨

🚥 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 accurately summarizes the main change: adding contract and DoD receipts for a regression test related to OMN-9413. It is specific, clear, and directly corresponds to the changeset contents.
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-9413-occ-evidence

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

Existing receipts bound only to omnibase_infra PR #1634. Receipt-gate's
pr_ticket_mismatch requires at least one PASS receipt bound to this OCC PR's number.
jonahgabriel added a commit that referenced this pull request May 18, 2026
Existing receipt bound only to omnibase_core PR #1094. Receipt-gate
pr_ticket_mismatch requires at least one PASS receipt bound to this OCC PR.
@jonahgabriel
jonahgabriel enabled auto-merge (squash) May 18, 2026 03:06
@jonahgabriel
jonahgabriel merged commit fe18724 into main May 18, 2026
31 checks passed
@jonahgabriel
jonahgabriel deleted the jonah/omn-9413-occ-evidence branch May 18, 2026 03:06
jonahgabriel added a commit that referenced this pull request May 18, 2026
…idator workflow_call fix (#1089)

* evidence(OMN-11119): add contract and dod receipts for check-name validator workflow_call fix

Binds omnibase_core PR #1094 (extend validate-check-names.py to detect workflow_call
composite check names and emit WORKFLOW_CALL_COMPOSITE_NAME_MISMATCH).

* evidence(OMN-11119): add self-binding receipt for OCC PR #1089

Existing receipt bound only to omnibase_core PR #1094. Receipt-gate
pr_ticket_mismatch requires at least one PASS receipt bound to this OCC PR.
jonahgabriel added a commit that referenced this pull request Aug 30, 2026
… parse

Round 1 of dod-deploy-assessment was BLOCKed 3/3 by the contract-compliance
check, which EXECUTES dod_evidence rather than only shape-checking it. Two
distinct defects, both fixed here:

1. `grep -q` exits on first match and SIGPIPEs the upstream `base64 -d`. Under
   the runner's `pipefail` that surfaced as `Command failed (exit 141)` even
   for content that was present. Replaced with `grep -c`, which consumes the
   whole stream and still exits 1 on zero matches -- so the check stays
   falsifiable without the false RED.
2. The omnimarket check probed `?ref=dev` for a symbol that only lands when
   omnimarket#2225 merges -- but this contract is what unblocks #2225's own
   deploy-gate, so the two PRs deadlocked against each other. Rescoped to
   #2225's live file list (`pulls/2225/files`), the same shape OMN-16984 used.
   Still falsifiable: RED the moment that PR stops carrying the file.

The two omninode_infra checks stay pinned to `?ref=dev` and are genuinely GREEN
only because #1094 merged at 2026-08-30T17:22:24Z; both were RED before it.
All three verified locally against live GitHub (each prints 1, exit 0).

The kustomization check is deliberately separate from the manifest check: a
file committed but absent from the overlay's kustomization is never applied,
and a single check would read as done while nothing deploys.

Ticket: OMN-17210
jonahgabriel added a commit that referenced this pull request Aug 30, 2026
…uct PRs (#7736)

* evidence(OMN-17210): add a falsifiable deploy-scope DoD for both product PRs

The OMN-13317 autobind wrote only a `uv run pytest` behavior proof onto
contracts/OMN-17210.yaml. The deploy-gate correctly rejects that as
non-falsifiable on omnimarket#2225:

  DEPLOY GATE FAILED: PR touches runtime paths but no cited ticket has deploy
  DoD evidence. ... OMN-17210 [dod-occ-diff-derived-behavior-proof] REJECTED --
  no live-surface probe in command position (commands found: ['uv'])

pytest's exit status cannot depend on the state of any deployed or remote
surface, so it can never go RED for a deploy reason.

Adds `dod-deploy-assessment` with three checks, each putting a `gh api` read of
the LIVE dev branch in command position and grepping for a symbol that exists
nowhere on dev today -- so each is RED right now and only goes GREEN once the
corresponding PR actually lands:

- omnimarket#2225: `class HandlerReceiptGateProjectionRunner(BaseProjectionRunner)`
  on omnimarket dev. RED today -- node_projection_receipt_gate ships only the
  pure reducer and its handle_dict shim, no BaseProjectionRunner subclass.
- omninode_infra#1094: the savings writer Deployment's `python -m
  omnimarket.nodes.node_projection_savings.handlers.handler_savings` command
  line on omninode_infra dev. RED today -- the manifest does not exist there.
- omninode_infra#1094: the same manifest listed in
  k8s/onex-dev/runtime/kustomization.yaml, so a file landed without being wired
  into the overlay does not read as done. RED today -- that kustomization lists
  twelve runtime Deployments.

None reads back a receipt or contract this ticket's own PRs author, which is
the failure mode OMN-14505 added the falsifiability rule for.

Ticket: OMN-17210

* evidence(OMN-17210): make the deploy-scope checks pass live, not just parse

Round 1 of dod-deploy-assessment was BLOCKed 3/3 by the contract-compliance
check, which EXECUTES dod_evidence rather than only shape-checking it. Two
distinct defects, both fixed here:

1. `grep -q` exits on first match and SIGPIPEs the upstream `base64 -d`. Under
   the runner's `pipefail` that surfaced as `Command failed (exit 141)` even
   for content that was present. Replaced with `grep -c`, which consumes the
   whole stream and still exits 1 on zero matches -- so the check stays
   falsifiable without the false RED.
2. The omnimarket check probed `?ref=dev` for a symbol that only lands when
   omnimarket#2225 merges -- but this contract is what unblocks #2225's own
   deploy-gate, so the two PRs deadlocked against each other. Rescoped to
   #2225's live file list (`pulls/2225/files`), the same shape OMN-16984 used.
   Still falsifiable: RED the moment that PR stops carrying the file.

The two omninode_infra checks stay pinned to `?ref=dev` and are genuinely GREEN
only because #1094 merged at 2026-08-30T17:22:24Z; both were RED before it.
All three verified locally against live GitHub (each prints 1, exit 0).

The kustomization check is deliberately separate from the manifest check: a
file committed but absent from the overlay's kustomization is never applied,
and a single check would read as done while nothing deploys.

Ticket: OMN-17210

* evidence(OMN-17210): add deploy assessment receipt
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