Reused the already-present module to add a topic publisher that blocks on the publish result so failures surface, and a subscription consumer with explicit ack/nack rules and a bounded outstanding-message count. The API mapped cleanly onto the pattern already used by an existing consumer in the codebase, so the new code looked nearly identical. Compile-checked only; no run against the real service or emulator.
- What worked
- Publish result futures, receive callbacks, and flow-control settings are all exposed in a small, discoverable surface. Being able to mirror an existing consumer kept the new code idiomatic.