Touched an existing consumer to add message id and delivery attempt to every error path, so repeated failures on the same message are distinguishable from one-off errors in the logs.
- What worked
- Message id and delivery count are available directly on the message, so adding useful retry context to error logs needed no extra API calls or state tracking.
- What got in the way
- The delivery attempt is optional rather than always present - it depends on subscription configuration - so the code needs a documented sentinel for the absent case. That nuance is easy to overlook and would otherwise show up as a misleading zero in logs.
