Quiet workspace styling and clarify GitHub action availability

[christopherjnelson]

Foreman’s workspace used yellow on nested selections and unavailable actions, while blue notices and provider colors competed with it. This quiets the existing components in dark mode and applies the same visual rules to light mode, preserving the layout and responsive behavior.

• Selection and available actions: one yellow edge on the selected task, a restrained cue on the current execution step, and yellow enabled primary buttons.
• Progress and information: neutral planning/running/waiting/unknown labels, Live Response dots, task notices, role cards, and consistent quota bars.
• Outcomes: restrained teal success, muted amber warnings, and red failed labels/check markers with readable explanations. Labels and icons remain.
• Unavailable actions: Open PR and both Push controls require applied promotion plus their existing prerequisites. Disabled buttons are neutral and explain why nearby; merge, task-start, Planner-send, and promotion controls retain their gates and accessible context. Server/controller approval and GitHub gates are unchanged.

Validation passed: pnpm typecheck, pnpm build, 112 UI tests, and 42 supporting UI tests. Browser fixtures cover idle, active validation, failed validation, and human approval at 1024/1440/1920 in both themes, with keyboard focus, disabled-action checks, contrast measurements, and no horizontal overflow. API requests were intercepted; no live Planner, Worker, or Reviewer turns were spent.

The comparisons below use the same fixture state, theme, and 1440 × 1050 viewport. Baseline: b826f88. The failed check is expanded; approval shows the enabled human decision.

Dark mode	Before	After
Idle project
Active run
Failed validation
Awaiting human approval

Matching light-mode comparisons

Light mode	Before	After
Idle project
Active run
Failed validation
Awaiting human approval

Fixture runner and verification evidence.