Skip to content

feat(sidebar): add personalised clinical navigation - #2026

Merged
BigSimmo merged 3 commits into
mainfrom
codex/sidebar-live-rollout-pr
Aug 17, 2026
Merged

feat(sidebar): add personalised clinical navigation#2026
BigSimmo merged 3 commits into
mainfrom
codex/sidebar-live-rollout-pr

Conversation

@BigSimmo

Copy link
Copy Markdown
Owner

Summary

  • Roll out the personalised Clinical Guide sidebar to the production UI, including persistent editable shortcuts, three unheaded recent chats, a refined collapsed rail, and a permanent More modes entry.
  • Add the shared More modes editor with pin, unpin, reorder, search, keyboard focus return, and accessible mode labels; retain the existing Settings and account dialogs.
  • Add Light, Dark, and Auto appearance controls, shared-composer search focus, a live sidebar mockup, and generated route documentation.

Verification

  • npm run verify:pr-local — partial: runtime, installed-lock parity, changed-file formatting, lint, and typecheck passed. The full test stage stopped with four failures; the route-documentation failure was corrected and focused route/sidebar coverage passes. Build, RAG fixtures, and medication checks were not reached.
  • Focused fresh-base coverage: npm test -- tests/sidebar-live-mockup.dom.test.tsx tests/sidebar-pins.test.ts tests/sidebar-production.dom.test.tsx tests/favourites-auth-gate.dom.test.tsx tests/site-map.test.ts tests/route-reachability.test.ts — 34 passed.
  • npm run typecheck — passed.
  • npm run format — passed.
  • Focused isolated production Chromium sidebar journeys — passed during implementation.
  • UI verification not run: the complete npm run verify:ui suite; focused production/sidebar browser proof was used instead.
  • Release verification not run: not a release handoff.

Risk and rollout

  • Risk: shared navigation and local sidebar-preference state change; no retrieval, answer-generation, document-access, or clinical-output behaviour changes.
  • Rollback: revert 4326682f2.
  • Provider or production effects: None. No provider, migration, deployment, or hosted configuration change was made.

Clinical Governance Preflight

Not applicable: this is a client-side navigation and presentation change. Clinical claims, sources, retrieval, document access, patient-identifiable workflows, and provider configuration are unchanged.

Notes

  • Based on current main at f2cdb69f5.

@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.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

@supabase

supabaseBot commented Aug 17, 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 ↗︎.

@coderabbitai

coderabbitaiBot commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

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:29 minutes

Limit details: You’ve used all 1 included review currently available under your plan. You completed 94 included PR reviews in the past 7 days; at that activity level, included reviews refill at 1 review per hour.

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: 0a536b70-b719-4a9f-8d43-d23b5d9d027c

📥 Commits

Reviewing files that changed from the base of the PR and between ab7c513 and fc415ae.

📒 Files selected for processing (18)
  • docs/site-map.md
  • playwright.config.ts
  • src/app/globals.css
  • src/app/mockups/mockups-layout-client.tsx
  • src/app/mockups/sidebar-live/page.tsx
  • src/components/ClinicalDashboard.tsx
  • src/components/clinical-dashboard/ClinicalSidebar.tsx
  • src/components/clinical-dashboard/global-search-shell.tsx
  • src/components/clinical-dashboard/universal-search-command-surface.tsx
  • src/components/clinical-dashboard/use-sidebar-pins.ts
  • src/components/sidebar-live-mockup.tsx
  • src/components/sidebar-live-shell.module.css
  • tests/favourites-auth-gate.dom.test.tsx
  • tests/sidebar-live-mockup.dom.test.tsx
  • tests/sidebar-pins.test.ts
  • tests/sidebar-production.dom.test.tsx
  • tests/ui-sidebar-live-mockup.spec.ts
  • tests/ui-smoke.spec.ts

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

@github-actions

Copy link
Copy Markdown
Contributor

CI triage

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

  • Static PR checksneeds investigation: inspect the failing step and uploaded diagnostics; rerun only after classifying the cause.
  • PR requiredneeds investigation: inspect the failing step and uploaded diagnostics; rerun only after classifying the cause.

Compared with main CI run #11281 (cancelled).

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

@BigSimmo
BigSimmo enabled auto-merge (squash) August 17, 2026 10:28
- Replace deprecated --text-soft alias with --text-muted on the
appearance-menu label and search-shortcut kbd (TOKENS.md §6/§7).
- Bump the Edit-shortcuts and View-all-chats buttons from min-h-9 to
min-h-tap so they clear the 48px interactive tap floor.
- Route the new sidebar-live-shell.module.css literals (z-index,
padding, border-radius, gap, line-height) through design tokens or
the existing var(--local-name, fallback) escape hatch already used
by --z-raised in globals.css, instead of bare numeric literals.
Fixes the failing "Static PR checks" / check:design-system-contract
job blocking PR #2026.
@BigSimmo
BigSimmo disabled auto-merge August 17, 2026 10:36
@BigSimmo
BigSimmo merged commit 6806911 into mainAug 17, 2026
25 of 26 checks passed
@BigSimmo
BigSimmo deleted the codex/sidebar-live-rollout-pr branch August 17, 2026 10:46
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.

1 participant

@BigSimmo