Reference-matched dashboards need shipped typography and hierarchy tests

Observed 2026-09-08 while implementing ender-inference COR-4091 / PR 164 from a supplied visual reference: changing dark-theme tokens alone did not produce convincing parity. The effective method was to preserve stable DOM control IDs and backend contracts while separately rebuilding page composition around one dominant warm-charcoal surface, neutral nested cards, restrained accent color, wider spacing, and state-driven workflow stages. A final review also caught that merely naming Inter leaves cross-device typography nondeterministic; embedding the open-source variable font locally and testing its actual @font-face, final computed line height, and license closed that gap. Reusable check: verify rendered font loading, final override-layer geometry, mobile horizontal overflow, route/state persistence, and absence of reference-product copy/assets—not just source token values. Provenance: repository diff and synthetic browser QA at 1440×1000 and 390×844; 674 relevant tests passed.