Add semantic frontend design tokens

docs/tables_frontend_overhaul_implementation_plan.md

@@ -38,6 +38,7 @@ It is intentionally implementation-focused:
 | Date | Phase | Status | Notes |
 | --- | --- | --- | --- |
 | 2026-03-21 | Phase 0 | Completed | Created overhaul branch, audited the current frontend, and locked the route map, component boundaries, migration path, and shared-state ownership. |
+| 2026-03-21 | P1.1 | Completed | Replaced the legacy token root with semantic background, surface, text, border, focus, shadow, and semantic accent ramps while keeping compatibility aliases for incremental migration. |
 
 ### Lessons Learned
 
@@ -239,6 +240,23 @@ Create the implementation foundation so the visual overhaul does not start with
 
 ## Phase 1: Design System And Application Shell
 
+### Status
+
+`In progress`
+
+### Task Progress
+
+| Task | Status | Notes |
+| --- | --- | --- |
+| `P1.1` | Completed | Semantic token layer landed in `wwwroot/app.css` with compatibility aliases to keep existing pages stable. |
+| `P1.2` | Pending | Typography update will change font loading and global font tokens. |
+| `P1.3` | Pending | Theme modes will be introduced after typography is stable. |
+| `P1.4` | Pending | Theme persistence depends on the theme state service. |
+| `P1.5` | Pending | Shell replacement follows once tokens and theme plumbing exist. |
+| `P1.6` | Pending | Shell slots and nav utilities depend on the new shell. |
+| `P1.7` | Pending | Skip link and landmark work will land with the shell markup. |
+| `P1.8` | Pending | Tools-specific shell emphasis is final Phase 1 polish. |
+
 ### Goal
 
 Establish the shared shell, tokens, typography, and theme system that every destination will inherit.