Reduce release image size

[freshwax-codex]

Summary

• package the Next.js standalone runtime instead of the full production dependency tree
• bundle the BullMQ worker ahead of time while sharing the generated Prisma client
• retain automatic versioned migrations through an isolated, version-matched Prisma CLI
• report compressed image and layer sizes in the release workflow

Impact

The locally built Linux image measured approximately 176 MB compressed, down from the current approximately 350 MB release image. Startup remains a single-container flow: migration preparation and prisma migrate deploy run first, followed by the worker and web server.

The migration preparation script runs beside the standalone Prisma client and receives the isolated CLI path explicitly. This keeps container startup offline-safe and prevents Prisma from installing packages into the running container.

Validation

• npm run lint
• npx prisma validate
• npx prisma generate
• npm run build
• built and inspected the conflict-resolved Linux Docker image
• verified clean automatic migration, web health, and bundled worker operation
• verified populated schema upgrades from v0.0.4 and v0.1.0
• verified FRESHWAX_SKIP_DB_PUSH and FRESHWAX_DISABLE_WORKER
• verified missing-variable and migration-failure paths
• verified signal propagation and shutdown
• validated release workflow YAML and image-size reporting expressions