chore(OMN-18010): post-release dev version bump to 0.4.301

[onexbot-occ-writer]

Summary

Automated post-release disarm step (OMN-18010, porting OMN-13912). Publishing v0.4.300 left dev's [project].version equal to the highest published tag, which ARMS the OMN-16344 release-identity gate (scripts/check_release_identity.py) against every subsequent dev PR that touches src/**.

This PR bumps [project].version to 0.4.301 and re-locks uv.lock, so the gate is disarmed by the same flow that armed it rather than by whichever unrelated PR trips it first.

Ticket

OMN-18010 — releases are cut on an explicit trigger; this is the one bump PR that follows a cut, not a per-merge one.

Triggered by

https://github.com/OmniNode-ai/omnimarket/actions/runs/37271669408

Test plan

• the release-identity gate is green on this PR (that IS the behaviour under test)
• CI passes (lockfile resolves)

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

Static architectural lint — no model inference (OMN-14176).

[github-actions]

✅ Hostile Reviewer — PASSED

Blocking findings (critical/error): 0
Total findings: 2
Models succeeded: qwen3-review,gpt-oss-review

---

Gate semantics

Verdict	Meaning	Blocks merge?
passed	>=2 models succeeded, no critical/error findings	No
blocked	CRITICAL or ERROR findings found	Yes
degraded	Fewer than 2 models succeeded (infra unavailable/timeout)	Yes (OMN-15110)

Powered by omniintelligence.review_pairing.cli_review — node-based adversarial review via HandlerLlmCliSubprocess (OMN-8524)