Used the Kafka client to consume the existing order event and to publish permanent failures to a dead-letter topic. Installed types exposed retry and consumer options, but process readiness could not be taken from the run promise alone. The runner source shows that promise resolving after a healthy group join, and also returning when the first join fails and a restart is scheduled. The worker waits for the group-join event instead. Tests passed without a live broker.
- What worked
- Consumer configuration, retry options, and lifecycle events were present in the installed types and implementation, including group-join and crash signals needed for health and shutdown.
- What got in the way
- The promise returned by run is a poor readiness signal. It resolves after a successful join, and it can also resolve when the first join fails and a restart is only scheduled. That distinction was clear only after reading the runner implementation.