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>
1.6 KiB
Task 10 — Full-guide blocks
Agent: component-builder · Model: MiniMax-M3 Depends on: 07 ·
Parallel with: 08, 09, 11 · Blocks: 15 Worktree:
.agents/scripts/worktree.sh start 10 guide-blocks
Goal
The full guide's distinctive sections as components — static shells only. Task 15 wires the interactivity.
Scope
src/components/blocks/ — PhasePanel.astro, FleetDiagram.astro,
HandoffTable.astro, WorktreeMap.astro, RouteTable.astro,
SkillPackage.astro.
Source
full-guide/index.html (22 KB) + styles.css + responsive.css.
Critical: the data-* hooks are asserted by name
verify.mjs requires these survive: data-phase="plan|build|review",
data-tree="main|ui", data-worker="ui", data-route="plan",
data-model-provider="openai|claude|gemini", data-effort="low|medium|high",
data-skill-file="skill", data-skill-step="observe|validate",
data-common-skill="ponytail|caveman|unlazy", role="tablist",
id="hands-on".
Each is a real feature hook, not decoration. Losing one is losing a feature.
Watch for
responsive.css is 30 KB of append-only overrides on top of styles.css. Do
not port it wholesale. Take what each component needs, then prove the rest is
dead. Expect to delete most of it — that is a win, not a risk, provided the
screenshots agree.
Done when
- Every
data-*hook above present in rendered output - Components take props and render static markup; no
client:*yet - Screenshots match the current guide at four widths
- Checklist complete;
pnpm run gategreen