t2-p3-02draft4–7h
Idempotency keys
requires: t2-p3-01
Spec
Idempotency-key support on task creation, so retried requests from flaky clients do not create duplicates. Test by firing the same request twice concurrently.
Why this matters
Concurrently, specifically. A sequential retry is caught by almost any implementation; two simultaneous requests find the race between "check if seen" and "record as seen", which is where the real bug lives.
Verify
No result yet. Run `learn verify t2-p3-02` locally, or push to trigger CI.
contract
unrun