vibed/quotesdb/.beans/quotesdb-fagr--implement-error-handling-consistent-error-envelope.md

title	status	type	priority	created_at	updated_at	blocked_by
'Implement error handling — consistent {"error": "..."} envelope for 400/403/404/422/500'	completed	task	normal	2026-03-10T23:32:11Z	2026-03-10T23:32:19Z	quotesdb-ghzc quotesdb-4t5j

The `quotesdb` API is built with Axum + Tokio, targeting Cloudflare Workers via `workers-rs`. It serves JSON at `/api/*` endpoints and persists data to Cloudflare D1 (production) or a local SQLite file via Turso (development). Source lives in `src/bin/api/`.

Shared types and utilities are in src/lib.rs — code placed there must compile for both the host target and wasm32-unknown-unknown.

All error responses must use a consistent JSON envelope: {"error": "message"}. The API returns errors with appropriate HTTP status codes: 400 Bad Request, 403 Forbidden (wrong auth), 404 Not Found, 422 Unprocessable Entity (validation), 500 Internal Server Error.

Implement an error type and Axum `IntoResponse` impl that serialises errors as `{"error": "..."}` with the correct HTTP status. Use this type consistently across all handlers — no handler should return raw strings or ad-hoc JSON error bodies. - All handler functions must return `Result` (or equivalent). - The error type should implement `From` conversions for `sqlx::Error`, `serde_json::Error`, and other common error types used in handlers. - 500 errors must not leak internal details to the client — log the full error server-side, return a generic message to the client. Use `superpowers:test-driven-development` — write unit tests that verify each error variant serialises correctly. Use `superpowers:verification-before-completion` before closing. Run in order from the `quotesdb/` directory:

cargo fmt
cargo check
cargo clippy
cargo test

`feat(quotesdb): implement consistent error envelope type for all API responses`