@3fn/core 14.0.0 → 14.1.0

package/.kiro/steering/Civitas-System-Overview.md

@@ -120,15 +120,6 @@ The three systems form a complete design system ecosystem: Rosetta defines the v
 
 ---
 
-## MCP Query
-
-For the full document:
-```
-get_document_full({ path: "civitas-system-overview" })
-```
-
-For specific sections:
-```
-get_section({ path: "civitas-system-overview", heading: "The Three-Layer Boundary" })
-get_section({ path: "civitas-system-overview", heading: "Relationship to Rosetta and Stemma" })
-```
+## Document Access
+
+This is an identity doc (Spec 119) — never MCP-served, always loaded in full into every agent's context. No query is needed to access it. If you need to point to a specific part of it, use an in-document § reference (e.g., this doc's § "The Three-Layer Boundary" or § "Relationship to Rosetta and Stemma"), not an MCP call.

package/.kiro/steering/Spec-Feedback-Protocol.md

@@ -228,15 +228,6 @@ The feedback document uses this structure:
 
 ---
 
-## MCP Query
+## Document Access
 
-For the full protocol:
-```
-get_document_full({ path: "spec-feedback-protocol" })
-```
-
-For specific sections:
-```
-get_section({ path: "spec-feedback-protocol", heading: "Stamp Format" })
-get_section({ path: "spec-feedback-protocol", heading: "Mandatory @ Mention Scanning" })
-```
+This is an identity doc (Spec 119) — never MCP-served, always loaded in full into every agent's context. No query is needed to access it. If you need to point to a specific part of it, use an in-document § reference (e.g., this doc's § "Stamp Format" or § "Mandatory @ Mention Scanning"), not an MCP call.

package/.kiro/steering/Task-Completion-Protocol.md

@@ -8,7 +8,7 @@ description: Operational law for ending a task — when to write completion docs
 # Task Completion Protocol
 
 **Date**: 2026-06-29
-**Last Reviewed**: 2026-07-14
+**Last Reviewed**: 2026-08-12
 **Purpose**: The end-of-task operational sequence (completion docs, tiers, parent vs. subtask, stop-and-wait, PR flow) — operational law, always loaded
 **Organization**: process-standard
 **Scope**: cross-project
@@ -37,7 +37,7 @@ get_section({ path: "completion-documentation-guide", heading: "Documentation Ti
 1. [ ] Run targeted tests relevant to the change (not the full suite)
 2. [ ] Create completion doc: `.kiro/specs/[spec]/completion/task-N-M-completion.md`
 3. [ ] Mark subtask complete (use the `taskStatus` tool)
-4. [ ] **Commit is optional and judgment-based — not mechanical per subtask.** When you commit, **commit AND push the unit branch** (`task/<spec>-<unit-slug>` or `task/<spec>-<N>-<slug>`, created at the first subtask — `git switch -c` or the completion tooling's equivalent); the two stay coupled because the push is the off-machine backup guarantee (a local-only commit is not backed up). Commit-and-push at a **checkpoint** (delicate or potentially-breaking work — a restore point worth having), when **backup-worthy work has accumulated** (a unit branch is longer-lived than a single task, so more unpushed work sits at risk between merges — push before the pile grows), or at a **session/handoff boundary**. Do NOT commit mechanically after every trivial subtask — the unit squash-merges anyway, so subtask granularity is cosmetic to `main`'s history. No PR opens and no required checks fire until unit completion. Subtasks do NOT open PRs. Never commit to `main`.
+4. [ ] **Commit is optional and judgment-based — not mechanical per subtask.** When you commit, **commit AND push the unit branch** (`task/<spec>-<unit-slug>` or `task/<spec>-<N>-<slug>`, created at the first subtask — `git switch -c` or the completion tooling's equivalent); the two stay coupled because the push is the off-machine backup guarantee (a local-only commit is not backed up). Commit-and-push at a **checkpoint** (delicate or potentially-breaking work — a restore point worth having), when **backup-worthy work has accumulated** (a unit branch is longer-lived than a single task, so more unpushed work sits at risk between merges — push before the pile grows), or at a **session/handoff boundary**. Do NOT commit mechanically after every trivial subtask — the unit squash-merges anyway, so subtask granularity is cosmetic to `main`'s history. No PR opens and no required checks fire until unit completion. Subtasks do NOT open PRs.
 5. [ ] **STOP** and wait for user authorization
 
 ### For PARENT TASKS (Implementation or Architecture type)
@@ -48,7 +48,7 @@ get_section({ path: "completion-documentation-guide", heading: "Documentation Ti
 5. [ ] Complete the parent on its unit branch: `./.kiro/hooks/complete-task.sh "..."`.
    - **If this parent IS its own merge unit** (a standalone task, or a small single-unit spec): the tooling opens the PR and reports the URL.
    - **If this parent is one of several in a declared multi-parent unit** (see the spec's tasks.md unit grouping): the tooling commits the completion+summary docs on the branch — **no PR yet**. The PR opens when the UNIT completes (its final/gating parent).
-6. [ ] **STOP** — if a PR opened, report the PR URL; otherwise report the on-branch parent completion. **The task is accepted when Peter merges the UNIT's PR** (merge on green = the authorization act). Never merge your own PR; never push to `main`.
+6. [ ] **STOP** — if a PR opened, report the PR URL; otherwise report the on-branch parent completion. **The task is accepted when Peter merges the UNIT's PR** (merge on green = the authorization act). Never merge your own PR.
 
 ### For PARENT TASKS (Setup or Documentation type)
 1. [ ] Verify artifacts created/updated as specified
@@ -58,7 +58,7 @@ get_section({ path: "completion-documentation-guide", heading: "Documentation Ti
 5. [ ] Complete the parent on its unit branch: `./.kiro/hooks/complete-task.sh "..."`.
    - **If this parent IS its own merge unit**: the tooling opens the PR and reports the URL.
    - **If this parent is one of several in a declared multi-parent unit** (spec's tasks.md unit grouping): the tooling commits the completion+summary docs on the branch — **no PR yet**; the PR opens at UNIT completion.
-6. [ ] **STOP** — if a PR opened, report the PR URL; otherwise report the on-branch parent completion. **The task is accepted when Peter merges the UNIT's PR** (merge on green = the authorization act). Never merge your own PR; never push to `main`.
+6. [ ] **STOP** — if a PR opened, report the PR URL; otherwise report the on-branch parent completion. **The task is accepted when Peter merges the UNIT's PR** (merge on green = the authorization act). Never merge your own PR.
 
 ---
 
@@ -77,7 +77,7 @@ Branch → PR → required checks → merge.
 3. **Dependent tasks branch from `main` after the prior task's PR merges.** Starting a dependent task before the prior merge is not sanctioned by default — this composes with stop-and-wait (Peter's go for the next task typically follows his merge of the prior one), so the wait costs nothing in practice. Exception, only on Peter's explicit direction: branch from the prior task branch and declare `Stacked-on: #<PR>` in the PR body; stacked PRs merge in base-first order.
 4. At **unit** completion (a standalone task, a small single-unit spec, or the final/gating parent of a declared multi-parent unit), the tooling commits, pushes the branch, **opens a PR**, and reports the PR URL. A parent completing *inside* a multi-parent unit commits its completion+summary docs on the branch and does NOT open a PR — its acceptance is the unit's merge.
 5. Required checks run on the PR. A failing check blocks merge at the platform.
-6. **Peter merges on green** (see The Merge Rule below). **Squash-merge is the ONLY merge method** — the repository is configured to allow squash-merge only (method drift closed by configuration, not convention). The PR collapses to one commit on `main`, preserving the atomic-commit-per-task history the release tool scans; the PR title becomes the commit subject.
+6. **Peter merges on green** (see The Merge Rule below). The repository is configured **squash-merge-only** (method drift closed by configuration, not convention). The PR collapses to one commit on `main`, preserving the atomic-commit-per-unit history that serves as the release changelog spine; the PR title becomes the commit subject.
 7. Direct pushes to `main` are rejected by branch protection, **admins included**.
 
 **A task is complete at MERGE, not at PR-open.** The PR is the submission; the merge is the acceptance.
@@ -121,7 +121,7 @@ Branch → PR → required checks → merge.
 
 ### The Merge Rule
 
-- **Agents open PRs; Peter merges on green** during bake-in (Spec 125-A Task 5's gate). Agents NEVER merge their own PRs and NEVER push to `main`.
+- **Agents open PRs; Peter merges on green** during bake-in (Spec 125-A Task 5's gate). Agents NEVER merge their own PRs.
 - Any later **delegation of merge-on-green must be a recorded rule** (ballot or committed record with date and scope) — never a verbal grant. The relayed-authority lesson: authority is a record.
 - **Standing carve-out, surviving any delegation**: PRs touching governance law (`governance/**`, `.kiro/steering/**`, `.kiro/docs/ballots/**`, agent prompts/configs) stay Peter-merged — the closest ratification proxy until 125-B's CODEOWNERS layer.
 
@@ -148,7 +148,7 @@ When the gate must be bypassed (broken gate, urgent fix the checks themselves bl
 - **All tasks**: STOP after completion — never auto-proceed to the next task. Authorization to START the next task is governed by Start Up Tasks; the merge that completes this task is not that authorization.
 - **Parent vs. subtask** is the load-bearing distinction: subtasks get targeted tests + a completion doc + an **optional, judgment-based** branch commit-and-push (at a checkpoint, on backup-worthy accumulation, or at a session/handoff boundary — not mechanically per subtask); parents get full validation + completion doc + summary doc, committed on the branch.
 - **The merge unit is the coherent unit** — the smallest chunk that is coherent-on-its-own AND reviewable as a single diff, DECLARED in the spec's tasks.md (a small spec = one unit = one PR; a large spec declares internal units). The unit's completion opens the PR; a parent inside a multi-parent unit is done-on-branch, accepted at the unit's merge.
-- **A task is accepted at the MERGE of its unit.** Agents open PRs at unit completion; Peter merges on green. Never merge your own PR; never push to `main` (branch protection rejects it, admins included).
+- **A task is accepted at the MERGE of its unit.** Agents open PRs at unit completion; Peter merges on green. Never merge your own PR. Pushes to `main` are rejected by branch protection (admins included).
 - **On merge, the unit's branch is cleaned up** — remote auto-deleted by repo setting; local deleted on return to `main`; stale/unmerged branches swept in the monthly Civitas health check.
 - **A checks-only merge is NOT ratification**: governance-law changes still ratify via the record-first ballot protocol (`.kiro/docs/ballots/README.md`).
 - **Delegated-tier capture (exception-based)**: if the agent/model that actually did the work **diverged** from the task's planned `**Agent**: <agent> (<Model>)` — a different tier, or additional agents pulled in — record the delta and a one-line reason in the completion doc. A plan that held needs no note. This is a cheap data-point, **not** a justification to defend (overriding a stale or rote stamp is the *correct* move) — it feeds model-tier recalibration and process audits. Agent-evolution (routing/scope estimate was off) and model-evolution (cognitive-demand estimate was off) are distinct signals — note which. See `process-orchestration-model-selection`.

package/.kiro/steering/start-up-tasks.md

@@ -19,7 +19,7 @@ description: Essential pre-task checklist — date verification, governance heal
 
 2. **Civitas Governance Health Check**
    
-   IF it's been >30 days since last governance health check **[2026-08-02]**, THEN flag: "Governance health check overdue — Thurgood (Civitas steward) should run the monthly health check before proceeding."
+   IF it's been >30 days since last governance health check **[2026-08-25]**, THEN flag: "Governance health check overdue — Thurgood (Civitas steward) should run the monthly health check before proceeding."
    
    *Only Thurgood runs the health check. All agents check the date and flag if overdue.*
 
@@ -83,7 +83,7 @@ description: Essential pre-task checklist — date verification, governance heal
    
    **WHEN validating parent task completion THEN:**
    - **Default**: Use `npm test` (comprehensive functional validation)
-   - **If task modifies release tool or is performance-critical**: Use `npm run test:all` (adds the performance suites; the cost difference is now seconds, so when in doubt, run `test:all`)
+   - **If task is performance-critical**: Use `npm run test:all` (adds the performance suites; the cost difference is now seconds, so when in doubt, run `test:all`)
    
    **WHEN task involves performance changes THEN:**
    - Run BOTH `npm run test:performance` AND `npm run test:performance:isolated` (perf coverage is split across the two lanes), or simply `npm run test:all`
@@ -92,7 +92,7 @@ description: Essential pre-task checklist — date verification, governance heal
    **Decision tree:**
    ```
    Is this a parent task completion?
-   ├─ YES → Does task modify release tool or performance systems?
+   ├─ YES → Does task modify performance systems?
    │   ├─ YES → npm run test:all (includes performance regression tests)
    │   └─ NO → npm test (comprehensive functional validation)
    └─ NO → Does task involve performance changes?
@@ -105,7 +105,7 @@ description: Essential pre-task checklist — date verification, governance heal
    - `npm run test:all` additionally runs the performance suites (seconds of extra cost, but wall-clock-sensitive — avoid under heavy machine load)
    - Most parent tasks only need functional validation
    
-   **Default assumption**: Use `npm test` for parent tasks unless working on release tool or performance systems.
+   **Default assumption**: Use `npm test` for parent tasks unless working on performance systems.
 
 6. **Model-tier calibration — when this task will delegate to subagents**
    

package/dist/ComponentTokens.android.kt

@@ -1,6 +1,6 @@
 /**
  * DesignerPunk Design System - Component Tokens
- * Generated: 2026-08-12T03:23:17.012Z
+ * Generated: 2026-08-26T14:15:24.259Z
  * Version: 1.0.0
  * Platform: Android (Kotlin Constants)
  *
@@ -45,11 +45,11 @@ object ButtonIconTokens {
     // Small button variant uses 8px padding (1× base) for minimal footprint in dense UI layouts while meeting minimum touch target requirements
     val insetSmall = SpacingTokens.space100
     // Large button size (48px = 6× base) provides generous touch target exceeding tapAreaRecommended, calculated as icon (24px) + padding (12px × 2)
-    val sizeLarge = SpacingTokens.size600
+    val sizeLarge = SizingTokens.size600
     // Medium button size (40px = 5× base) provides standard touch target, calculated as icon (18px) + padding (10px × 2) rounded to grid
-    val sizeMedium = SpacingTokens.size500
+    val sizeMedium = SizingTokens.size500
     // Small button size (32px = 4× base) provides compact visual footprint, calculated as icon (13px) + padding (8px × 2) rounded to grid
-    val sizeSmall = SpacingTokens.size400
+    val sizeSmall = SizingTokens.size400
 }
 
 /** InputCheckbox Component Tokens */
@@ -74,26 +74,26 @@ object InputRadioTokens {
 
 /** Progress Component Tokens */
 object ProgressTokens {
+    // Connector line thickness (1px). References borderDefault primitive for consistent border treatment across the design system.
+    val connectorThickness = BorderWidthTokens.borderWidth100
     // Small node base size (12px). Inactive dots in compact mobile contexts.
-    val nodeSizeSm = SpacingTokens.size150
+    val nodeSizeSm = SizingTokens.size150
     // Medium node base size (16px). Default inactive dot size.
-    val nodeSizeMd = SpacingTokens.size200
+    val nodeSizeMd = SizingTokens.size200
     // Large node base size (20px). Inactive dots in desktop contexts.
-    val nodeSizeLg = SpacingTokens.size250
+    val nodeSizeLg = SizingTokens.size250
     // Current node emphasis for sm (16px). +4px over base 12px for non-color visual differentiation.
-    val nodeSizeSmCurrent = SpacingTokens.size200
+    val nodeSizeSmCurrent = SizingTokens.size200
     // Current node emphasis for md (20px). +4px over base 16px for non-color visual differentiation.
-    val nodeSizeMdCurrent = SpacingTokens.size250
+    val nodeSizeMdCurrent = SizingTokens.size250
     // Current node emphasis for lg (24px). +4px over base 20px for non-color visual differentiation.
-    val nodeSizeLgCurrent = SpacingTokens.size300
+    val nodeSizeLgCurrent = SizingTokens.size300
     // Small gap between nodes (6px = 0.75× base). Tight spacing for compact pagination dots in mobile contexts.
     val nodeGapSm = SpacingTokens.space075
     // Medium gap between nodes (8px = 1× base). Default spacing for stepper nodes, providing clear separation without excessive whitespace.
     val nodeGapMd = SpacingTokens.space100
     // Large gap between nodes (12px = 1.5× base). Generous spacing for detailed steppers with labels in desktop contexts.
     val nodeGapLg = SpacingTokens.space150
-    // Connector line thickness (1px). References borderDefault primitive for consistent border treatment across the design system.
-    val connectorThickness = SpacingTokens.borderWidth100
 }
 
 /** VerticalListItem Component Tokens */

package/dist/ComponentTokens.ios.swift

@@ -1,6 +1,6 @@
 ///
 /// DesignerPunk Design System - Component Tokens
-/// Generated: 2026-08-12T03:23:17.012Z
+/// Generated: 2026-08-26T14:15:24.259Z
 /// Version: 1.0.0
 /// Platform: iOS (Swift Constants)
 ///
@@ -45,11 +45,11 @@ public enum ButtonIconTokens {
     /// Small button variant uses 8px padding (1× base) for minimal footprint in dense UI layouts while meeting minimum touch target requirements
     public static let insetSmall: CGFloat = SpacingTokens.space100
     /// Large button size (48px = 6× base) provides generous touch target exceeding tapAreaRecommended, calculated as icon (24px) + padding (12px × 2)
-    public static let sizeLarge: CGFloat = SpacingTokens.size600
+    public static let sizeLarge: CGFloat = SizingTokens.size600
     /// Medium button size (40px = 5× base) provides standard touch target, calculated as icon (18px) + padding (10px × 2) rounded to grid
-    public static let sizeMedium: CGFloat = SpacingTokens.size500
+    public static let sizeMedium: CGFloat = SizingTokens.size500
     /// Small button size (32px = 4× base) provides compact visual footprint, calculated as icon (13px) + padding (8px × 2) rounded to grid
-    public static let sizeSmall: CGFloat = SpacingTokens.size400
+    public static let sizeSmall: CGFloat = SizingTokens.size400
 }
 
 /// InputCheckbox Component Tokens
@@ -74,26 +74,26 @@ public enum InputRadioTokens {
 
 /// Progress Component Tokens
 public enum ProgressTokens {
+    /// Connector line thickness (1px). References borderDefault primitive for consistent border treatment across the design system.
+    public static let connectorThickness: CGFloat = BorderWidthTokens.borderWidth100
     /// Small node base size (12px). Inactive dots in compact mobile contexts.
-    public static let nodeSizeSm: CGFloat = SpacingTokens.size150
+    public static let nodeSizeSm: CGFloat = SizingTokens.size150
     /// Medium node base size (16px). Default inactive dot size.
-    public static let nodeSizeMd: CGFloat = SpacingTokens.size200
+    public static let nodeSizeMd: CGFloat = SizingTokens.size200
     /// Large node base size (20px). Inactive dots in desktop contexts.
-    public static let nodeSizeLg: CGFloat = SpacingTokens.size250
+    public static let nodeSizeLg: CGFloat = SizingTokens.size250
     /// Current node emphasis for sm (16px). +4px over base 12px for non-color visual differentiation.
-    public static let nodeSizeSmCurrent: CGFloat = SpacingTokens.size200
+    public static let nodeSizeSmCurrent: CGFloat = SizingTokens.size200
     /// Current node emphasis for md (20px). +4px over base 16px for non-color visual differentiation.
-    public static let nodeSizeMdCurrent: CGFloat = SpacingTokens.size250
+    public static let nodeSizeMdCurrent: CGFloat = SizingTokens.size250
     /// Current node emphasis for lg (24px). +4px over base 20px for non-color visual differentiation.
-    public static let nodeSizeLgCurrent: CGFloat = SpacingTokens.size300
+    public static let nodeSizeLgCurrent: CGFloat = SizingTokens.size300
     /// Small gap between nodes (6px = 0.75× base). Tight spacing for compact pagination dots in mobile contexts.
     public static let nodeGapSm: CGFloat = SpacingTokens.space075
     /// Medium gap between nodes (8px = 1× base). Default spacing for stepper nodes, providing clear separation without excessive whitespace.
     public static let nodeGapMd: CGFloat = SpacingTokens.space100
     /// Large gap between nodes (12px = 1.5× base). Generous spacing for detailed steppers with labels in desktop contexts.
     public static let nodeGapLg: CGFloat = SpacingTokens.space150
-    /// Connector line thickness (1px). References borderDefault primitive for consistent border treatment across the design system.
-    public static let connectorThickness: CGFloat = SpacingTokens.borderWidth100
 }
 
 /// VerticalListItem Component Tokens

package/dist/ComponentTokens.web.css

@@ -1,6 +1,6 @@
 /**
  * DesignerPunk Design System - Component Tokens
- * Generated: 2026-08-12T03:23:17.012Z
+ * Generated: 2026-08-26T14:15:24.259Z
  * Version: 1.0.0
  * Platform: Web (CSS Custom Properties)
  *
@@ -63,6 +63,8 @@
   --inputradio-box-lg: var(--size-500);
 
   /* Progress Component Tokens */
+  /* Connector line thickness (1px). References borderDefault primitive for consistent border treatment across the design system. */
+  --progress-connector-thickness: var(--border-width-100);
   /* Small node base size (12px). Inactive dots in compact mobile contexts. */
   --progress-node-size-sm: var(--size-150);
   /* Medium node base size (16px). Default inactive dot size. */
@@ -81,8 +83,6 @@
   --progress-node-gap-md: var(--space-100);
   /* Large gap between nodes (12px = 1.5× base). Generous spacing for detailed steppers with labels in desktop contexts. */
   --progress-node-gap-lg: var(--space-150);
-  /* Connector line thickness (1px). References borderDefault primitive for consistent border treatment across the design system. */
-  --progress-connector-thickness: var(--border-width-100);
 
   /* VerticalListItem Component Tokens */
   /* Block padding at rest state (1px border). 11px padding + 1px border = 12px per side, achieving 48px total with 24px content. Uses TokenWithValue pattern as no primitive token exists for 11px. */

package/dist/DesignTokens.android.kt

@@ -1,6 +1,6 @@
 /**
  * DesignerPunk Design System - Android Tokens
- * Generated: 2026-08-12T03:23:16.999Z
+ * Generated: 2026-08-26T14:15:24.246Z
  * Version: 1.0.0
  * Platform: Android (Kotlin Constants)
  */

package/dist/DesignTokens.dtcg.json

@@ -3,8 +3,8 @@
   "$extensions": {
     "designerpunk": {
       "version": "1.0.0",
-      "generatedAt": "2026-08-12T03:23:17.012Z",
-      "rosettaVersion": "14.0.0"
+      "generatedAt": "2026-08-26T14:15:24.259Z",
+      "rosettaVersion": "14.1.0"
     }
   },
   "space": {

package/dist/DesignTokens.ios.swift

@@ -1,6 +1,6 @@
 ///
 /// DesignerPunk Design System - iOS Tokens
-/// Generated: 2026-08-12T03:23:16.997Z
+/// Generated: 2026-08-26T14:15:24.243Z
 /// Version: 1.0.0
 /// Platform: iOS (Swift Constants)
 ///

package/dist/DesignTokens.web.css

@@ -1,6 +1,6 @@
 /**
  * DesignerPunk Design System - Web Tokens
- * Generated: 2026-08-12T03:23:16.987Z
+ * Generated: 2026-08-26T14:15:24.233Z
  * Version: 1.0.0
  * Platform: Web (CSS Custom Properties)
  *

package/dist/android/DesignTokens.android.kt

@@ -1,6 +1,6 @@
 /**
  * DesignerPunk Design System - Android Tokens
- * Generated: 2026-08-02T19:49:06.784Z
+ * Generated: 2026-08-26T02:25:48.217Z
  * Version: 1.0.0
  * Platform: Android (Kotlin Constants)
  */

package/dist/browser/designerpunk.esm.js

@@ -4830,6 +4830,11 @@ function defineComponentTokens(config) {
     const tokenName = `${component.toLowerCase()}.${key}`;
     if (isTokenWithReference(definition)) {
       const primitiveToken = definition.reference;
+      if (typeof primitiveToken.category === "string" && primitiveToken.category !== family) {
+        throw new Error(
+          `Token family mismatch in defineComponentTokens() for component '${component}': token '${key}' is declared in a '${family}' family call but references primitive '${primitiveToken.name}' from the '${primitiveToken.category}' family. Every token in a call is stamped with that call's family, which drives platform output (e.g. the generated '${family.charAt(0).toUpperCase() + family.slice(1)}Tokens' class reference), so this would emit a non-existent platform member. Fix: move '${key}' into a separate defineComponentTokens() call with family: '${primitiveToken.category}', or use the value path if no token-chain relationship is intended.`
+        );
+      }
       const value = primitiveToken.baseValue;
       values[key] = value;
       registeredTokens.push({
@@ -7916,15 +7921,15 @@ var AvatarSizingTokens = defineComponentTokens({
     "size.xxl": {
       reference: sizingTokens.size1600,
       reasoning: "Extra extra large avatar (128px). Full profile view, onboarding."
-    }
-  }
-});
-var AvatarTokens = 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: SIZING_BASE_VALUE * 1.5,
       reasoning: "Icon size for xs avatar (12px = 1.5\xD7 base) maintains 50% ratio (12/24). No existing icon token at this size, so component token fills the gap."