fix(serverust-events): SqsBroker não faz ack silencioso sem handler/ARN

[cursor]

Problema

Com Lambda ESM e ReportBatchItemFailures, qualquer registro SQS ausente de batchItemFailures é tratado como sucesso e removido da fila pelo runtime.

SqsBroker::handle_sqs_event ignorava mensagens sem event_source_arn parseável ou sem handler para o nome da fila extraído do ARN, devolvendo batchItemFailures vazio para esses registros. Cenário concreto: typo no subscribe("orders", …) vs fila real order, ou payload sem ARN; a função retornava sucesso e as mensagens eram descartadas sem processamento (perda de dados do ponto de vista da aplicação).

Correção

• Sem ARN válido ou sem handlers para a fila: se existir messageId, adiciona entrada em batchItemFailures para retry/DLQ.
• Sem messageId: mantém o limite anterior (só warn); a Lambda pode ainda fazer ack — documentado.

Validação

• cargo +stable test -p serverust-events --features sqs
• cargo +stable clippy -p serverust-events --features sqs --all-targets -- -D warnings
• cargo +stable check --workspace

Changelog

Entrada em [Unreleased] em CHANGELOG.md.

  

[cursor]

Risk assessment (automation)

Verdict: Medium–High risk (evidence from diff only).

Why

• Surface: SqsBroker::handle_sqs_event in serverust-events — Lambda SQS ESM + ReportBatchItemFailures batch handling.
• Behavior change: Records without a parseable event_source_arn or without a registered handler previously produced no batch_item_failures (implicit success → Lambda could remove messages). They now add batch_item_failures when message_id is present, changing retry/DLQ vs silent drop for misconfiguration paths.
• Blast radius: Any deployment using this broker with partial batch failure reporting; operational semantics of “success” vs “failure” for edge cases shift (intended correctness fix, still pipeline-level).
• Evidence: consumer.rs control-flow rewrite + sqs_consumer.rs expectations + CHANGELOG.md.

Review policy: Under the automation rules, Medium+ would require human review (up to 2 reviewers) and would not be eligible for bot self-approval at Medium–High.

Merge state: This pull request is already merged (merged_at present). No reviewer assignment or approval action taken here.

CODEOWNERS: No CODEOWNERS file found in the repository snapshot used for this run.

  

_{Sent by Cursor Automation: Assign PR reviewers}