[KAJdev]

Calling a remote function or task, reading pod logs, or uploading a build could fail with only an HTTP status. Printing the HTTP exception could also expose the account key or task token from request headers.

HTTP failures surface as AppHTTPError, an AppError subclass carrying the method, URL, status, and a response excerpt capped at 1,024 characters. For example, a 500 response containing {"error":"GPU capacity exhausted"} includes that explanation alongside the failed request. Job-status errors include the same detail and the job ID. If the body cannot be read, the error still reports the HTTP status.

Diagnostic URLs omit credentials and query strings. Excerpts redact reflected request credentials, including signed upload parameters, and exceptions carry no request headers.

Fixes CON-2061
Fixes CON-2057