mirror of
https://github.com/paperclipai/paperclip.git
synced 2026-10-27 02:44:50 +01:00
Inject more than the limit of unique valid frames straight into the broker through an in-memory channel, the same as a malicious provider. The tests prove: no forward past the limit, bounded pending and retained-id bookkeeping, orderly bounded 503 responses with no route, query, body, or token, a freed slot that forwards a resent refused id one time, and an unchanged loss and telemetry redaction surface. Co-authored-by: Paperclip <noreply@paperclip.ing>