fix(OMN-14560): wire the omnimarket drift guard into cli_node.py

[jonahgabriel]

Summary

OMN-14560: the onex node/onex run dispatch path (cli_node.py) has ZERO
drift-guard wiring -- the identical gap OMN-14531 (#2291) fixed for
onex skill (cli_skill.py), flagged there as a known out-of-scope
follow-up. Before this fix, a machine with a canonical $OMNI_HOME/omnimarket
clone but omnimarket drifted/absent from the venv got a bare
Unknown node '<name>' from run_node_by_name -- no pointer to the actual
cause or the repair command.

Mirrors OMN-14531's fix exactly, reusing the same
omnimarket_drift_guard.check_omnimarket_drift() helper (no duplicated
logic):

1. Added --omni-home, bound to the $OMNI_HOME envvar (same pattern as
   cli_skill.py).
2. Call check_omnimarket_drift() at the top of run_node_by_name, before
   _resolve_packaged_contract, converting OmnimarketDriftError to a
   click.ClickException.

onex node and onex run are both [project.entry-points."onex.cli"]
aliases for the same run_node_by_name function, so one wiring point fixes
both dispatch surfaces.

Stack status

#2291 / OMN-14531 has merged to dev; this PR is now rebased to a single top commit on current dev and the diff is limited to cli_node.py, tests/unit/cli/conftest.py, and tests/unit/cli/test_cli_node.py.

RED -> GREEN evidence (dod_evidence)

New test_drift_guard_fires_before_unknown_node_lookup in
tests/unit/cli/test_cli_node.py:

• RED (stashed the cli_node.py fix, kept the test): all 8 tests in the
  file error out -- AttributeError: <module cli_node> has no attribute 'check_omnimarket_drift' (proves the pre-fix module has zero guard
  wiring for the fixture/test to even attach to).
• GREEN (fix restored): 8/8 pass. The new test drives the exact
  OMN-14531 regression shape (canonical clone present, omnimarket not
  installed from git) through the CLI and asserts the loud
  OmnimarketDriftError message fires before node resolution ever runs,
  instead of the CLI's formatted Unknown node '<name>'. error.

Wiring the guard surfaced the same non-hermeticity gap OMN-14531 had to
guard against in test_cli_skill.py, but here across three files that all
reach run_node_by_name (test_cli_node.py, test_cli_node_receipt.py,
test_onex_run.py -- the last invokes it via the onex run alias through
the full cli group). Added a shared tests/unit/cli/conftest.py autouse
fixture (neutralize + delenv OMNI_HOME) instead of duplicating a
file-local fixture three times.

Manual repro against the real onex node/onex run CLI on this
operator's actually-drifted venv (omnimarket absent, canonical clone
present):

$ uv run onex node definitely_not_a_real_node
Error: omnimarket is NOT INSTALLED from git in this interpreter (absent, or
installed from PyPI/a non-VCS source), but a canonical clone exists at
$OMNI_HOME/omnimarket (HEAD 48c03808155e). 'onex skill'/'onex run' dispatch
for market-provided nodes (e.g. node_aislop_sweep) will fail with 'Unknown
node'. Repair with: scripts/install-node-skill-package.sh --execute (or
scripts/check-omnimarket-venv-drift.sh --repair). See
docs/runbooks/node-skill-package-install.md.
exit 1

$ uv run onex run definitely_not_a_real_node
(identical output -- same underlying function via the "run" alias)

Local gates: ruff format --check / ruff check / mypy clean on touched
files; full pre-commit run clean; tests/unit/cli/ full suite: 342
passed, 19 skipped (pre-existing omnimarket-not-in-CI-venv skips,
unrelated).

OCC

Central OCC companion is being authored by Codex after #2291 landed and this branch was cleaned to a one-commit diff.

Evidence-Source: OCC#4104
Evidence-Ticket: OMN-14560
Evidence-Commit: db334ebb3298811dcdea8f7cf3dd7c9bd4e2eb1c

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 35 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: f18c0dac-e7d1-42c7-a9c8-0e9f80454477

📥 Commits

Reviewing files that changed from the base of the PR and between 525efba and d3cf8ce.

📒 Files selected for processing (3)

• src/omnibase_infra/cli/cli_node.py
• tests/unit/cli/conftest.py
• tests/unit/cli/test_cli_node.py

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch jonah/omn-14560-cli-node-drift-guard

---

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