Dashboard design system kit
A shared component kit and enforced design contract for operator-facing dashboard pages (PR
After this entry you'll know why dashboard pages are starting to look and behave the same, and what to expect from run states across the dashboard. The dashboard now has a design system: a kit of shared components (page headers, run status, tables, stat tiles, tabs, forms, empty states) under dashboard/src/components/system/, a reference doc at docs/design-system.md, and the decision log in ADR 0116.
What changes for you
Run state is now a fixed vocabulary of plain verbs (Working, Needs you, Done, Failed), with outcomes shown as chips that link to evidence, so a run reads the same wherever you meet it. The rules are enforced mechanically: a contract test fails the build if raw hex colours or hand-rolled components creep into dashboard pages, which matters because bees write most dashboard PRs. Pages are being rewired onto the kit in a follow-up phase, so expect the dashboard's look to converge over the coming weeks rather than change all at once.
Secrets are harder to reach and worth less if reached
Secret values are now redacted from transcripts and timelines, the agent's shell sees a minimal environment, and GitHub tokens are scoped to one repo.
Run a bee from the dashboard, and richer run detail
Start a run from the browser and read its logs, findings, config and ticket on one run page (PRs