docs: record the landed X3 coverage-gate review and capture its two follow-ups

[BigSimmo]

Summary

Two append-only memory records left over from the X3/#86 coverage-gate extraction (PR #1454, squashed as 102bb1f). Bundled into one PR per AGENTS.md § "PR bundling" — both are low-risk docs-only records, each in its own separately revertible commit.

• docs(ledger): record the landed X3 coverage-gate review. Appended with npm run ledger:append (never hand-written), keyed to the squash commit 102bb1f so ledger:lookup can resolve it. This row was deliberately held back while PR refactor(rag): extract evidence coverage gate #1454 was open: pushing a ledger-only tip would have cancelled that PR's in-flight CI run and marked every other open PR behind, which AGENTS.md prohibits. Now that refactor(rag): extract evidence coverage gate #1454 has merged, recording it is harmless.
• issues: capture the two follow-ups the extraction surfaced.
  • #086 updated in place, not duplicated — records that the coverage gate shipped, and names rag-hydration.ts as the next X3 unit because it re-homes the five rag.ts-only runtime symbols (measureSearchPhase, attachDocumentRankingMetadata, selectRankedRetrievalResults, attachPageVisualEvidence, applySecondStageRerankIfNeeded) that forced prepareCoverageGateResults to stay behind. That dependency was the one piece of engineering judgement from refactor(rag): extract evidence coverage gate #1454 not written down anywhere.
  • #145 (new) — an operator branch sync landing on a head whose CI is still running cancels a near-complete run. Observed three times in ~20 minutes on PR refactor(rag): extract evidence coverage gate #1454 (d49ac0f, 6de2bf5, d9598b7), cancelling Build + Unit coverage each time so no run finished and armed auto-merge never fired. The existing anti-churn rule covers only your own pushes, not syncs — which is the case that actually recurs. Explicitly distinguished from #095 (cancelled-job reporting, which worked correctly here), #129 and #116.

No source, test, config, or workflow file is touched.

Verification

• npm run verify:cheap

During development, use npm run verify:cheap as the faster iteration gate before the final PR-local preflight.

• npm run verify:ui when UI, routing, styling, browser behavior, reduced-motion, or forced-colors behavior changed
• npm run verify:release before release or handoff confidence claims

For retrieval, ranking, selection, chunking, source/citation rendering, or answer-contract changes, verify:pr-local runs eval:rag:offline automatically. Run the offline command directly during iteration before spending a live eval.

• npm run eval:retrieval:quality (must stay 36/36) when retrieval, ranking, selection, chunking, or scoring behavior changed — CI cannot run it (needs live keys), so run it locally and paste the summary. A metadata/governance-weighting change once buried correct docs (recall 1.0→0.76) and only this eval caught it.
• npm run eval:rag -- --limit 15 + npm run eval:quality -- --rag-only when answer generation, the synthesis prompt, or answer post-processing changed (grounded-supported must not drop; citation-failure 0)
• npm run check:production-readiness when clinical workflow, privacy, environment, Supabase, source governance, or deployment behavior changed
• npm run check:deployment-readiness when deployment startup, hosting, or rollout behavior changed

UI verification not run: docs-only diff, no UI, routing, styling, browser, reduced-motion, or forced-colors surface touched.

Verification not run (provider-backed): eval:retrieval:quality, eval:rag, eval:quality --rag-only, check:production-readiness, check:deployment-readiness — all call live OpenAI/Supabase, none is relevant to a docs-only diff, and none was run. No live evaluation, canary, ingestion, deployment, or release operation occurred.

Gates run

Command	Exit	Decisive output
npm run check:outstanding-issues	0	Outstanding-issues guard passed: 143 rows (70 open, 73 archived), unique ids, next-id=146 above the highest, no merge driver.
npm run check:branch-review-ledger	0	Branch review ledger guard passed: 124 live table records + 1206 archived …, ledger merge active, six cells each, no conflict markers, mojibake, heading records, or duplicates.
npm run format:check	0	All matched files use Prettier code style!
npm run verify:cheap	0	Test Files 436 passed (436) / Tests 4574 passed | 4 skipped (4578); docs link check passed: 1406 repo path references resolve; docs script-ref check passed: 397 npm-run reference(s) resolve to real scripts
git diff --check	0	no whitespace errors

Risk and rollout

• Risk: MINIMAL. Two append-only memory records; no executable code path, schema, config, or workflow is touched. The one non-obvious hazard is docs/outstanding-issues.md having no merge driver by design (#133), so an overlapping edit conflicts loudly — resolve by rebuilding from origin/main and re-applying only these rows, never by taking one side wholesale.
• Rollback: git revert either commit independently; they share no file.
• Provider or production effects: None. GitHub was used only to fetch main, push this branch, and open this PR.

Notes

• docs/branch-review-ledger.md remains append-only: no existing row was edited or deleted, and the new row was generated by ledger:append rather than hand-written, so it carries a resolvable 40-char HEAD.
• The branch name is reused but this is a new PR: the previous PR on this name merged and the remote branch was deleted, so per AGENTS.md the follow-up restarts from the latest main rather than stacking on merged history. The branch was recreated from origin/main at 102bb1f and carries only these two commits.
• #145 deliberately does not recommend disabling cancel-in-progress — superseded runs should still be cancelled; the cost is in when a sync lands, not in the cancellation policy.

RAG impact: no retrieval behaviour change — docs-only records, no src/lib/rag/** file touched

---

Generated by Claude Code

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

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: f73cd3c2-dd07-46d7-b0ca-fbc1f8909099

📥 Commits

Reviewing files that changed from the base of the PR and between 9e1d9cf and fdd7c95.

📒 Files selected for processing (2)

• docs/branch-review-ledger.md
• docs/outstanding-issues.md

---

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

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit:2d47dcb6df

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".