archilyzer

commit b1750da444c7298dc78788cbc98daaac0e2de934
parent 53f44d1945185c80a0c66e0a3b2f3027bc6e6817
Author: I Mean I'm Just Saying <imeanimjustsaying@kiwifarms.st>
Date:   Sat, 12 Sep 2026 13:41:12 -0400

plans: build:hub overwrites the export e2e fixture, and FACTS says so

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

Diffstat:
M
plans/FACTS.md
 | 
7
+++++++

1 file changed, 7 insertions(+), 0 deletions(-)
diff --git a/plans/FACTS.md b/plans/FACTS.md
@@ -858,6 +858,13 @@ client) and `mcp/src/search.ts` (server). MCP has 11 tools (`mcp/src/server.ts:1
 
 ## E2E environment
 
+**`build:hub` clobbers the export e2e fixture in the same worktree (hit 2026-09-12).**
+`export`'s `build:hub` runs `compose:hub`, which overwrites `export/public/corpus.json` and
+`sw.js` and drops the hub files beside them. An export e2e run after it in the same
+worktree then runs against a hub, not a site. Run the export suites first, or restore the
+site fixture (`corpus.json` from the duplicates-page worktree, remove the hub files, recopy
+`site-sw.js`) before them. All of those paths are gitignored, so nothing shows in `git status`.
+
 - `editor/playwright.config.ts` — editor on `PORT ?? 3011`, export on `EXPORT_PORT ?? 3010`.
   `E2E_MODE=start` → `pnpm start:test`, otherwise `pnpm dev:test` (`:10-11`).
   `fullyParallel: false`, `workers: 1`, `timeout: 30_000`.