#261 feat(dash): light-mode AA verdict colors, live-region pending queue, labeled TOTP input

[Anonymous]

Originally created by: fu351

Slice

• UX fix wave / UX.2 - dash a11y + honest light mode (2026-08-05 audit P1s)

What this PR does

The dash declared color-scheme: dark light but light mode never re-tuned the verdict tokens, so PASS/AUTH/BLOCK badges computed ~2.2-2.5:1 on light backgrounds. Light mode now carries its own AA-passing verdict and neutral values. The pending-approval queue - the one surface a human must notice - becomes perceivable beyond eyesight-on-tab: aria-live="polite" on the list, a pending count in the tab title, and each card shows its expiry time. The TOTP input gains an accessible name, and the card loses its 3px side-stripe + wide glow in favor of the existing 1px amber border and a tight shadow.

Tests added (run in CI)

• tests/unit/test_dash_serve.py: six new shell assertions - live region present, TOTP aria-label present, no side-stripe, light block re-tunes all four signal tokens, title carries the pending count, expiry rendered. Each fails against the previous shell.

Security checklist

• [x] Fails closed on error / uncertainty (no auth/decision-path changes)
• [x] No secret, full file, or unredacted prompt logged or committed (expiry is a timestamp already serialized by /api/pending)
• [x] Any guardrail/learning change is raise-only (presentation-only)
• [x] Every BLOCK/AUTH carries reason codes + a human explanation (unchanged)

Edge cases covered / Deviations from plan / Risks introduced

• Title count resets when the queue empties (update sits past the rebuild-skip guard, which fires on any set change).
• aria-live is on the pending list only - the decision feed stays silent by design (it would be chatty).

[Anonymous]

Ticket changed by: fu351

• status: open --> closed