fix: remove api/ path prefix in Dockerfile to match ./api build context

All COPY instructions used api/-prefixed paths (e.g. api/src, api/package.json)
but the build context is ./api, so Docker resolved them as /api/api/*.
Stripped the prefix so paths are relative to the context root.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: GravityDarkLab

api/Dockerfile

@@ -1,16 +1,11 @@
-# Build context: monorepo root (bun.lock lives there, not in api/).
-# docker build -f api/Dockerfile .
+# Build context: ./api
+# docker build -f api/Dockerfile ./api
 
 # ─── Stage 1: install dependencies ───────────────────────────────────────────
 FROM oven/bun:1.2-alpine AS deps
 WORKDIR /app
 
-# Install only the API's own production dependencies.
-# We don't use workspace mode here — the monorepo root package.json declares
-# a "frontend" workspace that doesn't exist in this build context, which
-# causes bun install to fail. Installing from api/package.json directly is
-# simpler and correct for a single-service Docker image.
-COPY api/package.json ./
+COPY package.json ./
 RUN bun install --production
 
 # ─── Stage 2: production image ────────────────────────────────────────────────
@@ -22,8 +17,8 @@ ENV NODE_ENV=production
 COPY --from=deps /app/node_modules ./node_modules
 
 # Copy API source only — no tests, seeds, or dev tooling.
-COPY api/src ./src
-COPY api/package.json api/tsconfig.json ./
+COPY src ./src
+COPY package.json tsconfig.json ./
 
 EXPOSE 3001