# ARAD LMS OS — UI, Appearance and Licensing Checklist

An item is checked only after implementation, migration and verification are complete.

- [x] Audit existing icon, toggle, appearance, window and plan implementations.
- [x] Establish semantic design tokens and global appearance/theme contracts.
- [x] Replace every switch/toggle implementation with the shared Switch components.
- [x] Standardize explorer icons and migrate Exams and Roles & Access.
- [x] Make every system surface consume the global transparency setting.
- [x] Add system/light/dark modes and Windows-like accent themes.
- [x] Migrate feature UI to shared primitives, components and patterns.
- [x] Replace plan/subscription gating with an annual organization license.
- [x] Run source audit, accessibility checks, interaction/visual tests, TypeScript, lint and production build.

## Contracts

- Feature code owns domain data and workflows; the design system owns visual primitives.
- Feature modules must not implement their own switch, explorer icon tile, window shell or color palette.
- Explorer tiles use a 48px container and 24px Lucide glyph. Action glyphs use semantic 16/20/24px sizes.
- Transparency changes surface alpha and blur, never the opacity of text or interactive content.
- Accent colors are semantic tokens and must retain readable focus, selection and status states.
- License access is resolved by one entitlement service; feature components do not inspect dates or license status directly.