Marcos Paulo
48c31dc1b3
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>
2.2 KiB
2.2 KiB
name, description
| name | description |
|---|---|
| astro-page | Migrate one hand-written HTML page of the ai-for-dummies site to an Astro route without changing its URL, content, or JS budget. Use for any page-level migration task. |
Migrating a page to Astro
Snapshot first, migrate second
The snapshot is the only objective evidence that no content was lost.
pnpm run serve & # vanilla site on :4173
node .agents/scripts/snapshot-route.mjs http://localhost:4173/models/ \
> .agents/snapshots/models.txt
Screenshot the same route at 560 / 800 / 1100 / 1600 px as well.
Migrate
cp .agents/templates/pages/chapter.astro src/pages/models.astro
Then, in order:
- Move markup into the layout + components. Reuse existing components before creating new ones.
- Move copy into
src/content/. Bothenandpt, copied literally — never retyped. - Move page CSS into component
<style>blocks. Do not portresponsive.csswholesale; take what this page needs and prove the rest dead. - Keep every
data-*hook.verify.mjsasserts many of them by name (data-phase,data-tree,data-route,data-model-provider, …). - Keep every ARIA attribute and the
<title>/<meta name="description">.
The URL must not change
Served from /ai-for-dummies/, so base is set in astro.config.mjs. Never
hand-write an internal absolute path; use import.meta.env.BASE_URL.
Trailing slashes matter. /models/ must not become /models.
If the page honours query params (the review desk uses ?author=, ?skill=,
?view=, ?file=, ?compare=, ?render=), they must still work — they are
documented in the page footer and shared externally.
Prove it
pnpm run build
node .agents/scripts/snapshot-route.mjs dist/models/index.html > /tmp/after.txt
diff .agents/snapshots/models.txt /tmp/after.txt # empty, or justify every line
node scripts/audit-ui.mjs
pnpm run verify
Then screenshots at the same four widths, and
../../checklists/before-page.md.
JS budget
A page that shipped zero JS must still ship zero. Check the build output. If
your migration added a client:load to a static page, you did it wrong.