# Brand & Product System changelog

## [1.1.2] — 2026-09-22

- Require persistent global navigation while content scrolls (NAVIGATION-06), with safe-area/anchor clearance, independently scrollable long side menus and real-browser desktop, narrow and zoom acceptance checks.

## [1.1.1] — 2026-09-22

- Connect the documented palette to generated runtime tokens and shared workspace controls across official apps. Add runtime drift checks and the suite adoption record.
- Record concrete simplifications and menu-focus/mobile fixes while keeping full workflow/accessibility certification separate.

## [1.1.0] — 2026-09-22

- Make the suite logo, buttons, menus/tabs and fields/panels first-class entries in the visual catalogue and search.
- Capture the existing website skewer and wordmark in a suite registry, with downloadable light/dark marks, square favicon, reusable HTML lockup, clear-space rules and explicit legacy guidance.
- Define measurable component geometry in tokens.json and generate both the reference CSS and a portable UI dimension table from it.
- Show button hierarchy, sizes and six states, keyboard-operable tabs, sidebar selection, form states and panel anatomy. Examples remain local demonstrations.
- Keep product-logo registry 1.0.0 and existing runtime styling unchanged; adoption is step two.

## [1.0.0] — 2026-09-22

- Extend the permanent logo library into a searchable, versioned product design standard with 19 chapters and 111 traceable rules.
- Define the warm-paper/forest target palette, accessible semantic states, typography, spacing, layouts and component behavior; preserve logo geometry and registry version 1.0.0.
- Define next-action, source-of-truth, central permission, SSO, automation, AI, privacy, incident, reporting and TV-mode principles with verification criteria.
- Add light/dark interactive reference examples, a downloadable review template, a staged app adoption plan and generated Markdown for the future public repository.
- Add deterministic build/drift checks and contrast validation. Runtime apps are not declared conformant; shared-token migration and per-app redesign remain step two.