Repository navigation
OMN-9071: Enable full runtime cron verification - #1608
Conversation
📝 WalkthroughWalkthroughUpdated ChangesContract verification script update and test
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
|
| 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)
There was a problem hiding this comment.
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
📒 Files selected for processing (2)
scripts/cron-contract-verify.shscripts/tests/test-cron-contract-verify.sh
…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
Summary
scripts/cron-contract-verify.shso the cron tick invokes/onex:contract_sweep --mode runtime --full-runtime-verificationinstead of runtime mode without the full verification flag.claude.Verification
bash scripts/tests/test-cron-contract-verify.sh-> 3 passed, 0 failed.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
onex_change_control.Summary by CodeRabbit
Evidence-Ticket: OMN-9071
Evidence-Source: OCC#1206