Repository navigation
chore(contracts): backfill ModelTicketContract for 50 done tickets [OMN-8637 wave 44] - #206
Merged
Merged
Conversation
…MN-8637 wave 44] Range: OMN-5598 - OMN-5651 Retroactive contracts for Done tickets completed in last 30 days.
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 3 minutes and 23 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the 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 configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (50)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
jonahgabriel
added a commit
that referenced
this pull request
Jun 11, 2026
…ults projection Central contract + dod_receipts for the P0.2b context-ROI experiment read loop: omnimarket node_projection_context_roi projection (PR #1178) and the omnidash /experiments hero+heatmap wiring (PR #206). - contracts/OMN-12955.yaml: 4 dod_evidence items (omnimarket, omnidash, deploy-assessment, occ-pr). - dod-omnimarket-pr: 8 golden-chain + dogfood tests, mypy strict, runtime sweep 299/299; PR #1178 head 8dbd829. - dod-omnidash-pr: 9 new tests, full suite 1259 passed, tsc/ESLint clean; PR #206 head 3533a6b. - dod-deploy-assessment: read-only .201 probe (executed) confirms the stability lane is up and the projection topic is unknown_topic pre-deploy; additive read-path PRs perform no live mutation; exact post-rebuild verification steps recorded for the batch rebuild agent. - dod-occ-pr: self-binding receipt. Receipt Honesty Gate + ticket-contract validation + yamlfmt all pass.
This was referenced Jun 11, 2026
jonahgabriel
pushed a commit
that referenced
this pull request
Jul 27, 2026
…nnable from the OCC clone The Contract Compliance Check executes every check_value with cwd = the OCC checkout (reference_dod_runner_workspace_mispointed). The original values ran `pytest tests/test_no_raw_prod_bypass_policy.py`, a path that exists only in omni_home — so the runner failed on a missing file, not on missing evidence. Repointed to quote-free gh probes against omni_home PR #206 and its head SHA; the RED/GREEN transcripts stay in probe_stdout and the evidence doc.
jonahgabriel
pushed a commit
that referenced
this pull request
Jul 27, 2026
…nnable from the OCC clone The Contract Compliance Check executes every check_value with cwd = the OCC checkout (reference_dod_runner_workspace_mispointed). The original values ran `pytest tests/test_no_raw_prod_bypass_policy.py`, a path that exists only in omni_home — so the runner failed on a missing file, not on missing evidence. Repointed to quote-free gh probes against omni_home PR #206 and its head SHA; the RED/GREEN transcripts stay in probe_stdout and the evidence doc.
jonahgabriel
pushed a commit
that referenced
this pull request
Jul 27, 2026
…nnable from the OCC clone The Contract Compliance Check executes every check_value with cwd = the OCC checkout (reference_dod_runner_workspace_mispointed). The original values ran `pytest tests/test_no_raw_prod_bypass_policy.py`, a path that exists only in omni_home — so the runner failed on a missing file, not on missing evidence. Repointed to quote-free gh probes against omni_home PR #206 and its head SHA; the RED/GREEN transcripts stay in probe_stdout and the evidence doc.
jonahgabriel
pushed a commit
that referenced
this pull request
Jul 27, 2026
…ith the OCC token
omni_home is a PRIVATE repo; onex_change_control is public and its CI
GITHUB_TOKEN cannot read it, so a cross-repo gh probe into omni_home fails the
Contract Compliance Check on token scope, not on missing evidence. Switched to
the established ${PR_NUMBER}/${REPO} template shape (same as OMN-15218), with
receipts recording the substituted omni_home #206 probes that were actually run.
The substantive proof stays where it is executable: the omni_home CI run of the
gate itself (No raw prod bypass, success on b56afb4f), plus the RED->GREEN
transcripts in probe_stdout and docs/evidence/2026-07-27-omn15243-stability-lane-gate.md.
This is a token-scope constraint, not a strengthening of the evidence.
jonahgabriel
pushed a commit
that referenced
this pull request
Jul 27, 2026
…nnable from the OCC clone The Contract Compliance Check executes every check_value with cwd = the OCC checkout (reference_dod_runner_workspace_mispointed). The original values ran `pytest tests/test_no_raw_prod_bypass_policy.py`, a path that exists only in omni_home — so the runner failed on a missing file, not on missing evidence. Repointed to quote-free gh probes against omni_home PR #206 and its head SHA; the RED/GREEN transcripts stay in probe_stdout and the evidence doc.
jonahgabriel
pushed a commit
that referenced
this pull request
Jul 27, 2026
…ith the OCC token
omni_home is a PRIVATE repo; onex_change_control is public and its CI
GITHUB_TOKEN cannot read it, so a cross-repo gh probe into omni_home fails the
Contract Compliance Check on token scope, not on missing evidence. Switched to
the established ${PR_NUMBER}/${REPO} template shape (same as OMN-15218), with
receipts recording the substituted omni_home #206 probes that were actually run.
The substantive proof stays where it is executable: the omni_home CI run of the
gate itself (No raw prod bypass, success on b56afb4f), plus the RED->GREEN
transcripts in probe_stdout and docs/evidence/2026-07-27-omn15243-stability-lane-gate.md.
This is a token-scope constraint, not a strengthening of the evidence.
jonahgabriel
added a commit
that referenced
this pull request
Jul 27, 2026
… to stability-class lanes (#5186) * evidence(OMN-15243): OCC companion — no-raw-prod-bypass gate extended to stability-class lanes Net-new files only: contracts/OMN-15243.yaml + 4 PASS DoD receipts covering the RED->GREEN transcript, the rule-11a .200 proof run, the non-vacuous-green probe, and the doctrine/mechanism coupling assertion. Product PR: OmniNode-ai/omni_home (branch jonah/omn-15243-no-raw-bypass-stability). * fix(OMN-15243): repoint OCC dod_evidence check_values at gh probes runnable from the OCC clone The Contract Compliance Check executes every check_value with cwd = the OCC checkout (reference_dod_runner_workspace_mispointed). The original values ran `pytest tests/test_no_raw_prod_bypass_policy.py`, a path that exists only in omni_home — so the runner failed on a missing file, not on missing evidence. Repointed to quote-free gh probes against omni_home PR #206 and its head SHA; the RED/GREEN transcripts stay in probe_stdout and the evidence doc. * fix(OMN-15243): make OCC check_values executable from the OCC clone with the OCC token omni_home is a PRIVATE repo; onex_change_control is public and its CI GITHUB_TOKEN cannot read it, so a cross-repo gh probe into omni_home fails the Contract Compliance Check on token scope, not on missing evidence. Switched to the established ${PR_NUMBER}/${REPO} template shape (same as OMN-15218), with receipts recording the substituted omni_home #206 probes that were actually run. The substantive proof stays where it is executable: the omni_home CI run of the gate itself (No raw prod bypass, success on b56afb4f), plus the RED->GREEN transcripts in probe_stdout and docs/evidence/2026-07-27-omn15243-stability-lane-gate.md. This is a token-scope constraint, not a strengthening of the evidence. * evidence(OMN-15243): add OCC self-bind receipt for PR #5186 and rebind hashes occ-preflight/eligibility requires at least one PASS receipt bound to the OCC PR itself (pr_number == 5186); without it the check reports 'no PASS receipt for one or more tickets binds to PR #5186'. Adds occ-self-bind-pr-5186 and rebinds every receipt to the post-yamlfmt contract bytes. --------- Co-authored-by: Jonah Gray <jonah.neugass@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Retroactive backfill of for Done tickets OMN-5598 - OMN-5651.
Part of OMN-8637. These tickets completed in last 30 days — contracts enable historical DoD verification.
Wave 44