Three copies of the theme engine had drifted, and the same button rendered at three densities depending on which tool drew it. This release makes theming one thing, owned once, and gives every tool the same shell.
One engine
- Moved out and shared The theme and density engine left the application client for a shared library path, ending the three divergent copies. The golden CSS snapshot transferred byte for byte.
- A density ladder Four steps from extra small to large on a 20-pixel base. Every control is one step smaller at medium than before; touch targets on mobile are unchanged.
- Hosts extend it A tool supplies sparse density overrides and registers its own component kinds without a library release.
- A bridge to the component framework Density and field tokens reach the framework's own CSS variables through cascade layers, with no importance overrides, and a runtime check catches a layer inversion that once dropped themed fonts silently.
What the user gets
- Dark mode A dark palette, and a watcher that follows the operating system's appearance.
- A theme of their own A user's theme resolves from their record with the company as fallback. Choosing is one role, editing definitions another.
- One shell Twelve entry points across three repositories bootstrap through one function. The shell owns the toolbar, the drawer, notifications, error transport, offline detection in eight locales, and the session health check.
Consistency in a product suite is not a design value. It is the absence of three copies of the same code.