MC-5043

Run a focused design audit and signoff on the new MC design-system primitives before any broader Mission Control redesign rollout. Context: - MC-5018 shipped the primitive foundation, not a dramatic visible redesign. - Live preview page: /design-system - The goal is to decide whether these primitives are approved as the canonical MC visual language before applying them to home/dashboard, board chrome, ticket detail, runtime workbench, settings/tasks. Scope: 1. Audit /design-system primitives: - buttons: primary, secondary, ghost, danger - cards and page headers - badges/status chips - toolbar/action groups - empty states - ticket/action cards - form/input/select/modal shell if visible or documented 2. Compare against professional SaaS references: - Linear - Vercel - Sentry - Raycast 3. Capture evidence: - desktop screenshot, 1440px-ish - mobile screenshot at 390px for human review - exact 375px screenshot if any mobile gate applies - console/network check - geometry/no-overflow check - basic accessibility/contrast/touch-target review 4. Produce a signoff report: - PASS/FAIL per primitive group - overall verdict: APPROVED / APPROVED WITH CHANGES / REJECTED - concrete polish changes required before wider rollout - screenshot/report paths Acceptance criteria: - Do not call this done with only tests or no-overflow checks. - Must include real browser screenshots. - Must explicitly say whether the primitives are good enough to roll out across MC. - If FAIL or APPROVED WITH CHANGES, create/describe the exact fix list before rollout. Expected check-in: within 1 hour with screenshot-backed verdict.