feat(OMN-16677): expose the tier-0 local runtime harness as onex run

[jonahgabriel]

What

Registers onex run <workflow> on the packaged onex click group, so the tier-0
infra-free local runtime harness (OMN-13420) is reachable as a product surface instead
of only as an internal module path against a venv-relative interpreter.

Before: ./.venv/bin/python -m omnibase_core.runtime.harness.harness_cli delegation ...
After: onex run delegation ...

How

src/omnibase_core/runtime/harness/harness_cli.py's argparse core is refactored into
shared callables — run_harness_workflow (the run itself) and build_inference_adapter
(adapter selection, including the fail-loud VALIDATION_ERROR on under-specified
combinations) — plus a WORKFLOW_DEFAULT_PROMPTS map that both entry points read, so the
accepted workflow names and their default prompts cannot drift apart.

src/omnibase_core/cli/cli_run.py is the new click command: flag parsing only, then
hand-off to run_harness_workflow. python -m omnibase_core.runtime.harness.harness_cli
remains as a thin argparse shim over the same callable. One implementation of the run, no
parallel copy, no back-compat rename.

run-node (remote Kafka node dispatch) is not renamed or otherwise touched beyond one
line of help text on each command distinguishing local in-process harness (run) from
remote dispatch (run-node).

Diff shape

 src/omnibase_core/cli/cli_commands.py            |   5 +
 src/omnibase_core/cli/cli_run.py                 | 134 ++++++++
 src/omnibase_core/cli/cli_run_node.py            |   4 +
 src/omnibase_core/runtime/harness/harness_cli.py | 151 ++++++--
 tests/unit/cli/test_cli_run_harness.py           | 418 +++++++++++++++++++++++
 5 files changed, 685 insertions(+), 27 deletions(-)

Verification

• tests/unit/cli/test_cli_run_harness.py (418 lines, TDD-first, click CliRunner) asserts
  exit code, evidence-packet fields (bus_impl: EventBusInmemory, infra_free: true), the
  sea variant, UUID-only --correlation-id handling, the surviving python -m shim, and
  the OMN-13496 false-green negative control — --inference fixture with no
  --fixture-completion still raises VALIDATION_ERROR.
• Governed pre-push impacted-test selector run on the .201 serialized queue lane, no
  bypass flags (PREPUSH_FULL_SUITE, ENABLE_SMART_TESTS, PREPUSH_ALLOW_LOCAL_FULL_SUITE,
  --no-verify all unused). This branch's selection was the whole tests/ tree.
• origin/dev was merged up into this branch before the push so it carries the OMN-16297
  flaky-assertion fix (omnibase_core#1602, squash 918ba72e22612a6b0d36750f15f35d8308934dd5);
  without it the run could be refused by a sub-millisecond wall-clock assertion unrelated to
  this change.

OMN-16677

Evidence-Ticket: OMN-16677
Evidence-Source: OCC#7295

[coderabbitai]

Warning

Review limit reached

Next included review available in 52 minutes.

View limit details

Limit details: You’ve used the included review currently available. Your 130 included PR review attempts over the past 7 days set your current allowance at 1 review per hour.

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).

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 3f976ea9-016e-4eb1-b3e8-323688866390

📥 Commits

Reviewing files that changed from the base of the PR and between 918ba72 and c458ac1.

📒 Files selected for processing (5)

• src/omnibase_core/cli/cli_commands.py
• src/omnibase_core/cli/cli_run.py
• src/omnibase_core/cli/cli_run_node.py
• src/omnibase_core/runtime/harness/harness_cli.py
• tests/unit/cli/test_cli_run_harness.py

---

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