Fix Docker build process and YAML syntax

- Fix YAML syntax error in buildspec.yml (multi-line string causing build failure)
- Remove complex runtime Dockerfile generation from buildspec
- Use proper multi-stage Docker build with Prisma generation
- Update Dockerfile to copy Prisma client from custom location (src/generated/client)
- Follow Docker best practices: generate Prisma client during Docker build, not in buildspec

This ensures:
- Clean YAML without syntax errors
- Proper separation of concerns (buildspec handles build, Docker handles packaging)
- Prisma client generated consistently in Docker environment
- No manual file copying between build phases

Author: claudfuen

apps/web/Dockerfile

@@ -66,9 +66,8 @@ COPY --from=builder /app/public ./public
 COPY --from=builder --chown=nextjs:nodejs /app/.next/standalone ./
 COPY --from=builder --chown=nextjs:nodejs /app/.next/static ./.next/static
 
-# Copy the generated Prisma client (including WASM files)
-COPY --from=builder --chown=nextjs:nodejs /app/node_modules/.prisma ./node_modules/.prisma
-COPY --from=builder --chown=nextjs:nodejs /app/node_modules/@prisma/client ./node_modules/@prisma/client
+# Copy the generated Prisma client from custom output location
+COPY --from=builder --chown=nextjs:nodejs /app/src/generated/client ./src/generated/client
 
 # Switch to non-root user
 USER nextjs

apps/web/buildspec.yml

@@ -50,45 +50,9 @@ phases:
       - ls -la .next/standalone/public/ || echo "❌ .next/standalone/public/ not found"
       - ls -la .next/standalone/server.js || echo "❌ server.js not found"
 
-      - echo "=== COPYING PRISMA CLIENT FOR RUNTIME ==="
-      - echo "Copying generated Prisma client to standalone build..."
-      - mkdir -p .next/standalone/src/generated
-      - cp -r src/generated/client .next/standalone/src/generated/ || echo "Warning: Custom Prisma client not found"
-      - echo "✅ Prisma client copied to standalone build"
-
       - echo "=== BUILDING DOCKER IMAGE WITH BUILD ARTIFACTS ==="
-      # Note: We're using a simplified runtime Dockerfile here because the build artifacts
-      # are already created. For local development or standard CI/CD, use the main Dockerfile
-      # which includes the full multi-stage build process.
-      - |
-        cat > Dockerfile.runtime << 'EOF'
-        # Use Node.js Alpine for smaller image size
-        FROM node:18-alpine AS runtime
-
-        WORKDIR /app
-
-        ENV NODE_ENV=production
-        ENV NEXT_TELEMETRY_DISABLED=1
-        ENV PORT=3000
-        ENV HOSTNAME="0.0.0.0"
-
-        # Copy the complete standalone build (includes Prisma client)
-        COPY .next/standalone ./
-
-        # Create non-root user for security
-        RUN addgroup -g 1001 -S nodejs && \
-            adduser -S nextjs -u 1001 && \
-            chown -R nextjs:nodejs /app
-
-        USER nextjs
-
-        EXPOSE 3000
-
-        # Use node to run the standalone server.js
-        CMD ["node", "server.js"]
-        EOF
-
-      - docker build -f Dockerfile.runtime -t $IMAGE_REPO_NAME:$IMAGE_TAG .
+      - echo "Using proper Docker build process with Prisma generation..."
+      - docker build -t $IMAGE_REPO_NAME:$IMAGE_TAG .
       - docker tag $IMAGE_REPO_NAME:$IMAGE_TAG $REPOSITORY_URI:$IMAGE_TAG
       - docker tag $IMAGE_REPO_NAME:$IMAGE_TAG $REPOSITORY_URI:latest