@3fn/core 14.0.0 → 15.0.0

package/dist/color/OklchValidator.d.ts

@@ -3,7 +3,7 @@
  *
  * Enforces:
  * - Lightness monotonicity (100→500 must decrease)
- * - Minimum step distance (≥0.08 between adjacent steps)
+ * - Minimum step distance between adjacent steps (per family class — see below)
  * - sRGB gamut compliance per token
  * - P3 gamut check (warning, not error)
  * - Chroma monotonicity for steps 300→500 (equal or decreasing)
@@ -11,6 +11,21 @@
  * - Neutral chroma ceiling (C ≤ 0.035)
  * - Neutral partition buffer gaps
  *
+ * **Where this is enforced**: the standing token test suites, which the PR gate runs —
+ * `src/tokens/__tests__/chromatic-channels.test.ts` (all 7 chromatic families through
+ * `validateFamily`) and `src/tokens/__tests__/neutral-partition.test.ts` (white/gray/black
+ * partition, chroma ceilings, and lightness scales). A color-family channel edit that
+ * violates a constraint fails CI. This validator is deliberately NOT wired into
+ * `npm run build` / `build:validate`: a consumer building from source should not have
+ * their build fail over the ecosystem's own color math — authorship errors belong in the
+ * authoring repo's test lane.
+ *
+ * **Minimum step distance is family-class-scoped.** 0.08 is calibrated for the chromatic
+ * families, whose five steps span a wide lightness range. The neutral bands are narrower
+ * by construction (white spans 1.00→0.80, black 0.28→0.00), so applying the chromatic
+ * threshold to them would report a violation where the scale is correct. Each class
+ * carries its own floor; see `MIN_STEP_DISTANCE`.
+ *
  * @see Spec 112 R1 AC6, R2 AC4, R8 AC2-3
  */
 export interface ValidationResult {
@@ -23,12 +38,37 @@ export interface ColorFamily {
     hue: number;
     lightness: number[];
     chroma: number[];
+    /** Family class for lightness-step calibration. Defaults to 'chromatic'. */
+    familyClass?: ColorFamilyClass;
 }
+/**
+ * Family classes for lightness-scale validation. Chromatic families share one set of
+ * constraints; each neutral band has its own, because the bands are narrow by design.
+ */
+export type ColorFamilyClass = 'chromatic' | 'white' | 'gray' | 'black';
+/**
+ * Minimum lightness distance between adjacent steps, per family class.
+ *
+ * - chromatic (0.08): five steps across a wide lightness range
+ * - white (0.05): band spans 1.00 → 0.80, so 0.05 per step
+ * - gray (0.08): band spans 0.72 → 0.32, so 0.10 per step — the chromatic floor holds
+ * - black (0.07): band spans 0.28 → 0.00, so 0.07 per step
+ *
+ * These are floors, not targets: a family may exceed its floor freely.
+ */
+export declare const MIN_STEP_DISTANCE: Record<ColorFamilyClass, number>;
 export declare class OklchValidator {
     /** Validate a complete color family against all constraints. */
     validateFamily(family: ColorFamily): ValidationResult;
-    /** Validate lightness scale: must be monotonically decreasing with min step ≥0.08. */
-    validateLightnessScale(steps: number[], familyName?: string): ValidationResult;
+    /**
+     * Validate a lightness scale: monotonically decreasing, with adjacent steps at least
+     * the family class's minimum distance apart.
+     *
+     * `familyClass` defaults to `'chromatic'` — the calibration this method was written
+     * against. Neutral bands must pass their own class, or a correct narrow band reports
+     * a false violation.
+     */
+    validateLightnessScale(steps: number[], familyName?: string, familyClass?: ColorFamilyClass): ValidationResult;
     /** Validate chroma scale: steps 300→500 must be equal or decreasing (darker = less chroma). */
     validateChromaScale(steps: number[], familyName?: string): ValidationResult;
     /** Check sRGB gamut compliance. P3-only values get a warning. */

package/dist/color/OklchValidator.js

@@ -4,7 +4,7 @@
  *
  * Enforces:
  * - Lightness monotonicity (100→500 must decrease)
- * - Minimum step distance (≥0.08 between adjacent steps)
+ * - Minimum step distance between adjacent steps (per family class — see below)
  * - sRGB gamut compliance per token
  * - P3 gamut check (warning, not error)
  * - Chroma monotonicity for steps 300→500 (equal or decreasing)
@@ -12,19 +12,49 @@
  * - Neutral chroma ceiling (C ≤ 0.035)
  * - Neutral partition buffer gaps
  *
+ * **Where this is enforced**: the standing token test suites, which the PR gate runs —
+ * `src/tokens/__tests__/chromatic-channels.test.ts` (all 7 chromatic families through
+ * `validateFamily`) and `src/tokens/__tests__/neutral-partition.test.ts` (white/gray/black
+ * partition, chroma ceilings, and lightness scales). A color-family channel edit that
+ * violates a constraint fails CI. This validator is deliberately NOT wired into
+ * `npm run build` / `build:validate`: a consumer building from source should not have
+ * their build fail over the ecosystem's own color math — authorship errors belong in the
+ * authoring repo's test lane.
+ *
+ * **Minimum step distance is family-class-scoped.** 0.08 is calibrated for the chromatic
+ * families, whose five steps span a wide lightness range. The neutral bands are narrower
+ * by construction (white spans 1.00→0.80, black 0.28→0.00), so applying the chromatic
+ * threshold to them would report a violation where the scale is correct. Each class
+ * carries its own floor; see `MIN_STEP_DISTANCE`.
+ *
  * @see Spec 112 R1 AC6, R2 AC4, R8 AC2-3
  */
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.OklchValidator = void 0;
+exports.OklchValidator = exports.MIN_STEP_DISTANCE = void 0;
 const OklchConverter_1 = require("./OklchConverter");
-const MIN_STEP_DISTANCE = 0.08;
+/**
+ * Minimum lightness distance between adjacent steps, per family class.
+ *
+ * - chromatic (0.08): five steps across a wide lightness range
+ * - white (0.05): band spans 1.00 → 0.80, so 0.05 per step
+ * - gray (0.08): band spans 0.72 → 0.32, so 0.10 per step — the chromatic floor holds
+ * - black (0.07): band spans 0.28 → 0.00, so 0.07 per step
+ *
+ * These are floors, not targets: a family may exceed its floor freely.
+ */
+exports.MIN_STEP_DISTANCE = {
+    chromatic: 0.08,
+    white: 0.05,
+    gray: 0.08,
+    black: 0.07,
+};
 const NEUTRAL_CHROMA_CEILING = 0.035;
 class OklchValidator {
     /** Validate a complete color family against all constraints. */
     validateFamily(family) {
         const errors = [];
         const warnings = [];
-        const lResult = this.validateLightnessScale(family.lightness, family.name);
+        const lResult = this.validateLightnessScale(family.lightness, family.name, family.familyClass ?? 'chromatic');
         errors.push(...lResult.errors);
         warnings.push(...lResult.warnings);
         const cResult = this.validateChromaScale(family.chroma, family.name);
@@ -41,18 +71,26 @@ class OklchValidator {
         }
         return { valid: errors.length === 0, errors, warnings };
     }
-    /** Validate lightness scale: must be monotonically decreasing with min step ≥0.08. */
-    validateLightnessScale(steps, familyName = '') {
+    /**
+     * Validate a lightness scale: monotonically decreasing, with adjacent steps at least
+     * the family class's minimum distance apart.
+     *
+     * `familyClass` defaults to `'chromatic'` — the calibration this method was written
+     * against. Neutral bands must pass their own class, or a correct narrow band reports
+     * a false violation.
+     */
+    validateLightnessScale(steps, familyName = '', familyClass = 'chromatic') {
         const errors = [];
         const warnings = [];
         const prefix = familyName ? `${familyName}: ` : '';
+        const minStep = exports.MIN_STEP_DISTANCE[familyClass];
         for (let i = 1; i < steps.length; i++) {
             if (steps[i] >= steps[i - 1]) {
                 errors.push(`${prefix}Lightness not monotonically decreasing: step ${(i) * 100}(${steps[i - 1]}) → step ${(i + 1) * 100}(${steps[i]})`);
             }
             const distance = steps[i - 1] - steps[i];
-            if (distance > 0 && distance < MIN_STEP_DISTANCE - 1e-10) {
-                errors.push(`${prefix}Lightness step distance ${distance.toFixed(3)} < ${MIN_STEP_DISTANCE} between steps ${i * 100} and ${(i + 1) * 100}`);
+            if (distance > 0 && distance < minStep - 1e-10) {
+                errors.push(`${prefix}Lightness step distance ${distance.toFixed(3)} < ${minStep} (${familyClass} minimum) between steps ${i * 100} and ${(i + 1) * 100}`);
             }
         }
         return { valid: errors.length === 0, errors, warnings };

package/dist/components/core/Avatar-Base/avatar.tokens.d.ts

@@ -34,6 +34,15 @@
  * - xs: calc(icon.size050 × 0.75) = 12px
  * - xxl: calc(icon.size050 × 4) = 64px
  *
+ * TOKEN FAMILY: all dimensional Avatar tokens (container `size.*` AND icon
+ * `icon.size.*` gap fillers) are registered by the single sizing-family call
+ * `AvatarSizingTokens` below. The `icon.size.*` pair previously lived in a
+ * separate `AvatarTokens` call stamped `family: 'spacing'` — a mislabel, since
+ * both are dimensional sizing values. `AvatarTokens` is removed; consumers use
+ * `AvatarSizingTokens` or the `getAvatarIconSize()` / `getAvatarSize()` accessors.
+ * Generated platform output is unaffected: both calls declare `component: 'Avatar'`,
+ * so all tokens still land in one `AvatarTokens` Swift enum / Kotlin object.
+ *
  * COLOR TOKENS (Spec 058):
  * Avatar color tokens are defined in this file following the Rosetta System architecture
  * which mandates component tokens live at src/components/[ComponentName]/tokens.ts.
@@ -52,13 +61,24 @@
  * @see .kiro/specs/058-component-token-architecture-cleanup for color token migration
  */
 /**
- * Avatar sizing tokens — container dimensions for each size variant.
+ * Avatar sizing tokens — container dimensions and icon dimensions for each size variant.
  *
  * Previously in a separate file (avatar-sizing.tokens.ts). Inlined to prevent
  * architectural anomaly (no other component splits tokens across files) and
  * simplify the package surface for sync.
  *
+ * ONE CALL PER FAMILY. Every token registered by a single defineComponentTokens()
+ * call is stamped with that call's `family`, and the family drives platform output
+ * (Swift type, Kotlin `.dp` suffix, primitive class name). The `icon.size.*` gap
+ * fillers below are dimensional sizing values, so they live in this sizing-family
+ * call — they were previously mis-stamped `family: 'spacing'` in a separate
+ * `AvatarTokens` call, the same latent mislabel class fixed for Button-Icon.
+ * Do NOT spread/merge this result with another call's result — the rich metadata
+ * rides on a non-enumerable brand (see src/build/tokens/defineComponentTokens.ts,
+ * TOKEN_CONTRACT_BRAND) that a spread would silently drop.
+ *
  * @see .kiro/specs/092-sizing-token-family/design.md
+ * @see src/components/core/Button-Icon/buttonIcon.tokens.ts for the two-call pattern
  */
 export declare const AvatarSizingTokens: import("../../../build/tokens").ComponentTokenValues<{
     'size.xs': {
@@ -85,31 +105,6 @@ export declare const AvatarSizingTokens: import("../../../build/tokens").Compone
         reference: import("../../../types").PrimitiveToken;
         reasoning: string;
     };
-}>;
-/**
- * Avatar component tokens defined using the hybrid authoring API.
- *
- * Each token either references a primitive spacing token or uses a family-conformant
- * derivation, and includes reasoning explaining why the token exists.
- *
- * NOTE: Web platform uses CSS calc() with icon tokens for sizing (see Avatar.styles.css).
- * These component tokens are primarily used for iOS/Android platforms and documentation.
- *
- * Size token values:
- * - size.xs: 24px (3 × base, references size300)
- * - size.sm: 32px (4 × base, references size400)
- * - size.md: 40px (5 × base, references size500)
- * - size.lg: 48px (6 × base, references size600)
- * - size.xl: 80px (10 × base, derivation)
- * - size.xxl: 128px (16 × base, derivation)
- *
- * Icon size token values (gap fillers - web uses calc() instead):
- * - icon.size.xs: 12px (1.5 × base, derivation) - web uses calc(icon.size050 × 0.75)
- * - icon.size.xxl: 64px (8 × base, derivation) - web uses calc(icon.size050 × 4)
- *
- * @see Requirements 2.1-2.6, 3.1, 3.6 in .kiro/specs/042-avatar-component/requirements.md
- */
-export declare const AvatarTokens: import("../../../build/tokens").ComponentTokenValues<{
     'icon.size.xs': {
         value: number;
         reasoning: string;

package/dist/components/core/Avatar-Base/avatar.tokens.js

@@ -35,6 +35,15 @@
  * - xs: calc(icon.size050 × 0.75) = 12px
  * - xxl: calc(icon.size050 × 4) = 64px
  *
+ * TOKEN FAMILY: all dimensional Avatar tokens (container `size.*` AND icon
+ * `icon.size.*` gap fillers) are registered by the single sizing-family call
+ * `AvatarSizingTokens` below. The `icon.size.*` pair previously lived in a
+ * separate `AvatarTokens` call stamped `family: 'spacing'` — a mislabel, since
+ * both are dimensional sizing values. `AvatarTokens` is removed; consumers use
+ * `AvatarSizingTokens` or the `getAvatarIconSize()` / `getAvatarSize()` accessors.
+ * Generated platform output is unaffected: both calls declare `component: 'Avatar'`,
+ * so all tokens still land in one `AvatarTokens` Swift enum / Kotlin object.
+ *
  * COLOR TOKENS (Spec 058):
  * Avatar color tokens are defined in this file following the Rosetta System architecture
  * which mandates component tokens live at src/components/[ComponentName]/tokens.ts.
@@ -53,7 +62,7 @@
  * @see .kiro/specs/058-component-token-architecture-cleanup for color token migration
  */
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.AvatarIconSizeTokenReferences = exports.AvatarSizeTokenReferences = exports.AvatarColorTokens = exports.AvatarTokens = exports.AvatarSizingTokens = void 0;
+exports.AvatarIconSizeTokenReferences = exports.AvatarSizeTokenReferences = exports.AvatarColorTokens = exports.AvatarSizingTokens = void 0;
 exports.getAvatarColorToken = getAvatarColorToken;
 exports.getAvatarSize = getAvatarSize;
 exports.getAvatarIconSize = getAvatarIconSize;
@@ -62,13 +71,24 @@ exports.getAvatarIconSizeTokenReference = getAvatarIconSizeTokenReference;
 const tokens_1 = require("../../../build/tokens");
 const SizingTokens_1 = require("../../../tokens/SizingTokens");
 /**
- * Avatar sizing tokens — container dimensions for each size variant.
+ * Avatar sizing tokens — container dimensions and icon dimensions for each size variant.
  *
  * Previously in a separate file (avatar-sizing.tokens.ts). Inlined to prevent
  * architectural anomaly (no other component splits tokens across files) and
  * simplify the package surface for sync.
  *
+ * ONE CALL PER FAMILY. Every token registered by a single defineComponentTokens()
+ * call is stamped with that call's `family`, and the family drives platform output
+ * (Swift type, Kotlin `.dp` suffix, primitive class name). The `icon.size.*` gap
+ * fillers below are dimensional sizing values, so they live in this sizing-family
+ * call — they were previously mis-stamped `family: 'spacing'` in a separate
+ * `AvatarTokens` call, the same latent mislabel class fixed for Button-Icon.
+ * Do NOT spread/merge this result with another call's result — the rich metadata
+ * rides on a non-enumerable brand (see src/build/tokens/defineComponentTokens.ts,
+ * TOKEN_CONTRACT_BRAND) that a spread would silently drop.
+ *
  * @see .kiro/specs/092-sizing-token-family/design.md
+ * @see src/components/core/Button-Icon/buttonIcon.tokens.ts for the two-call pattern
  */
 exports.AvatarSizingTokens = (0, tokens_1.defineComponentTokens)({
     component: 'Avatar',
@@ -98,37 +118,14 @@ exports.AvatarSizingTokens = (0, tokens_1.defineComponentTokens)({
             reference: SizingTokens_1.sizingTokens.size1600,
             reasoning: 'Extra extra large avatar (128px). Full profile view, onboarding.',
         },
-    },
-});
-/**
- * Avatar component tokens defined using the hybrid authoring API.
- *
- * Each token either references a primitive spacing token or uses a family-conformant
- * derivation, and includes reasoning explaining why the token exists.
- *
- * NOTE: Web platform uses CSS calc() with icon tokens for sizing (see Avatar.styles.css).
- * These component tokens are primarily used for iOS/Android platforms and documentation.
- *
- * Size token values:
- * - size.xs: 24px (3 × base, references size300)
- * - size.sm: 32px (4 × base, references size400)
- * - size.md: 40px (5 × base, references size500)
- * - size.lg: 48px (6 × base, references size600)
- * - size.xl: 80px (10 × base, derivation)
- * - size.xxl: 128px (16 × base, derivation)
- *
- * Icon size token values (gap fillers - web uses calc() instead):
- * - icon.size.xs: 12px (1.5 × base, derivation) - web uses calc(icon.size050 × 0.75)
- * - icon.size.xxl: 64px (8 × base, derivation) - web uses calc(icon.size050 × 4)
- *
- * @see Requirements 2.1-2.6, 3.1, 3.6 in .kiro/specs/042-avatar-component/requirements.md
- */
-exports.AvatarTokens = (0, tokens_1.defineComponentTokens)({
-    component: 'Avatar',
-    family: 'spacing',
-    tokens: {
-        // Icon size tokens (gap fillers for sizes without existing icon tokens)
-        // These fill gaps where no standard icon token exists at the required 50% ratio
+        // Icon size tokens (gap fillers for sizes without an existing icon token).
+        // Kept on the VALUE path deliberately: sizing primitives exist at both values
+        // (size150 = 12, size800 = 64), but the reference path currently emits a
+        // fabricated `SizingTokens.<name>` class on iOS/Android that no generated or
+        // hand-written platform file defines. Switching these to `reference:` would
+        // trade compiling output (`12.dp`) for non-compiling output and break
+        // Avatar.android.kt's `val iconSizeXs: Dp = GeneratedAvatarTokens.iconSizeXs`.
+        // Revisit once TokenFileGenerator.getFamilyClassName emits a real platform type.
         'icon.size.xs': {
             value: SizingTokens_1.SIZING_BASE_VALUE * 1.5,
             reasoning: 'Icon size for xs avatar (12px = 1.5× base) maintains 50% ratio (12/24). No existing icon token at this size, so component token fills the gap.',
@@ -254,7 +251,7 @@ function getAvatarSize(variant) {
  * @see Requirements 3.1, 3.6 in .kiro/specs/042-avatar-component/requirements.md
  */
 function getAvatarIconSize(variant) {
-    return exports.AvatarTokens[`icon.size.${variant}`];
+    return exports.AvatarSizingTokens[`icon.size.${variant}`];
 }
 /**
  * Semantic token references for Avatar size values

package/dist/components/core/Avatar-Base/index.d.ts

@@ -6,7 +6,7 @@
  */
 export type { AvatarProps, AvatarType, AvatarSize } from './types';
 export { AVATAR_DEFAULTS } from './types';
-export { AvatarTokens, getAvatarSize, getAvatarIconSize, getAvatarSizeTokenReference, getAvatarIconSizeTokenReference, AvatarSizeTokenReferences, AvatarIconSizeTokenReferences, } from './avatar.tokens';
+export { AvatarSizingTokens, getAvatarSize, getAvatarIconSize, getAvatarSizeTokenReference, getAvatarIconSizeTokenReference, AvatarSizeTokenReferences, AvatarIconSizeTokenReferences, } from './avatar.tokens';
 export type { AvatarSizeVariant, AvatarIconSizeVariant } from './avatar.tokens';
 export { AvatarBaseElement } from './platforms/web/Avatar.web';
 //# sourceMappingURL=index.d.ts.map

package/dist/components/core/Avatar-Base/index.js

@@ -6,12 +6,12 @@
  * @see .kiro/specs/042-avatar-component/requirements.md for requirements
  */
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.AvatarBaseElement = exports.AvatarIconSizeTokenReferences = exports.AvatarSizeTokenReferences = exports.getAvatarIconSizeTokenReference = exports.getAvatarSizeTokenReference = exports.getAvatarIconSize = exports.getAvatarSize = exports.AvatarTokens = exports.AVATAR_DEFAULTS = void 0;
+exports.AvatarBaseElement = exports.AvatarIconSizeTokenReferences = exports.AvatarSizeTokenReferences = exports.getAvatarIconSizeTokenReference = exports.getAvatarSizeTokenReference = exports.getAvatarIconSize = exports.getAvatarSize = exports.AvatarSizingTokens = exports.AVATAR_DEFAULTS = void 0;
 var types_1 = require("./types");
 Object.defineProperty(exports, "AVATAR_DEFAULTS", { enumerable: true, get: function () { return types_1.AVATAR_DEFAULTS; } });
 // Token exports
 var avatar_tokens_1 = require("./avatar.tokens");
-Object.defineProperty(exports, "AvatarTokens", { enumerable: true, get: function () { return avatar_tokens_1.AvatarTokens; } });
+Object.defineProperty(exports, "AvatarSizingTokens", { enumerable: true, get: function () { return avatar_tokens_1.AvatarSizingTokens; } });
 Object.defineProperty(exports, "getAvatarSize", { enumerable: true, get: function () { return avatar_tokens_1.getAvatarSize; } });
 Object.defineProperty(exports, "getAvatarIconSize", { enumerable: true, get: function () { return avatar_tokens_1.getAvatarIconSize; } });
 Object.defineProperty(exports, "getAvatarSizeTokenReference", { enumerable: true, get: function () { return avatar_tokens_1.getAvatarSizeTokenReference; } });

package/dist/components/core/Button-CTA/Button-CTA.refs.d.ts

@@ -0,0 +1,83 @@
+/**
+ * Button-CTA Component Tokens
+ *
+ * Component-specific tokens for Button-CTA that don't fit into the general
+ * semantic token system. These tokens are specific to button sizing and layout.
+ *
+ * Token Naming Pattern: buttonCTA.[property].[variant]
+ *
+ * Stemma System Naming: [Family]-[Type] = Button-CTA
+ * Component Type: Standalone (no behavioral variants)
+ *
+ * Related Requirements:
+ * - Requirement 6.1-6.3: Minimum width requirements for button sizes
+ * - Design Decision H3: Component-specific tokens with semantic naming
+ */
+/**
+ * Minimum Width Tokens
+ *
+ * These tokens define the minimum width for each button size variant.
+ * Values are chosen to ensure buttons have adequate touch targets and
+ * visual presence while maintaining compositional architecture principles.
+ *
+ * Design Rationale (from H3):
+ * - Component-specific tokens provide clarity for button sizing
+ * - Semantic naming (small/medium/large) balances component needs with system conventions
+ * - Compositional architecture maintained through mathematical relationships
+ *
+ * Token linkage (corrected 2026-09-19 per the token-doc accuracy pass, F8 —
+ * see .kiro/issues/2026-09-19-token-source-accuracy-followups.md): these values
+ * are NOT independent literals — they equal the `sizing` primitive family's
+ * size700/size900/size1000 tokens exactly, and Token-Family-Sizing.md § "Component
+ * Consumers" already documented Button-CTA as a consumer of those three tokens.
+ * The values below now reference those primitives directly instead of restating
+ * their values, per the component-token construction rule (component tokens
+ * must reference an existing primitive or conform to its value system, never
+ * restate an arbitrary number). This is a linkage fix only — the rendered
+ * values (56 / 72 / 80) are unchanged.
+ *
+ * Values:
+ * - Small: 56px (7 × 8px baseline grid, references size700)
+ * - Medium: 72px (9 × 8px baseline grid, references size900)
+ * - Large: 80px (10 × 8px baseline grid, references size1000)
+ */
+export declare const ButtonCTATokens: {
+    /**
+     * Minimum width for small buttons
+     *
+     * Usage: Small buttons in compact layouts, secondary actions
+     * Value: 56px (7 × 8px baseline grid) — references sizingTokens.size700
+     * Platforms: Web, iOS, Android
+     */
+    readonly minWidth: {
+        readonly small: number;
+        /**
+         * Minimum width for medium buttons
+         *
+         * Usage: Standard buttons, primary actions
+         * Value: 72px (9 × 8px baseline grid) — references sizingTokens.size900
+         * Platforms: Web, iOS, Android
+         */
+        readonly medium: number;
+        /**
+         * Minimum width for large buttons
+         *
+         * Usage: Prominent buttons, hero actions
+         * Value: 80px (10 × 8px baseline grid) — references sizingTokens.size1000
+         * Platforms: Web, iOS, Android
+         */
+        readonly large: number;
+    };
+};
+/**
+ * Type definitions for Button-CTA tokens
+ */
+export type ButtonCTAMinWidthVariant = keyof typeof ButtonCTATokens.minWidth;
+/**
+ * Helper function to get minWidth token value
+ *
+ * @param variant - The button size variant (small, medium, large)
+ * @returns The minimum width value in pixels
+ */
+export declare function getButtonCTAMinWidth(variant: ButtonCTAMinWidthVariant): number;
+//# sourceMappingURL=Button-CTA.refs.d.ts.map

package/dist/components/core/Button-CTA/Button-CTA.refs.js

@@ -0,0 +1,86 @@
+"use strict";
+/**
+ * Button-CTA Component Tokens
+ *
+ * Component-specific tokens for Button-CTA that don't fit into the general
+ * semantic token system. These tokens are specific to button sizing and layout.
+ *
+ * Token Naming Pattern: buttonCTA.[property].[variant]
+ *
+ * Stemma System Naming: [Family]-[Type] = Button-CTA
+ * Component Type: Standalone (no behavioral variants)
+ *
+ * Related Requirements:
+ * - Requirement 6.1-6.3: Minimum width requirements for button sizes
+ * - Design Decision H3: Component-specific tokens with semantic naming
+ */
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.ButtonCTATokens = void 0;
+exports.getButtonCTAMinWidth = getButtonCTAMinWidth;
+const SizingTokens_1 = require("../../../tokens/SizingTokens");
+/**
+ * Minimum Width Tokens
+ *
+ * These tokens define the minimum width for each button size variant.
+ * Values are chosen to ensure buttons have adequate touch targets and
+ * visual presence while maintaining compositional architecture principles.
+ *
+ * Design Rationale (from H3):
+ * - Component-specific tokens provide clarity for button sizing
+ * - Semantic naming (small/medium/large) balances component needs with system conventions
+ * - Compositional architecture maintained through mathematical relationships
+ *
+ * Token linkage (corrected 2026-09-19 per the token-doc accuracy pass, F8 —
+ * see .kiro/issues/2026-09-19-token-source-accuracy-followups.md): these values
+ * are NOT independent literals — they equal the `sizing` primitive family's
+ * size700/size900/size1000 tokens exactly, and Token-Family-Sizing.md § "Component
+ * Consumers" already documented Button-CTA as a consumer of those three tokens.
+ * The values below now reference those primitives directly instead of restating
+ * their values, per the component-token construction rule (component tokens
+ * must reference an existing primitive or conform to its value system, never
+ * restate an arbitrary number). This is a linkage fix only — the rendered
+ * values (56 / 72 / 80) are unchanged.
+ *
+ * Values:
+ * - Small: 56px (7 × 8px baseline grid, references size700)
+ * - Medium: 72px (9 × 8px baseline grid, references size900)
+ * - Large: 80px (10 × 8px baseline grid, references size1000)
+ */
+exports.ButtonCTATokens = {
+    /**
+     * Minimum width for small buttons
+     *
+     * Usage: Small buttons in compact layouts, secondary actions
+     * Value: 56px (7 × 8px baseline grid) — references sizingTokens.size700
+     * Platforms: Web, iOS, Android
+     */
+    minWidth: {
+        small: SizingTokens_1.sizingTokens.size700.baseValue,
+        /**
+         * Minimum width for medium buttons
+         *
+         * Usage: Standard buttons, primary actions
+         * Value: 72px (9 × 8px baseline grid) — references sizingTokens.size900
+         * Platforms: Web, iOS, Android
+         */
+        medium: SizingTokens_1.sizingTokens.size900.baseValue,
+        /**
+         * Minimum width for large buttons
+         *
+         * Usage: Prominent buttons, hero actions
+         * Value: 80px (10 × 8px baseline grid) — references sizingTokens.size1000
+         * Platforms: Web, iOS, Android
+         */
+        large: SizingTokens_1.sizingTokens.size1000.baseValue,
+    },
+};
+/**
+ * Helper function to get minWidth token value
+ *
+ * @param variant - The button size variant (small, medium, large)
+ * @returns The minimum width value in pixels
+ */
+function getButtonCTAMinWidth(variant) {
+    return exports.ButtonCTATokens.minWidth[variant];
+}
+//# sourceMappingURL=Button-CTA.refs.js.map

package/dist/components/core/Button-CTA/Button-CTA.tokens.d.ts

@@ -23,40 +23,50 @@
  * Design Rationale (from H3):
  * - Component-specific tokens provide clarity for button sizing
  * - Semantic naming (small/medium/large) balances component needs with system conventions
- * - Values don't need to align with existing primitive tokens (space700, space900, space1000)
  * - Compositional architecture maintained through mathematical relationships
  *
+ * Token linkage (corrected 2026-09-19 per the token-doc accuracy pass, F8 —
+ * see .kiro/issues/2026-09-19-token-source-accuracy-followups.md): these values
+ * are NOT independent literals — they equal the `sizing` primitive family's
+ * size700/size900/size1000 tokens exactly, and Token-Family-Sizing.md § "Component
+ * Consumers" already documented Button-CTA as a consumer of those three tokens.
+ * The values below now reference those primitives directly instead of restating
+ * their values, per the component-token construction rule (component tokens
+ * must reference an existing primitive or conform to its value system, never
+ * restate an arbitrary number). This is a linkage fix only — the rendered
+ * values (56 / 72 / 80) are unchanged.
+ *
  * Values:
- * - Small: 56px (7 × 8px baseline grid)
- * - Medium: 72px (9 × 8px baseline grid)
- * - Large: 80px (10 × 8px baseline grid, aligns with space1000)
+ * - Small: 56px (7 × 8px baseline grid, references size700)
+ * - Medium: 72px (9 × 8px baseline grid, references size900)
+ * - Large: 80px (10 × 8px baseline grid, references size1000)
  */
 export declare const ButtonCTATokens: {
     /**
      * Minimum width for small buttons
      *
      * Usage: Small buttons in compact layouts, secondary actions
-     * Value: 56px (7 × 8px baseline grid)
+     * Value: 56px (7 × 8px baseline grid) — references sizingTokens.size700
      * Platforms: Web, iOS, Android
      */
     readonly minWidth: {
-        readonly small: 56;
+        readonly small: number;
         /**
          * Minimum width for medium buttons
          *
          * Usage: Standard buttons, primary actions
-         * Value: 72px (9 × 8px baseline grid)
+         * Value: 72px (9 × 8px baseline grid) — references sizingTokens.size900
          * Platforms: Web, iOS, Android
          */
-        readonly medium: 72;
+        readonly medium: number;
         /**
          * Minimum width for large buttons
          *
          * Usage: Prominent buttons, hero actions
-         * Value: 80px (10 × 8px baseline grid, aligns with space1000)
+         * Value: 80px (10 × 8px baseline grid) — references sizingTokens.size1000
          * Platforms: Web, iOS, Android
          */
-        readonly large: 80;
+        readonly large: number;
     };
 };
 /**