@radicool/throughline 0.15.0 → 0.17.0

package/references/native-adapter-config.md

@@ -0,0 +1,996 @@
+# Native adapter configuration (GENERATED)
+
+> **GENERATED FILE — do not edit by hand.** Source: `scripts/lib/sd-native.mjs`,
+> which is unit-tested in Node and installed into the consumer's repo.
+> Regenerate with `node scripts/build-native-adapter-config.mjs`; CI gates
+> freshness with `--check`.
+
+The Style Dictionary configuration a native adapter (`ios-swift`,
+`android-kotlin`, or any generated native target) needs in order to emit
+**correct** output from a real DTCG token source.
+
+**Why this exists.** The stock `ios-swift` and `compose` transform groups
+produce output that compiles and is wrong. Run against a real source, the stock
+configuration emitted every `px`-authored dimension at ×16 its authored value,
+leaked `color-mix()` expressions into Swift, and left dual-node aliases as bare
+`px` literals — all at exit `0`. None of that is a Style Dictionary limitation.
+All of it is configuration.
+
+**You do not need to copy any of this.** It ships as
+`${CLAUDE_PLUGIN_ROOT}/scripts/lib/sd-native.mjs`. Install it beside
+`lib/dtcg.mjs` and `lib/native-literal.mjs` and call it:
+
+```js
+import StyleDictionary from 'style-dictionary';
+import { registerNativeTransforms, nativePlatform, nativeSources }
+  from './scripts/lib/sd-native.mjs';
+
+registerNativeTransforms(StyleDictionary);
+
+for (const mode of ['light', 'dark']) {
+  const sd = new StyleDictionary({
+    source: nativeSources(sourcesFor(mode)),
+    preprocessors: ['dtcg/resolve-dual-node'],
+    platforms: {
+      ios: nativePlatform({ platform: 'ios-swift', buildPath: `out/${mode}/` }),
+    },
+  });
+  await sd.buildAllPlatforms();
+}
+```
+
+The sections below are the module's own source, inlined so the configuration
+stays reviewable. Pair this with `${CLAUDE_PLUGIN_ROOT}/references/sync-adapters.md`,
+which covers the adapter contract itself.
+
+## Imports
+
+`node:fs` plus the siblings `lib/dtcg.mjs` and `lib/native-literal.mjs` this
+plugin already installs — nothing else. Style Dictionary is passed in as a
+parameter, never imported, which is what keeps this module installable into a
+consumer's repo.
+
+```js
+import { readFileSync } from 'node:fs';
+import {
+  flattenDtcg,
+  resolveValue,
+  findModeCollisions,
+  TEXT_UNIT_NAMES,
+  TEXT_ROLE_UNIT,
+  EXT_NS,
+  textRoleGraph,
+} from './dtcg.mjs';
+import { isValidLiteral, GRAMMAR, CSS_CONSTRUCT } from './native-literal.mjs';
+```
+
+## 1. Read the authored unit
+
+**This replaces `size/swift/remToCGFloat` and the `size/compose/*` transforms,
+and it is the single most important piece.** Those assume every dimension is
+authored in `rem` and multiply by 16. Against a `px`-authored source that
+silently produces output at sixteen times scale which compiles and ships.
+
+```js
+// Read the magnitude from the AUTHORED value's own unit.
+//
+// The stock size/swift/remToCGFloat and size/compose/rem* transforms assume rem
+// and multiply by 16. Against a px-authored source that emits text.sm: "14px"
+// as CGFloat(224.00) — valid, compiling, and sixteen times too large.
+//
+// iOS points and Android dp both map 1:1 to CSS px by convention. A unitless
+// dimension is a ratio and is never scaled. % and em are container- or
+// parent-relative, so there is genuinely no build-time native magnitude.
+export function magnitude(authored) {
+  const m = String(authored).trim().match(/^(-?(?:\d+(?:\.\d+)?|\.\d+))([a-z%]*)$/);
+  if (!m) return null;
+  const n = Number(m[1]);
+  if (m[2] === 'px' || m[2] === '') return n;
+  if (m[2] === 'rem') return n * 16;
+  return null;
+}
+```
+
+## 2. Compute `color-mix()` to a literal
+
+A CSS expression has no native equivalent, and Style Dictionary does no colour
+math. Native adapters resolve to literals; for a `color-mix` that means
+actually computing the blend. Register this **before** the platform's colour
+transform, so the colour transform receives a valid hex8 rather than a CSS
+function.
+
+```js
+// Compute a color-mix() against transparent to a literal hex8.
+//
+// A CSS expression has no native equivalent and Style Dictionary does no colour
+// math, so it resolves the inner reference and leaves the function wrapper in
+// the output. Against `transparent` in srgb the result is the inner colour at
+// the stated alpha.
+const MIX = /^color-mix\(in srgb,\s*(#[0-9a-fA-F]{6})\s+([\d.]+)%,\s*transparent\)$/;
+
+export function colorMixToHex8(value) {
+  const m = String(value).trim().match(MIX);
+  if (!m) return null;
+  const alpha = Math.round((Number(m[2]) / 100) * 255)
+    .toString(16)
+    .padStart(2, '0');
+  return `${m[1]}${alpha}`.toLowerCase();
+}
+```
+
+## 3. Resolve aliases and hoist dual-node children
+
+Style Dictionary's resolver will not traverse into a node that carries both a
+`$value` and children, and its collector stops there too. The dual-node pattern
+is invalid DTCG — the Design Tokens Format Module's 30 July 2026 draft, §6.1,
+requires tools to report it as an error, and §6.2's `$root` is the sanctioned
+way to pair a value with children. Figma-derived sources emit it anyway:
+`text.sm` holds `$value: "14px"` *and* a `text.sm.lineHeight` child. So every
+alias to such a child fails to resolve, and the child is never emitted at all.
+
+Both are fixed before Style Dictionary sees the tree.
+
+```js
+// Resolve aliases and hoist dual-node children, before Style Dictionary sees
+// the tree.
+//
+// Two distinct SD limitations, both caused by a node carrying BOTH a $value and
+// children — invalid DTCG: the Format Module's 30 July 2026 draft, §6.1,
+// requires tools to report this as an error; §6.2's $root is the sanctioned
+// way to pair a value with children. Common in Figma-derived sources anyway,
+// where text.sm holds $value "14px" plus a text.sm.lineHeight child:
+//
+//   1. The resolver will not traverse into such a node, so every alias to the
+//      child fails to resolve and emits as a bare literal.
+//   2. The collector also stops there, so the child is never emitted at all.
+//
+// Resolving here also handles references embedded inside an expression, which
+// SD's whole-value matcher misses. Pre-resolving costs nothing on native
+// targets: they set outputReferences: false, so references flatten regardless.
+//
+// Marks a node whose AUTHORED $value was a whole-value reference, so the hoist
+// can decline to override the type DTCG 5.2.2 rule 1 already determined from the
+// referent. A WeakSet keyed on the node object, rather than a property written
+// onto it, holds structural idempotency exactly: structuredClone drops the
+// membership along with the rest of the identity, so preprocess(preprocess(x))
+// is deepEqual to preprocess(x) with no leak question to manage.
+const WAS_REF = new WeakSet();
+const WHOLE_REF = /^\{[^}]+\}$/;
+
+function interpolate(value, flat) {
+  return value.replace(/\{([^}]+)\}/g, (whole, ref) => {
+    try {
+      return String(resolveValue(ref, flat));
+    } catch {
+      return whole;
+    }
+  });
+}
+
+function resolveInPlace(node, flat, prefix = []) {
+  for (const [key, val] of Object.entries(node)) {
+    if (key.startsWith('$')) continue;
+    if (!val || typeof val !== 'object') continue;
+    const path = [...prefix, key];
+    if ('$value' in val && typeof val.$value === 'string') {
+      if (WHOLE_REF.test(val.$value)) {
+        WAS_REF.add(val);
+        try {
+          val.$value = resolveValue(path.join('.'), flat);
+        } catch {
+          /* leave an unresolvable reference in place for SD to report */
+        }
+      } else {
+        val.$value = interpolate(val.$value, flat);
+      }
+    }
+    resolveInPlace(val, flat, path);
+  }
+  return node;
+}
+
+// text.sm.lineHeight becomes text.smLineHeight, which name/camel renders as
+// textSmLineHeight — the identical symbol the un-hoisted path would produce.
+//
+// Collisions are COLLECTED, not thrown here: the walk has to continue to report
+// every one, and the recursion is depth-first, so throwing from a frame would
+// report one subtree. preprocess throws once, after the whole tree is walked.
+//
+// On collision the assignment is SKIPPED. Continuing to overwrite while
+// collecting means later detections are computed against a tree already
+// corrupted — the enclosing loop's Object.entries snapshot still holds the
+// detached node, and its own children then hoist out of a subtree no longer
+// reachable.
+//
+// hoisted in node walks the prototype chain, so a camel-joined name matching
+// an inherited Object.prototype member (toString, valueOf, ...) reported a
+// collision against a sibling that does not exist. Object.hasOwn checks the
+// tree's own keys only.
+function hoistDualNodes(node, collisions, prefix = [], groupType = undefined) {
+  // The $type a plain member of THIS frame inherits, and the one a child
+  // hoisted INTO it will inherit — the same value, because the hoist makes the
+  // child a member of node. A node carrying a $value is a token, not a group
+  // (DTCG 6.1), so it is not an inheritance source: look through it and keep
+  // the chain from above. That also covers the nested case, where node is a
+  // dual node and the child hoists past it on the next frame up anyway.
+  const inherited = '$value' in node ? groupType : (node.$type ?? groupType);
+  // Which hoisted names THIS pass has already claimed, and the authored path
+  // of the child that claimed each one — a collision here is a second hoist
+  // landing on a name no sibling ever authored. Local to this frame: node is
+  // fixed per invocation, so collisions are always within one parent's key
+  // space.
+  const claimedBy = new Map();
+  for (const [key, val] of Object.entries(node)) {
+    if (key.startsWith('$') || !val || typeof val !== 'object') continue;
+    hoistDualNodes(val, collisions, [...prefix, key], inherited);
+    if ('$value' in val) {
+      for (const [childKey, childVal] of Object.entries(val)) {
+        if (childKey.startsWith('$') || !childVal || typeof childVal !== 'object') continue;
+        const hoisted = key + childKey[0].toUpperCase() + childKey.slice(1);
+        const from = [...prefix, key, childKey].join('.');
+        if (Object.hasOwn(node, hoisted)) {
+          const existingNode = node[hoisted];
+          const isGroup = existingNode !== null && typeof existingNode === 'object' && !('$value' in existingNode);
+          collisions.push({
+            from,
+            onto: [...prefix, hoisted].join('.'),
+            isGroup,
+            claimant: claimedBy.get(hoisted),
+            existing: isGroup
+              ? undefined
+              : existingNode && typeof existingNode === 'object'
+                ? existingNode.$value
+                : existingNode,
+          });
+          continue;
+        }
+        // The carry pays for what the hoist costs: the dual node is the
+        // child's closest $type-bearing ancestor as authored, and after the
+        // hoist it is a sibling, so that type is lost unless it travels.
+        //
+        // Two cases where nothing was lost, so nothing is carried. A
+        // reference-valued child already has its referent's resolved type, and
+        // DTCG 5.2.2 rule 1 ranks that above inheritance. And where an
+        // enclosing GROUP supplies a type, that group was the child's
+        // inheritance source all along — 5.2.2 inherits from the closest parent
+        // group, and the dual node is a token — so it still is after the hoist,
+        // and carrying would shadow it.
+        //
+        // The invariant, stated no wider than it holds: the hoist never
+        // CHANGES a type DTCG inheritance already determines. Where it
+        // determines none, the carry supplies the dual node's — a repair, not
+        // a reading of the source. So an enclosing group wins even where its
+        // type suits the child badly, because the hoist is not entitled to
+        // improve on what the source says; but the carry firing at all is the
+        // hoist saying something the source did not.
+        if (
+          !('$type' in childVal) &&
+          '$type' in val &&
+          !WAS_REF.has(childVal) &&
+          inherited === undefined
+        ) {
+          childVal.$type = val.$type;
+        }
+        node[hoisted] = childVal;
+        delete val[childKey];
+        claimedBy.set(hoisted, from);
+      }
+    }
+  }
+  return node;
+}
+
+// Which native unit a dimension belongs in: Compose's Dp, or its TextUnit.
+//
+// $type cannot answer this. DTCG's type set has no fontSize — font sizes are
+// dimension, and so are spacing, radius and stroke widths — so the stock
+// size/compose/remToSp filter on $type === 'fontSize' never fires on a
+// spec-compliant source and every font size falls through to dp.
+//
+// The role therefore comes from the one place a DTCG source states it: the
+// member names the Format Module's 30 July 2026 draft, §9.8, fixes at MUST
+// level for the typography composite. Two of the five are dimension-valued:
+// fontSize and letterSpacing. §9.8 types lineHeight as a NUMBER multiplier, so
+// a source following the spec exactly emits no dimension-typed lineHeight and
+// this rule never fires on one. Figma-derived sources — what this module
+// targets — emit px line heights typed dimension, and those are the majority of
+// the tokens the rule fixes on a real source. lineHeight is named here anyway
+// because Compose's TextStyle takes TextUnit for all three, with no Dp
+// overload, so a px line height must reach the sp branch to be usable at all.
+//
+// The limit, stated rather than hidden: §9.8 puts those names inside a
+// composite token's $value object, while Figma-derived sources put them as
+// sibling tokens in a group. Reading them there mirrors the spec's vocabulary;
+// it is not a guarantee the spec makes. A source naming its font size
+// typography.body.size sets $extensions itself and is honoured below.
+//
+// Defined in lib/dtcg.mjs and imported above, so textRoleGraph applies the
+// identical set. Two definitions of this set would drift.
+
+// Reverse-DNS, per DTCG's $extensions convention. Exported because the
+// transforms and their tests address the same key.
+//
+// Defined in lib/dtcg.mjs and re-exported here: the transforms and their tests
+// address this key through sd-native.mjs, and that surface does not move.
+export { EXT_NS };
+
+// px and rem only. magnitude() reads a bare number as an unscaled ratio, so a
+// lineHeight authored "1.5" would otherwise be stamped and emit 1.50.sp —
+// which compiles and renders 1.5sp text, trading a loud failure for a silent
+// one. Since #52 a unitless value is declined by every size transform and
+// emits bare, which is what DTCG 8.7 and 9.8 say a ratio is, so this gate is
+// no longer the only thing standing between a ratio and 1.50.sp. It stays
+// because the stamp is also the override's carrier, and stamping a ratio as
+// text would still be a claim the source never made.
+// em joins px and rem since #64: Compose's TextUnit has a real .em, so an
+// em-valued letterSpacing is a text-role dimension like any other. It is still
+// a unit — the gate's job is to exclude the UNITLESS value, whose role the
+// source never stated.
+//
+// Defined in lib/dtcg.mjs and imported above, for the same reason as
+// TEXT_UNIT_NAMES: textRoleGraph gates on it too.
+
+// Runs AFTER resolveInPlace and BEFORE hoistDualNodes. Both halves matter.
+//
+// After resolution, because the unit is not in the authored text: a semantic
+// font size is authored "{text.3xl}" and carries no unit at all. Reading the
+// authored string would classify only the px-authored primitives — 13 of 39
+// on a real source.
+//
+// Before the hoist, because the hoist consumes the leaf name:
+// text.xs.lineHeight becomes text.xsLineHeight, and the name this rule matches
+// on is gone. Matching a suffix against the camel-joined name instead would
+// couple the rule to the hoist's naming scheme, and case-insensitively it
+// false-positives on names like baselineHeight.
+function classifyTextUnits(node) {
+  for (const [key, val] of Object.entries(node)) {
+    if (key.startsWith('$') || !val || typeof val !== 'object') continue;
+    if (
+      TEXT_UNIT_NAMES.has(key) &&
+      '$value' in val &&
+      val.$type === 'dimension' &&
+      TEXT_ROLE_UNIT.test(String(val.$value).trim())
+    ) {
+      val.$extensions ??= {};
+      val.$extensions[EXT_NS] ??= {};
+      const ns = val.$extensions[EXT_NS];
+      // A source that states the role itself wins — for a value that HAS a
+      // unit. The override chooses between dp and sp; it does not manufacture
+      // one, so a unitless value is declined by every size transform regardless
+      // of what is stamped here (see isRatio, #52). Declining to overwrite IS
+      // the feature: it costs no configuration parameter, and it is what makes
+      // the pass idempotent.
+      if (!('nativeUnit' in ns)) ns.nativeUnit = 'text';
+    }
+    classifyTextUnits(val);
+  }
+  return node;
+}
+
+// Runs AFTER classifyTextUnits and BEFORE hoistDualNodes, on the SAME two
+// grounds that pass gives: after, so a role the source or the member name
+// already stated wins; before, because the hoist rewrites text.xs.lineHeight to
+// text.xsLineHeight and the graph's paths are written in pre-hoist names.
+//
+// The three gates are classifyTextUnits's, verbatim — a dimension, a value with
+// a unit, and no role already recorded. A unitless value is never stamped: no
+// size transform claims one since #52, and stamping a ratio as text would still
+// be a claim the source never made.
+//
+// A path may name no node at all. resolveInPlace deliberately leaves an
+// unresolvable reference in place for Style Dictionary to report, so the graph
+// can hold an edge to a token that does not exist. Skip it. This is also what
+// keeps the second preprocess pass from throwing, and idempotency with it.
+function applyTextRoleGraph(node, typographic) {
+  for (const path of typographic) {
+    let target = node;
+    for (const segment of path.split('.')) {
+      target = target && typeof target === 'object' ? target[segment] : undefined;
+    }
+    if (!target || typeof target !== 'object' || !('$value' in target)) continue;
+    if (target.$type !== 'dimension') continue;
+    if (!TEXT_ROLE_UNIT.test(String(target.$value).trim())) continue;
+    target.$extensions ??= {};
+    target.$extensions[EXT_NS] ??= {};
+    const ns = target.$extensions[EXT_NS];
+    if (!('nativeUnit' in ns)) ns.nativeUnit = 'text';
+  }
+  return node;
+}
+
+export function preprocess(dict) {
+  const collisions = [];
+  // Read from the UNRESOLVED dict, before resolveInPlace flattens the aliases
+  // the graph is made of.
+  const { typographic } = textRoleGraph(dict);
+  const out = hoistDualNodes(
+    applyTextRoleGraph(
+      classifyTextUnits(resolveInPlace(structuredClone(dict), flattenDtcg(dict))),
+      typographic,
+    ),
+    collisions,
+  );
+  if (collisions.length) {
+    const shown = collisions
+      .slice(0, 5)
+      .map((c) => {
+        const line = `  ${c.from} -> ${c.onto}`;
+        if (c.isGroup) {
+          return line + (c.claimant ? ` (a group, already claimed by the hoist of ${c.claimant})` : ' (a group)');
+        }
+        return c.claimant
+          ? `${line} (already claimed by the hoist of ${c.claimant}, value ${JSON.stringify(c.existing)})`
+          : `${line} (would overwrite ${JSON.stringify(c.existing)})`;
+      })
+      .join('\n');
+    const more = collisions.length > 5 ? `\n  ...and ${collisions.length - 5} more` : '';
+    throw new Error(
+      `${collisions.length} hoisted token name(s) collide with an existing sibling or with a name an earlier hoist already claimed.\n` +
+        "A dual node's child is renamed to a camel-joined sibling, and that name may already be taken — by an authored token or group, or by another dual node's child hoisted earlier in the same pass.\n" +
+        'Hoisting would silently discard one of the two. Rename the child, the sibling, or whichever colliding child should keep the name.\n' +
+        `${shown}${more}`,
+    );
+  }
+  return out;
+}
+```
+
+## 4. Assemble the platform from the stock list
+
+Build the transform list from Style Dictionary's **stock group**, replacing only
+the rem-assuming size transforms. A hand-picked list silently drops whatever it
+forgets — three real defects arose exactly that way.
+
+**The `dp`/`sp` split is fixed here; two narrower Android-only limits remain.**
+Style Dictionary's Compose transforms select on `$type`, and DTCG's type set
+does not line up with what they expect — there is no `fontSize` type, because
+DTCG types font sizes as `dimension`. So the role is taken instead from the
+member names DTCG §9.8 fixes for the typography composite, stamped onto
+`$extensions` during preprocessing, and the two Compose transforms partition on
+that stamp. Measured against a real source: 39 declarations that emitted `dp`
+now emit `sp`, with the Swift output byte-identical.
+
+What remains:
+
+- **A scale primitive nothing references emits as `dp`.** `text.base: "16px"`
+  is a font size only to a human, so #63 takes the role from the reference
+  graph instead: a dimension referenced only by `fontSize`, `letterSpacing` or
+  `lineHeight` members is stamped typographic too. That is structural rather
+  than nominal, so it needs no path convention. A primitive **nothing**
+  references has no signal at all and is not inferred —
+  `tokens:validate-output` names it with an `unreferenced-text-sibling`
+  advisory, and a source-side `nativeUnit` stamp settles it.
+- **An `em` letter spacing reaches Compose but not Swift.** `size/unit-aware/compose-em`
+  emits it as a real `.em` TextUnit, parenthesised — `(-0.03).em` — because
+  `-0.03.em` parses as `-(0.03.em)` and needs an `unaryMinus` operator, while
+  the parenthesised form compiles regardless. iOS is excluded deliberately, not
+  pending: letter spacing there is an `NSAttributedString` kern in points,
+  which needs the font size the token does not carry, so no constant Swift
+  could emit would be right at every font size.
+
+The first is Android-only. `size/unit-aware/swift` filters
+`dimension || fontSize` and emits `CGFloat`, which carries no unit to be wrong
+about; iOS handles Dynamic Type at the use site via `UIFontMetrics`.
+`tokens:validate-output` passes in both cases: it checks magnitude, not unit.
+
+**A unitless value is no longer one of them.** DTCG §8.2.1 requires a dimension
+to carry a unit, §8.7's `number` is the type for a ratio, and §9.8 types
+`lineHeight` as one — so `leading.normal: "1.5"` typed `dimension` is malformed
+input. No size transform claims it: it emits bare on both platforms, which is
+byte-for-byte what a correctly typed `number` already produced, so correcting
+the source's `$type` changes no output. `tokens:validate-output` reports it as
+a `unitless-dimension` advisory, which does not gate — the emitted value is
+right under the ratio reading, and only the author can say whether a ratio is
+what was meant.
+
+**The stock list is accounted for, not transcribed.** `PLATFORMS` records the
+stock group each platform mirrors, and `auditStockGroups` checks at
+registration that every transform in that live group is either run here or
+declined in writing, with a reason. A stock transform this config has never
+decided about warns; it is never silently dropped. The check warns and never
+throws — a new stock transform is usually harmless, and the fatal direction, a
+transform we run being removed, already makes Style Dictionary throw on an
+unknown name. It runs in your build because that is the only place the
+installed Style Dictionary version is knowable: ThroughLine declares no
+dependency on it.
+
+```js
+// Build each platform's transform list from Style Dictionary's STOCK group,
+// replacing only the rem-assuming size transforms and inserting the color-mix
+// computation ahead of the colour transform. A hand-picked list silently drops
+// whatever it forgets; three real defects arose that way, including Compose
+// font sizes rendered in dp instead of sp.
+//
+// That last one is fixed for tokens whose role a DTCG source actually states:
+// classifyTextUnits stamps fontSize, letterSpacing and lineHeight members, and
+// the sp transform gates on the stamp rather than on a $type DTCG never emits.
+// Two limits remain, one Android-only and one affecting both platforms, both
+// measured rather than theoretical — see
+// docs/superpowers/notes/2026-08-28-text-role-inference-e2e.md:
+//
+//   - A scale primitive states no role, so #63 infers one from the reference
+//     graph: a dimension referenced only by fontSize, letterSpacing or
+//     lineHeight members is itself typographic. text.base: "16px" is stamped
+//     because a fontSize references it. A primitive NOTHING references stays
+//     dp on Android — no structural signal exists for it, so it is not
+//     inferred, and tokens:validate-output raises an unreferenced-text-sibling
+//     advisory naming it rather than leaving the gap silent. This is not the
+//     complete list of remaining limits (spec §8 names five more); the one a
+//     consumer is likeliest to hit is mode dependence — the same token can
+//     emit sp in one build and dp in another, because the graph only sees the
+//     files that build includes.
+//   - An em-valued letterSpacing reaches Compose as a real .em TextUnit since
+//     #64, but only where the text role is stamped. A role-less em value is
+//     still filtered out of native output entirely, on both platforms.
+//
+// The third — a unitless ratio emitting as dp — is fixed by #52: no size
+// transform claims a unitless value, so it emits bare on both platforms, and
+// tokens:validate-output reports it as a unitless-dimension advisory.
+//
+// The lists below mirror Style Dictionary's stock groups, and nothing derives
+// them at runtime — what runs stays deliberate and reviewable. But nothing is
+// transcribed either: auditStockGroups checks at registration that every name
+// in the live stock group is either run here or declined in writing, so a
+// stock transform this config has never made a decision about is loud rather
+// than silently dropped.
+//
+// Both groups were verified byte-identical in SD 4.4.0 and 5.5.2. The `ios`
+// group was not — it renamed size/remToPt to size/remToFloat between them, and
+// 5.x added seven transforms overall. The drift this guards against is real;
+// it has simply not landed on the two groups we build from.
+const PLATFORMS = {
+  'ios-swift': {
+    stockGroup: 'ios-swift',
+    transforms: [
+      'attribute/cti',
+      'name/camel',
+      'value/color-mix-to-hex8',
+      'color/UIColorSwift',
+      'content/swift/literal',
+      'asset/swift/literal',
+      'size/unit-aware/swift',
+      'value/swift-string-literal',
+    ],
+    destination: 'Tokens.swift',
+    format: 'ios-swift/enum.swift',
+  },
+  'android-kotlin': {
+    stockGroup: 'compose',
+    transforms: [
+      'attribute/cti',
+      'name/camel',
+      'value/color-mix-to-hex8',
+      'color/composeColor',
+      'size/unit-aware/compose-dp',
+      'size/unit-aware/compose-sp',
+      'size/unit-aware/compose-em',
+      'value/kotlin-string-literal',
+    ],
+    destination: 'Tokens.kt',
+    format: 'compose/object',
+  },
+};
+
+// Stock transforms this config deliberately does NOT run. The reason is the
+// point: an entry here is a decision on the record, where an absence from
+// PLATFORMS is indistinguishable from an oversight.
+//
+// Keyed by transform name alone, with no platform qualifier. That is safe only
+// because every name here is platform-prefixed, so no cross-platform collision
+// is expressible. Declining an unprefixed name — a hypothetical shared
+// "size/px" — would widen silently across both platforms and must convert this
+// to a per-platform map.
+const DECLINED_STOCK_TRANSFORMS = {
+  'size/swift/remToCGFloat': 'rem-assuming — replaced by size/unit-aware/swift',
+  'size/compose/remToDp': 'rem-assuming — replaced by size/unit-aware/compose-dp',
+  'size/compose/remToSp': 'rem-assuming — replaced by size/unit-aware/compose-sp',
+  'size/compose/em': 'rem-assuming — replaced by size/unit-aware/compose-em',
+};
+
+// Report every transform in a platform's live stock group that this config
+// neither runs nor explicitly declined. Pure: it takes Style Dictionary's
+// hooks.transformGroups and returns formatted warning strings, so the wording
+// is what the tests assert and the caller is a bare loop.
+//
+// Warns, never throws. The dangerous direction is an ADDITION we never learned
+// about, which is usually harmless and occasionally important — throwing would
+// break a build over a change the consumer cannot fix. The fatal direction, a
+// transform we run being removed, already makes Style Dictionary throw on an
+// unknown transform name.
+//
+// Order is never compared: our lists are hand-ordered for our own reasons and
+// do not inherit stock order. Removals are never reported: a declined name
+// disappearing is a non-event.
+export function auditStockGroups(transformGroups) {
+  if (typeof transformGroups !== 'object' || transformGroups === null) {
+    return [
+      "throughline: could not read Style Dictionary's stock transform groups " +
+        '(hooks.transformGroups is not an object), so this adapter cannot check ' +
+        'whether its transform lists are still complete.',
+    ];
+  }
+  const warnings = [];
+  for (const [platform, preset] of Object.entries(PLATFORMS)) {
+    const group = preset.stockGroup;
+    if (!group || !Array.isArray(preset.transforms)) {
+      warnings.push(
+        `throughline: PLATFORMS['${platform}'] is incomplete — it needs both ` +
+          'stockGroup and transforms — so its transform list cannot be checked ' +
+          "against Style Dictionary's stock groups. This is a throughline " +
+          'packaging defect — please report it.',
+      );
+      continue;
+    }
+    const stock = transformGroups[group];
+    if (!Array.isArray(stock)) {
+      warnings.push(
+        `throughline: Style Dictionary has no "${group}" transform group, which ` +
+          `PLATFORMS['${platform}'] mirrors. The stock group may have been ` +
+          'renamed or removed. Upgrade @radicool/throughline, or report your ' +
+          'Style Dictionary version.',
+      );
+      continue;
+    }
+    const unaccounted = stock.filter(
+      (name) =>
+        !preset.transforms.includes(name) &&
+        !Object.hasOwn(DECLINED_STOCK_TRANSFORMS, name),
+    );
+    if (unaccounted.length) {
+      const n = unaccounted.length;
+      warnings.push(
+        `throughline: Style Dictionary's "${group}" transform group has ${n} ` +
+          `transform${n === 1 ? '' : 's'} this adapter neither runs nor declined: ` +
+          `${unaccounted.join(', ')}. Native output may be incomplete. Upgrade ` +
+          '@radicool/throughline, or report your Style Dictionary version. ' +
+          `(Maintainer repair: add each to PLATFORMS['${platform}'].transforms, ` +
+          'or to DECLINED_STOCK_TRANSFORMS with a reason.)',
+      );
+    }
+  }
+  return warnings;
+}
+
+// % and em are container- or parent-relative, so there is no build-time native
+// magnitude. Filter on the AUTHORED value, not on $type — a "100%" token may be
+// typed string rather than dimension.
+const WEB_ONLY_UNIT = /^-?[\d.]+(%|em)$/;
+
+// The em magnitude, which magnitude() deliberately does not return: em has no
+// build-time px equivalent, so it is not a native LENGTH. It is a TextUnit.
+const EM_VALUE = /^(-?(?:\d+(?:\.\d+)?|\.\d+))em$/;
+
+export function nativeFilter(token, platform) {
+  const v = String(token.original?.$value ?? token.$value).trim();
+  if (!WEB_ONLY_UNIT.test(v)) return true;
+  // One exception, and it is narrow. Compose has a real .em TextUnit, so an
+  // em letterSpacing DOES have a native form there — unlike %, which has none
+  // anywhere. It survives only where all three hold: the platform is Compose,
+  // the value is em, and the token carries the text role. An em SPACING has no
+  // TextUnit meaning and still drops.
+  //
+  // iOS is deliberately excluded rather than pending. Letter spacing there is
+  // an NSAttributedString kern in points, which needs the font size the token
+  // does not carry, so there is no value Swift could emit that would not be
+  // wrong at some font size.
+  return platform === 'android-kotlin' && EM_VALUE.test(v) && isTextUnit(token);
+}
+
+// A CSS function has no native form. Quoting it would produce a string that
+// compiles and means nothing — the exact failure class this module exists to
+// prevent, and worse than the bare value, which at least fails to compile.
+// Leave it bare so the filter drops it.
+//
+// No \s* before the paren: CSS function notation forbids whitespace between
+// the name and the open paren, and a real font family can legitimately
+// contain one — "Helvetica (Regular)". Requiring the paren immediately after
+// the identifier is what tells that apart from linear-gradient(, calc(,
+// var(, and color-mix(.
+const CSS_FUNCTION = /^[A-Za-z][A-Za-z0-9-]*\(/;
+
+// Did the transforms leave a value with no native form at all?
+//
+// A different question from nativeFilter's, which is about the AUTHORED
+// value. This reads the TRANSFORMED $value. A value that already parses as a
+// literal passes outright. A value that does not is dropped only if it is
+// ALSO shaped like a CSS function call — a linear-gradient, say, which has no
+// native rendering whatsoever. Everything else invalid but not function-shaped
+// stays and fails loudly at compile time: duration ("200ms"), cubicBezier
+// ("0.5,0,1,1"), and, on Kotlin, content and asset, which have no stock
+// quoting transform there. Silently dropping those would hide a forgotten
+// $type behind a shorter output file instead of a build failure.
+//
+// A CSS_CONSTRUCT match is exempt from the drop even though it fails
+// isValidLiteral: calc(...) and var(...) are unrescued but valid identifiers,
+// and an unrescued color-mix(...) variant is a rescue this module's own
+// color-mix transform simply did not match — none of those are "no native
+// form", they are unimplemented rescues. Dropping them here would make
+// no-foreign-syntax in validate-token-output.mjs unreachable, so they are
+// kept and left to fail loudly there instead.
+export function hasNativeForm(token, platform) {
+  const grammar = GRAMMAR[platform];
+  if (!grammar) {
+    throw new Error(`unknown native platform "${platform}" (expected ${Object.keys(GRAMMAR).join(' or ')})`);
+  }
+  const v = String(token.$value).trim();
+  return isValidLiteral(v, grammar) || CSS_CONSTRUCT.test(v) || !CSS_FUNCTION.test(v);
+}
+
+export function nativePlatform({ platform, buildPath, className = 'Tokens', packageName }) {
+  const preset = PLATFORMS[platform];
+  if (!preset) {
+    throw new Error(
+      `unknown native platform "${platform}" (expected ${Object.keys(PLATFORMS).join(' or ')})`,
+    );
+  }
+  if (platform === 'android-kotlin' && !packageName) {
+    throw new Error(
+      'android-kotlin requires a packageName: the compose/object template emits ' +
+        '`package ${packageName ?? ""}`, so omitting it produces a bare "package " ' +
+        'line, which is not valid Kotlin',
+    );
+  }
+  const fileOptions = platform === 'android-kotlin' ? { className, packageName } : { className };
+  return {
+    transforms: [...preset.transforms],
+    // Carried here, not left to the caller: authored() reads the ORIGINAL
+    // $value, so without this preprocessor every aliased dimension still holds
+    // an unresolved {spacing.space.4}, no size transform fires, and the build
+    // emits bare px literals. preprocess is idempotent, so a project that also
+    // declares it at top level is harmless.
+    preprocessors: ['dtcg/resolve-dual-node'],
+    buildPath,
+    options: { outputReferences: false },
+    files: [
+      {
+        destination: preset.destination,
+        format: preset.format,
+        options: fileOptions,
+        filter: (token) => nativeFilter(token, platform) && hasNativeForm(token, platform),
+      },
+    ],
+  };
+}
+```
+
+## 5. Guard the per-mode source list
+
+Style Dictionary deduplicates by dot-path, so one build over both a light and a
+dark definition of the same token keeps whichever file sorts last and drops the
+other mode with no diagnostic. Pass every build's sources through
+`nativeSources`, which returns them, so the check cannot be skipped by
+forgetting it.
+
+```js
+// Guard the source list for ONE mode, and return it so it can only be used
+// through this call.
+//
+// Style Dictionary deduplicates by dot-path, so a build whose sources contain
+// both a light and a dark definition of the same token keeps whichever file
+// sorts last and drops the other mode with no diagnostic. Wrapping the value
+// the build already needs makes the check unskippable: omitting it means
+// deleting a call whose return value is consumed.
+//
+//   source: nativeSources(sourcesForThisMode)
+//
+// An unexpanded glob is the failure that actually lands here, and a raw ENOENT
+// on the literal string "tokens/*.json" reads as a crash rather than a
+// diagnosis. Name the path and what was expected.
+const EXPECTED = 'nativeSources takes explicit file paths for ONE mode — never a glob, never a directory.';
+
+function readTokenFile(file) {
+  let raw;
+  try {
+    raw = readFileSync(file, 'utf8');
+  } catch (err) {
+    throw new Error(`cannot read token source "${file}": ${err.message}\n${EXPECTED}`);
+  }
+  try {
+    return JSON.parse(raw);
+  } catch (err) {
+    throw new Error(`token source "${file}" is not valid JSON: ${err.message}\n${EXPECTED}`);
+  }
+}
+
+export function nativeSources(paths) {
+  const parsed = paths.map((file) => ({ file, dtcg: readTokenFile(file) }));
+  const collisions = findModeCollisions(parsed);
+  if (collisions.length === 0) return paths;
+
+  const shown = collisions
+    .slice(0, 5)
+    .map((c) => `  ${c.path}: ${c.defs.map((d) => d.file).join(' vs ')}`)
+    .join('\n');
+  const more = collisions.length > 5 ? `\n  ...and ${collisions.length - 5} more` : '';
+  throw new Error(
+    `${collisions.length} token path(s) are defined differently across this build's sources.\n` +
+      'Style Dictionary keeps whichever file sorts last, silently dropping a whole mode.\n' +
+      'Build once per mode, passing an explicit source list for that mode only.\n' +
+      `${shown}${more}`,
+  );
+}
+```
+
+## 6. Register with Style Dictionary
+
+One call. Style Dictionary is a parameter, never an import, which is what lets
+this module install into a consumer's `packages/tokens/scripts/lib/`.
+
+```js
+// Register everything with a Style Dictionary instance. SD is a parameter, not
+// an import, so this module stays zero-dependency and installable.
+const authored = (token) => magnitude(token.original?.$value ?? token.$value);
+const isDimension = (token) => token.$type === 'dimension';
+const isFontSize = (token) => token.$type === 'fontSize';
+const hasMagnitude = (token) => authored(token) !== null;
+// A unitless value is a ratio, not a measurement. DTCG 8.2.1 requires a
+// dimension to carry a unit ("still required even if $value.value is 0"), 8.7's
+// `number` is the type for a multiplier, and 9.8 types lineHeight as one — so a
+// unitless dimension is malformed input, and appending dp/sp/CGFloat to it
+// invents a unit the source never stated. Declining it emits the raw value,
+// which is exactly what a correctly typed `number` already produces.
+//
+// Reads the ORIGINAL authored value, like authored(), and must: preprocess has
+// already resolved references by transform time, and a value transform earlier
+// in the chain may have rewritten $value.
+const RATIO = /^-?(?:\d+(?:\.\d+)?|\.\d+)$/;
+const isRatio = (token) => RATIO.test(String(token.original?.$value ?? token.$value).trim());
+// The role preprocess stamped. $type cannot carry it — see classifyTextUnits.
+const isTextUnit = (token) => token.$extensions?.[EXT_NS]?.nativeUnit === 'text';
+const emMagnitude = (token) => {
+  const m = String(token.original?.$value ?? token.$value)
+    .trim()
+    .match(EM_VALUE);
+  return m ? Number(m[1]) : null;
+};
+
+// Quote string-valued tokens no stock transform covers.
+//
+// Style Dictionary quotes by $type: content/swift/literal and
+// asset/swift/literal handle $type content and asset. A $type: fontFamily token
+// matches neither and emits bare — `public static let f = Nunito Sans`, which
+// is not Swift. There is no stock transform for it.
+const QUOTED_TYPES = new Set(['fontFamily', 'string']);
+
+// A DTCG fontFamily may be a list; join it into one native string.
+function stringValue(token) {
+  const v = Array.isArray(token.$value) ? token.$value.join(', ') : token.$value;
+  return typeof v === 'string' ? v : null;
+}
+
+// DTCG permits fontWeight as a keyword ("bold") as well as a number. The
+// keyword form emits as a bare identifier and hits the identical failure;
+// "400" already emits as a valid native integer and must stay untouched.
+function isQuotable(token) {
+  const v = stringValue(token);
+  if (v === null) return false;
+  if (CSS_FUNCTION.test(v)) return false;
+  if (QUOTED_TYPES.has(token.$type)) return true;
+  return token.$type === 'fontWeight' && Number.isNaN(Number(v.trim()));
+}
+
+const escapeCommon = (s) =>
+  s
+    .replace(/\\/g, '\\\\')
+    .replace(/"/g, '\\"')
+    .replace(/\n/g, '\\n')
+    .replace(/\r/g, '\\r')
+    .replace(/\t/g, '\\t');
+
+export function registerNativeTransforms(StyleDictionary) {
+  StyleDictionary.registerPreprocessor({
+    name: 'dtcg/resolve-dual-node',
+    preprocessor: preprocess,
+  });
+
+  StyleDictionary.registerTransform({
+    name: 'value/color-mix-to-hex8',
+    type: 'value',
+    transitive: true,
+    filter: (token) => colorMixToHex8(token.$value) !== null,
+    transform: (token) => colorMixToHex8(token.$value),
+  });
+
+  // Stock size/swift/remToCGFloat filters dimension OR fontSize; match it.
+  StyleDictionary.registerTransform({
+    name: 'size/unit-aware/swift',
+    type: 'value',
+    transitive: true,
+    filter: (token) => (isDimension(token) || isFontSize(token)) && hasMagnitude(token) && !isRatio(token),
+    transform: (token) => `CGFloat(${authored(token).toFixed(2)})`,
+  });
+
+  // sp is what respects the user's font-scale accessibility setting, and
+  // Compose's TextStyle takes TextUnit — not Dp — for fontSize, lineHeight and
+  // letterSpacing, so a Dp there does not even compile at the use site. One .dp
+  // transform for both would silently defeat the first and loudly break the
+  // second. The split is driven by the role classifyTextUnits stamped, plus
+  // Style Dictionary's own $type: fontSize convention for sources that use it.
+  StyleDictionary.registerTransform({
+    name: 'size/unit-aware/compose-dp',
+    type: 'value',
+    transitive: true,
+    filter: (token) => isDimension(token) && !isTextUnit(token) && hasMagnitude(token) && !isRatio(token),
+    transform: (token) => `${authored(token).toFixed(2)}.dp`,
+  });
+
+  StyleDictionary.registerTransform({
+    name: 'size/unit-aware/compose-sp',
+    type: 'value',
+    transitive: true,
+    filter: (token) => (isTextUnit(token) || isFontSize(token)) && hasMagnitude(token) && !isRatio(token),
+    transform: (token) => `${authored(token).toFixed(2)}.sp`,
+  });
+
+  // em is a THIRD text unit, not a variant of sp. Compose's .em is relative to
+  // the font size at the use site, which is what an em letterSpacing means, so
+  // it needs neither a magnitude nor a conversion. dp and sp both decline these
+  // already — magnitude() returns null for em — so nothing contends.
+  //
+  // The parentheses are load-bearing. `-0.03.em` parses as `-(0.03.em)`, which
+  // kotlinc 2.4.10 rejects with "unresolved reference 'unaryMinus'" unless
+  // TextUnit defines that operator. `(-0.03).em` compiles either way, and
+  // negatives are the common case: a tight letterSpacing is negative.
+  StyleDictionary.registerTransform({
+    name: 'size/unit-aware/compose-em',
+    type: 'value',
+    transitive: true,
+    filter: (token) => (isTextUnit(token) || isFontSize(token)) && emMagnitude(token) !== null,
+    transform: (token) => `(${emMagnitude(token).toFixed(2)}).em`,
+  });
+
+  // Two transforms rather than one platform-sniffing transform, because the
+  // escaping genuinely differs: "$foo" is template interpolation in Kotlin, so
+  // a literal $ must be escaped there and must NOT be in Swift, where \$ is not
+  // a valid escape at all.
+  StyleDictionary.registerTransform({
+    name: 'value/swift-string-literal',
+    type: 'value',
+    transitive: true,
+    filter: isQuotable,
+    transform: (token) => `"${escapeCommon(stringValue(token))}"`,
+  });
+
+  StyleDictionary.registerTransform({
+    name: 'value/kotlin-string-literal',
+    type: 'value',
+    transitive: true,
+    filter: isQuotable,
+    transform: (token) => `"${escapeCommon(stringValue(token)).replace(/\$/g, '\\$')}"`,
+  });
+
+  // Last, so every registration side effect has completed before anything is
+  // printed. Fires once per REGISTRATION — typically once per process, not once
+  // per build: the documented usage registers once and then constructs one
+  // StyleDictionary per mode, and the stock groups cannot change between modes.
+  //
+  // The ?. chain is what turns a caller with no hooks into undefined, which
+  // auditStockGroups reports as unreadable rather than silently skipping.
+  for (const warning of auditStockGroups(StyleDictionary?.hooks?.transformGroups)) {
+    console.warn(warning);
+  }
+}
+```
+
+## Verify, always
+
+Configuration this specific is exactly what regresses unnoticed, because every
+failure mode above produces output that compiles. Run `tokens:validate-output`
+against each generated file with the same source list that file's build used,
+and treat it as a gate rather than a spot check:
+
+```
+node scripts/validate-token-output.mjs \
+  --source tokens/color-primitives.json --source tokens/text-primitives.json \
+  --output out/light/Tokens.swift --platform ios-swift --min-match 1
+```
+
+A clean run reports 100% of emitted symbols matched with zero rule failures.
+Anything less means the configuration drifted — so **pass `--min-match 1`**.
+The flag's default is `0.5`, which is a floor against wholly unparseable output
+rather than the gate this doc describes; without it a 60% match rate exits `0`.
+See `${CLAUDE_PLUGIN_ROOT}/scripts/README.md`.
+
+"Matched" means an emitted symbol's name resolved to a source token. Numeric
+magnitudes are additionally compared; colour and string values are matched by
+name only, and no rule checks that the output compiles.