docs: close ledger #009 #010 #032 #041 #063

[BigSimmo]

Summary

Closes outstanding-issues ledger items with docs/decision records only (no application or RAG behavior changes):

• Bump lucide-react from 1.16.0 to 1.17.0 #9 — Keep GET /api/jobs as intentional administrator/ops listing; product UI uses /api/ingestion/jobs. Decision: docs/api-jobs-ops-surface.md.
• Improve Clinical KB design and RAG hardening #10 — Audited coming-soon placeholders in forms/favourites/presentation; all honest disabled / aria-disabled (or presentational toggles). No fake-interactive controls; leave unwired.
• Fix: Bind Next.js to 0.0.0.0 instead of localhost #32 — Reinforce governance ranking penalties/boosts as REFUTED guardrail in docs/rag-behaviour/*. Do not implement.
• Fix clinical dose-verification & safety gaps missed by early-merged #38 #41 — Brief: extend Easy Read/Standard Factsheets model; no second patient-facing mode (docs/factsheets-reading-model-brief.md).
• [WIP] Enhance clinical safety and governance measures #63 — Brief: Current Clinical Work product/privacy/persistence; no storage/UI (docs/current-clinical-work-brief.md).

Also fixes CI/PR hygiene found on review:

• Prettier formatting on touched docs (Static PR checks failure).
• Removes leftover PR_POLICY_BODY.md from merged docs: search performance review ledger (cross-mode) #1134 that had overwritten this PR description with unrelated search-performance text (this file is the temporary sync template for the correct body).

RAG impact: no retrieval behaviour change — docs/guardrail reinforcement and product briefs only; no edits under src/lib/rag/**, clinical-search, ranking, or eval fixtures.

Verification

• npm run verify:cheap (passed on tip 95d68c6b; 3318 tests)
• npx prettier --check on touched docs after format fix
• npm run check:branch-review-ledger
• UI verification not run: docs-only; no UI/routing/styling product changes
• Provider/eval gates not run: no retrieval/ranking/answer behavior change

Risk and rollout

• Risk: Low — documentation, ledger archive, and PR-body template hygiene
• Rollback: Revert the docs commits
• Provider or production effects: None

Notes

Recommended queue order gap closed after removing #063. Gated brief follow-ups (wire coming-soon features, Current Clinical Work storage/UI, second Factsheets mode, governance ranking) are intentionally not implemented.

[coderabbitai]

Warning

Review limit reached

@BigSimmo, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 10 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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 78008b90-db1f-40af-9861-937cca22b4ff

📥 Commits

Reviewing files that changed from the base of the PR and between de1a82b and 7c58302.

📒 Files selected for processing (13)

• PR_POLICY_BODY.md
• docs/api-jobs-ops-surface.md
• docs/branch-review-ledger.md
• docs/codebase-index.md
• docs/current-clinical-work-brief.md
• docs/factsheets-reading-model-brief.md
• docs/outstanding-issues.md
• docs/rag-behaviour/README.md
• docs/rag-behaviour/refuted-approaches.md
• docs/rag-behaviour/safeguards.md
• docs/site-map.md
• docs/wiring-conventions.md
• scripts/generate-site-map.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch cursor/ledger-009-010-032-041-063-519b

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

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

[github-actions]

CI triage

CI failed on this PR. Automated classification of the 2 failed job(s):

• Static PR checks — needs investigation: inspect the failing step and uploaded diagnostics; rerun only after classifying the cause.
• PR required — needs investigation: inspect the failing step and uploaded diagnostics; rerun only after classifying the cause.

Compared with main CI run #5327 (success).

Classification is evidence routing, not permission to ignore a failure. Exact quarantined Playwright identities remain governed by the flake ledger.