The invisible separator
A code point survives while the glyph does not announce it.
The strings project and project may render identically. The second contains U+200B ZERO WIDTH SPACE between “pro” and “ject.” A raw-code-point scanner sees the distinction immediately. A keyword matcher, tokenizer, search index, or line-breaking engine may handle it differently.
A: U+0070 U+0072 U+006F U+006A U+0065 U+0063 U+0074
B: U+0070 U+0072 U+006F U+200B U+006A U+0065 U+0063 U+0074
Defensive test: preserve the original, enumerate all code points and Unicode categories, then compare NFC and NFKC copies. U+200B generally remains under those normalization forms, so an explicit format-character policy is still required.
Demonstrates
Visually similar text can have a categorically different logical representation that deterministic software can detect.
Does not demonstrate
That every tokenizer preserves the character, that every model understands a code, or that the anomaly is malicious.