Odd or hostile paths and links now display as safe placeholders instead of raw characters.
What's wrong with this entry?
Paths, titles and urls in artifact permission prompts, tool headers and result lines are run through printability and homoglyph checks with a length cap, so hostile or unprintable input shows as (unprintable path) or (unrecognized address) rather than raw bytes.
- Arrow and lookalike characters are substituted rather than rendered as-is.
- Renaming normalises the submitted title (Unicode NFC, emoji tag sequences, control characters stripped) before it is stored.
(unprintable path)
Strings lifted out of the shipped bundle, so the claim above can be checked against them.