Skip to content

feat(therapy-compass): mobile-first Recommend scenario sheet - #2411

Merged
BigSimmo merged 4 commits into
mainfrom
codex/therapy-recommend-redesign
Aug 27, 2026
Merged

feat(therapy-compass): mobile-first Recommend scenario sheet#2411
BigSimmo merged 4 commits into
mainfrom
codex/therapy-recommend-redesign

Conversation

@BigSimmo

@BigSimmoBigSimmo commented Aug 27, 2026

Copy link
Copy Markdown
Owner

Summary

  • Redesign Therapy Compass Recommend (/therapy-compass/recommend) with a minimal header and mobile-first clinical scenario sheet
  • Extract shared RecommendScenarioFields (situation textarea + Setting/Time/Support/Cautions chips) used by phone sheet and desktop inline composer
  • Move Copy shortlist / Refine in catalogue actions to the results toolbar; ranking logic unchanged

Verification

  • npx vitest run tests/recommend-screen.dom.test.tsx tests/therapy-compass-responsive-contract.test.ts — 17/17 passed locally
  • Pre-push guard: lint, format, typecheck on changed files
  • npm run verify:ui — UI verification deferred; change is scoped to Therapy Recommend layout only

UI verification not run: scoped mobile sheet + desktop composer refactor; DOM/responsive contract tests cover structure.

Risk and rollout

  • Risk: Low — UI-only layout change on one Therapy Compass screen; no binding/ranking changes
  • Rollback: Revert PR
  • Provider or production effects: None
  • RAG impact: no retrieval behaviour change — UI-only Therapy Recommend layout; ranking logic unchanged

Clinical Governance Preflight

Not applicable — UI-only layout change with no clinical data, ingestion, or answer-contract changes.

Notes

  • Phone: compact Clinical scenario trigger opens a sheet with full situation + constraint editor
  • Desktop: lighter inline composer remains (sm+); no shared phone bottom dock on this route

@coderabbitai

coderabbitaiBot commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

Next included review available in 51 minutes.

View limit details

Limit details: You’ve used the included review currently available. Your 97 included PR review attempts over the past 7 days set your current allowance at 1 review per hour.

Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: ac58bfc9-db2a-4347-8e4b-2e6d1f4a3cf0

📥 Commits

Reviewing files that changed from the base of the PR and between 39545f0 and e8a5a90.

⛔ Files ignored due to path filters (2)
  • docs/design-system/COMPONENTS.md is excluded by !docs/**, !**/*.md
  • docs/design-system/adoption-manifest.json is excluded by !docs/**
📒 Files selected for processing (5)
  • src/components/therapy-compass/recommend-scenario-control.tsx
  • src/components/therapy-compass/recommend-scenario-fields.tsx
  • src/components/therapy-compass/screens/recommend-screen.tsx
  • tests/recommend-screen.dom.test.tsx
  • tests/therapy-compass-responsive-contract.test.ts

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

@supabase

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

@github-actions

github-actionsBot commented Aug 27, 2026

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 #14124 (failure).

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

@BigSimmo
BigSimmo marked this pull request as ready for review August 27, 2026 05:21
@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, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

@cursor

cursorBot commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_f50a1218-7d33-479d-8b30-09557d8c9112)

Redesign the Therapy Recommend top section with a minimal header, a compact phone trigger that opens a sheet for the clinical situation and constraint chips, and a lighter desktop inline composer. Move shortlist actions into the results toolbar while preserving ranking behaviour.
Co-authored-by: Cursor <cursoragent@cursor.com>
@BigSimmo
BigSimmoforce-pushed the codex/therapy-recommend-redesign branch from 5ffaaba to 32bf192CompareAugust 27, 2026 05:40
@BigSimmoBigSimmo changed the title Refactor DSM compare into a unified side-by-side layoutfeat(therapy-compass): mobile-first Recommend scenario sheetAug 27, 2026
BigSimmoand others added 3 commits August 27, 2026 13:53
…nd scenario control
Satisfy the Therapy design-system contract by replacing raw buttons with InteractiveRow for the phone trigger and Button for Done.
Co-authored-by: Cursor <cursoragent@cursor.com>
@BigSimmo
BigSimmo enabled auto-merge (squash) August 27, 2026 06:09
@BigSimmo
BigSimmo merged commit 41a35bf into mainAug 27, 2026
29 checks passed
@BigSimmo
BigSimmo deleted the codex/therapy-recommend-redesign branch August 27, 2026 06:17
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