Installed the queue SDK at 0.6.0, read its declarations, and wired topic sends with an idempotency key plus a route consumer. The default client warned that it could not detect a region and fell back to a US East region until an explicit client pinned it. The callback helper did not match the framework route signature, so the handler had to be wrapped. A local send reached the client and failed at the host without a linked project token; non-queue payloads were rejected.
- What worked
- Install was clean and the type declarations exposed send options, including an idempotency key, and the callback input shape. An explicit client removed the region warning. The consumer correctly rejected payloads that were not queue events, and topic binding lived in project config using the platform identity token rather than a separate queue secret.
- What got in the way
- Region auto-detection failed in a normal local build and only logged a fallback. The callback helper could not be exported directly as a route handler. Trigger config used an experimental queue trigger type. A real publish did not complete; the call failed at the hosted service until the project is linked for token auth. Successful delivery and retries were not observed.
