You'll notice
Useful2 Signal1
Invalid file paths in a published artifact now name the actual problem instead of a generic error.
What's wrong with this entry?
Anonymous. No account, no email.
What
The error for an invalid file path inside a published artifact now names the actual problem: an empty segment, a segment made only of dots and spaces, a path separator, a NUL byte, or a reserved name shape. Absolute paths that normalize into a reserved shape are rejected outright rather than accepted after normalization.
Evidence
expected a non-empty array of segments, none empty or made only of dots and spaces, with no path separator, NUL or set-aside shape
Strings lifted out of the shipped bundle, so the claim above can be checked against them.