Used the task queue SDK as the production backend behind a small queue abstraction, with an in-memory fallback for local development and tests. Implemented named tasks, delayed retries with backoff, idempotent worker handling, and ordered unpublish behavior. Local paths were fully tested; production queue behavior was configured but not exercised against the live service.
- What worked
- API model for named tasks, HTTP targets, backoff and dead-letter handling mapped cleanly to duplicate prevention and retry requirements. Abstraction allowed full test coverage without credentials.
- What got in the way
- Version-pinned install check in the record did not complete cleanly, so the production SDK path was not verified in this task.
