Improve formulation builder disabled-state accessibility

[BigSimmo]

Summary

• replace opacity-only disabled styling on formulation builder navigation with explicit token-based disabled surfaces
• preserve native disabled semantics while keeping labels readable in light, dark, and forced-colors modes
• add Playwright coverage for disabled state, focus rejection, enabled transitions, and axe
• update Create label.yml #64 while leaving the unavailable historical worktree untouched

RAG impact: no retrieval behaviour change — UI-only disabled-state styling; no retrieval, ranking, answer, or source behavior changed.

Verification

• npm run verify:pr-local — passed on this exact linear current-main branch; includes build, client-bundle secret scan, 3,431 unit tests, and offline RAG fixture validation
• npm run verify:ui — hosted Production UI passed on this exact head; all formulation journeys are green
• npm run verify:release — not run; provider-backed and not required for this UI-only change
• Focused formulation Chromium: 2/2 passed on this exact branch
• Hosted Static, Unit, Build, Production UI, Advisory UI, Semgrep, Gitleaks, PR Policy, and required aggregate all passed
• GitHub still displays the superseded PR Policy run cancelled because applying skip-branch-sync restarted that workflow; the replacement PR Policy run and required aggregate are green

Risk and rollout

• Risk: Low — scoped Tailwind utility changes on two natively disabled buttons; no logic, API, data, auth, or clinical-output behavior changes.
• Rollback: Revert 9a41adb2; no database or migration rollback is involved.
• Provider or production effects: None.

Clinical Governance Preflight

N/A — UI-only disabled-state presentation; no ingestion, answer generation, retrieval/ranking, source rendering, document access, privacy, production environment, or clinical output behavior changed.

Notes

• Superseded conflicted PRs Improve formulation builder disabled-state accessibility #1219, Improve formulation builder disabled-state accessibility #1223, and Improve formulation builder disabled-state accessibility #1226 are closed and must not merge.
• Two independent frontend/accessibility and regression reviews found no P0-P2 findings on the identical product/test change.
• The historical agent/formulation-disabled-contrast worktree remains preserved but unavailable. This PR does not modify or discard it.
• This branch intentionally remains linear and carries skip-branch-sync; do not merge main into it if main advances.
• GitHub reports this PR MERGEABLE and BEHIND; required checks are green, so it is ready for squash merge without another branch update.

  

[supabase]

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]

Warning

Review limit reached

@BigSimmo, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 38 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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 0e6fb1c4-5d8c-4aed-a1d0-3d1407d1d9e7

📥 Commits

Reviewing files that changed from the base of the PR and between 79d1c87 and 505af2b.

📒 Files selected for processing (4)

• docs/branch-review-ledger.md
• docs/outstanding-issues.md
• src/components/formulation/formulation-builder-page.tsx
• tests/ui-formulation.spec.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch cursor/formulation-accessibility-linear-14d4

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[chatgpt-codex-connector]

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.

[BigSimmo]

Open-PR hygiene note (2026-07-26): GitHub reports CONFLICTING; local merge-tree shows a real content conflict only in docs/outstanding-issues.md (branch ~15 behind main). Product CI looked green on the prior tip. Please merge origin/main and resolve the ledger/outstanding-issues append with union/append-only rules (do not drop main rows), then push — or ask for a Run PR sync pass.

[github-actions]

CI triage

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

• Static PR checks — needs investigation: inspect the failing step and uploaded diagnostics; rerun only after classifying the cause.
• PR required — needs investigation: inspect the failing step and uploaded diagnostics; rerun only after classifying the cause.

Compared with main CI run #5767 (success).

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