J3W1 / DESIGN SYSTEM

Release comparison

Compare two pinned theme revisions, inspect historical specimens, and follow explicit dependency evidence.

Source revision 1faefcf014c8bf01a6b27308ea796da968773a81

Choose a release or a published commit checkpoint. Both sides keep their own values, status and provenance. A checkpoint is not a new release or approval. Proposed and heritage profiles remain inspection-only.

Available comparisons

Every comparison below is available without JavaScript. JSON and Markdown downloads include the full input pins, digests, changes, dependency references, verification steps and limitations.

What the visual reference means

Before and after frames use each revision's maintained specimen markup and styles through the same parsed renderer. The initial seven components reuse the workbench inventory, with every recorded variant and state. Frames use 640 × 480 CSS pixels, comfortable density, left-to-right direction, static motion endpoints and no historical JavaScript. Open a frame directly for a full-width view.

Fonts come from the same browser and machine; no font binaries are bundled or fetched. Different machines can use different fallbacks. Changed fixtures and requested fonts are reported so their effects are not mistaken for palette regressions. Actual captures and accessibility checks remain separate execution evidence.

Compare another pinned pair locally

npm run release:compare -- --from v0.1.0 --to b601998b3711dcd62949d497ed828af2089f9544 --out ../release-comparison

The output directory must be new and have an existing, non-redirected parent. The command reads local Git objects without building historical code or fetching a branch. Missing historical exports remain unsupported; missing reverse indexes are reported, with direct mappings used where available.