Skills with visually identical names can no longer sneak past collision checks.
What's wrong with this entry?
Skill and command name collisions are compared after normalizing confusable characters, so a synced skill with a visually identical name can no longer slip past the check that drops it in favour of a local skill of the same name.
- Names are put through NFKC, then separators, control characters, format characters, default-ignorable code points and the braille blank U+2800 are stripped.
- All dash punctuation and the minus sign fold to
-; five colon lookalikes (U+A789, U+2236, U+0589, U+05C3, U+02D0) fold to:. - Case folding is applied last.
/[\ua789\u2236\u0589\u05c3\u02d0]/g
Strings lifted out of the shipped bundle, so the claim above can be checked against them.