What each finding means—and what it does not.

Decide Use the token unless the direct value must remain independent from theme or system changes.

Decide Merge it into the token if the small difference carries no real semantic or accessibility role.

Decide Keep separate semantic names when their roles may diverge; otherwise alias them to one canonical token.

Decide Keep both only if the subtle distinction communicates a state, layer, brand role, or accessibility requirement.

Decide Name its specific role or fold it into the established palette. One-off artwork and data visualization colors are often valid exceptions.

Decide Consolidate levels that do the same job; preserve levels that express distinct states or depth.

Decide Standardize the notation when it improves search and maintenance. Keep authored formats when a tool or color space requires them.

Decide Align it when the text serves an existing role; keep it when the content hierarchy genuinely needs another step.

Decide Reuse the role’s line height unless content density, language, or typeface metrics justify the difference.

Decide Verify the loaded font’s axes. Variable fonts may make an in-between weight entirely intentional.

Decide Keep purposeful code, data, editorial, or display faces; remove accidental local stacks.

Decide Prefer one declaration path so later typography changes do not split the roles apart.

Decide Snap it to the scale unless geometry, optical alignment, or an external asset requires the offset.

Decide Confirm it as a local adjustment or replace it with the scale. Screen-reader-only geometry is excluded.

Decide Keep relative units when they must scale with text or context; otherwise use one convention.

Decide Use the nearest named utility when the difference is incidental; retain exact values for real geometry constraints.

Decide Reuse the established shape unless the component’s role needs a visibly different silhouette.

Decide Consolidate accidental differences; preserve widths that indicate focus, selection, or hierarchy.

Decide Keep the distinction only when it communicates a different control family or state.

Decide Reuse one recipe unless the difference creates a clearly distinct elevation or focus state.

Decide Name the overlay role and align it with the stacking scale; third-party widgets may need an explicit exception.

Decide Confirm whether layers, specificity, or source order can express the intent. Utility and accessibility overrides can be legitimate.

Decide Merge them when the layout change is shared; keep both when distinct breakpoints prevent a real failure.

Decide Confirm the unique transition or align it with the named responsive scale.

Decide Prefer a named threshold when related layout changes should stay synchronized.

Decide Merge them if the component changes in the same way; keep them when separate internal layouts truly need both.

Decide Promote it when it belongs to the wider system; keep it local when the component owns the decision.

Decide Confirm which layer owns the final value and remove declarations that no longer have a distinct purpose.

Decide Keep the override only when its higher precedence is explicit and intentional.

Decide Reuse the shared owner when the behavior is the same; preserve separate domain components when their responsibilities differ.

Decide Bring it back to the shared component or record why this context needs a maintained variant.

Decide Confirm the new vocabulary as intentional or return the source to an established value.

Decide Restore the repair, or record that the product decision changed. Regression status is ledger evidence, not guesswork.

Decide Inspect the new direct values and restore token use where the bypass was not deliberate.