Skip to content

OMN-9071: Enable full runtime cron verification - #1608

Merged
jonahgabriel merged 2 commits into
mainfrom
jonah/omn-9071-full-runtime-cron
May 20, 2026
Merged

jonahgabriel merged 2 commits into
mainfrom
jonah/omn-9071-full-runtime-cron

Conversation

@jonahgabriel

@jonahgabriel jonahgabriel commented May 19, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • Updates scripts/cron-contract-verify.sh so the cron tick invokes /onex:contract_sweep --mode runtime --full-runtime-verification instead of runtime mode without the full verification flag.
  • Adds a shell regression test that builds a temporary canonical clone, runs the cron wrapper in dry-run mode, and proves the full-runtime prompt is emitted without executing claude.

Verification

  • bash scripts/tests/test-cron-contract-verify.sh -> 3 passed, 0 failed.
  • Push preflight hooks passed for jonah/omn-9071-full-runtime-cron: mypy, pyright, ONEX validation, clean root directory, duplicate model filename check, Pydantic pattern validation, single class per file, enum governance, __all__ exports, and DoD evidence advisory.

OCC Evidence

  • Central OCC evidence files are intentionally not included in this product PR. They will be added separately in onex_change_control.

Summary by CodeRabbit

  • Chores
    • Enhanced contract verification process to utilize comprehensive runtime verification capabilities, replacing the previous narrower verification mode
    • Added automated regression tests for contract verification workflows to validate correct behavior during dry-run execution scenarios

Review Change Stack

Evidence-Ticket: OMN-9071
Evidence-Source: OCC#1206

@coderabbitai

coderabbitai Bot commented May 19, 2026 •

Copy link
Copy Markdown
📝 Walkthrough

Walkthrough

Updated scripts/cron-contract-verify.sh to use --full-runtime-verification flag for runtime contract sweep delegation. Added scripts/tests/test-cron-contract-verify.sh as a regression test that validates dry-run behavior using isolated Git clones and mocked claude binary.

Changes

Contract verification script update and test

Layer / File(s) Summary
Script update to full runtime verification
scripts/cron-contract-verify.sh
Comment documentation and PROMPT configuration now specify --full-runtime-verification flag for the /onex:contract_sweep delegation.
Regression test for dry-run behavior
scripts/tests/test-cron-contract-verify.sh
New test script with assertion helpers, cleanup and setup functions (canonical clone initialization and mocked claude binary), and main test case that validates dry-run output includes expected full runtime verification flags and excludes registration-only messaging and allowed-tools invocation.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 A script now sweeps with vigor bright,
Full runtime checks to set things right,
A test ensures no stone's unturned,
So contracts flow as they have earned! 🌙

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 14.29% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and specifically describes the main change: enabling full runtime verification for cron contract verification, which aligns with the core objective of updating the cron script to use --full-runtime-verification flag.
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.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.

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

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch jonah/omn-9071-full-runtime-cron

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

@github-actions
github-actions Bot enabled auto-merge May 19, 2026 16:14
@github-actions

github-actions Bot commented May 19, 2026 •

Copy link
Copy Markdown
Contributor

⚠️ Hostile Reviewer — DEGRADED (informational)

Blocking findings (critical/error): 0
Total findings: 0
Models succeeded: none

Note: All reviewer models failed or were unavailable. Degraded results are informational during the pilot phase (OMN-8524) and do not block merge. Error: cli_review exited non-zero (all models failed or binary error)


Gate semantics (pilot phase)

Verdict Meaning Blocks merge?
passed No critical/error findings No
blocked CRITICAL or ERROR findings found Yes
degraded All models unavailable (infra) No (pilot)

Powered by omniintelligence.review_pairing.cli_review — node-based adversarial review via HandlerLlmCliSubprocess (OMN-8524)

@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 `@scripts/tests/test-cron-contract-verify.sh`:
- Around line 79-87: The push command currently pushes the local branch named
"main" (git -C "${clone}" push -u origin main -q ...) which can fail if the
checked-out branch is "master"; update the push to push the current HEAD to the
remote main ref (use git -C "${clone}" push -u origin HEAD:main ...) so the
current branch (HEAD) is deterministically published as remote ref "main" and
avoids CI flakiness.
🪄 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: fe1dee9d-9ec4-4d05-b915-a6d5ebdd7b2f

📥 Commits

Reviewing files that changed from the base of the PR and between 3e4ed0c and 3b1c376.

📒 Files selected for processing (2)
  • scripts/cron-contract-verify.sh
  • scripts/tests/test-cron-contract-verify.sh

Comment thread scripts/tests/test-cron-contract-verify.sh
@github-actions
github-actions Bot added this pull request to the merge queue May 20, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to no response for status checks May 20, 2026
@jonahgabriel
jonahgabriel added this pull request to the merge queue May 20, 2026
Merged via the queue into main with commit 2ebfbed May 20, 2026
93 of 96 checks passed
@jonahgabriel
jonahgabriel deleted the jonah/omn-9071-full-runtime-cron branch May 20, 2026 15:11
jonahgabriel added a commit that referenced this pull request Jul 9, 2026
…1860)

## Summary

Phase 3 of OMN-13502 (epic OMN-13498, golden-chain de-fake) for the
omniclaude side of the flip.

- OMN-13500 (#1849) burned omniclaude's `no-faked-boundary` detector
self-scan down from 61 findings (55 `mock_assigned_to_boundary` + 6
`patch_httpx_egress`) to **zero**, verified live on this branch via `uv
run python -m
omnibase_core.validation.no_faked_boundary.runtime_no_faked_boundary src
tests` → `No faked-boundary violations found.`
- This PR drops `--report-only` from both surfaces that ran the
detector:
  - `.github/workflows/no-faked-boundary.yml` (CI mirror)
- `.pre-commit-config.yaml` `check-no-faked-boundary` hook (local
mirror)
- Job/hook name renamed from `"No Faked Boundary Gate (report-only)"` to
the bare `"No Faked Boundary Gate"` so it can become a dev
branch-protection required context **after** it lands and reports once
on a dev commit — required-context addition is a separate follow-up
step, not part of this PR, per the ordering constraint (a required
context that has never reported wedges every PR).

## DoD evidence

Ticket OMN-13502 carries dod_evidence from the parallel
omnibase_core/omnimarket legs of this same phase-3 flip (PRs #1377,
#1378, #1608, OCC receipts #3530, #3533, #3535, #3587). This PR is the
omniclaude leg of the same de-fake flip.

## Test plan

- [x] `uv run python -m
omnibase_core.validation.no_faked_boundary.runtime_no_faked_boundary src
tests` → 0 findings (confirms flip is safe)
- [x] `pre-commit run --all-files` — `check-no-faked-boundary` passes; 3
pre-existing/unrelated failures confirmed present identically on
`origin/dev` without this diff (Windows-path string in
`architecture-handshakes/validator-requirements.yaml`, cross-repo
`@main` ref in `call-occ-preflight.yml`, `hook-bits-drift` missing
sibling `omnibase_core` checkout in this worktree)
- [x] `uv run pytest tests/ -v -m "unit and not integration"` → 9103
passed, 26 skipped, 1 pre-existing failure
(`test_checkout_occ_contracts_shell_suite`, missing `gtimeout`/`timeout`
binary on this Mac — confirmed identical failure on `origin/dev` without
this diff)

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **Chores**
* Strengthened boundary-checking by making the related validation gates
enforce new findings (pre-commit and CI now fail builds instead of only
reporting).
* Improved CI reliability across varied runners with more consistent
dependency setup, Linux-specific readiness handling, and a more
controlled streaming-test service lifecycle.
* Enhanced security scanning by adjusting runner selection logic and
expanding secret-scan coverage for pull requests, plus safer handling of
privileged filesystem setup.
* Updated timeouts and checkout depth to make workflow execution more
consistent.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

Evidence-Source: OCC#3599
Evidence-Ticket: OMN-13502
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