Guardrails, UI Standardization, and Product Signals

Shipped

• Added guardrail scripts:
  • check-marketing-untouched.mjs to protect marketing surfaces
  • check-training-legacy-classes.mjs to prevent reintroducing legacy training CSS drift
• Standardized Button imports across the app for consistency (@/components/ui/button)
• Enhanced training styling foundations:
  • Training-specific tokens imported via globals.css
  • Added training-local UI primitives (Button/Card/Dialog) for cleaner consistency
  • Improved training layout/sidebar and added theme toggle support
• Expanded product signal checks so key flows are easier to measure before they reach users
• Continued accessibility improvements across dialogs and forms
• Added/updated documentation for styling boundaries and design system conventions

Why

• Guardrails keep the codebase coherent as UI systems evolve (and prevent accidental regressions)
• Standardized imports reduce component drift and styling inconsistencies
• Better product signals speed up iteration without exposing sensitive data

Next

• Ship user-facing builder improvements and duration schema upgrades
• Expand Insights into a genuinely day-1 valuable hub with robust empty states