CodeVetter · Repo Unpack · Contributor handoff
chromaui/chromatic-cli
Begin with the shared pipeline and its adapters before editing individual tasks. Preserve task-result semantics, input precedence, Action synchronization, and the distinction between v1 selection and v2 hash collection. Tests and CI were inspected, not executed, and this bounded brief cannot establish passing checks or comprehensive coverage. Any later executable validation needs separate authorization because setup, publishing, initialization, and patch builds have material side effects.
- Read package.json, bin-src/register.js, node-src/index.ts, context.ts, and types.ts first: they define exported surfaces, dispatch, pipeline order, client setup, and state contracts.
- Use the repository's Yarn 4 toolchain in an authorized development session; packageManager pins yarn@4.18.0, and existing scripts provide yarn test, yarn typescript:check, yarn lint, and yarn build. This investigation executed none of them.
- Prefer edits at extractInput/run/applyOutput task seams; keep Options readonly to task dependencies and mutate Runtime for effective forceRebuild changes. Account for the explicitly documented live-Context exceptions in upload and preparation.
- Preserve partial/skip versus skip-self behavior: partial and skip halt downstream tasks, while skip-self permits continuation. Patch restoration must remain outside the skippable render pipeline.
- For option changes, inspect precedence and validation before extending CLI, config, Node, or Action interfaces; retain dependent-option checks, strict schema behavior, and the Action's merge-queue-specific exitZeroOnChanges default.
- For TurboSnap changes, read the dispatcher and golden hashes first: v2 returns fallback after writing/uploading hashes, v1 still supplies story selection, and exact hash constants protect comparisons with older baselines.
- Treat token handling, metadata uploads, and workspace operations as side-effect boundaries: diagnostics redact named tokens, metadata includes configuration/log files, init installs dependencies, and patch restoration invokes hard resets.
- For later authorized verification, start with adjacent Vitest cases and then the configured CI checks; preserve the distinction between mocked orchestration tests and live packed-package smoke tests. Reconcile Node >=22, bundle node20 targets, and Action node24 when changing runtime compatibility.