Errors from our API reach you unchanged again

The error page at the edge recognised our app by a header that our API responses do not carry, so a real error from the API, with our error code and the link to the docs, was replaced by a generic "unavailable" message. Every response from the platform now carries a fixed header the edge checks first, so an agent or the command line tool sees the error we meant, and the health endpoint's own status passes through untouched.