docs(issues): capture site-audit + measurement follow-ups (#012–#017)

[BigSimmo]

Summary

Docs-only. Records the follow-ups surfaced by the 2026-07-21 site-audit + bundle/measurement pass into the durable docs/outstanding-issues.md ledger so they survive session context reset. No source, RAG, clinical, or config changes — a single markdown file.

Renumbered after merging main: main added its own #011 (auth DB-connection allocation) via a separate ledger update, so these follow-ups were shifted from #011–#016 to #012–#017 and the next-id marker to 018. main's #011 is kept intact; no other ledger rows changed.

Six new rows (#012–#017), all P3:

• Align project dependencies and cleanup stale branches #12 — Slim the lazy cross-mode differentials chunk. Notably, I verified the 860 KB differentials snapshot is not an initial-bundle leak — cross-mode-links.tsx:150 loads cross-mode-differentials.ts via a dynamic import(), so it's correctly code-split into a lazy async chunk. The remaining opportunity is that the lazy chunk still pulls the full snapshot to build a tiny catalog; a precomputed index would slim it (M-effort). This corrects a misread earlier in the audit.
• [codex] Clinical KB cleanup readiness #13 — Route-chunk + dev-only mockup catalogue JSON weight (specifiers ~180 KB, forms ~132 KB, formulation ~52 KB; *-mockups.tsx chunks).
• Clean stale frontend identity and CSS #14 — Realize the next/image win on Supabase signed previews (the perf(ui): content-first detail pages + loading & motion quick wins #1024 images config is inert until previews move off raw <img>).
• Normalize formatting line endings #15 — Content-first fallback regression tests (CodeRabbit follow-up on perf(ui): content-first detail pages + loading & motion quick wins #1024).
• Document npm optional dependency tree noise #16 — "Big but not easy" structural + motion perf (PPR/static shells given app-wide dynamic rendering, sidebar grid-template-columns animation, Therapy Compass JSON defer, dialog dynamic imports).
• Bump @types/node from 25.9.1 to 25.9.2 #17 — Field Web-Vitals baseline via live Lighthouse (in-sandbox prod vitals were blocked on Supabase secrets; dev-mode CLS measured excellent at 0.00–0.04).

RAG impact: no retrieval behaviour change — docs-only, no retrieval/ranking/selection/eval files touched.

Verification

• npm run verify:pr-local
  • Verification not run: docs-only change (a single markdown ledger file). Formatted with Prettier so format:check passes; no code, tests, or config touched. The merge from main also carries its own already-merged changes (eval-canary workflow + branch-review-ledger), which are no-ops relative to main.

Risk and rollout

• Risk: None — documentation only.
• Rollback: revert the ledger commit.
• Provider or production effects: None.

Notes

• Origin: full-site "big easy wins" audit → shipped quick wins in perf(ui): content-first detail pages + loading & motion quick wins #1024 → measurement pass (build:analyze + Turbopack verification, which found the fix already merged as fix(ui): correct file:disabled variant order so the dev server compiles #1026). This PR banks the remaining, deliberately-deferred follow-ups so the audit doesn't evaporate.

🤖 Generated with Claude Code

https://claude.ai/code/session_01UbhUVWVJRwDibC2YtJ6aRX

Summary by CodeRabbit

• Documentation
  • Updated the outstanding-issues tracker with additional newly documented items (#011–Bump @types/node from 25.9.1 to 25.9.2 #17).
  • Advanced the issue numbering to keep the tracker in sync with the latest additions.
  • Included follow-ups covering auth database connection handling, search-related behavior, image optimization, performance and bundle-size considerations, and real-world Web Vitals measurement via Lighthouse.

[coderabbitai]

📝 Walkthrough

Walkthrough

Updates the outstanding-issues ledger by advancing the next issue ID to 018 and adding open items #011–#017.

Changes

Outstanding issues ledger

Layer / File(s)	Summary
Update issue ledger docs/outstanding-issues.md	Advances the issues:next-id marker to 018 and adds seven open-item records covering authentication allocation, payload and chunk sizing, image optimization, fallback tests, deferred performance work, and Web Vitals measurement.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• BigSimmo/Database#1046: Updates the same issue ledger counter and adds the authentication DB-connection allocation entry.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly summarizes the docs-only ledger update and the site-audit follow-ups it records.
Description check	✅ Passed	The description follows the template with Summary, Verification, Risk and rollout, and Notes, and it includes the required verification note.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/site-audit-quick-wins-21v9gb

---

_{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 ↗︎.