Files
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.3 KiB

Task 14 — Rules page

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

Goal

/rules/ → Astro. Separate from task 13: it is a standalone bilingual case study with its own stylesheet (rules/styles.css, 9.8 KB), its own script (rules/app.js, 16 KB), and its own responsive contract.

Asserted by verify.mjs

  • rulesHtml must have no external <script>/<link> — it is explicitly checked as a standalone page
  • rulesCss must contain @media(min-width:2200px), @media(max-width:900px), @media(max-width:600px), prefers-reduced-motion

Task 02 collapses those breakpoints to named tokens. Coordinate with the verification engineer — the assertion must be re-pointed at the token, not deleted. Screenshot at the old widths (900, 600, 2200) to prove equivalence.

Watch for

rules/styles.css shares --accent and --deep with styles.css — it is on the first palette. Confirm task 02 canonicalized it the same way.

Done when

  • Snapshot diff empty; bilingual toggle works, <html lang> follows
  • Responsive behaviour identical at 600/900/2200
  • No external dependency; checklist complete; pnpm run gate green