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>
39 lines
1.3 KiB
Markdown
39 lines
1.3 KiB
Markdown
# Task 09 — Chapter blocks
|
|
|
|
**Agent**: `component-builder` · **Model**: MiniMax-M3 **Depends on**: 07 ·
|
|
**Parallel with**: 08, 10, 11 · **Blocks**: 13, 14 **Worktree**:
|
|
`.agents/scripts/worktree.sh start 09 chapter-blocks`
|
|
|
|
## Goal
|
|
|
|
The shared furniture of `/models/`, `/agents/`, `/skills/`, `/summary/`,
|
|
`/rules/` — five pages that today duplicate the same markup five times.
|
|
|
|
## Scope
|
|
|
|
`src/components/blocks/` — `ChapterHero.astro`, `SectionGrid.astro`,
|
|
`ComparisonTable.astro`, `TopBar.astro`, `SiteFooter.astro`.
|
|
`src/layouts/ChapterLayout.astro`.
|
|
|
|
## Source
|
|
|
|
`chapters.css` is already the shared layer; the duplication is in the five HTML
|
|
files. Diff them against each other first — what differs is props, what matches
|
|
is the component.
|
|
|
|
## Watch for
|
|
|
|
- `TopBar` carries `aria-current="page"`. Preserve it; it is the only indication
|
|
of location for assistive tech.
|
|
- The tables in `/models/` and `/rules/` scroll horizontally on narrow screens
|
|
(`overflow-x:auto`, `min-width` on the inner element). Keep that — dropping it
|
|
makes the tables unreadable on a phone, and `audit-ui.mjs` asserts related
|
|
responsive tokens.
|
|
|
|
## Done when
|
|
|
|
- [ ] All five pages' markup expressible with these components
|
|
- [ ] Rendered text identical to current pages
|
|
- [ ] Zero JS
|
|
- [ ] Checklist complete; `pnpm run gate` green
|