LevelFive-Studio yanks Helix Tribune off Cloudflare and replants it on AWS

@saratpediredla-level5 has rebuilt the helix-tribune fork end-to-end on Amazon Web Services. The frontend now runs on CloudFront and Lambda instead of Cloudflare's edge network, the backend lives in a containerized service with LibreOffice baked in for document conversion, and the database moves off Supabase onto Aurora - Amazon's managed Postgres - fronted by a connection pooler. Infrastructure is described in one place using SST, so the whole environment can be deployed as a unit.

The rewrite was deliberate rather than cosmetic. The team swapped Supabase's built-in authentication for Clerk, a third-party identity service, and pulled out Supabase's row-level database permissions in favor of access checks written directly into the backend routes. Object storage moves to S3 and email switches to SES, Amazon's transactional mail service. A companion document spells out which files will fight with future updates from the upstream Mike project and which won't.