Theme-aware status colors across Pekan
Status and emphasis colors throughout the desktop app now follow the active theme. Alerts, validation messages, priority badges, delivery states, destructive actions, informational callouts, and success indicators no longer rely on Tailwind's fixed light palette. Each state instead uses a semantic background, border, and text color defined by the current theme, removing pale blocks and bright outlines from Ember and Midnight while retaining clear distinctions between outcomes such as cancelled and failed, or delivered and needs attention.
The same semantic vocabulary now covers every renderer surface, including a dedicated warning border and complete contrast checks for modified, informational, special, warning, and stale states in the custom theme editor. Repeated priority styling has one shared definition, and a repository guard prevents fixed palette classes from returning. Agent worktrees also receive the live run-telemetry hook, and local verification now catches untranslated interface strings before an isolated branch can be reported as delivered.
Highlights
- Status and emphasis surfaces adapt cleanly to every shipped light and dark theme.
- Custom themes warn about unreadable semantic status combinations.
- A local guard prevents fixed Tailwind color palettes from returning.
- Isolated agent runs retain telemetry and block delivery on catalog violations.