Skip to content

Finish ClinicalDashboard admin decomposition: SettingsDialog + dashboard-nav cutover, dead-code cleanup - #336

Merged
BigSimmo merged 5 commits into
mainfrom
claude/dashboard-decomp-final
Jul 7, 2026
Merged

Finish ClinicalDashboard admin decomposition: SettingsDialog + dashboard-nav cutover, dead-code cleanup#336
BigSimmo merged 5 commits into
mainfrom
claude/dashboard-decomp-final

Conversation

@BigSimmo

Copy link
Copy Markdown
Owner

Summary

Completes the deferred admin-surface phase of the ClinicalDashboard decomposition (debt tracked in docs/process-hardening.md Phase 3). Monolith: 4,373 → ~3,450 lines; only the orchestrator, its data/state hooks, and small render/stream helpers remain.

  • ToolsHub + MobileSectionFab → clinical-dashboard/dashboard-nav.tsx (move-only). The prepared refactor: extract SettingsDialog + dashboard-nav overlays from ClinicalDashboard (move-only) #250 sibling had drifted from the live monolith (missing prop members, stale colour tokens) and was regenerated verbatim from the current monolith block before wiring. Back-imports (ApplicationsLauncherWorkspace, navigationHashes, mobileSectionFabMediaQuery) follow the existing benign back-edge pattern.
  • SettingsDialog cluster (+ 7 Settings* helpers) → clinical-dashboard/settings-dialog.tsx (move-only). The refactor: extract SettingsDialog + dashboard-nav overlays from ClinicalDashboard (move-only) #250 sibling predated the auth-email sign-in flow (useAuthSession/settingsEmail/submitSettingsEmail absent) — wiring it as-is would have regressed settings sign-in — so it too was regenerated verbatim. Both consumers repointed: the monolith render and global-mockup-search-shell.tsx. 24 now-orphaned monolith imports stripped.
  • Deleted the dead clinical-dashboard/document-admin/ directory (document-drawer.tsx, label-helpers.ts, index.ts) — shadowed by the live document-admin.tsx file in module resolution; imported by nothing.
  • Merge with main's type-scale migration (c09b3ee): the migration had rewritten font-size classes inside the monolith blocks this PR moves, so the cutover was redone against main's migrated blocks — the extracted modules carry the new text-2xs/text-sm-minus/text-base-minus classes; no design regression.
  • Debt log updated (docs/process-hardening.md Phase 3 now reflects refactor: extract SettingsDialog + dashboard-nav overlays from ClinicalDashboard (move-only) #250/refactor: extract document-admin — completes ClinicalDashboard decomposition (move-only) #251 landed + this cutover); added docs/archive/operator-decisions-2026-07-06.md recording operator approval to apply the two pending live migrations (M13, storage_cleanup_jobs index reconcile) and deploy the indexing-v3-agent edge function from any live-connected session.

Move integrity: every block moved verbatim (diff-verified), and the live-surface data-testid/aria-label corpus was proven byte-identical before/after each move and across the main merge (sorted-attribute sha1).

Verification

  • npm run verify:cheap — pass (runtime, sitemap, lint [5 pre-existing warnings, 0 errors], typecheck, 1,181 unit tests)
  • npm run verify:ui109/109 passed post-merge (settings dialog via ui-smoke account-settings assertions; ToolsHub via ui-tools*; MobileSectionFab via ui-overlap)
  • npm run verify:release before release or handoff confidence claims
  • npm run format:check — pass
  • npm run eval:retrieval:quality — N/A: no retrieval, ranking, selection, chunking, or scoring change (UI move-only)
  • npm run eval:rag / eval:quality — N/A: no answer-generation change
  • npm run check:production-readiness — N/A: no clinical workflow, privacy, environment, Supabase, or deployment behavior change
  • npm run check:deployment-readiness — N/A: no deployment startup change

Clinical Governance Preflight

UI module reorganization only; no ingestion/answer/search/source/privacy changes.

  • 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 — no clinical decision-support behavior changed

Notes

  • Per the standing convention, the barrel clinical-dashboard/index.ts was not extended; modules are imported by deep path.
  • The docs/archive/operator-decisions-2026-07-06.md items (live migrations + edge deploy) still need execution from a live-connected session — this PR only records the approval.

🤖 Generated with Claude Code

https://claude.ai/code/session_01XPVNBVo4cg9PEYtNhJZBQY


Generated by Claude Code

claude added 4 commits July 6, 2026 13:46
…d-nav module (move-only)
The prepared dashboard-nav.tsx sibling from #250 had drifted from the live
monolith (missing prop members, stale colour tokens), so it was regenerated
verbatim from the current monolith block (1072-1436) before wiring. Exports:
ToolsHub, buildMobileSectionFabState, MobileSectionFab; back-imports
(ApplicationsLauncherWorkspace, navigationHashes, mobileSectionFabMediaQuery)
follow the existing benign back-edge pattern. Monolith 4373 -> 4007 lines.
Live-surface data-testid/aria-label corpus verified byte-identical pre/post.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XPVNBVo4cg9PEYtNhJZBQY
…og module (move-only)
The prepared settings-dialog.tsx from #250 predated the auth-email sign-in
flow (useAuthSession/settingsEmail/submitSettingsEmail all absent), so it was
regenerated verbatim from the current monolith block (518-1070) before wiring.
Repointed both consumers: the monolith render and global-mockup-search-shell
(which now imports SettingsDialog from the module and only
recentQueryStorageKey from the monolith). Stripped 24 now-orphaned monolith
imports. Monolith 4007 -> 3454 lines. Live-surface data-testid/aria-label
corpus verified byte-identical pre/post.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XPVNBVo4cg9PEYtNhJZBQY
…log; record operator approvals
The document-admin/ directory (document-drawer.tsx, label-helpers.ts,
index.ts) was an unwired leftover shadowed by the live document-admin.tsx
file in module resolution — nothing imported it. The process-hardening
Phase-3 log now reflects that #250/#251 landed and the admin cutover is
finished. docs/archive/operator-decisions-2026-07-06.md records the
operator's approval to apply the two pending live migrations (M13,
storage_cleanup_jobs index reconcile) and deploy the indexing-v3-agent
edge function from any live-connected session.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XPVNBVo4cg9PEYtNhJZBQY
…mp-final
# Conflicts:
#	src/components/ClinicalDashboard.tsx
#	src/components/clinical-dashboard/document-admin/document-drawer.tsx
#	src/components/clinical-dashboard/settings-dialog.tsx
@supabase

supabaseBot commented Jul 6, 2026

Copy link
Copy Markdown

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

@BigSimmo
BigSimmo marked this pull request as ready for review July 6, 2026 18:18
@BigSimmo
BigSimmo enabled auto-merge July 6, 2026 18:18
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
@BigSimmo
BigSimmo merged commit 46217a6 into mainJul 7, 2026
5 checks passed
@BigSimmo
BigSimmo deleted the claude/dashboard-decomp-final branch July 8, 2026 16:10
BigSimmo added a commit that referenced this pull request Aug 18, 2026
BigSimmo pushed a commit that referenced this pull request Aug 18, 2026
Resolves the one real conflict GitHub reported (`mergeable_state: dirty`, base
at dc7e518): `tests/design-token-contract.test.ts`.
Both sides appended a new `describe` block to the end of the same file and the
two shared a trailing `});` pair, so git could not tell them apart:
- ours: "category accents stay out of the semantic palette" — the three guards
keeping identity accents off the danger/warning/success/info families.
- theirs: "responsive breakpoint tokens (Task #336)" — the --bp-* / --breakpoint-*
assertions.
There is no semantic overlap between them, so both are kept and each is closed
explicitly rather than sharing a terminator. Verified by content, not by the
merge exiting cleanly: the file now declares both describes, and the suite runs
40 tests where ours alone ran 39 and theirs added 1 — so neither side was
silently dropped.
Gates on the merged tree: typecheck, lint, `npm run test` (651 files, 7016
passed / 4 skipped).
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XGhewT2mmRoRTynjWfF1Vn
BigSimmo pushed a commit that referenced this pull request Aug 18, 2026
PR #2081 (already merged) queued "update" flags for #222, #321, and
#336 noting they were still open after PR #2072. This PR queues its
own newer, more complete requests for the same three rows (two
"done" decisions, one updated "PARTIAL" status), which the ledger
inbox tool correctly refuses to auto-reconcile as a silent
overwrite — it requires an explicit cancel decision per row.
Cancels the three now-superseded #2081 flags in favor of this PR's
requests, fixing the docs:check-links / ledger-inbox failure in
Static PR checks.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015qDHwBNZYyRLdJHqSkiYTg
BigSimmo pushed a commit that referenced this pull request Aug 18, 2026
Cancels four pending requests found while diagnosing the docs:check-links
CI failure — two were duplicates of already-applied requests (#222, #336,
each already closed by a different, more accurate applied request), and
two asserted "done" outcomes for work this branch's final state does not
actually contain after the fabricated-content revert (#318: lexicon
sign-off and loperamide exclusion; #309: filter-density fix). All four
are cancelled via immutable cancel requests rather than deleted, per
ledger-write discipline.
BigSimmo pushed a commit that referenced this pull request Aug 18, 2026
Cancels 88868df4-c310-4ac2-9e83-cd3ad7702a1d, another false "done" claim
from this branch's original batch (same pattern as #222/#318/#309/#336):
#183 asks for a live Sentry production metric alert, blocked on missing
credentials and unreachable via a code diff. This branch's actual final
diff contains no Sentry or alerting changes. Also resolves a collision
with a separate, legitimate concurrent update request on the same row
from an unrelated branch.
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@BigSimmo@claude@cursoragent