Remove redundant section header from differentials Presentations/Diagnoses streams - #2049
Conversation
…noses streams Drop the "Presentation pathways"/"Clinical entries" heading and its subtitle so result cards render directly below the search results band instead of behind a duplicate label.
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
This pull request has been ignored for the connected project Preview Branches by Supabase. |
Caution Review failedAn error occurred during the review process. Please try again later. Comment |
CI triageCI failed on this PR. Automated classification of the 2 failed job(s):
Compared with main CI run #11455 (success). Classification is evidence routing, not permission to ignore a failure. Exact quarantined Playwright identities remain governed by the flake ledger. |
Summary
<h2>heading and its subtitle fromDifferentialStreamWorkspace(src/components/differentials/differential-stream-workspace.tsx) so result cards render directly below the search results band on both/differentials/presentationsand/differentials/diagnoses, instead of behind a duplicate label.entriesLabelfield from the per-stream copy table.Verification
npm run typecheck— cleannpx eslint src/components/differentials/differential-stream-workspace.tsx tests/differential-stream-page.dom.test.tsx tests/ui-route-coverage.spec.ts— cleannpx prettier --check <changed files>— "All matched files use Prettier code style!"node scripts/run-vitest.mjs run tests/differential-stream-page.dom.test.tsx— 7 passed (7)npm run verify:pr-local— not run: this is a localized, non-behavioural text/heading removal confined to one component's section header (no shared chrome/composer/routing/data change); the focused DOM test plus typecheck/lint above cover the plausible regression surface for this diff.npm run verify:ui— not run for the same reason; no shared search-chrome, composer, or cross-page UI foundation was touched, only a page-local<h2>/subtitle removed. Playwright'sui-route-coverage.spec.tsassertion on this heading was updated to match, but the full Chromium gate was not run.Risk and rollout
Notes
Generated by Claude Code