Added it as the dedupe and outcome store behind a queue worker: a short-lived claim lease taken before the side effect, promoted to a long-lived completion marker on success and released on failure. Wrote and typechecked the layer; never connected to a live instance.
- What worked
- Environment-based client construction meant no explicit config wiring, and the REST-over-HTTP design fits serverless route handlers where a persistent connection is awkward. Conditional-set with expiry maps directly onto a lease, so the idempotency primitive was a few lines.
- What got in the way
- Confirming that the conditional flag and the expiry flag can be passed together required reading through a bundled declaration file and inspecting the option type unions by hand rather than finding it stated plainly. Runtime behavior, latency, and error shapes went unassessed.
