commit e5dbb17d0447e72db615ccf3ce5b04fd0f1ba05b
parent acd83ceb04369765701f07551d23d2de87643e1b
Author: I Mean I'm Just Saying <imeanimjustsaying@kiwifarms.st>
Date: Wed, 30 Sep 2026 22:56:41 -0400
plans: implementer-rules — the homepage build gate is build:nodata, never run build (its prebuild indexes whatever transcripts/ is visible); the corpus link is for next build only
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Diffstat:
1 file changed, 6 insertions(+), 0 deletions(-)
diff --git a/plans/tools/implementer-rules.md b/plans/tools/implementer-rules.md
@@ -39,6 +39,12 @@ the Next.js reference for this version.
or export-related e2e, because the live editor's build-deploy job regenerates the primary's.
- **Export build gate is `pnpm --filter export exec next build`** — NOT `run build`, which runs
`build:data` into a worktree-local `transcripts/`.
+- **Homepage build gate is `pnpm --filter homepage run build:nodata`** (or `exec next build`) — NEVER
+ `run build`: its `prebuild` runs `archilyzer index` and `compose homepage` against whatever
+ `transcripts/` is visible. With the primary's corpus linked in for a capped build (the umtool rule
+ below), `run build` is an index build against the real corpus (release 13 W2's catch-up, 2026-09-30:
+ three minutes, two records rewritten by identical code, stopped). The corpus link is for `next build`
+ only; never run a package's `build` script, a `prebuild` hook, an index or a fixture builder with it.
- **tsc per commit:** `pnpm -r --no-bail --workspace-concurrency=1 exec tsc --noEmit` from the
worktree root must be clean before every commit (worktrees have no stale `.next/dev/types`).
- **Never boot a second editor against the real corpus.** Your worktree's e2e uses its own
