ci(OMN-13902): sibling-lock-refresh workflow (fan-out)

[jonahgabriel]

OMN-13902 — sibling-lock-refresh workflow (fan-out to omnibase_infra)

Fans out the proven canary workflow (omnimemory#400 — merged, all gates green
incl. Dep Provenance Gate) to omnibase_infra. Adds
.github/workflows/sibling-lock-refresh.yml: a daily (+ workflow_dispatch)
scheduled job that runs uv lock --upgrade-package for each omninode sibling
and opens a chore(deps): bot PR when uv.lock changes. Git/tag-pinned
siblings in [tool.uv.sources] are left untouched — uv lock --upgrade-package cannot move an immutable rev/tag — so the Dep-Provenance
state is preserved automatically with no per-repo tuning.

CI-only change: one workflow YAML file, no runtime contract, no deploy.

Supersedes the prematurely-closed first attempt (same branch), reopened now that
OMN-13902 carries dod_evidence via the OCC contract in OCC#3617.

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

Ref: OMN-13902

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 26 minutes

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

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 8d71836c-60a4-43e5-9181-1bf6a65ddf1f

📥 Commits

Reviewing files that changed from the base of the PR and between 25fcce5 and 31e2268.

📒 Files selected for processing (1)

• .github/workflows/sibling-lock-refresh.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch jonah/omn-13902-sibling-lock-refresh

---

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

[jonahgabriel]

Closing this fan-out PR as premature — the mechanism is proven and merged on the
omnimemory canary (omnimemory#400, all gates green incl. Dep Provenance Gate).

Fan-out to this repo is blocked out-of-order: its receipt-gate/occ-preflight
require OMN-13902 to carry dod_evidence (and heavy repos need an OCC companion),
but OMN-13902 is still Backlog. Correct sequence is: land canary (done) →
dod_evidence + Done on OMN-13902 → fan out with OCC companions. Deferring to that
mechanical follow-up rather than leaving a red PR. Branch preserved.

[jonahgabriel]

Auto-merged by merge-sweep | correlation_id: 5c2bab15-cf3a-40bc-bfce-513a1e8a6a04