Migrate to a design system

Words are in build-design-system/references/glossary.md, bans, widths and voice in the accepted .design-system/taste.md. The system is settled and behaviour stays unchanged, except for announced data-bug fixes. A missing token or component is a gap for the system's owner, never a workaround here. The Never list in build-design-system holds for the coordinator and every worker.

Scripts are in this skill's scripts/. Run each from the repo root as node <this skill>/scripts/<name>.mjs, except scripts/legacy.mjs, which is copied into the repo's scripts/ so CI runs its ratchet. Captures and pixel diffs use build-design-system/scripts/capture.mjs and build-design-system/scripts/pixdiff.mjs, and capture installs build-design-system/scripts/capture-guard.mjs before the first navigation.

Modes

Audit mode is the default. It writes only under .design-system/, which .git/info/exclude keeps out of every commit, cuts no branch, commits nothing and ends with the inventory, the plan and the offer of the full run with its size. Full mode starts only when the ask names the migration or the person accepted the offer (Go, <budget>). "Clean it up" and "fix it" are not clearance.

Steps