Adam Moussa eae4d67e00 Apply cross-review findings (Phase 2/4/5 hardening) ... From the cross_reviewer (GPT-4.1) per-PR passes, now that the orchestrator is back up: Phase 2 (classifier): - Process ALL S3 records, not just event["Records"][0] — batched notifications no longer silently dropped (the review's only BLOCK). - Derive the partition dt from the S3 event time, not the Lambda wall-clock — stable across retries / the midnight boundary. - Add an SQS dead-letter queue so a failed run surfaces instead of dropping a day's data after Lambda's retries. Phase 4 (Slack): - Stage throttling (rate 10 / burst 20) on the public /slack/interactions HTTP API. (AWS WAF doesn't attach to apigwv2 HTTP APIs; stage throttling is the mechanism.) Phase 5 (Grafana): - Explicit encrypted=True on the gp3 root volume. Tests: synth assertions for the DLQ, stage throttling, and the encrypted volume. 60/60 pass; cdk synth green for both stacks. Deferred NITs (print->logging, sig- failure source-IP logging, S3 versioning, CIDR-maintenance runbook) -> Phase 6. NOTE: like the earlier deploy fixes these sit on phase-5 but span phases — the classifier/DLQ to #8, throttling to #10, encryption to #11 — reconcile at merge. The encrypted-volume change needs the deferred clean instance replacement to take effect (can't encrypt a live volume in place).		2026-05-29 11:29:14 -04:00
..
classifier	Apply cross-review findings (Phase 2/4/5 hardening)	2026-05-29 11:29:14 -04:00
slack_post	Fix dashboard rendering: barchart panel type + metadata off the table prefix	2026-05-28 18:49:41 -04:00