Files

T

Marcos Paulo 48c31dc1b3 build: migrate from npm to pnpm

Ten git worktrees each carried their own 225 MB node_modules (1.1 GB across
five) and paid 11s per `npm ci`. pnpm hardlinks from a shared store: the same
five worktrees cost ~250 MB total, and a fresh install is 4s.

What changed beyond the mechanical rename:

- `overrides` moved to `pnpm-workspace.yaml`. pnpm 11 does not read the `pnpm`
  field in package.json *or* npm's top-level `overrides`, and it fails silently
  — the vite/defu/language-server pins would have quietly stopped applying.
- Build scripts are blocked by default in pnpm; esbuild and sharp are allowed
  explicitly via `allowBuilds` (renamed from `onlyBuiltDependencies` in 11).
- `packageManager` + `engines` pin the toolchain.
- gate.sh rejects a package-lock.json/yarn.lock/bun.lock outright, so an agent
  running `npm install` out of habit fails loudly instead of building a second,
  divergent dependency tree.
- CI bootstraps pnpm with `npm install --global pnpm@11.25.0` rather than
  corepack (unbundled as of Node 25) or pnpm/action-setup (this self-hosted
  act-runner has never run a job; fetching a third-party action is not
  something to discover on the first one).

Two pre-existing CI bugs fixed while in the file:

- the gate installed with `npm install --package-lock=false`, which discarded
  the lockfile the previous session had just fixed.
- the visual-regression step imported `playwright`, which is not a dependency,
  and `visual-regression.mjs` has no compare mode anyway — in CI it overwrote
  its own baselines and passed unconditionally. Removed with a comment; it
  comes back when it can diff.

The `publish` job is now manual (`workflow_dispatch`). During the migration
dist/ holds three HTML files against the live pages branch's ten, so publishing
on every push to main would take the site down to a stub. Restore at task 20.

HANDOVER.md's incident log still says npm where it describes what happened at
the time; that is history, not a missed rename.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-09-05 04:29:42 +00:00

1.2 KiB

Raw Permalink Blame History

Task 13 — Chapter pages ×4

Agent: page-migrator · Model: MiniMax-M3 Depends on: 03, 09 · Parallel with: 12, 14, 17 · Blocks: 15, 16 Worktree: .agents/scripts/worktree.sh start 13 page-chapters

Goal

/models/, /agents/, /skills/, /summary/ as Astro routes. One task because they share a layout — four near-identical migrations, and doing them together is what proves ChapterLayout is right.

Blocks 15 and 16 because those pages link here and share the layout.

Hard constraints

Four URLs unchanged, trailing slashes included
/skills/ has an interactive package explorer (skills/app.js, data-skill-file, data-skill-step) — that becomes an island, and it is the only JS across these four pages. The other three ship zero.
All data-* hooks preserved; verify.mjs asserts several

Done when

Four snapshot diffs empty
Three pages ship 0 bytes JS; /skills/ ships only its island
Screenshots match at four widths
Checklist complete for each page; pnpm run gate green

Do not

Do not generalise ChapterLayout beyond these four. /rules/ is task 14 and has its own interaction model.

1.2 KiB Raw Permalink Blame History Unescape Escape