Make runtime warning critical (codex)

[numnx]

🧩 Task: Make runtime warning critical

Automated task PR opened by Code UX for T03.

📋 Summary

Sprint: Sprint 159 · Header Menu bar - Token throughput + Runtime warning · Task: T03

Add a polished header-bar token throughput signal for app-wide and selected-project usage, and make the runtime-not-ready warning a critical red animated warning that is hard to miss while preserving accessibility and existing header behavior.

📝 Full Task Prompt

## Objective
Make the header runtime-not-ready warning visually critical by using a red warning badge with an animated exclamation mark, while keeping the Docker status menu keyboard-accessible and reduced-motion safe.

## Scope
- dashboard/src/v2/components/DockerStatusMenu.tsx
- tests/dashboard/v2/docker-status-menu.test.tsx
- docs/dashboard/onboarding.md
- docs/dashboard/dashboard-guide.md
- docs-web/user/troubleshooting.md
- docs-web/content/docs/user-troubleshooting.mdx

## Implementation Requirements
1. Replace the current amber `Cluster not ready` header badge with a red critical warning treatment that includes an exclamation icon or glyph and a motion-safe animation that draws attention without depending on motion for meaning.
2. Add appropriate `role="alert"` or assertive live semantics for the non-ready state, while avoiding repeated announcements during normal hover or menu refreshes.
3. Update the Docker status trigger accessible name so screen-reader users hear that the runtime is not ready when readiness reports `cluster.status === "not_ready"`.
4. Keep the popover content, focus trap, Escape handling, hover handling, dependency details, and ready-state styling intact except where the critical warning treatment requires consistent red status tokens.
5. Add focused tests that mock readiness as not ready and ready, assert the red warning copy/icon semantics, verify the animated marker is motion-safe, and confirm the ready state does not render the critical warning.
6. Update onboarding, dashboard guide, and troubleshooting docs to describe the red runtime-not-ready warning and the Docker/Git dependency checks behind it.

## Constraints
- Do not change the readiness API contract or dependency detection logic.
- Do not make the warning dismissible; it must remain tied to actual runtime readiness.
- Respect reduced motion by leaving a static exclamation and color/state label when animation is disabled.
- Do not weaken existing Docker menu keyboard navigation or focus restoration behavior.

## Verification
- Run `pnpm exec vitest run tests/dashboard/v2/docker-status-menu.test.tsx`.
- Run `pnpm run typecheck:dashboard`.
- Success means the not-ready header state is red and attention-grabbing, ready state remains quiet, and accessibility assertions pass.

✅ QA Review

⏳ QA review runs after this PR is opened. Check the task card in the dashboard for the outcome once it lands.

🤖 Model & Provider

Provider	Codex CLI
Model	gpt-5.5

⏱️ Timing

Started	2026-07-07 04:32:38 UTC
Finished	2026-07-07 04:38:42 UTC
Duration	6m 4s

📊 Token Usage

Metric	Value
Input tokens	172,697
Cached input tokens	1,196,032
Output tokens	13,606
Total tokens	1,382,335
Invocations	1
Tool calls	46
Active time	5m 18s

Included usage estimate (subscription/local login): $1.87

🌿 Branch Info

Base: feature/CODUX-159-header-menu-bar-token-throughput-runtime-warning
Head: task/feature-codux-159-header-menu-bar-token-throughp-t03-codex-mra5kq81

---

🤖 Generated by Code UX