Semantic interactive tokens are missing success and info tones

[pomfrida]

Found during the Chip migration (#5225). The interactive token groups from the #5280 restructure cover accent, neutral, danger and warning — but not success and info:

Group	Covers	Missing
background-interactive-*	accent, neutral, danger, warning	success, info
border-interactive-*	accent, neutral, danger, warning	success, info
text-interactive-*	accent, danger, warning, link	success, info, neutral
icon-interactive-*	accent, danger, warning, link	success, info, neutral

The static tokens (background-success, text-info, …) do exist, but they cover calm surfaces like banners — not hover/pressed states.

Consequence: any component with interactive success or info tones (Chip today, more to come) cannot use the semantic layer and has to point at raw shade numbers instead. That bypasses the design intent — and decisions like the resting-shade question in #5282 then have to be duplicated by hand in component code instead of landing once in Tokens Studio.

Flagging so the missing tones can be added to the semantic sets in Tokens Studio — ideally in the same round as #5282, so components can drop the raw-shade workaround.

[claude]

These issues look related and may be worth cross-referencing:

• Author import-ready Tokens Studio JSON for the missing beta colour tokens #5221 — Author import-ready Tokens Studio JSON for the missing beta colour tokens (closed): the direct predecessor for this class of gap. Closed as completed on 5 Aug because the feat: update tokens from Tokens Studio release #5280 restructure covered most of its scope; its closing comment enumerates what the release did and didn't cover, and the missing success/info tones look like another entry for that "not covered" list.
• Dark palette scales are non-monotonic: step 6 duplicates step 3 #5282 — Dark palette scales are non-monotonic: step 6 duplicates step 3 (open): the other Tokens Studio fix found during the same Chip migration, and the one this issue asks to be bundled with so both land in a single Studio round.
• [Chip] Migrate to new beta colour tokens #5223 — [Chip] Migrate to new beta colour tokens (open): the migration that surfaced the gap; Chip's success and info tones are the ones currently forced onto raw shade numbers.
• 🎨 Implement Alpha‑Channel approach for disabled states #4741 — 🎨 Implement Alpha-Channel approach for disabled states (open): the other semantic gap the feat: update tokens from Tokens Studio release #5280 restructure left open, spun out of Author import-ready Tokens Studio JSON for the missing beta colour tokens #5221 in the same way — same source, likely the same Studio round.

This comment was generated by an LLM and may be inaccurate. Please verify that the linked issues are actually relevant.

[alexlvrs]

Deliberately out of scope:

• neutral for text/icon interactive — already covered by the primary text/icon tokens, so a dedicated interactive neutral would just duplicate.
• selected state — stays scoped to accent and neutral only.

[pomfrida]

@alexlvrs Thanks — success/info in the interactive groups is what Chip needs, and using text-primary/icon-primary for neutral works fine on our side.

Just to confirm the intent behind that last part: neutral interactive text is meant to be state-static (always neutral-12), unlike accent which shifts 10→11→12 across default/hover/pressed? If that's deliberate we'll write it into the migration recipe (#5245) so it reads as a design choice rather than a missing token.

[eddiman]

@alexlvrs has added these in Tokens Studio — verified against the live project on main just now. 36 new tokens, exactly the gap in the table above and nothing else:

Group	Added
background.interactive.{success,info}.{emphasis,muted}	12
border.interactive.{success,info}.{emphasis,muted}	12
text.interactive.{success,info}	6
icon.interactive.{success,info}	6

They follow the existing ladders — emphasis 9→10→11, background muted 2→3→4, border muted 4→5→7, text 10→11→12. The deliberate exclusions from the scoping comment held: no text/icon.interactive.neutral, and no selected for the new tones.

#5282 is fixed in the same round as requested — input.scale.dark.6 went 0.47 → 0.595, so it now sits between step 5 (0.58) and step 7 (0.61) instead of duplicating step 3.

Both are waiting on a Tokens Studio release + studio tokens pull before they land in the repo — the export from #5280 still shows the old state. Once that's through, Chip can drop the raw-shade workaround.