OMN-11011 classify package migrations

[jonahgabriel]

Evidence-Source: OCC#1072
Evidence-Ticket: OMN-11011

Summary

• Classifies the OMN-11011 omnimarket package migrations after generated-tree exclusion.
• Documents that nightly_loop_decisions, nightly_loop_iterations, and review_bot_bypass_log each have exactly one scanned omnimarket node migration and require no suppressions or repairs.
• Adds a regression test for the local package migration ownership paths.

Evidence

• uv run pytest tests/test_migration_ownership_omn11011.py -q
• uv run ruff check tests/test_migration_ownership_omn11011.py
• uv run pytest tests/test_golden_chain_duplication_sweep.py -q
• $OMNI_HOME/onex_change_control/.venv/bin/check-migration-conflicts --repos-root $OMNI_HOME --repos omnibase_core omnibase_infra omniclaude omnidash omniintelligence omnimarket omnimemory onex_change_control --suppressions-file $OMNI_HOME/onex_change_control/migration_conflict_suppressions.yaml

Notes

• Full canonical .git repo scan still reports unrelated schema_migrations and plan_entitlements conflicts outside the OMN-11011 ownership fence; captured in docs/evidence/omn-11011-migration-package-classification.md.
• No dashboard, runtime, node_service_registry, deploy, restart, or migration DDL changes.
• Central OCC evidence: evidence(OMN-11011): bind package migration classification onex_change_control#1072

[coderabbitai]

Warning

Rate limit exceeded

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

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ 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: 5ea6dd05-7f24-4999-af45-33085bfca1f9

📥 Commits

Reviewing files that changed from the base of the PR and between 2a2be49 and 2840a54.

📒 Files selected for processing (2)

• docs/evidence/omn-11011-migration-package-classification.md
• tests/test_migration_ownership_omn11011.py

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch jonah/omn-11011-schema-classify-package-migrations

---

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

[github-actions]

✅ Architectural Review — PASSED

Errors: 0
Warnings: 0

What this checks

Rule	Description
ARCH-TOPIC-001	No hardcoded Kafka topic strings in handler code
ARCH-DI-001	No event_bus=None bypass
ARCH-DI-002	No direct Handler instantiation outside workflow_runner/adapters
ARCH-DI-003	No reinvented DI containers
ARCH-TOPIC-002	contract.yaml topics follow `onex.{cmd

---

No architectural violations found.

Powered by node_pr_review_bot

[github-actions]

✅ PR Review Bot — CLEAN

Findings: 0
Run ID: ``

Note: Reviewer models are running as stubs (OMN-7969–OMN-7972 pending). Architectural findings from Phase 1 (arch-lint) are the authoritative signal until model handlers land.

---

Verdict semantics

Verdict	Meaning
clean	No blocking findings
risks_noted	Findings noted; threads passed verification
blocking_issue	MAJOR/CRITICAL findings not resolved — do not merge

Powered by node_pr_review_bot — FSM pipeline with multi-model review fan-out

[github-actions]

⚠️ 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)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud