38dcca0cfe
Why: end-to-end test of "design a notification card with dismiss x button" surfaced that MiniMax-M2.7 emits a path node named "Dismiss Icon". Tokenisation gives "dismiss" but Lucide doesn't have a `dismiss` key — the resolver fell through prefix/substring fallbacks and wrote the placeholder lucide:circle, leaving the card with a hollow ring where the X should be. What: 5 new aliases added in lock-step to icon-dictionary.ts (client commonAliases) + icon.ts (server NAME_ALIASES per existing comment): - dismiss → x (close button intent) - closebutton → x (compacted from "Close Button Icon") - cancel → x (cancel-action close icon) - remove → x (remove-action close icon) - expand → maximize-2 - collapse → minimize-2 NOT aliased: `cross`. Lucide already ships a `cross` icon (the Christian-cross shape) and overriding it would lose that geometry. "Cross" disambiguation is left to the model — if it really means a close button, telling it to write "Dismiss Icon" / "Close Icon" via the icon-catalog skill is enough. Tests: 3 new it.each cases (Dismiss / Cancel / Remove Icon → /x/). 1069 / 1069 AI tests pass (was 1066; +3). |
||
|---|---|---|
| .. | ||
| __tests__ | ||
| api | ||
| opencode | ||
| plugins | ||
| utils | ||