Publishing pins the exact file you approved, refusing device paths and flagging symlinks or hard links.
What's wrong with this entry?
Before publishing a file, Claude Code now classifies the source path. Device- and NT-namespace paths and loopback network paths are refused outright. Symlinked files, hard-linked files, a symlinked parent directory or a changed device/inode mark the source as unverified. The identity it resolved (device, inode, size, modification time in nanoseconds) is pinned to the approving tool use, so the approved file cannot be swapped for a different one before the publish runs.
- Loopback network paths are called out specifically because they name a local file while bypassing its verification; the tool asks for the path spelled plainly instead.
- Runs on the publish permission path itself, with no separate flag.
file_path: loopback network paths name local files but skip their verification — spell the path plainly
Strings lifted out of the shipped bundle, so the claim above can be checked against them.