docs(issues): capture db-query-perf operator follow-ups

[BigSimmo]

Summary

• Re-declare dark body/heading ink and companion roles on .dark .ckb-v2 after the cascade port so light .ckb-v2 matching inside dark subtrees cannot resolve light ink on dark surfaces.
• Merge origin/main to clear DIRTY mergeability (prefer main’s post-feat(design-system): v2 token layer + 26 components — reconciled, cascade-ported, forced-colours owned #1538/fix(design-system): critique fixes + post-merge truth sweep (bundled hygiene PR) #1541 component copies; keep this tip’s dark-ink contract + HCM transparent overlay-backdrop rationale).
• Tabs: aria-controls only on the selected tab when a panel is owned (unselected tabs no longer point at missing IDs).
• Tooltip: compose mouse/focus/keydown handlers with the child’s existing handlers instead of replacing them.

RAG impact: no retrieval behaviour change — design-system token dark-cascade fix and unadopted UI component a11y only; no file under src/lib/rag/**, clinical-search, retrieval-selection, ranking, eval harness, golden fixtures, or retrieval RPCs is touched.

Verification

• npm run verify:pr-local
• focused: vitesttests/ckb-v2-token-contract.test.ts + tests/ui-v2-components.dom.test.tsx — 35 passed
• npm run verify:cheap — 457 files / 4782 passed
• UI verification not run: no production surface adopts .ckb-v2 / these components yet; phone-chrome and visual journeys unchanged. Prefer CI Production UI on this tip.

Risk and rollout

• Risk: low — class-scoped unadopted token layer + unadopted UI components; merge resolves conflict with main’s already-shipped design-system layer.
• Rollback: revert the squash / tip commits; no schema, data, or provider surface.
• Provider or production effects: None.

Clinical Governance Preflight

• Source-backed claims still require linked source verification before clinical use
• No patient-identifiable document workflow was introduced or expanded without explicit governance approval
• Supabase target remains Clinical KB Database (sjrfecxgysukkwxsowpy)
• Service-role keys and private document access remain server-only
• Demo/synthetic content remains clearly separated from real clinical sources
• Source metadata, review status, and outdated/unknown-source behavior remain conservative
• Deployment classification/TGA SaMD impact was checked when clinical decision-support behavior changed

Notes

• Remaining playbook work stays in later tranches (SPEC §13).
• Companion design-system docs already on main via docs(design-system): resolved five-document spec set + repair of the broken sentry merge #1531 / docs(design-system): perfection pass — per-component contracts, playbook, authoring DoD, usage rules #1537 / feat(design-system): v2 token layer + 26 components — reconciled, cascade-ported, forced-colours owned #1538 / fix(design-system): critique fixes + post-merge truth sweep (bundled hygiene PR) #1541.

Summary by CodeRabbit

• Documentation
  • Updated the outstanding-issues ledger with new and resolved database reliability tasks.
• Maintenance
  • Refreshed database schema tracking metadata.
  • Added an index to improve retrieval of relevant document images.
  • Updated recorded metadata for API rate-limit processing.

[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]

📝 Walkthrough

Walkthrough

The PR updates the issue ledger and records completed hosted database verification. It regenerates the drift manifest with new metadata, a searchable document-images index, and an updated consume_api_rate_limit definition hash.

Changes

Ledger and manifest synchronization

Layer / File(s)	Summary
Drift manifest regeneration supabase/drift-manifest.json	The manifest records updated generation metadata, the document_images_searchable_doc_page_relevance_idx index, and a new definition hash for consume_api_rate_limit.
Issue ledger updates docs/outstanding-issues.md	The ledger advances the next issue ID, adds the Sentry database-span p95 alert task, and archives hosted migration verification and manifest regeneration tasks.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

• BigSimmo/Database#1519: Updates the same issue ledger with archived and resolved records.
• BigSimmo/Database#1518: Advances the issue marker and adds or archives ledger entries.

Suggested reviewers:claude, cursoragent

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description uses the required headings but describes unrelated UI and design-system changes instead of the documented issue and drift-manifest updates.	Replace the description with the actual objectives, affected files, migration and drift-manifest verification, issue closure details, and relevant risk information.

✅ Passed checks (4 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 describes the documentation change that captures database query performance operator follow-ups.

---

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

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

[qodo-code-review]

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →