style(panel): neutral Start — the readiness pill is the header's only colour (#179)

[sebyx07]

What changed

The header's Start/Stop toggle no longer takes the accent treatment. .dz-readiness__toggle now uses the button-ghost mixin (with the strong border) in both states instead of button-primary for Start; the is-running class and its per-state override block are deleted from both the SCSS and the TSX, since the two states no longer differ in dress — only in glyph (play/stop) and label.

Files:

• src/entrypoints/sidepanel/components/ReadinessDropdown.scss
• src/entrypoints/sidepanel/components/ReadinessDropdown.tsx

Before / after

• Before: with a configured provider the header showed three warm elements at once — the readiness pill, an accent-washed Start (orange fill + orange edge + orange text), and the primary button below. Stop was already an outlined ghost, so the header also changed brightness every time a session started or ended.
• After: Start and Stop are the same neutral outlined ghost every other secondary control uses — transparent fill, --dz-border-strong outline, neutral text, wash on hover, half-opacity when disabled. The readiness pill is the only coloured element in the header, matching the monochrome reference. The pill's own colours are untouched.

Out of scope

The epic's other remaining item — uppercase mono reference typography — is deliberately not ported: the issue itself notes "SET UP PROVIDER" is much wider than "Set up provider" and truncates at the 360px panel width.

Test plan

• DZ_TEST_WORKERS=2 bun run verify clean (lint + typecheck + 2654 unit/integration tests).
• No tests asserted on the removed class or the toggle's colours; E2E specs target .dz-readiness__toggle by label/enabled state only.

Refs #179

🤖 Generated with Claude Code

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[coderabbitai]

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

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: c0907e16-5aa4-4784-8ed3-d876781d6cb9

📥 Commits

Reviewing files that changed from the base of the PR and between af042ae and 53c68f6.

📒 Files selected for processing (2)

• src/entrypoints/sidepanel/components/ReadinessDropdown.scss
• src/entrypoints/sidepanel/components/ReadinessDropdown.tsx

Warning

.coderabbit.yaml has a parsing error

The CodeRabbit configuration file in this repository has a parsing error and default settings were used instead. Please fix the error(s) in the configuration file. You can initialize chat with CodeRabbit to get help with the configuration file.

💥 Parsing errors (1)

Validation error: Too big: expected string to have <=250 characters at "tone_instructions"

⚙️ Configuration instructions

• Please see the configuration documentation for more information.
• You can also validate your configuration using the online YAML validator.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

---

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