Chromatic Init

Wires Chromatic — the team-facing visual regression / approval gate at the end of the design loop (contract §1, step 4). Runs after Storybook exists (storybook-init). Usually invoked by design-init.

Shared contract

Read design-contract.md — Chromatic is the PUBLISH stage; design-loop calls it once a component's render has converged and tests pass.

Targets

Chromatic is set up once per Storybook target (contract §2): one Chromatic project, one token, one publish script per target. A single-Storybook repo has one target at the root using CHROMATIC_PROJECT_TOKEN — steps 1–7 as written. With several targets (a monorepo), run steps 1–7 once per target, inside the target's dir, and name each token env var after the target (CHROMATIC_PROJECT_TOKEN_<KEY>). Separate projects keep each target's baselines and review queue independent.