Keep container verification focused on runtime behavior

.github/workflows/container.yml

@@ -25,7 +25,7 @@ jobs:
           cache: npm
       - run: npm ci
       - uses: docker/setup-buildx-action@v3
-      - name: Build and run offline checks
+      - name: Build container
         uses: docker/build-push-action@v6
         with:
           context: .

Dockerfile

@@ -1,12 +1,10 @@
 FROM node:22-bookworm-slim AS build
 WORKDIR /app
 ENV CI=true WRANGLER_SEND_METRICS=false GOMEMLIMIT=2GiB GOMAXPROCS=2
-RUN apt-get update && apt-get install -y --no-install-recommends git \
-    && rm -rf /var/lib/apt/lists/*
 COPY package.json package-lock.json ./
 RUN npm ci
 COPY . .
-RUN npm run check && npm run build
+RUN npm run build
 
 FROM node:22-bookworm-slim AS runtime
 WORKDIR /app

docs/TRUENAS.md

@@ -9,7 +9,9 @@ runtime prototype does not change public release or rules-mode gates.
 ## Checkpoint images
 
 Every push to `main` starts `.github/workflows/container.yml`. The Docker build
-runs types, lint, offline tests and the production build using the lockfile.
+runs the production build using the lockfile. Types, lint and offline tests
+remain part of source checkpoint verification rather than being repeated in
+the container build.
 Before publishing, CI creates an isolated container and volume, checks accepted
 and rejected HTTP origins, verifies saved-seat restoration through restart and
 container replacement, then runs the HTTP integration suite.