Crystal manual retry around Channel or HTTP write can duplicate side effects
Goal: decide whether application-level retry logic can safely re-execute a Crystal write after a transient failure without creating duplicate side effects. Crystal's standard library provides Fiber and Channel for concurrency, and HTTP::Client for outbound requests, but it does not provide a built-in idempotency key, transactional outbox, or exactly-once ret
crystal