# Token inventory — every declared and raw value in `html/` **Task:** `T3.1` · **Items:** `C3` part 1, `S5` part 1 · **Produced:** August 15, 2026 **Branch:** `feat/wp-suite-r2-implementation` · **Read by:** `T3.2`, `T3.5`, `T9.3` This is the mapping table `T3.2` builds from. Nothing here changes a stylesheet — `T3.1` is inventory only. Everything below was read from the working tree at `b105135` (end of wave 2), not quoted from the review. **Read [§8 Near-duplicates](#8-near-duplicates--where-unintended-visual-change-will-come-from) before writing a single line of `T3.2`.** That section is the whole risk in this wave. --- ## 0. The rule this wave is enforcing From `CLAUDE.md`: > After wave 3 there is exactly one place a color, spacing or type value is defined. Page > stylesheets alias that source and declare nothing new. And the constraint `T3.2` adds on top: > **Do not** change any rendered value in this task. Those two together mean one thing that has to be said out loud, because it is the difference between a clean wave 3 and a broken one: > ### Consolidation is not unification. > > Where two sheets declare the **same** value under different names, `T3.2` collapses them to > one declaration and aliases the names. That is free — nothing renders differently. > > Where two sheets declare **different** values for the same role — `--shadow-lg`, the two > banner-border greens, the three mono stacks — `T3.2` gives **each value its own canonical > name** and records the pair in §8. Collapsing those is a *visual change*, which `T3.2` > forbids. It belongs to `T3.3`/`T3.4`/`T3.5` or to `backlog.md`. > > A "consolidation" that quietly picks a winner between two near-identical greys is exactly > the failure this wave exists to prevent. --- ## 1. Scope: what "four token systems" actually means `wave-3.md:22` and `IMPLEMENTATION.md` both say "the four stylesheets". Per **D1** in `docs/reference/file-map.md` there are **six**, and after `T2.2` a seventh surface matters: the launcher's inline `