remarque-tokens 0.25.0 → 0.26.0

package/AGENT_RULES.md

@@ -325,9 +325,10 @@ the documented DTCG divergences.
 
 ## Installing the Skills
 
-This package ships two Claude Code skills under the npm subpath exports
-`remarque-tokens/skills/remarque` and `remarque-tokens/skills/adopt`
-(resolving to `skills/remarque/SKILL.md` and `skills/remarque-adopt/
+This package ships three Claude Code skills under the npm subpath
+exports `remarque-tokens/skills/remarque`, `remarque-tokens/skills/adopt`,
+and `remarque-tokens/skills/new-page` (resolving to `skills/remarque/
+SKILL.md`, `skills/remarque-adopt/SKILL.md`, and `skills/remarque-new-page/
 SKILL.md` in the installed package). Claude Code only discovers skills
 from a project's own `.claude/skills/` (or `~/.claude/skills/`), never
 from `node_modules` — copy them in explicitly, one `cp` per skill:
@@ -336,14 +337,16 @@ from `node_modules` — copy them in explicitly, one `cp` per skill:
 mkdir -p .claude/skills
 cp -r node_modules/remarque-tokens/skills/remarque .claude/skills/remarque
 cp -r node_modules/remarque-tokens/skills/remarque-adopt .claude/skills/remarque-adopt
+cp -r node_modules/remarque-tokens/skills/remarque-new-page .claude/skills/remarque-new-page
 ```
 
 The copies are versioned with the installed package, not auto-updating —
-re-copy both after a MAJOR bump, or any time this file's
+re-copy all three after a MAJOR bump, or any time this file's
 "Machine-Readable Output" shape changes.
 
 - `remarque` — the build/review contract for pages on the current version (tier rules, archetypes, pitfalls #6/#7).
 - `remarque-adopt` — the version-bump/migration playbook (this file's "Machine-Readable Output" section is its main dependency): verify the resolved version past the 0.x caret freeze, discover newly-required tokens from `remarque-audit --json`, solve missing values against the consumer's own backgrounds, classify `remarque-drift --json` output, report against a fixed PR-body contract.
+- `remarque-new-page` — the page-building procedure, companion to (not a restatement of) the `remarque` loader skill: pick the archetype, fetch-and-verify the relevant registry item instead of transcribing its markup, wire the page per the pitfalls above, gate acceptance on `remarque-audit --json` plus the registry item's own markup-contract assertions.
 
 ---
 

package/CHANGELOG.md

@@ -4,6 +4,19 @@ 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.26.0 — 2026-07-23
+
+`remarque-new-page` skill (closes #108) + `token-drift.yml` optional audit input (closes #110) — the last two items of the skill-suite/CI program.
+
+### Added
+
+- **`.claude/skills/remarque-new-page/SKILL.md`** — a third Claude Code skill, a companion to (not a restatement of) the existing `remarque` loader skill: five steps, each ending in a machine gate. (1) load the loader skill's three files rather than build from training-data token values; (2) pick one of REMARQUE.md's seven archetypes, never an invented eighth; (3) for module-backed pages (Essay/Broadsheet/Forms/Palette Deck) fetch the registry item — `node_modules/remarque-tokens/registry/<name>.json` or the served URL — and **verify its sha256 against the `integrity` pin before applying anything** (the same transcription bug issue #89 documents, a hand-copied sidenote `aria-label` that drifted out of DOM order); (4) wire the page per AGENT_RULES pitfalls #6 (string-form `@import` only)/#7 (unlayered tokens import) and the `.remarque-prose`/`.content-reading` pairing (`.remarque-prose` supplies typography only, never centers the column); (5) gate acceptance on `remarque-audit --json` reporting `passed: true` **and** the registry item's own markup-contract assertions (sidenote DOM-order, `data-entry-number`/`attr()`, label/`aria-describedby` pairing, `data-palette`/`data-theme` co-location — per module).
+- **All three skills now ship in the npm tarball.** `scripts/lib/skills.mjs`'s shared `SKILLS` table gains the new skill (canonical `.claude/skills/remarque-new-page/SKILL.md`, packaged `skills/remarque-new-page/SKILL.md`) — `scripts/build-skills.mjs`/`scripts/test-skills.mjs` cover it automatically through that shared table, no separate wiring needed for the freshness/frontmatter/flag/path checks. `scripts/test-pack.mjs`'s hardcoded tarball-listing and installed-package assertions are extended to check for the third skill explicitly (that script doesn't read the shared table). New export: `remarque-tokens/skills/new-page` (→ `skills/remarque-new-page/SKILL.md`). `package.json`'s existing `skills/` files entry already covers the new directory; no `files` change needed.
+- **README + AGENT_RULES.md "Installing the Skills"** — both updated for three skills (three `cp` commands instead of two) and both skill-listing bullets extended with a `remarque-new-page` entry.
+- **`.github/workflows/token-drift.yml`: three new OPTIONAL `workflow_call` inputs** — `run-audit` (boolean, default `false`), `palette-path` (string, default `''`), `src-dir` (string, default `'.'`). When `run-audit: true`, a new step runs `npx remarque-audit --palette <palette-path> --src <src-dir>` from the consumer's own checkout, against the remarque-tokens the consumer already installed under `package-dir` — one workflow call now covers both the drift and audit gates instead of a caller wiring a second script step by hand. `palette-path`/`src-dir` are relative to `package-dir` (the audit step's working directory), matching how `npx remarque-audit` is normally invoked locally. The step fails fast with a clear `::error::` if `run-audit: true` but `palette-path` is left blank (workflow_call has no conditional-required-input mechanism). **Backward compatible by construction:** `run-audit` defaults to `false`, and both existing callers — williamzujkowski.github.io's `audits.yml` and tsundoku's `deploy.yml`, both read on their own `main` branches for this release — call this workflow today with only `css-file`/`package-dir`/`remarque-ref`, so neither is affected without opting in.
+- **`run-golden` deliberately NOT added**, despite the issue text raising it alongside `run-audit`. `scripts/palette-golden.mjs` is remarque-internal tooling: it binds THIS package's own `tokens-palette.css` to the `remarque-light`/`remarque-dark` reference palettes from `@williamzujkowski/oklch-terminal-themes` and checks remarque's own release hasn't drifted from its golden values. It ships no CLI bin (`package.json`'s `bin` only exports `remarque-audit`/`remarque-drift`/`remarque-theme`) and takes no `--palette`/`--src` arguments a generic consumer could point at their own stylesheet — there is no consumer-facing analog to generify, unlike `run-audit`/`remarque-audit`. Documented inline in the workflow's own header comment.
+- Version-only regeneration of `tokens.json`/`tokens.d.ts`/`registry.json`/`registry/*.json` (no token, CSS, or registry-content changes this release — `tokens.schema.json` unchanged).
+
 ## 0.25.0 — 2026-07-23
 
 `remarque-adopt` skill + skills npm export (closes #107) — ratified 3-0 (skill-suite vote, 2026-07-23), the anchor item of the skill suite. Codifies the consumer-conformance playbook run five times in one day as hand-written agent briefs (williamzujkowski.github.io#381, tsundoku#243/#237, remarque-starter#7/#8) into a procedural, machine-gated skill.

package/README.md

@@ -69,11 +69,12 @@ The agent rules define build order, non-negotiable rules, disallowed patterns, a
 
 Packaging for agent tooling:
 - **npm exports:** `remarque-tokens/agent-rules` (→ `AGENT_RULES.md`) and `remarque-tokens/spec` (→ `REMARQUE.md`), alongside the existing `remarque-tokens/tokens.json`, so a project can point an agent at `node_modules/remarque-tokens/AGENT_RULES.md` without hardcoding a filename.
-- **Claude Code skills (two):**
+- **Claude Code skills (three):**
   - [`.claude/skills/remarque/SKILL.md`](.claude/skills/remarque/SKILL.md) — triggers on "remarque" / "design system" / new-page work, loads all three files, and states the tier rules, the audit command, and the two build-time pitfalls (unlayered-token-import, string-form `@import`) that pass a green build while silently breaking.
   - [`.claude/skills/remarque-adopt/SKILL.md`](.claude/skills/remarque-adopt/SKILL.md) — triggers on "bump remarque-tokens" / "upgrade the design system" / "adopt remarque in an existing site" / an audit that starts failing after a version bump. The consumer-conformance playbook (issue #107): verify the resolved version past the 0.x caret freeze, discover newly-required tokens from `remarque-audit --json` mechanically, solve missing values against the *consumer's own* backgrounds (keep-if-passing), classify `remarque-drift --json` output (FAIL/WARN/INFO), and report against a fixed PR-body contract. Every step ends in a machine gate — `passed: true`, not agent judgment.
+  - [`.claude/skills/remarque-new-page/SKILL.md`](.claude/skills/remarque-new-page/SKILL.md) — triggers on "new page" / "add a page" / "build an essay/archive/landing page" / "use an archetype". A companion to the `remarque` loader skill, not a parallel restatement of it: pick the archetype from REMARQUE.md, fetch the relevant registry item and verify its sha256 against the `registry.json` pin before applying it (issue #89's transcription-bug prevention), wire the page per AGENT_RULES pitfalls, and gate acceptance on `remarque-audit --json` plus the registry item's own markup-contract assertions (issue #108).
 
-  Both ship in the npm tarball under `skills/` (see "Installing the skills" below) as well as living at `.claude/skills/` in this repo.
+  All three ship in the npm tarball under `skills/` (see "Installing the skills" below) as well as living at `.claude/skills/` in this repo.
 - **Live tokens endpoint:** the demo site serves the current `tokens.json` at **https://williamzujkowski.github.io/remarque/tokens.json**, and its schema at **https://williamzujkowski.github.io/remarque/tokens.schema.json** — a remote agent can fetch current token values (and validate their shape) directly instead of trusting training data.
 - **Markup-contract registry:** a shadcn-`registry-item.json`-shaped, version-pinned, hash-verified registry of known-good markup for the Essay/Broadsheet/Forms/Palette Deck modules — **https://williamzujkowski.github.io/remarque/registry.json** (index) and **https://williamzujkowski.github.io/remarque/registry/essay.json** (per item; also `broadsheet`/`forms`/`palette-deck`). Fetch and apply the markup instead of transcribing it from spec prose — see REMARQUE.md's "The Registry" and AGENT_RULES.md's "Prefer the Registry Over Transcribing Prose."
 
@@ -88,11 +89,12 @@ in explicitly, one `cp` per skill:
 mkdir -p .claude/skills
 cp -r node_modules/remarque-tokens/skills/remarque .claude/skills/remarque
 cp -r node_modules/remarque-tokens/skills/remarque-adopt .claude/skills/remarque-adopt
+cp -r node_modules/remarque-tokens/skills/remarque-new-page .claude/skills/remarque-new-page
 ```
 
 The copies are versioned with whatever `remarque-tokens` version is
-installed at copy time, not auto-updating — re-run both `cp` commands
-after any MAJOR bump (and any time `AGENT_RULES.md`'s "Machine-Readable
+installed at copy time, not auto-updating — re-run all three `cp`
+commands after any MAJOR bump (and any time `AGENT_RULES.md`'s "Machine-Readable
 Output" shape changes) to pick up the current playbook.
 
 ## Files

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "remarque-tokens",
-  "version": "0.25.0",
+  "version": "0.26.0",
   "engines": {
     "node": ">=18"
   },
@@ -87,6 +87,7 @@
     "./registry/*": "./registry/*.json",
     "./skills/remarque": "./skills/remarque/SKILL.md",
     "./skills/adopt": "./skills/remarque-adopt/SKILL.md",
+    "./skills/new-page": "./skills/remarque-new-page/SKILL.md",
     "./package.json": "./package.json"
   },
   "files": [

package/registry/broadsheet.json

@@ -4,7 +4,7 @@
   "type": "remarque:contract",
   "title": "Broadsheet Pattern",
   "description": "The editorial Landing/archive pattern: masthead, lead article, numbered entry list, and post-header kicker. Entry numerals are generated from `data-entry-number` via `attr()`, never `counter()`, and every kicker/dateline row is true `font-variant-caps: all-small-caps`, never `text-transform: uppercase`.",
-  "version": "0.25.0",
+  "version": "0.26.0",
   "integrity": "sha256-BZea38PRdob4OfmdGN0eDw3U0adl7SEsdrjKgSewK9A=",
   "dependencies": [
     "remarque-tokens"

package/registry/essay.json

@@ -4,7 +4,7 @@
   "type": "remarque:contract",
   "title": "Essay Module",
   "description": "Sidenotes + sticky TOC rail for long-form Essay pages: margin notes relocated into real DOM order, right after the paragraph that cites them, numbered by CSS counter and labeled `aria-label=\"Note N\"` in the same order the counter advances — the mechanism that prevents the sidenote aria-label/DOM-order transcription bug found in the flagship migration (#89, williamzujkowski.github.io#380).",
-  "version": "0.25.0",
+  "version": "0.26.0",
   "integrity": "sha256-zr04H0+0xf01OWLk6B2A9ziZOYJd4Sq5q5/cib65lbU=",
   "dependencies": [
     "remarque-tokens"

package/registry/forms.json

@@ -4,7 +4,7 @@
   "type": "remarque:contract",
   "title": "Forms Primitives",
   "description": "Native field/input/checkbox/radio/button primitives with state-color wiring. Every `.remarque-input` pairs `for`/`id` with its `.remarque-field-label`, and every `.remarque-field-message` is wired via `aria-describedby` on the control — the paint-layer `data-state` attribute is never the only signal; `aria-invalid`/`aria-describedby` on the input carry the real accessibility contract.",
-  "version": "0.25.0",
+  "version": "0.26.0",
   "integrity": "sha256-WfYjcf04Dxxx7X21U5b6DrY90Qw95p0zkCQszoh77tE=",
   "dependencies": [
     "remarque-tokens"

package/registry/palette-deck.json

@@ -4,7 +4,7 @@
   "type": "remarque:contract",
   "title": "Palette Deck (markup contract only — no executable content)",
   "description": "Markup/wiring contract for the Palette Deck: set `data-palette` on the same root element as `data-theme` and the two compose independently. This item ships ONLY that HTML fragment. `deck.js` — the runtime module itself, a dependency-free ~60-line ESM file — is deliberately NOT embedded here: the registry’s blocking no-executable-content condition is held to an unambiguous zero-`<script>`-tag bar across every item, so neither `deck.js` nor the FOUC-restore `<script>` sample documented alongside it in REMARQUE.md is included. Consume `deck.js` the normal way, via the `remarque-tokens/deck` package import (`dependencies` below); read the FOUC-restore snippet from the `docs` URL.",
-  "version": "0.25.0",
+  "version": "0.26.0",
   "integrity": "sha256-WGgBZ2j0VnLPRAZlzv/4G1Wu9rKqTdXf1536dWWu8nU=",
   "dependencies": [
     "remarque-tokens"

package/registry.json

@@ -2,14 +2,14 @@
   "$schema": "https://williamzujkowski.github.io/remarque/registry.schema.json",
   "name": "remarque-tokens",
   "homepage": "https://williamzujkowski.github.io/remarque/",
-  "version": "0.25.0",
+  "version": "0.26.0",
   "items": [
     {
       "name": "essay",
       "type": "remarque:contract",
       "title": "Essay Module",
       "description": "Sidenotes + sticky TOC rail for long-form Essay pages: margin notes relocated into real DOM order, right after the paragraph that cites them, numbered by CSS counter and labeled `aria-label=\"Note N\"` in the same order the counter advances — the mechanism that prevents the sidenote aria-label/DOM-order transcription bug found in the flagship migration (#89, williamzujkowski.github.io#380).",
-      "version": "0.25.0",
+      "version": "0.26.0",
       "integrity": "sha256-zr04H0+0xf01OWLk6B2A9ziZOYJd4Sq5q5/cib65lbU=",
       "file": "registry/essay.json"
     },
@@ -18,7 +18,7 @@
       "type": "remarque:contract",
       "title": "Broadsheet Pattern",
       "description": "The editorial Landing/archive pattern: masthead, lead article, numbered entry list, and post-header kicker. Entry numerals are generated from `data-entry-number` via `attr()`, never `counter()`, and every kicker/dateline row is true `font-variant-caps: all-small-caps`, never `text-transform: uppercase`.",
-      "version": "0.25.0",
+      "version": "0.26.0",
       "integrity": "sha256-BZea38PRdob4OfmdGN0eDw3U0adl7SEsdrjKgSewK9A=",
       "file": "registry/broadsheet.json"
     },
@@ -27,7 +27,7 @@
       "type": "remarque:contract",
       "title": "Forms Primitives",
       "description": "Native field/input/checkbox/radio/button primitives with state-color wiring. Every `.remarque-input` pairs `for`/`id` with its `.remarque-field-label`, and every `.remarque-field-message` is wired via `aria-describedby` on the control — the paint-layer `data-state` attribute is never the only signal; `aria-invalid`/`aria-describedby` on the input carry the real accessibility contract.",
-      "version": "0.25.0",
+      "version": "0.26.0",
       "integrity": "sha256-WfYjcf04Dxxx7X21U5b6DrY90Qw95p0zkCQszoh77tE=",
       "file": "registry/forms.json"
     },
@@ -36,7 +36,7 @@
       "type": "remarque:contract",
       "title": "Palette Deck (markup contract only — no executable content)",
       "description": "Markup/wiring contract for the Palette Deck: set `data-palette` on the same root element as `data-theme` and the two compose independently. This item ships ONLY that HTML fragment. `deck.js` — the runtime module itself, a dependency-free ~60-line ESM file — is deliberately NOT embedded here: the registry’s blocking no-executable-content condition is held to an unambiguous zero-`<script>`-tag bar across every item, so neither `deck.js` nor the FOUC-restore `<script>` sample documented alongside it in REMARQUE.md is included. Consume `deck.js` the normal way, via the `remarque-tokens/deck` package import (`dependencies` below); read the FOUC-restore snippet from the `docs` URL.",
-      "version": "0.25.0",
+      "version": "0.26.0",
       "integrity": "sha256-WGgBZ2j0VnLPRAZlzv/4G1Wu9rKqTdXf1536dWWu8nU=",
       "file": "registry/palette-deck.json"
     }

package/scripts/lib/skills.mjs

@@ -1,7 +1,8 @@
 /*
- * Shared table + tiny helpers for the two Claude Code skills this package
- * ships and packages — used by scripts/build-skills.mjs (prepack copy +
- * CI freshness gate) and scripts/test-skills.mjs (content validation).
+ * Shared table + tiny helpers for the three Claude Code skills this
+ * package ships and packages — used by scripts/build-skills.mjs (prepack
+ * copy + CI freshness gate) and scripts/test-skills.mjs (content
+ * validation).
  *
  * `.claude/skills/<name>/SKILL.md` is the ONE canonical, hand-authored
  * copy of each skill (also what a local Claude Code session in this repo
@@ -24,6 +25,12 @@ export const SKILLS = [
     packaged: 'skills/remarque-adopt/SKILL.md',
     exportName: './skills/adopt',
   },
+  {
+    name: 'remarque-new-page',
+    canonical: '.claude/skills/remarque-new-page/SKILL.md',
+    packaged: 'skills/remarque-new-page/SKILL.md',
+    exportName: './skills/new-page',
+  },
 ];
 
 /*

package/skills/remarque-new-page/SKILL.md

@@ -0,0 +1,121 @@
+---
+name: remarque-new-page
+description: >
+  Build a new page in a project that consumes `remarque-tokens` — pick the
+  right archetype, fetch registry items instead of transcribing markup,
+  wire the page per AGENT_RULES pitfalls, and gate on remarque-audit plus
+  the registry's own markup-contract assertions. Use when the user says
+  "new page", "add a page", "build an essay", "build an archive page",
+  "build a landing page", "use an archetype", or asks for a page in a
+  Remarque-consuming project. Companion to the `remarque` loader skill —
+  load that one first for the tier rules and the two build-time pitfalls;
+  this skill is the page-building procedure on top of it, not a
+  restatement of it.
+license: MIT
+---
+
+# remarque-new-page
+
+Five steps, each ending in a gate. This sits on top of the `remarque`
+loader skill and does not restate its tier rules or pitfalls — it applies
+them to the specific job of adding one new page.
+
+## 1. Load the loader skill's three files
+
+Run the `remarque` skill first. If skill resolution isn't available in
+this context, read `AGENT_RULES.md`, `REMARQUE.md`, and `tokens.json`
+yourself — see that skill's file table for the consumer-project vs.
+in-repo paths. Do not build from training-data memory of token values or
+tier rules; both change across releases and the current values live only
+in those three files.
+
+- Gate: you can name which tier (`core`/`palette`) governs the tokens
+  this page will touch, and you have the CURRENT `tokens.json` open —
+  not a cached mental model from an older version.
+
+## 2. Pick the archetype
+
+`REMARQUE.md`'s "Page Archetypes" section defines seven: Essay, Project
+Dossier, Notebook, Landing, Reference/Docs, Changelog, Gallery. Match the
+request to exactly one — "essay"/"blog post" → Essay; "archive"/"index of
+posts" → Landing (often paired with the Broadsheet pattern below);
+"docs"/"reference" → Reference/Docs. Do not invent an eighth.
+
+- Gate: you can quote the chosen archetype's "Always includes"/"Never
+  includes" lists from the spec, not paraphrase them from memory.
+
+## 3. Module-backed pages: fetch the registry item, verify, apply
+
+If the archetype uses one of the four registry-backed modules — Essay
+(sidenotes/TOC rail), Broadsheet (Landing/archive pattern), Forms, or
+Palette Deck — do not transcribe markup from REMARQUE.md's prose. That is
+the exact failure mode issue #89 documents: a hand-copied sidenote
+`aria-label` drifted out of DOM order. Fetch the item instead:
+
+```bash
+cat node_modules/remarque-tokens/registry/essay.json   # or broadsheet/forms/palette-deck
+# or, if not installed locally:
+curl -s https://williamzujkowski.github.io/remarque/registry/essay.json
+```
+
+Then **verify integrity before applying anything** — recompute the sha256
+over the fetched item's `files[].content` and compare it to that item's
+own `integrity` field (both are the pin recorded in `registry.json`'s
+index):
+
+```bash
+node -e '
+  const fs = require("fs"), crypto = require("crypto");
+  const item = JSON.parse(fs.readFileSync(process.argv[1], "utf8"));
+  const bytes = Buffer.from(item.files.map(f => f.content).join(""));
+  console.log("sha256-" + crypto.createHash("sha256").update(bytes).digest("base64"));
+' node_modules/remarque-tokens/registry/essay.json
+# compare stdout, byte for byte, to that same file's "integrity" field
+```
+
+Apply `files[].content` verbatim — the `remarque:css` entry as the CSS
+module, the `remarque:markup` entry's `usage.html` as the page's starting
+DOM — rather than retyping either from memory.
+
+- Gate: the computed hash matches `integrity` exactly. A mismatch means
+  stop and re-fetch; never apply an unverified payload.
+
+## 4. Wire it per AGENT_RULES pitfalls
+
+Three mistakes pass a green build with no warning, so verify them
+explicitly:
+
+- **Unlayered tokens import (Pitfall #7).** Never `@import
+  "remarque-tokens" layer(...)` — layering makes every `@theme inline`
+  mapped utility circular and invalid.
+- **String-form `@import` only (Pitfall #6).** `@import './tokens.css';`,
+  never `@import url(...)` — Tailwind v4/Lightning CSS silently drops the
+  latter for local files. Verify the built CSS contains `.remarque-prose`
+  after touching any import.
+- **`.remarque-prose` + `.content-reading` pairing.** `.remarque-prose`
+  supplies typography only; it does not center the column. Every reading
+  column needs both classes together, and (Pitfall #2) the page's header
+  must share the same centered measure the prose body uses, or the two
+  misalign.
+
+- Gate: grep the built CSS for `.remarque-prose` (proves the import
+  survived), and confirm every prose block in the new page carries
+  `content-reading` alongside it.
+
+## 5. Acceptance
+
+```bash
+npx remarque-audit --palette <file> --src <dir> --json
+```
+
+Requires `passed: true` in the JSON — not "looks close." If the page used
+a registry module, also re-check it against that module's own
+markup-contract rule from AGENT_RULES.md's Quality Checklist: Essay's
+sidenote/TOC-rail DOM-order + `aria-label` rule, Broadsheet's
+`data-entry-number`/`attr()` + small-caps rule, Forms' label/
+`aria-describedby` pairing rule, or Palette Deck's `data-palette`/
+`data-theme` co-location rule.
+
+- Gate: `remarque-audit --json` reports `passed: true`, AND the
+  module-specific markup-contract rule above holds. Either failing means
+  the page isn't done.

package/tokens.d.ts

@@ -1,6 +1,6 @@
 /*
  * Remarque design tokens — GENERATED from tokens.json by
- * scripts/tokens-json.mjs (v0.25.0). Do not edit — the CSS
+ * scripts/tokens-json.mjs (v0.26.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

@@ -3,7 +3,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.25.0",
+      "version": "0.26.0",
       "tiers": {
         "core": "immutable identity — overriding forks the system",
         "palette": "sanctioned personalization surface — override freely, then run remarque-audit"