remarque-tokens 0.9.0 → 0.10.0

package/CHANGELOG.md

@@ -4,6 +4,27 @@ 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.10.0 — 2026-07-23
+
+Color-provider Phase 2 groundwork: the upstream dataset now pairs its own
+themes, so the bridge no longer needs to be told what goes with what.
+
+### Changed
+- **`remarque-theme`: `--dark` is now optional.** Dataset 0.2.0 of
+  `@williamzujkowski/oklch-terminal-themes` ships a `counterpart` field
+  (canonical light↔dark pairing, curated for ambiguous families —
+  upstream #128); when the light theme declares one, the bridge uses it.
+  A counterpart slug is validated exactly like a user-supplied `--dark`
+  (index membership before any path resolution). Lights without a
+  counterpart still require `--dark`; nothing is guessed from names.
+- **Corpus test now enumerates pairs from the `counterpart` field**
+  instead of the name-stem heuristic it shipped with — the dataset is
+  authoritative; the heuristic is gone.
+- Dev-pinned dataset bumped `0.1.0` → `0.2.0` (485 → 547 themes; the
+  corpus now includes deriving Remarque's palette from its own upstreamed
+  `remarque-light`/`remarque-dark` terminal themes, upstream #127).
+  `peerDependencies` widened to `>=0.1.0 <0.3.0`.
+
 ## 0.9.0 — 2026-07-22
 
 Color-provider bridge release (consensus-ratified 7-0, higher_order panel;

package/REMARQUE.md

@@ -77,14 +77,14 @@ The palette tier (all `--color-*` tokens) can be *supplied* rather than hand-aut
 [`@williamzujkowski/oklch-terminal-themes`](https://www.npmjs.com/package/@williamzujkowski/oklch-terminal-themes) is the reference provider: a dataset of terminal color schemes converted to OKLCH. Run it through the bundled bridge:
 
 ```
-npx remarque-theme <light-slug> --dark <dark-slug> [-o palette-override.css]
+npx remarque-theme <light-slug> [--dark <dark-slug>] [-o palette-override.css]
 ```
 
 Terminal themes carry only `background/foreground/cursor/selection` + 16 ANSI slots — a few of Remarque's 15 semantic slots map directly, and most themes fail the AAA `fg-muted` 7:1 line as authored. So `remarque-theme` *derives* rather than maps: **hue and chroma carry the theme's personality; lightness is solved per slot** (binary search against the same contrast targets as the Enforcement Checklist below, with in-gamut chroma clamping) so the output passes `remarque-audit` by construction. The accent hue comes from the theme's cursor color if it's chromatic, otherwise the most saturated classic ANSI color, and is kept consistent between the light and dark half of a pair.
 
 The audit remains the gate regardless of provenance — `remarque-theme` self-verifies its own output against the same checks before it will emit anything, but a site that hand-edits a generated palette (or points at a provider with pathological input colors) still runs through `remarque-audit` in CI like any other palette.
 
-**Pairing contract:** the dataset does not yet carry light/dark pairing metadata (tracked upstream: [`oklch-terminal-themes#128`](https://github.com/williamzujkowski/oklch-terminal-themes/issues/128)), so `--dark <slug>` is explicitly required — there is no implicit or guessed dark counterpart. `remarque-theme` also rejects a light slug that isn't tagged `isDark: false` and a dark slug that isn't tagged `isDark: true`.
+**Pairing contract:** dataset 0.2.0+ carries a `counterpart` field linking each paired theme to its canonical opposite-polarity variant ([`oklch-terminal-themes#128`](https://github.com/williamzujkowski/oklch-terminal-themes/issues/128)), and `--dark` defaults to it — `npx remarque-theme rose-pine-dawn` alone derives the rosé-pine pair. For a light theme without a counterpart (or an older dataset), `--dark <slug>` remains required; nothing is ever guessed from names. `remarque-theme` also rejects a light slug that isn't tagged `isDark: false` and a dark slug that isn't tagged `isDark: true`.
 
 ---
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "remarque-tokens",
-  "version": "0.9.0",
+  "version": "0.10.0",
   "engines": {
     "node": ">=18"
   },
@@ -31,10 +31,10 @@
     "drift": "node scripts/drift-check.mjs"
   },
   "devDependencies": {
-    "@williamzujkowski/oklch-terminal-themes": "0.1.0"
+    "@williamzujkowski/oklch-terminal-themes": "0.2.0"
   },
   "peerDependencies": {
-    "@williamzujkowski/oklch-terminal-themes": "^0.1.0"
+    "@williamzujkowski/oklch-terminal-themes": ">=0.1.0 <0.3.0"
   },
   "peerDependenciesMeta": {
     "@williamzujkowski/oklch-terminal-themes": {

package/scripts/theme.mjs

@@ -41,12 +41,12 @@ 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]
 
   <light-slug>     slug of a theme with isDark=false in ${PKG_SPEC}
-  --dark <slug>    slug of a theme with isDark=true (required — the
-                    dataset has no light/dark pairing metadata yet, see
-                    oklch-terminal-themes#128)
+  --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`;
 
 function die(msg) {
@@ -67,7 +67,7 @@ for (let i = 0; i < argv.length; i++) {
   else positional.push(a);
 }
 const lightSlug = positional[0];
-if (!lightSlug || !darkSlug) die(USAGE);
+if (!lightSlug) die(USAGE);
 
 /* ── Resolve @williamzujkowski/oklch-terminal-themes ─────────────────
  * Tried from the consumer's cwd first (a project that installs the
@@ -123,6 +123,18 @@ function requireSlug(slug, label) {
 }
 
 const lightMeta = requireSlug(lightSlug, 'light');
+/* --dark defaults to the dataset's counterpart field (0.2.0+). The value
+ * still goes through requireSlug like a user-supplied one — a dataset
+ * entry is not trusted further than the CLI arg it replaces. */
+if (!darkSlug) {
+  darkSlug = lightMeta.counterpart;
+  if (!darkSlug) {
+    die(
+      `"${lightSlug}" has no counterpart in the installed ${PKG_SPEC} dataset — ` +
+      `pass --dark <slug> explicitly (or upgrade the dataset; pairing metadata landed in 0.2.0)`
+    );
+  }
+}
 const darkMeta = requireSlug(darkSlug, 'dark');
 if (lightMeta.isDark !== false) die(`light slug "${lightSlug}" has isDark=${lightMeta.isDark}, expected false`);
 if (darkMeta.isDark !== true) die(`dark slug "${darkSlug}" has isDark=${darkMeta.isDark}, expected true`);

package/tokens.json

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