chore(ui): prune the unused vendored color tokens

[renefloor]

Stacked on #182 — review and merge that first; this PR's base is feat/update-color-tokens, so its diff is only the cleanup.

stream_tokens.dart carried 502 constants of which 163 were read. This PR removes the 159 unread color constants (158 in light/, 159 in dark/ — see the asymmetry note below). The dimension constants are deliberately left alone — see the note at the bottom.

The unread constants were unreachable as well as unread: the files sit under internal/, are excluded from the barrel contract, and are imported by exactly two files — stream_colors.dart (light only) and stream_color_scheme.dart (both). Nothing public is touched.

One commit per category, so a bisect stays meaningful:

Commit	Dropped	Why it was dead
c46b2da	4	backgroundElevationElevation0..3 — unread, and the names no longer exist upstream after the core/chat/video namespace split.
1f12b4b	124	Derived component tokens (badge, button, avatar, control, chat, input, reaction, presence). Dead by architecture: only root semantics are vendored, and a component re-derives its values from a StreamColorScheme field. StreamBadgeNotification reads colorScheme.accentError, not a badgeBgError constant.
c662af3	31	Root semantics whose field resolves through the generated swatch instead (textPrimary ??= chrome.shade900). Verified against the resolved swatch shade in both modes before deleting — redundancy, not a competing value.
38f7062	—	Docs only: refreshes the two skill claims this prune invalidates.

Also fixes a light/dark asymmetry

dark/ carried borderUtilityFocus (0x4078A8FF) with no counterpart in light/ — 501 light vs 502 dark. Upstream has only border/utility/**focused** ({brand.150}), which generates #C3D9FF light / #19418D dark, exactly what borderFocus ??= brand.shade150 already resolves to. So it was a stale name carrying a stale value, and nothing read it.

Both files now declare 343 identical constants. That symmetry is what lets the check:tokens guard in the follow-up PR pass.

Verification

analyze is the load-bearing check here: these are static const members reached only through a prefixed import, so a deleted-but-used constant is an undefined_getter compile error, not a lint. It passes across all four packages, and --ignore="*example*" does not exclude the gallery, so that is analyzed too.

The deletion is exactly minimal rather than approximate: 163 color constants remain and all 163 have a reader. No deleted name has a reference anywhere in the repo — including apps/, scripts/, tests, and the tracked generated output.

format:verify and check:barrels pass. flutter test is +397 -56, but that is a null result rather than evidence: no test, golden, or source file changes, so the count could not have moved. The 56 are the pre-existing macOS-golden drift.

Note if you grep this yourself: a bare-name search for accentPrimary or textPrimary returns ~1100 hits, because those are also StreamColorScheme field names. Every hit is colorScheme.X; the only reference form for a token is StreamTokens.X.

Scope: colors only

The "every constant has a reader" property now holds for colors. 180 dimension constants (size*, space*, radius*, font*, lineHeight*, typography*, and the component dimension groups) remain unread, deliberately.

An earlier revision of this branch deleted those too, on the grounds that the package does not sync dimensions from upstream. That was wrong — those values mirror upstream exactly, ordering included, and typography specifically comes from the web flavor, the only one carrying the Geist family this package ships.

They are unreferenced for a different reason: StreamSpacing, StreamRadius and StreamTokensTypography hard-code the same numbers instead of reading the constants. That is the swatch-versus-baked-hex hazard one layer up — nothing ties the class to the constant it mirrors, so the two can drift silently.

Deleting them would remove the evidence of that gap rather than the gap, so it is handled separately by wiring those classes to the constants. The check_tokens.dart guard that fails CI on an unreferenced token moved to that PR too, since it can only pass once the dimensions are wired.

This also resolves an apparent tension in the skill: "do not vendor button/*" governs button colors, which this PR drops, while the dimensions carve-out keeps buttonPaddingX* and friends.

No changelog entry

Deliberate. The policy is conditional on changing package behavior, and nothing read these constants. StreamTokens is internal — private constructor, under internal/, listed in check_barrels.yaml's internal_dirs, and exported from no barrel — so the removals are outside the deprecation policy too.

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 62adf9d2-3f3c-4c81-b317-3c6f48872db7

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 68.57%. Comparing base (16869c5) to head (38f7062).
⚠️ Report is 1 commits behind head on feat/update-color-tokens.

Additional details and impacted files

@@                    Coverage Diff                    @@
##           feat/update-color-tokens     #183   +/-   ##
=========================================================
  Coverage                     68.57%   68.57%           
=========================================================
  Files                           210      210           
  Lines                          8593     8593           
=========================================================
  Hits                           5893     5893           
  Misses                         2700     2700           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.