auth/boundaries
An error response to an unauthenticated or low-trust caller includes the internal exception text, stack trace, config value or internal metric as-is, instead of a short neutral status. The way the response is built, or the exception-to-response mapping, is what leaks.
An API route returns {error: e.message} on failure, and a failed login shows the caller the database host name and the SQL that broke.
Not a second route that skips an existing redaction step — that is Second entry point skips the check.
No published story mentions this species yet. When a hunter publishes one after catching it, it appears here.