Under the hood
Useful1 Signal3
Published-file reads gained a second route via a capability lookup; failures explain the relay is unavailable.
What's wrong with this entry?
Anonymous. No account, no email.
What
The check deciding whether published-file and asset reads can run is now satisfied by either the original condition or a new alternative that sits behind a capability lookup. When neither holds in a remote cloud session, the read fails as before with the relay reported unavailable, and its long explanation now lives in shared constants.
Details
- What turns the second condition on is decided by that capability lookup rather than by anything set in this build.
Evidence
relay_unavailable
Strings lifted out of the shipped bundle, so the claim above can be checked against them.