IngestQueue.put() turns ANY error into an innocuous-looking 503

IngestQueue.put() is supposed to convert exactly one condition — the queue staying full for the entire timeout window — into a BackpressureError, which the router turns into a 503. The except clause currently catches any Exception, not just the asyncio.TimeoutError that asyncio.wait_for raises on a genuine timeout. If some other, unrelated bug ever raised an exception from inside this code path, it would be silently reclassified as ordinary backpressure — a 503, indistinguishable from the DB just being slow. Nobody gets paged, no error is logged as an error, and whoever's on call has no way to tell "the queue is genuinely full" apart from "something actually broke" from the outside.

IngestQueue.put() is supposed to convert exactly one condition — the queue staying full for the entire timeout window — into a BackpressureError. Its except clause catches any Exception, so an unrelated bug anywhere in that code path would be silently reclassified as ordinary backpressure.

1. pytest practice_tickets/tests/test_ticket_12_queue_put_exception_type.py -v — replaces the internal queue's put() with something that raises a RuntimeError and confirms what IngestQueue.put() does with it.

Catching Exception "just to be safe" is a common instinct, but it means the function can no longer distinguish "the specific thing I know how to handle" from "literally anything else that could possibly go wrong." That distinction is the entire value of a narrow except clause — it's what lets an unrelated bug fail loudly instead of being silently absorbed into a well-understood, already-monitored code path.

Look at the except clause in IngestQueue.put (app/buffer.py). asyncio.wait_for raises a specific, well-documented exception type on timeout — which one, exactly, and how does that compare to what's currently being caught?