Skip to content

chore(OMN-10474): add quality scoring coverage receipts - #622

Merged
jonahgabriel merged 1 commit into
mainfrom
jonah/omn-10474-quality-scoring-receipts
May 1, 2026
Merged

jonahgabriel merged 1 commit into
mainfrom
jonah/omn-10474-quality-scoring-receipts

Conversation

@jonahgabriel

@jonahgabriel jonahgabriel commented May 1, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Validation

  • uv run validate-yaml contracts/OMN-10474.yaml — pass
  • uv run python - <<'PY' ... ModelDodReceipt.model_validate(...) ... PY — 3 receipts valid
  • uv run python -m omnibase_core.validation.receipt_gate_cli --pr-body '' --pr-title 'test(OMN-10474): add golden chain coverage for node_quality_scoring_compute' --contracts-dir contracts --receipts-dir drift/dod_receipts --current-repo omnimarket --current-pr-number 497 --pr-author jonahgabriel — pass

Related: OmniNode-ai/omnimarket#497

@coderabbitai

coderabbitai Bot commented May 1, 2026

Copy link
Copy Markdown

Warning

Rate limit exceeded

@jonahgabriel has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 43 seconds before requesting another review.

To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing.

⌛ How to resolve this issue?

After the wait time has elapsed, 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 have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: cd15cab9-ccd9-40ca-bf97-3e67e31054b5

📥 Commits

Reviewing files that changed from the base of the PR and between cf06755 and 364f99f.

📒 Files selected for processing (4)
  • contracts/OMN-10474.yaml
  • drift/dod_receipts/OMN-10474/dod-001/command.yaml
  • drift/dod_receipts/OMN-10474/dod-002/command.yaml
  • drift/dod_receipts/OMN-10474/dod-003/command.yaml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch jonah/omn-10474-quality-scoring-receipts

Review rate limit: 0/5 reviews remaining, refill in 43 seconds.

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

@jonahgabriel
jonahgabriel enabled auto-merge May 1, 2026 17:25
@jonahgabriel
jonahgabriel added this pull request to the merge queue May 1, 2026
Merged via the queue into main with commit dcd9954 May 1, 2026
29 checks passed
@jonahgabriel
jonahgabriel deleted the jonah/omn-10474-quality-scoring-receipts branch May 1, 2026 18:45
jonahgabriel added a commit that referenced this pull request May 13, 2026
…r 10940/10941/10949

- Add contracts for OMN-10936 (reviewdog-caller omniclaude), OMN-10942 (contract routing policy),
  OMN-10944 (dashboard projection API contract)
- Update OMN-10949 contract to cover infra PR #1588 and market PR #622 in addition to market #616
- Fix contract_sha256 in OMN-10940 receipts (pr-1580, pr-1586) — contract was updated with
  pr-1586 evidence item, changing the hash
- Add contract_sha256 to OMN-10941 pr-1587 receipt (was missing)
- Update OMN-10949 pr-616 receipt contract_sha256 to reflect expanded contract
- Add receipts: OMN-10936/pr-1582, OMN-10942/pr-621, OMN-10944/pr-620, OMN-10949/pr-1588, OMN-10949/pr-622
jonahgabriel added a commit that referenced this pull request May 14, 2026
…and receipt bundle for 6 tickets (#999)

* contract(OMN-10940,OMN-10941): add OCC contracts and receipts for infra PRs 1586 and 1587

- OMN-10940: add dod-omnibase-infra-pr-1586 evidence binding PR #1586 (E2E
  golden-chain task-delegated event test) to the OMN-10940 contract
- OMN-10941: new contract + receipt for PR #1587 (max_tokens propagation
  regression tests)

Both receipts are required for the receipt-gate Evidence-Source check on
PRs 1586 and 1587.

* contract: add OMN-10936/10942/10944 contracts + fix receipt hashes for 10940/10941/10949

- Add contracts for OMN-10936 (reviewdog-caller omniclaude), OMN-10942 (contract routing policy),
  OMN-10944 (dashboard projection API contract)
- Update OMN-10949 contract to cover infra PR #1588 and market PR #622 in addition to market #616
- Fix contract_sha256 in OMN-10940 receipts (pr-1580, pr-1586) — contract was updated with
  pr-1586 evidence item, changing the hash
- Add contract_sha256 to OMN-10941 pr-1587 receipt (was missing)
- Update OMN-10949 pr-616 receipt contract_sha256 to reflect expanded contract
- Add receipts: OMN-10936/pr-1582, OMN-10942/pr-621, OMN-10944/pr-620, OMN-10949/pr-1588, OMN-10949/pr-622

* contract(OMN-10949): add deploy evidence item + update receipt hashes

- Add deploy-evidence-pricing-version dod_evidence item to satisfy deploy-gate
  (pricing_manifest_version is additive schema field, no runtime restart needed)
- Update contract_sha256 in all OMN-10949 receipts (pr-616, pr-1588, pr-622) to
  reflect updated contract hash

* contract: add OCC self-binding receipts (pr-999) + fix all contract_sha256 hashes

- Add dod-occ-pr-999 evidence items to all 6 ticket contracts (OMN-10936/10940/10941/10942/10944/10949)
- Create dod-occ-pr-999/command.yaml self-binding receipts for each ticket
- Update all downstream receipt contract_sha256 fields to reflect updated contract hashes
- Fixes OCC eligibility pr_ticket_mismatch failure (receipts now bind to OCC PR #999)

* receipt(OMN-10949): add deploy-evidence-pricing-version receipt for deploy-gate

* fix: add headRefName to probe_stdout in OMN-10942/OMN-10944 receipts (CR review)

* ci(OMN-10940): suppress delegation_events migration name conflict

The Migration Conflict Check on PR #999 flagged delegation_events as a
NAME_CONFLICT between omnibase_infra/078_create_delegation_events.sql
(Postgres projection, 22 cols, UUID PK) and
omniclaude/001_create_delegation_tables.sql (SQLite hook-side capture,
15 cols, INTEGER PK).

Different databases, different access patterns. The omnibase_infra side
is the canonical projection consumed by HandlerProjectionDelegation from
onex.evt.omniclaude.task-delegated.v1 (OMN-10526). The omniclaude side
is the local hook-side store pinned to the projection contract
(OMN-10604). Neither shares a Postgres instance with the other.

Suppress the conflict using the existing schema_evolution reason — the
same pattern already used for llm_call_metrics and savings_estimates,
which have an identical infra-vs-omniclaude split.

No code changes; this is a CI suppressions update only.
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