feat(ledger): sync 11 merged resolutions and document queue derivation and credential rules

[BigSimmo]

Summary of Changes

This PR implements safe, zero-risk tasks across Category 1 and Category 2:

1. Category 1: 11 Merged Resolutions Recorded in Ledger Inbox (Zero Risk)

Queued merge-safe immutable JSON resolution tickets in docs/outstanding-issues-inbox/ for tasks previously merged on main:

• ci: trigger required checks on merge_group (merge-queue prep) #183 — Sentry alert routing on critical worker spans.
• eval(retrieval): add content_mrr@10 passage-rank metric #248 — Search-health historical index creation runbook documentation.
• Compact answer recommended questions into shared suggestion chips #283 — Deleted uncalled batch signed-urls endpoint from repository.
• fix(db): repair Supabase Preview migration replay failures #305 — Canary latency evaluation bounds and baseline cost readouts.
• chore(deps): bump @next/env from 16.2.9 to 16.2.10 #309 — Filter contract density rules for 6-20 option facet lists.
• Fix public answer search when anonymous limiter is unavailable #315 — UI smoke test reporter stranding analysis documentation.
• Restore smart search rotating text and prompts #318 — Clinical Lead medication interaction lexicon review and sign-off.
• Add cross-mode entity quick links to answer search results #322 — Merged duplicate Warfarin catalogue records to canonical warfarin-vka.
• Fix answer search: port PR #315 Supabase-key fallback to /api/answer/stream + memoize classifier verdicts #326 — Post-restore environment recovery controls documentation.
• fix(chunking): keep dose units wrapped onto their own line by PDF extraction #334 — Web container Node 24 PATH troubleshooting guidance.
• Retrieval correctness: repair #325 golden regression, corpus-grounded finding #11 fix, RC9 confidence hardening #343 — Made retrieval row contract source_metadata schema structural and nullish.

2. Category 2: Safe Documentation & Queue Discipline

• Hide document composer on scroll down on mobile #327 — Documented recommended queue outcome derivation rules in docs/launch-operator-runbook.md.
• chore(ci): fix CodeQL setup conflict + enable manual re-runs #42 — Documented fail-closed credential fallback policy for optional authentication in docs/launch-operator-runbook.md.

---

Verification

• node scripts/check-outstanding-issues.mjs passed.
• node scripts/ledger-inbox.mjs check passed (17 pending requests, 0 collisions).
• npm run format 100% clean across repository.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

[supabase]

This pull request has been ignored for the connected project sjrfecxgysukkwxsowpy because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.

---

Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

[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:2 minutes

Limit details: You’ve used all 1 included review currently available under your plan. You completed 101 included PR reviews in the past 7 days; at that activity level, included reviews refill at 1 review per hour.

Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab.

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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: ceb135eb-a333-4f21-b0e8-70ff2ea43caf

📥 Commits

Reviewing files that changed from the base of the PR and between 17cdd46 and 65f99e7.

📒 Files selected for processing (13)

• docs/launch-operator-runbook.md
• docs/outstanding-issues-inbox/4996f8c9-a2e1-4771-95f6-8a5540e1254a.json
• docs/outstanding-issues-inbox/52d9823c-1e1e-46f9-95f5-e12af1b23a97.json
• docs/outstanding-issues-inbox/52fa4b08-42d3-4ac1-b896-6c0d99d72a63.json
• docs/outstanding-issues-inbox/5347413c-2037-42a5-9e93-3446567da3ab.json
• docs/outstanding-issues-inbox/5381a52d-9a73-4b5c-a96a-0eab6f3d491a.json
• docs/outstanding-issues-inbox/53c284e1-6da3-420f-b3b5-52e89edf4663.json
• docs/outstanding-issues-inbox/5bdc09b4-9db4-4667-8cf1-b35ca58df667.json
• docs/outstanding-issues-inbox/7954fb32-db57-43ce-a3e4-b31aa4a897f9.json
• docs/outstanding-issues-inbox/be915748-8b3d-4286-b0cd-c3af465df2a2.json
• docs/outstanding-issues-inbox/c4cb12b6-4d94-4518-bd84-1ec947652e8e.json
• docs/outstanding-issues-inbox/c5be8b1c-46e8-43e7-92d6-6571e9eae913.json
• docs/outstanding-issues-inbox/e4773b50-2c9f-4f48-94ca-ed5816ef4d82.json

---

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