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>
46 lines
1.6 KiB
Markdown
46 lines
1.6 KiB
Markdown
# Task 07 — Primitives
|
||
|
||
**Agent**: `component-builder` · **Model**: MiniMax-M3 — **use this task to
|
||
calibrate the model routing before fanning out** **Depends on**: 02 ·
|
||
**Blocks**: 08–11 **Worktree**:
|
||
`.agents/scripts/worktree.sh start 07 primitives`
|
||
|
||
## Goal
|
||
|
||
The four smallest reusable pieces, so the four parallel block tasks compose
|
||
rather than reinvent.
|
||
|
||
## Scope
|
||
|
||
`src/components/primitives/` — `Eyebrow.astro`, `Rule.astro`, `Callout.astro`,
|
||
`CodeBlock.astro`. Nothing else.
|
||
|
||
## Why these four
|
||
|
||
Each appears 10+ times across the current stylesheets:
|
||
|
||
- **Eyebrow** — `10–11px` monospace, `letter-spacing:.08–.1em`, uppercase. The
|
||
single most repeated treatment on the site and a signature of the design.
|
||
- **Rule** — the `border-top: 4px solid var(--gold)` section divider.
|
||
- **Callout** — gold-background emphasis block (`.callout`, `.thesis`).
|
||
- **CodeBlock** — `<pre>` on `--ink` with gold text.
|
||
|
||
## Steps
|
||
|
||
Copy `.agents/templates/components/static-block.astro` for each. Typed props,
|
||
tokens only, zero JS. Then grep the current CSS for every place each treatment
|
||
appears and confirm the component covers them all — if it needs five variants,
|
||
you have found two components, not one.
|
||
|
||
## Done when
|
||
|
||
- [ ] `.agents/checklists/before-component.md` complete for all four
|
||
- [ ] Rendered output visually identical to the CSS classes they replace
|
||
- [ ] `pnpm run gate` green
|
||
- [ ] **Routing note written**: how many iterations, what the model got wrong.
|
||
This decides whether 08–11 run on M3 or move to Codex.
|
||
|
||
## Do not
|
||
|
||
Do not build blocks or touch pages. Do not edit `tokens.css`.
|