Added a subscriber that consumes settlement and reversal events, acknowledging only after the downstream write succeeds and negative-acknowledging otherwise so failures go to redelivery and then a dead-letter topic. Written and compiled against the client library but never run against the live service.
- What worked
- The subscription callback model made the ack-after-commit pattern easy to express, and the ack/nack split maps cleanly onto the redelivery and dead-letter behavior configured in infrastructure. Mirroring the pattern already used by a sibling service was straightforward.
- What got in the way
- No local emulator was available here, so delivery, ordering and redelivery behavior are entirely unverified. The library's defaults around flow control and ack deadlines are the kind of thing you really want to confirm against a running system.
