[sbalabanov]

TL;DR: Explain why bad queue information is logged and rejected, not retried.

Summary

This is a comment-only clarification of the existing policy: invalid queue information is logged and rejected, not retried. The same bad input will not repair itself, so any follow-up is an operator decision. With no later dead-letter queue, rejection may mark the delivery finished and discard it.

Repro

1. Send a message whose queue fields disagree, such as Tenant=tenant-a and queue_name=tenant-b.
2. Validation logs the error and rejects the message before the handler runs.
3. With no later dead-letter queue, rejection may mark it finished without another attempt. This PR documents that existing outcome; it does not change or retry the message.

Test Plan

Checked with the existing tests:

• Invalid queue information is rejected before the handler runs.
• SQL rejection without a downstream dead-letter queue is still acknowledged; normal dead-letter handling is unchanged.
• Existing validation tests and error logging are unchanged; the net code diff is only the explanatory comment.

Revert Plan

Remove the comment; existing message handling stays the same.

Issues

[cla-assistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[cla-assistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}