[jonahgabriel]

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-Source: OCC#6647
Evidence-Ticket: OMN-13902

[coderabbitai]

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)

• uv.lock is excluded by !**/*.lock

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: d8f68ba1-47a5-49b7-8e71-c200c96291f6

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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

[github-actions]

❓ Hostile Reviewer — UNKNOWN

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

---

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 — node-based adversarial review via HandlerLlmCliSubprocess (OMN-8468/OMN-8524)

[jonahgabriel]

Closing in favor of tomorrow's fresh sibling-lock-refresh run rather than continuing to patch this PR.

Root-cause update (thanks omn16140-fix-1): the receipt-gate identity-binding axis needs the ticket ref in the branch name OR a commit message — not the Evidence-Ticket trailer (that was the original OMN-16140 proposal but is circular and got rejected). This PR's title now carries OMN-13902 (OMN-16159), but its single commit's message doesn't, and amending it locally to add the ref hits an unrelated, pre-existing failure — the ONEX Node Migration Vendor Sync Check pre-commit hook reports real omnibase_infra/omnimarket migration-vendor drift (node_hook_event_capture) on this branch's stale base, unrelated to this PR's uv.lock-only diff. Forcing the amend through with --no-verify is against the hard no-bypass rule, and fixing the drift is out of scope here.

sibling-lock-refresh.yml runs daily (06:17 UTC) and will open a fresh PR tomorrow with a new uv.lock diff. Once the title-fix PR (#2781) merges, that fresh PR's title will already carry the ticket ref; the branch/commit-message axis still needs a template fix (tracked as an addendum on OMN-16159) plus OMN-16140 landing on omnibase_core dev before daily bot PRs pass unattended. Evidence trail preserved (Evidence-Source: OCC#6647, onex_change_control), not superseded.