[xirothedev]

Why

The self-hosted LocalStack lives on a LAN box — GitHub-hosted runners can't reach it. CI instead boots a throwaway LocalStack (S3-only community image, pinned s3-latest) as a job service container, exactly the pattern go-test already uses for Postgres.

What

New storage-smoke CI job, gated on the existing app paths filter:

• service: localstack/localstack:s3-latest, SERVICES: s3, health awslocal s3 ls
• seed webdevstudios-storage with the preinstalled aws CLI (dummy creds)
• bun run smoke:localstack — the committed StorageService put→get→delete check from feat(api): LocalStack S3 testing, path-style storage, dist boot + JWT TTL fixes #55

Trigger

Nothing manual: runs on every PR/push touching apps/api/** (or ci.yml itself, so this PR exercises it). workflow_dispatch still available for a manual run.

[xirothedev]

Found while testing the job live: localstack/localstack:s3-latest is discontinued (v2026.03 switched every localstack/localstack:*: latest tag to Pro-with-auth; the container exits with a license banner). Pinned to 4.4— the last free community release; verified locally that it boots unauthenticated, serves S3, andawslocal s3 ls` works as healthcheck.