What probably matters to youSection of the release
What
Passing an unusable socket path used to be logged and ignored. It now fails with a user-facing error naming the flag, spelling out what was rejected: a remote or UNC path, or a pipe name with extra segments or a trailing dot or space.
Details
The refusal is recorded as a start-failure cause path_refused; when the path did not come from the flag explicitly, it is recorded without throwing.
Storage is now threaded through peer sends and shutdown, so peer notices and hold receipts carry it.
Evidence
not a usable local socket address (a remote/UNC path, or a pipe name with extra segments or a trailing dot/space)
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
