chore(deps): bump omnibase-core to 0.46.13 (OMN-16677)

[onexbot-occ-writer]

Summary

Automated dependency bump triggered by a new release of omnibase_core (0.46.13).

• Updates uv.lock via uv lock --upgrade-package omnibase_core
• Updates pyproject.toml exact pin (==X.Y.Z) to match, when this repo pins that exactly
• No other source code changes

Cascade provenance (OMN-16286)

This PR carries no dedicated testing of its own beyond this repo's own
CI running against the new lockfile. Its cited evidence below is the
upstream release's own Evidence-Ticket/Evidence-Source pair, which
already proved the released package version -- reused honestly rather
than fabricated or exempted:

• Source repo: OmniNode-ai/omnibase_core
• Released version: 0.46.13

Triggered by

Release workflow: https://github.com/OmniNode-ai/omnibase_core/actions/runs/33081004459

Test plan

• CI passes (lockfile resolution is valid)
• Downstream tests pass with the new dependency version

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

[github-actions]

⚠️ Hostile Reviewer — DEGRADED (informational)

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

Note: All reviewer models failed or were unavailable. Degraded results are informational during the pilot phase (OMN-8468/OMN-8524) and do not block merge. Error: all review endpoints [192.168.86.201:8000 192.168.86.201:8000 ] unreachable — preflight short-circuit (no models available)

---

Gate semantics (pilot phase)

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

Powered by omniintelligence.review_pairing.cli_review — multi-model adversarial review (OMN-8468/OMN-8524)

[jonahgabriel]

Blocked on a real incompatibility the bump surfaced — filed as OMN-16761

This PR cannot land as-is. Diagnosis of run 33081139145, four distinct failures, one of them not mechanical.

Blocker — Tests (Split 4/15), job 98554099218 (OMN-16761)

Five failures in tests/unit/cli/test_onex_run.py, one root cause: omnibase_core 0.46.13 added a built-in onex run that shadows this repo's onex.cli entry point of the same name.

onex.cli extension 'run' conflicts with an existing command, skipping

onex run --help now resolves to core's tier-0 harness (Usage: onex run [OPTIONS] {delegation|sea}), not cli_node:run_node_by_name. The tests are correct and passed on 0.46.11; they assert this repo's documented onex run contract, which core has taken over.

Relevant history: OMN-8938 (Done, 2026-04-16) renamed core's onex run → onex node. This repo kept run as an alias pointing at the identical callable as node, and that alias was never retired. Core has now legitimately reused the freed name.

Resolution needs a decision (retire the alias here vs. rename core's command), so it is deliberately not being made inside a dependency pin-bump PR. Tracked in OMN-16761.

Mechanical, but not worth applying while the blocker stands

• Tests (Split 1/15) (98554099253) + runner-image-build-smoke — stale runner image identity: lock identity_digest is stale, shared_env_digest mismatch. Fix: scripts/ci/runner_image_identity.py --mode generate
• Tests (Split 11/15) (98554099796) — Fallback matrix drift detected. Fix: uv run python scripts/update_version_matrix.py
• Tests (Split 12/15) (98554099212) — test_seam_released_core_pin: omnibase_core.__version__='0.46.13' but fixture freezes '0.46.11'

All three are ordinary bump churn. Regenerating them now would leave a still-red PR open and would likely conflict with whoever lands the OMN-16761 fix, so they are left for that change to carry.

Status

Leaving this PR open and untouched. The three sibling cascade legs (omniclaude#2055, onex_change_control#7300, omniintelligence#856) are being handled separately; this one waits on OMN-16761.

Evidence-Ticket: OMN-16677