chore(deps, OMN-13902): refresh omninode sibling locks [bot]

[onexbot-occ-writer]

Automated sibling version-alignment (OMN-13902).

uv lock --upgrade-package refreshed the omninode sibling pins in
uv.lock to the latest in-range PyPI releases. Git/tag-pinned siblings
(see [tool.uv.sources]) were left untouched.

Opened automatically so stale-sibling-lock drift no longer requires a
manual repin ticket. Review the lock delta and merge on green CI.

Evidence-Ticket: OMN-13902
Evidence-Source: OCC#8563

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

---

Gate semantics (pilot phase)

Verdict	Meaning	Blocks merge?
passed	No critical/error findings	No
blocked	CRITICAL or ERROR findings found	Yes
degraded	Reviewer ran but every model failed mid-run	No (pilot)
infra_error	cli_review failed to run at all (install/crash) after 2 attempts	Yes

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

[onexbot-occ-writer]

No OCC evidence companion was minted for this PR.

this PR is already bound to OCC#8563; its evidence companion exists and nothing needs authoring

To clear this: Nothing to do — the companion already exists.

Reported by node_occ_companion_effect (decline code already_bound, OMN-16665). This decision was made against the PR's LIVE state at compute time, not at publish time — a green publisher job only means the command reached the broker.