npm - remarque-tokens - Versions diffs - 0.18.0 → 0.19.0 - Mend

remarque-tokens 0.18.0 → 0.19.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (9) hide show

package/AGENT_RULES.md +2 -0
package/CHANGELOG.md +59 -0
package/REMARQUE.md +127 -0
package/deck.js +70 -0
package/package.json +5 -2
package/scripts/lib/css-tokens.mjs +11 -2
package/scripts/theme.mjs +38 -7
package/tokens.d.ts +1 -1
package/tokens.json +1 -1

package/AGENT_RULES.md CHANGED Viewed

@@ -146,6 +146,7 @@ project/
 ├── essay.css                 # Optional Essay module: sidenotes + sticky TOC rail (own subpath, NOT aggregated — import explicitly)
 ├── broadsheet.css            # Optional Broadsheet pattern: masthead, lead, entry list, post kicker (own subpath, NOT aggregated — import explicitly)
 ├── forms.css                 # Optional form control primitives: field/input/checkbox/radio/button, state-color wiring (own subpath, NOT aggregated — import explicitly)
+├── deck.js                   # Optional Palette Deck module: switch/persist/restore between remarque-theme-generated palettes (own subpath, NOT aggregated — dependency-free ESM, no CSS of its own)
 ├── print.css                 # Print stylesheet (own subpath, NOT aggregated — import explicitly)
 ├── theme.css                 # Tailwind v4 adapter (@theme inline) — import after tailwindcss + tokens
 ├── tailwind.config.js        # Tailwind v3 ONLY — v4 projects use theme.css instead
@@ -209,6 +210,7 @@ Before considering any implementation complete, verify:
 - [ ] If the Essay uses sidenotes/a TOC rail (`remarque-tokens/essay`): `.remarque-sidenote-ref`/`.remarque-sidenote` alternate in strict DOM order, the rail never intrudes into `.remarque-prose`'s own measure, and the page renders correctly with `essay.css`'s `@media` block deleted (the narrow-viewport/no-JS fallback)
 - [ ] If a Landing/archive page uses the Broadsheet pattern (`remarque-tokens/broadsheet`): entry numerals are generated from `data-entry-number` via `attr()` (not `counter()`), the entry list stays a `<ul>` (not `<ol>` — the numeral is `aria-hidden` and decorative), and every kicker/dateline row uses `font-variant-caps: all-small-caps`, never `text-transform: uppercase`
 - [ ] If a page uses form controls (`remarque-tokens/forms`): checkboxes/radios are styled with `accent-color` only — never `appearance: none` plus a hand-drawn replacement; every control (input, button, checkbox/radio label) is ≥44×44px; validation state lives on `.remarque-field[data-state]` AND a real `aria-invalid`/`aria-describedby` pair on the input, not `data-state` alone; disabled controls use `--color-disabled`, never a state color
+- [ ] If a page uses the Palette Deck (`remarque-tokens/deck`): `data-palette` is set/cleared on the same root element as `data-theme` (they compose, never conflict); the FOUC-safe restore is a synchronous classic `<script>` physically in `<head>` (never `type="module"`, which defers); the switcher control itself is a native, keyboard-operable element (e.g. `.remarque-input` `<select>`) at ≥44×44px, not a hand-rolled widget; every registered palette was generated via `remarque-theme --scope`, never hand-authored
 - [ ] Mobile version is roomy — not a compressed desktop layout
 - [ ] Mobile nav links have ≥44px touch targets
 - [ ] No pure white or pure black backgrounds

package/CHANGELOG.md CHANGED Viewed

@@ -4,6 +4,65 @@ All notable changes to `remarque-tokens` are documented here. Token value
 changes always state the design rationale — downstream sites pin against
 these entries when syncing.
+## 0.19.0 — 2026-07-23
+Palette Deck module (closes #56).
+### Added
+- **`deck.js` — palette-deck module (issue #56, re-scoped by 2026-07-23
+  consensus panel).** New own-subpath export (`remarque-tokens/deck`,
+  `remarque-tokens/deck.js`) — a dependency-free ~60-line ESM file, NOT
+  aggregated into `tokens.css` (it ships no CSS at all). Deliberately
+  THIN: the original theme-deck graduation proposal (12 terminal
+  palettes as `:root[data-theme-deck]` overrides) predates
+  `remarque-theme`; the panel re-scoped it to cover only what that
+  pipeline doesn't already provide — switching, persisting, and
+  FOUC-safely restoring a choice among already-generated palettes.
+  Generation, contrast solving, and hue/pairing remain entirely
+  `remarque-theme`'s job.
+  - `createDeck(names, opts?)` — registers a set of palette names,
+    returns `{ names, current, apply, restore }`. `apply(name)` sets/
+    clears `data-palette` on the root element and persists the choice to
+    `localStorage` (default key `remarque-palette`); `apply(null)`
+    reverts to the unscoped default. `restore()` re-applies a persisted
+    choice without re-persisting it (for the post-paint sync step — the
+    actual FOUC guard is a duplicated inline snippet, documented in
+    REMARQUE.md, matching how the light/dark theme toggle's own `<head>`
+    script already works). Unknown names throw rather than setting an
+    unvalidated attribute value.
+- **`--scope <name>` on `remarque-theme`.** Emits the derived palette
+  under `[data-palette="<name>"]` / `[data-palette="<name>"][data-theme="dark"]`
+  instead of `:root` / `[data-theme="dark"]`, so several generated
+  palettes can coexist in one stylesheet. `<name>` is validated with the
+  same slug grammar as `<light-slug>`/`--dark` before it is interpolated
+  into the attribute selector (security review precedent from #75/#76 —
+  it is the only control here, since a scope name has no upstream index
+  to check against). Derivation and self-verification are unaffected by
+  scoping — a scoped and unscoped run of the same pair emit
+  byte-identical declarations, differing only in the wrapping selector
+  (fixture-tested).
+- **`remarque-audit` recognizes scoped palettes directly.**
+  `scripts/lib/css-tokens.mjs`'s `isLightRoot` now treats a bare
+  `[data-palette="name"]` block as that scope's light root (one more
+  exact-match case, symmetric with the existing `[data-theme="light"]`
+  special case) — `isDarkBlock` needed no change, since
+  `[data-palette="name"][data-theme="dark"]` already matched its
+  existing rule. A `--scope`'d file is auditable exactly like any other
+  palette file; no "audit the unscoped version first" workaround is
+  needed. See REMARQUE.md "Palette Deck" for the full audit story and
+  why this was the smaller correct fix over a bespoke attribute-selector
+  grammar.
+- **Demo (`site/`):** a Palette Deck section on `/tokens` with a native
+  `<select class="remarque-input">` switcher (gruvbox / rosé-pine,
+  pinned slugs `gruvbox-light`/`gruvbox-dark` and
+  `rose-pine-dawn`/`rose-pine`), generated at build time by
+  `site/scripts/build-palette-deck.mjs` into `public/palettes/*.css`
+  (gitignored, regenerated every build — same pattern as
+  `public/tokens.json`). FOUC-safe restore snippet added to
+  `BaseLayout.astro`'s `<head>`, alongside the existing theme-toggle
+  script. VR baselines: `tokens.astro` only (new section on that page);
+  every other page is untouched by this release.
 ## 0.18.0 — 2026-07-23
 Form control primitives + reference components (closes #27, closes #30).

package/REMARQUE.md CHANGED Viewed

@@ -1121,6 +1121,133 @@ instead and keep Remarque to the page's editorial chrome around it.
 ---
+## Palette Deck
+A tiny runtime (`remarque-tokens/deck`, `deck.js`) for switching between
+several `remarque-theme`-generated palettes on one site — register a set
+of palette names, switch the active one, persist the choice, restore it
+before first paint. Issue #56.
+**What this module deliberately does NOT do.** The flagship site's
+`theme-deck.css` (12 terminal palettes as `:root[data-theme-deck=…]`
+overrides) was originally proposed for upstreaming as-is. A 2026-07-23
+consensus panel (3-0) re-scoped it: generation, contrast solving, and
+hue/pairing all now come from `remarque-theme` (`scripts/theme.mjs`,
+"Color Providers" above) — that pipeline makes deriving a new palette
+nearly free, so graduating a second, parallel generator would just
+duplicate it. What's left — and what this module is *only* — is the part
+`remarque-theme` doesn't provide: switching between already-generated
+palettes at runtime. No color math, no contrast solving, no palette
+authoring lives in `deck.js`; it is a dependency-free ~60-line ESM file
+that sets an attribute, reads/writes `localStorage`, and hands back
+enough to build a FOUC-safe restore. If you need to *generate* a palette,
+see "Color Providers"; this section is exclusively about *switching*
+between ones you already have.
+### The mechanism: `--scope`
+`remarque-theme` gained a `--scope <name>` flag for this module. Without
+it, output owns `:root` / `[data-theme="dark"]` outright — the normal,
+single-palette case. With `--scope <name>`, the same derivation emits
+under `[data-palette="<name>"]` / `[data-palette="<name>"][data-theme="dark"]`
+instead, so several generated palettes can coexist in one stylesheet
+(or several stylesheets) without fighting over `:root`:
+```
+npx remarque-theme gruvbox-light --dark gruvbox-dark --scope gruvbox -o palettes/gruvbox.css
+npx remarque-theme rose-pine-dawn --dark rose-pine --scope rose-pine -o palettes/rose-pine.css
+```
+`--scope`'s value is interpolated into a CSS attribute selector, so it is
+validated with the exact same slug grammar as `<light-slug>`/`--dark`
+(lowercase alphanumeric segments joined by single hyphens) before it
+touches any output — a scope name is a caller-supplied label with no
+upstream index to check it against, which is exactly why the regex
+carries the full weight here rather than acting as defense-in-depth for
+a separate lookup. Derivation, self-verification, and every contrast/
+gamut guarantee in "Color Providers" are **completely unaffected by
+scoping** — `theme.mjs` self-verifies the derived `[L, C, H]` values
+before it ever chooses a selector to emit them under, so a scoped and
+unscoped run of the same light/dark pair produce byte-identical
+declarations, differing only in which selector wraps them (fixture-
+tested in `scripts/test-theme.mjs`).
+### The audit story for scoped palettes
+`remarque-audit`'s selector classification (`scripts/lib/css-tokens.mjs`,
+`isLightRoot`/`isDarkBlock`) recognizes `[data-palette="name"]` directly:
+a bare `[data-palette="name"]` block counts as that scope's light root
+(the same kind of exact-match special case the file already carries for
+`[data-theme="light"]`), and `[data-palette="name"][data-theme="dark"]`
+was already recognized as dark by the existing rule (it contains the
+`[data-theme="dark"]` substring and starts with `[`) — no change needed
+there. This was the smaller correct fix, not a bespoke new
+attribute-selector grammar: one exact-match regex, symmetric with a
+pattern the file already used, rather than teaching the parser to
+understand arbitrary compound attribute selectors. The result: a
+`--scope`'d file is auditable exactly like any other palette file —
+`npx remarque-audit --palette palettes/gruvbox.css --src <dir>` — no
+"generate the unscoped version first" workaround required.
+### Markup/wiring contract
+Set (or clear) `data-palette` on `<html>`, alongside the existing
+`data-theme` attribute — the two compose independently. A deck palette
+carries *both* light and dark halves, so the light/dark toggle keeps
+working no matter which palette (or none) is active:
+```html
+<html data-theme="dark" data-palette="gruvbox">
+```
+```js
+import { createDeck } from 'remarque-tokens/deck';
+const deck = createDeck(['gruvbox', 'rose-pine']); // registered names
+deck.restore();                 // re-apply a persisted choice, if any
+deck.apply('rose-pine');        // switch + persist
+deck.apply(null);                // back to the unscoped default palette
+deck.current();                  // 'rose-pine' | null
+```
+`createDeck` validates every `apply()` call against the registered name
+list and throws on an unknown one — the deck never sets an attribute
+value it wasn't told about. Persistence (`localStorage`, default key
+`remarque-palette`) degrades to in-memory-only if storage is unavailable
+(private browsing, SSR) rather than throwing.
+**FOUC-safe restore.** Exactly like the light/dark theme toggle's own
+`<head>` script (see the demo's `BaseLayout.astro`), the deck's restore
+must run as a synchronous, render-blocking **classic** inline script
+physically in `<head>` — an ESM `<script type="module">` is deferred by
+the HTML spec and would let the default palette flash before the stored
+one applies. So the head snippet duplicates the ~3-line read-and-apply
+logic directly rather than importing `deck.js` (the same reason the
+theme toggle's head script doesn't import anything either):
+```html
+<script is:inline>
+  (function() {
+    var p = localStorage.getItem('remarque-palette');
+    if (p) document.documentElement.setAttribute('data-palette', p);
+  })();
+</script>
+```
+`deck.js` itself is loaded later (deferred/module, after first paint) to
+wire the switcher UI's change handler and to keep `restore()` available
+for pages that need to re-derive `current()` after the fact.
+### Provenance
+Re-scoped from the flagship site's theme-deck on the way up (issue #56,
+consensus panel, 2026-07-23) — see the root README's "Graduation"
+section. The original proposal predated `remarque-theme`; once that
+pipeline existed, generating N palettes stopped being the hard part and
+switching between them became the only piece worth a shared module.
+---
 ## Signature Moves
 These are the repeatable visual tells that make a Remarque site recognizable:

package/deck.js ADDED Viewed

@@ -0,0 +1,70 @@
+/*
+ * Remarque — Palette Deck (runtime switching between remarque-theme
+ * generated palettes)
+ * ───────────────────────────────────────────────────────────────────
+ * PROVENANCE — re-scoped, not graduated as-is. The flagship site's
+ * theme-deck (12 terminal palettes, `[data-theme-deck]`) was proposed for
+ * upstreaming whole in issue #56; a 2026-07-23 consensus panel (3-0)
+ * re-scoped it: generation, contrast solving, and pairing all now come
+ * from `remarque-theme` (`scripts/theme.mjs`, "Color Providers"), so this
+ * module is deliberately THIN — it does none of that. All it does:
+ *
+ *   1. register the set of valid palette names,
+ *   2. switch the active one (`data-palette` on the root element),
+ *   3. persist the choice (localStorage), and
+ *   4. hand back enough to build a FOUC-safe restore (see REMARQUE.md
+ *      "Palette Deck" for the inline <head> snippet — that snippet does
+ *      NOT import this module; it duplicates the ~3 lines of restore
+ *      logic directly, the same way the light/dark theme toggle's own
+ *      head script duplicates rather than imports, because a FOUC guard
+ *      must be a synchronous classic script and this file is an ESM
+ *      module).
+ *
+ * No framework, no build step, no CSS authored here — `--scope`'d palette
+ * files (npx remarque-theme <slug> --scope <name>) are the caller's job.
+ */
+const ATTR = 'data-palette';
+const DEFAULT_STORAGE_KEY = 'remarque-palette';
+/**
+ * @param {(string | { name: string })[]} palettes registered palette names
+ *   (or `{ name }` objects, for callers that also carry a label/slug pair)
+ * @param {{ root?: HTMLElement, storageKey?: string }} [opts]
+ */
+export function createDeck(palettes, opts = {}) {
+  const root = opts.root || document.documentElement;
+  const storageKey = opts.storageKey || DEFAULT_STORAGE_KEY;
+  const names = palettes.map((p) => (typeof p === 'string' ? p : p.name));
+  function isValid(name) {
+    return name == null || names.includes(name);
+  }
+  function current() {
+    return root.getAttribute(ATTR);
+  }
+  /** Switch palettes. `name === null` reverts to the unscoped default. */
+  function apply(name, { persist = true } = {}) {
+    if (!isValid(name)) throw new Error(`remarque palette-deck: unknown palette "${name}" (registered: ${names.join(', ') || '(none)'})`);
+    if (name) root.setAttribute(ATTR, name);
+    else root.removeAttribute(ATTR);
+    if (persist) {
+      try {
+        if (name) localStorage.setItem(storageKey, name);
+        else localStorage.removeItem(storageKey);
+      } catch { /* storage unavailable (private mode) — in-memory only for this load */ }
+    }
+  }
+  /** Re-apply a previously persisted choice (no-op if none / unknown). */
+  function restore() {
+    let stored = null;
+    try { stored = localStorage.getItem(storageKey); } catch { /* ignore */ }
+    if (stored && isValid(stored)) apply(stored, { persist: false });
+    return current();
+  }
+  return { names, current, apply, restore };
+}

package/package.json CHANGED Viewed

@@ -1,6 +1,6 @@
 {
   "name": "remarque-tokens",
-  "version": "0.18.0",
+  "version": "0.19.0",
   "engines": {
     "node": ">=18"
   },
@@ -32,7 +32,7 @@
     "drift": "node scripts/drift-check.mjs"
   },
   "devDependencies": {
-    "@williamzujkowski/oklch-terminal-themes": "0.3.0",
+    "@williamzujkowski/oklch-terminal-themes": "0.4.0",
     "culori": "^4.0.2"
   },
   "peerDependencies": {
@@ -74,6 +74,8 @@
     "./broadsheet.css": "./broadsheet.css",
     "./forms": "./forms.css",
     "./forms.css": "./forms.css",
+    "./deck": "./deck.js",
+    "./deck.js": "./deck.js",
     "./agent-rules": "./AGENT_RULES.md",
     "./spec": "./REMARQUE.md",
     "./package.json": "./package.json"
@@ -101,6 +103,7 @@
     "essay.css",
     "broadsheet.css",
     "forms.css",
+    "deck.js",
     "scripts/lib/css-tokens.mjs"
   ]
 }

package/scripts/lib/css-tokens.mjs CHANGED Viewed

@@ -54,12 +54,21 @@ const parts = (prelude) => prelude.split(',').map((s) => s.trim());
 const DARKISH = /(\.dark\b|\[data-theme="dark"\])/;
 const ROOTISH = /^(:root|html|body)\b/;
+// A bare palette-deck scope selector (remarque-tokens/deck, issue #56) — no
+// [data-theme] of its own, so it plays the same "light root" role for that
+// scope that :root plays sitewide. Exact-match, same shape as the existing
+// `[data-theme="light"]` special case immediately below — not a general
+// attribute-selector grammar, just one more enumerated light-ish selector.
+const PALETTE_SCOPE_LIGHT = /^\[data-palette="[a-z0-9-]+"\]$/;
 export const isLightRoot = (b) =>
   b.context === '' && parts(b.prelude).some((s) =>
-    (ROOTISH.test(s) && !DARKISH.test(s)) || s === '[data-theme="light"]');
+    (ROOTISH.test(s) && !DARKISH.test(s)) || s === '[data-theme="light"]' || PALETTE_SCOPE_LIGHT.test(s));
 /* Dark: media-query :root, the canonical [data-theme="dark"], or the
-   class-convention :root.dark / html.dark (compatibility bridge). */
+   class-convention :root.dark / html.dark (compatibility bridge). A scoped
+   deck palette's dark block ([data-palette="name"][data-theme="dark"])
+   already matches unchanged: DARKISH finds the [data-theme="dark"]
+   substring, and the selector starts with "[". */
 export const isDarkBlock = (b) =>
   (b.context.includes('prefers-color-scheme') && b.context.includes('dark') &&
     parts(b.prelude).some((s) => ROOTISH.test(s) && !DARKISH.test(s))) ||

package/scripts/theme.mjs CHANGED Viewed

@@ -50,13 +50,22 @@ try {
   OWN_VERSION = JSON.parse(readFileSync(join(HERE, '..', 'package.json'), 'utf8')).version;
 } catch { /* provenance is best-effort */ }
-const USAGE = `usage: remarque-theme <light-slug> [--dark <dark-slug>] [-o out.css]
+const USAGE = `usage: remarque-theme <light-slug> [--dark <dark-slug>] [-o out.css] [--scope <name>]
   <light-slug>     slug of a theme with isDark=false in ${PKG_SPEC}
   --dark <slug>    slug of a theme with isDark=true; defaults to the light
                     theme's "counterpart" from the dataset (0.2.0+) when it
                     has one, and is required when it doesn't
-  -o, --output     write the derived palette here instead of stdout`;
+  -o, --output     write the derived palette here instead of stdout
+  --scope <name>   emit under [data-palette="<name>"] instead of :root — for
+                    the palette-deck module (remarque-tokens/deck), where
+                    several generated palettes coexist in one stylesheet and
+                    are switched at runtime. <name> is validated with the
+                    same slug grammar as a theme slug (lowercase
+                    alphanumeric + hyphen) — it is interpolated into a CSS
+                    attribute selector, so it goes through the same
+                    byte-for-byte validation as light-slug/dark-slug above,
+                    not just a shape check (see "Security" above)`;
 function die(msg) {
   console.error(msg);
@@ -66,18 +75,33 @@ function die(msg) {
 /* ── CLI args ─────────────────────────────────────────────────────── */
 const argv = process.argv.slice(2);
-let darkSlug, outFile;
+let darkSlug, outFile, scopeName;
 const positional = [];
 for (let i = 0; i < argv.length; i++) {
   const a = argv[i];
   if (a === '--dark') darkSlug = argv[++i];
   else if (a === '-o' || a === '--output') outFile = argv[++i];
+  else if (a === '--scope') scopeName = argv[++i];
   else if (a === '-h' || a === '--help') { console.log(USAGE); process.exit(0); }
   else positional.push(a);
 }
 const lightSlug = positional[0];
 if (!lightSlug) die(USAGE);
+/* --scope is interpolated into a CSS attribute selector
+ * ([data-palette="<name>"]) — validated against the SAME slug grammar as
+ * light-slug/dark-slug below (SLUG_RE), not a looser check. Unlike those
+ * two, there's no upstream index to match it against (a scope name is the
+ * caller's own label, not a theme lookup key), so the regex IS the whole
+ * control here — which is exactly why it stays as strict as the lookup
+ * keys' defense-in-depth regex: lowercase alphanumeric + hyphen only,
+ * nothing that could break out of the quoted attribute value or inject
+ * additional CSS. */
+const SCOPE_RE = /^[a-z0-9]+(?:-[a-z0-9]+)*$/;
+if (scopeName !== undefined && !SCOPE_RE.test(scopeName)) {
+  die(`--scope "${scopeName}" is invalid — must be lowercase alphanumeric segments joined by single hyphens (e.g. "gruvbox", "rose-pine")`);
+}
 /* ── Resolve @williamzujkowski/oklch-terminal-themes ─────────────────
  * Tried from the consumer's cwd first (a project that installs the
  * themes package at its own top level), then from this script's own
@@ -734,9 +758,16 @@ selfVerify('dark', dark.raw);
 const decls = (tokens, indent = '  ') => Object.entries(tokens).map(([k, v]) => `${indent}--${k}: ${v};`).join('\n');
+const regenCmd = `npx remarque-theme ${lightSlug} --dark ${darkSlug}${scopeName ? ` --scope ${scopeName}` : ''}`;
+const lightSelector = scopeName ? `[data-palette="${scopeName}"]` : ':root';
+const darkSelector = scopeName ? `[data-palette="${scopeName}"][data-theme="dark"]` : '[data-theme="dark"]';
+const scopeNote = scopeName
+  ? `\n *\n * Scoped for remarque-tokens/deck (--scope "${scopeName}") — this is one\n * palette among several coexisting in a stylesheet, switched at runtime\n * via [data-palette] rather than owning :root outright. Self-verification\n * below runs on the same derived [L,C,H] values regardless of scope; see\n * REMARQUE.md "Palette Deck" for the audit story on scoped output.`
+  : '';
 const css = `/*
  * Generated by remarque-theme (remarque-tokens ${OWN_VERSION}) — DO NOT HAND-EDIT.
- * Regenerate instead: npx remarque-theme ${lightSlug} --dark ${darkSlug}
+ * Regenerate instead: ${regenCmd}
  *
  * Source themes (${PKG_SPEC}@${themesVersion}):
  *   light = "${lightSlug}"   dark = "${darkSlug}"
@@ -744,15 +775,15 @@ const css = `/*
  *
  * Palette tier only (--color-*, --weight-display) — see REMARQUE.md
  * "Token Tiers" / "Color Providers". Self-verified against the same
- * contrast + gamut checks as remarque-audit before being emitted.
+ * contrast + gamut checks as remarque-audit before being emitted.${scopeNote}
  */
-:root {
+${lightSelector} {
 ${decls(light.tokens)}
   --weight-display: 400;
 }
-[data-theme="dark"] {
+${darkSelector} {
 ${decls(dark.tokens)}
 }
 `;

package/tokens.d.ts CHANGED Viewed

@@ -1,6 +1,6 @@
 /*
  * Remarque design tokens — GENERATED from tokens.json by
- * scripts/tokens-json.mjs (v0.18.0). Do not edit — the CSS
+ * scripts/tokens-json.mjs (v0.19.0). Do not edit — the CSS
  * (tokens-core.css + tokens-palette.css) is the source of truth;
  * tokens.json is the intermediate machine-readable form this file is
  * generated from. Regenerate with: node scripts/tokens-json.mjs

package/tokens.json CHANGED Viewed

@@ -2,7 +2,7 @@
   "$description": "Remarque design tokens — GENERATED from tokens-core.css + tokens-palette.css by scripts/tokens-json.mjs. Do not edit; the CSS is the source of truth.",
   "$extensions": {
     "remarque": {
-      "version": "0.18.0",
+      "version": "0.19.0",
       "tiers": {
         "core": "immutable identity — overriding forks the system",
         "palette": "sanctioned personalization surface — override freely, then run remarque-audit"