build: emit the production build to site/ for publishing

The factory publishes the servable app from site/, so point Vite's
outDir there and ignore it. Update the README and architecture notes
that referenced the old dist/ path.

Author: ctkrug

.gitignore

@@ -1,6 +1,6 @@
 node_modules/
 dist/
-site/dist/
+site/
 coverage/
 *.log
 npm-debug.log*

README.md

@@ -64,7 +64,7 @@ npm run dev       # local dev server
 npm test          # vitest unit tests
 npm run test:e2e  # playwright real-browser tests (npx playwright install first)
 npm run lint      # eslint
-npm run build     # static production build (output: dist/)
+npm run build     # static production build (output: site/)
 ```
 
 ## Status

docs/ARCHITECTURE.md

@@ -61,7 +61,7 @@ without simulating DOM events.
 
 - `npm run dev` — Vite dev server.
 - `npm run build` — static production build (relative `base: "./"` so it works
-  from a subpath like `apps.charliekrug.com/diff-poster/`); output in `dist/`.
+  from a subpath like `apps.charliekrug.com/diff-poster/`); output in `site/`.
 - `npm test` — vitest (jsdom environment); `npm run lint` — eslint.
 - `npm run test:e2e` — Playwright, against a real Chromium render at the
   three declared breakpoints (`e2e/`, config in `playwright.config.js`). jsdom

vite.config.js

@@ -4,4 +4,11 @@ export default defineConfig({
   // Relative asset paths so the built site works when served from any
   // subpath (e.g. apps.charliekrug.com/diff-poster), not just the domain root.
   base: "./",
+  // Emit the static build to site/ — the directory the factory publishes as
+  // the live app; the app is its own landing page (wordmark, GitHub link,
+  // and the below-fold explainer/FAQ all ship in index.html).
+  build: {
+    outDir: "site",
+    emptyOutDir: true,
+  },
 });