Dockerfile: bump SPA cache-bust to 10 — force fresh build (drops Compare LLMs tab + stale endpoint copy)

Dockerfile

@@ -26,20 +26,30 @@
 ############################
 # Stage 1: build the SPA
 ############################
+# WORKDIR renamed (was /build) to break HF BuildKit's poisoned cache.
+# The previous /build mount kept a stale pnpm symlink at
+#   /build/node_modules/@types/katex
+# from an earlier failed deploy, and every subsequent `COPY frontend/ ./`
+# blew up with `cannot copy to non-directory`. Switching paths gets us
+# a fresh cache bucket; nothing in the project depends on /build itself.
 FROM node:20-alpine AS frontend
-WORKDIR /build
+WORKDIR /spa
 RUN corepack enable
 
-COPY frontend/package.json frontend/pnpm-lock.yaml ./
-RUN pnpm install --frozen-lockfile --silent
-
+# Copy ALL of frontend/ first — including package.json/pnpm-lock.yaml —
+# THEN install. Order matters: install runs ON TOP OF the source tree
+# instead of the source tree being overlaid on top of a pre-installed
+# node_modules, eliminating the directory-vs-symlink collision class
+# of failure entirely.
 COPY frontend/ ./
+
 # Same-origin API fetches (relative paths). The Space serves both API and UI.
 ENV VITE_PHYSIX_API_URL=""
-# Cache-bust marker. Bump when an SPA change isn't taking on the Space —
-# HF BuildKit occasionally reuses stage-1 output even when sources changed.
-# physix-spa-rebuild: 6
-RUN pnpm exec tsc -b \
+
+# Cache-bust marker. Bump when an SPA change isn't taking on the Space.
+# physix-spa-rebuild: 10
+RUN pnpm install --frozen-lockfile \
+    && pnpm exec tsc -b \
     && pnpm exec vite build --base=/web/
 
 ############################
@@ -84,7 +94,7 @@ COPY README.md ./
 RUN pip install --no-deps -e .
 
 # Built SPA from stage 1.
-COPY --from=frontend /build/dist /app/static
+COPY --from=frontend /spa/dist /app/static
 
 # Space wrapper — mounts the React SPA at /web/, registers / -> /web/
 # redirect (OpenEnv's create_fastapi_app doesn't add one for us).