Clinical primary buttons in Clinical blue; My Day lists the flagged item once

Merged
BI
1mo ago
+107-66

User description

Summary

Follow-ups to #3453. The owner agreed to all three on 11 Oct.

  • Before: in Clinical, most main buttons were near-black. Only two pages were blue, and each had its own one-off override. After: the shared primary button takes the area colour everywhere. That means Clinical blue by default and a Work area's own colour inside its frame (design rule C8.3). The two one-off overrides are gone. High-contrast mode keeps the native button colours.
  • Before: My Day showed the most important item twice, first in the amber flag card and then again as the first row of Needs you. After: Needs you leaves that item out of its rows while the flag shows. "All N" still counts it, so the link matches the full list it opens. If the flag card is hidden, the item is listed in Needs you as before. When the flagged item is the only one, Needs you says "Nothing else needs you today." instead of "Nothing needs you right now".
  • Emergent tags stay red. That was already the case after #3453, so this PR has no change for it.

Areas touched: Personal practice, App experience, Design system

Verification

  • Checks run:
    • npx vitest run tests/my-day-dashboard.dom.test.tsx tests/my-day-page.dom.test.tsx tests/my-day-dashboard.test.ts: Tests 101 passed (101)
    • The button colour tests (guide centre, recommend, CME routines and state notice, open shifts board, design-system): Tests 160 passed (160)
    • check:diff-integrity: PASS — 3 changed test file(s), 99 -> 101 test case(s)
    • tsc, eslint and prettier are clean on the changed files.
    • Browser and forced-colours checks are left to CI.

Risk and rollout

  • Risk: visual only. Clinical's primary buttons change from near-black to blue. My Day's Needs you shows one fewer row while the flag card is showing.
  • Rollback: revert this PR.
  • Provider or production effects: none.

Notes

  • The primary button now sets the command colour tokens on itself, so existing class names and tests are unchanged. Other filled controls that use the command colour (tabs, pagination) are not changed.

🤖 Generated with Claude Code

https://claude.ai/code/session_01T6yVRM8TyEHCooxU8ke9nA

Generated by Claude Code

Summary by cubic

Sets the shared primary button to take the area colour everywhere (Clinical blue by default, a Work area's own colour inside its frame) and stops My Day's Needs you from repeating the item the flag card above already shows.

Primary buttons

  • The two one-off per-page overrides are removed; the Work pressed state falls back to a readable deep shade, and high-contrast mode keeps the native button pair.
  • Emergent tag red and other filled command-colour controls are unchanged.

Needs you

  • The flagged item is left out of the rows while the flag shows; the "All N" count still includes it so the link matches the full list it opens.
  • Hiding the flag card brings the item back into the rows. When the flagged item is the only one and nothing is hidden, the card reads "Nothing else needs you today."

CodeAnt-AI Description

Match primary button colors to each area and remove duplicate My Day items

What Changed

  • Primary buttons use Clinical blue by default and the Work area's color inside its frame; high-contrast mode keeps native button colors.
  • My Day no longer lists the flagged item twice while the flag card is visible. The “See all” count still includes it, and hiding the flag card restores it to the list.
  • The “Needs you” message no longer says that zero items are hidden until tomorrow.

Impact

✅ Clinical buttons match their area
✅ No duplicate flagged items in My Day
✅ “See all” still opens the full item list

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

Summary by Gitar

  • Needs you copy:
    • Drops the "hidden until tomorrow" note when no items are hidden, so it only appears when total exceeds waiting
  • Primary buttons:
    • Adds the primary variant to the specifier builder continue button and the Documents search link in search/page.tsx

This will update automatically on new commits.