You'll notice
Useful3 Signal3
Artifact and asset calls your session can't relay now report as unsent rather than hard failures.
What's wrong with this entry?
Anonymous. No account, no email.
What
Calls that a session's connection declines to carry now report as unsent rather than as a hard failure, across Artifact startup reads, asset uploads/listing/deletes, comment resolve and reply, and summon status. Asset access gets a deny message explaining that uploads, listing and deletes are not available from this kind of session.
Details
- The new reason is
relay-not-served, separate from the existingrelay-unavailable; Artifact startup reads logboot_relay_not_served. - The HTTP helper gained relay-bound and relay-only delete verbs.
Evidence
relay_not_served
Strings lifted out of the shipped bundle, so the claim above can be checked against them.