@3fn/core 13.0.0 → 14.1.0

package/governance/Rosetta-System-Architecture.md

@@ -313,10 +313,11 @@ Semantic color tokens are resolved into light and dark mode sets before generati
 │                       MODE RESOLUTION SUBSYSTEM                              │
 ├─────────────────────────────────────────────────────────────────────────────┤
 │                                                                              │
-│   Level 1: Primitive Mode Values                                             │
-│   ├── Primitives carry distinct light/dark values in ColorTokenValue         │
-│   ├── Same primitive name in both modes — primitive handles differentiation │
-│   ├── Handles the common case (~85% of semantic color tokens)               │
+│   Level 1: Primitive Value Resolution (no mode variance)                     │
+│   ├── Primitives are single OKLCH triples — NO mode dimension (Spec 112)    │
+│   ├── No dark override → token falls back to the base (light) reference,    │
+│   │   resolving to the SAME value in both modes                             │
+│   ├── The common case — see npm run audit:mode-parity for the live split    │
 │   └── Resolved by: SemanticValueResolver                                    │
 │                                                                              │
 │   Level 2: Semantic Overrides                                                │
@@ -334,7 +335,8 @@ Semantic color tokens are resolved into light and dark mode sets before generati
 │                                                                              │
 │   Fallback Behavior                                                          │
 │   ├── Absent dark override → token uses base (light) primitive reference    │
-│   ├── Absent dark primitive value → primitive's light value used            │
+│   │   — the ONLY fallback that fires; primitives have no mode values to     │
+│   │   fall back from (legacy ColorTokens.ts is deprecated, Spec 115)        │
 │   ├── Fallback is graceful degradation, not build failure                   │
 │   └── Mode parity audit reports fallback usage: npm run audit:mode-parity   │
 │                                                                              │
@@ -631,16 +633,16 @@ The exemption is **not silent**: each exempt subsystem has a **paired boot/smoke
 
 ```
 # Get this document
-get_document_full({ path: ".kiro/steering/Rosetta-System-Architecture.md" })
+get_document_full({ path: "rosetta-system-architecture" })
 
 # Get specific sections
-get_section({ path: ".kiro/steering/Rosetta-System-Architecture.md", heading: "Token Pipeline Architecture" })
-get_section({ path: ".kiro/steering/Rosetta-System-Architecture.md", heading: "OKLCH Color Pipeline" })
-get_section({ path: ".kiro/steering/Rosetta-System-Architecture.md", heading: "Component Token Integration" })
-get_section({ path: ".kiro/steering/Rosetta-System-Architecture.md", heading: "Subsystem Entry Points Summary" })
+get_section({ path: "rosetta-system-architecture", heading: "Token Pipeline Architecture" })
+get_section({ path: "rosetta-system-architecture", heading: "OKLCH Color Pipeline" })
+get_section({ path: "rosetta-system-architecture", heading: "Component Token Integration" })
+get_section({ path: "rosetta-system-architecture", heading: "Subsystem Entry Points Summary" })
 
 # For token creation governance and guides
-get_section({ path: ".kiro/steering/Token-Governance.md", heading: "Token Creation Guides" })
+get_section({ path: "token-governance", heading: "Token Creation Guides" })
 ```
 
 ---

package/governance/Test-Behavioral-Contract-Validation.md

@@ -14,7 +14,7 @@ description: Framework for validating behavioral contracts across web, iOS, and
 **Scope**: cross-project
 **Layer**: 2
 **Relevant Tasks**: component-development, cross-platform-validation, testing
-**Last Reviewed**: 2026-01-02
+**Last Reviewed**: 2026-07-15
 
 ---
 
@@ -210,13 +210,11 @@ pressable_validation_checklist:
     - [ ] Click/tap triggers action
     - [ ] Enter key triggers action (web)
     - [ ] Space key triggers action (web)
-    - [ ] Action NOT triggered when disabled
     
   state_validation:
     - [ ] Default state is correct
     - [ ] Hover state appears (desktop only)
     - [ ] Pressed/active state appears
-    - [ ] Disabled state prevents interaction
     
   outcome_validation:
     - [ ] onPress callback is invoked
@@ -226,7 +224,6 @@ pressable_validation_checklist:
     
   accessibility_validation:
     - [ ] role="button" or semantic button (web)
-    - [ ] aria-disabled when disabled (web)
     - [ ] Screen reader announces button
     
   cross_platform_validation:
@@ -305,38 +302,49 @@ error_state_validation_checklist:
     - [ ] Android: TalkBack announces error
 ```
 
-### Disabled State Contract Validation
+### Disabled State Exclusion Guard Validation
 
-**Contract Definition**: Prevents interaction when disabled
+**Provenance**: As of the 2026-07-15 adjudication (`.kiro/issues/button-cta-disabled-state-adjudication.md`), the no-disabled-states philosophy holds corpus-wide with **zero exceptions** — Button-CTA was the last component carrying `state_disabled`, and it has been removed. No component in the corpus may declare a disabled state as a behavioral contract, and `blend.disabledDesaturate` (along with the other disabled-state blend wrappers) is deprecated. Validation for this contract type has inverted: rather than validating that a disabled state behaves correctly, validation now confirms a disabled state does **not exist** and cannot be reintroduced.
+
+**Contract Definition**: Component has no disabled state. Interaction affordances are always active; unavailable actions are handled by not rendering the component (or by another contract — see Philosophy Alternatives below), never by disabling it in place.
+
+**Rationale**: DesignerPunk does not support disabled states for usability and accessibility reasons. If an action is unavailable, the component should not be rendered.
 
 ```yaml
-disabled_state_validation_checklist:
-  trigger_validation:
-    - [ ] Disabled state activates when disabled=true
-    - [ ] Disabled state deactivates when disabled=false
-    
-  state_validation:
-    - [ ] Component cannot receive focus
-    - [ ] Component cannot be clicked/tapped
-    - [ ] Visual styling indicates disabled state
-    - [ ] Cursor shows not-allowed (web)
-    
-  outcome_validation:
-    - [ ] onPress/onChange NOT called when disabled
-    - [ ] Desaturated colors applied (blend.disabledDesaturate)
-    - [ ] Component is visually distinct from enabled
-    
-  accessibility_validation:
-    - [ ] aria-disabled="true" set (web)
-    - [ ] Disabled state communicated to AT
-    - [ ] Component removed from tab order (web)
-    
+disabled_state_exclusion_guard_checklist:
+  schema_validation:
+    - [ ] state_disabled is declared under contracts.yaml `excludes:` (NOT under `contracts:`)
+    - [ ] Excludes entry carries the standardized reason: "DesignerPunk does not support disabled states for usability and accessibility reasons. If an action is unavailable, the component should not be rendered."
+
+  api_surface_validation:
+    - [ ] Component exposes no disabled prop/property
+    - [ ] Component does not list `disabled` in observedAttributes (web) or an equivalent observed-attribute mechanism per platform
+
+  ignored_input_validation:
+    - [ ] A consumer-set disabled attribute is ignored — not forwarded to internal/shadow elements
+    - [ ] No disabled-styling class is applied when a disabled attribute is set
+    - [ ] No aria-disabled (or platform-equivalent) attribute is applied when a disabled attribute is set
+    - [ ] Press/activation still fires normally even when a consumer sets a disabled attribute
+
+  rendered_output_validation:
+    - [ ] No disabled attribute is ever rendered on any platform
+    - [ ] No aria-disabled attribute is ever rendered on any platform
+    - [ ] No platform-equivalent disabled semantic (e.g., Android `enabled = false`, iOS `.disabled()`) is ever applied
+
   cross_platform_validation:
-    - [ ] Web: aria-disabled and tabindex=-1
-    - [ ] iOS: .disabled() modifier applied
-    - [ ] Android: enabled = false in semantics
+    - [ ] Web: no disabled/aria-disabled attribute, no tabindex=-1 for disabled reasons
+    - [ ] iOS: no `.disabled()` modifier applied
+    - [ ] Android: no `enabled = false` in semantics
 ```
 
+**Philosophy Alternatives** — when a spec's design outline reaches for "disabled," redirect to the pattern that actually fits:
+
+- **In-flight async action** → `state_loading` (component shows a loading/busy state; the action remains conceptually available, just pending)
+- **Form input momentarily invalid** → validate-on-press / validate-on-submit (surface the error, do not disable the control)
+- **Action genuinely unavailable** → do not render the component/action at all
+
+**Mirror reference**: `src/components/core/Button-CTA/__tests__/ButtonCTA.test.ts`, `describe('No Disabled State (philosophy exclusion)')` — the canonical exclusion-guard test block this checklist is derived from.
+
 ### Hover State Contract Validation
 
 **Contract Definition**: Visual feedback on hover (desktop only)
@@ -347,7 +355,6 @@ hover_state_validation_checklist:
     - [ ] Hover state triggers on mouse enter
     - [ ] Hover state clears on mouse leave
     - [ ] Hover state NOT shown on touch devices
-    - [ ] Hover state NOT shown when disabled
     
   state_validation:
     - [ ] Background color changes on hover

package/governance/Test-Failure-Audit-Methodology.md

@@ -8,7 +8,7 @@ description: Reusable methodology for conducting test failure audits — workflo
 # Test Failure Audit Methodology
 
 **Date**: 2025-12-26
-**Last Reviewed**: 2025-12-26
+**Last Reviewed**: 2026-07-08
 **Purpose**: Reusable methodology guidance for conducting test failure audits, including workflow steps, pattern identification, and lessons learned from Specs 025/026/029
 **Organization**: process-standard
 **Scope**: cross-project

package/governance/Token-Family-Accessibility.md

@@ -2,14 +2,13 @@
 id: token-family-accessibility
 inclusion: manual
 name: Token-Family-Accessibility
-aliases: accessibility token work
 description: Accessibility token family — focus indicators, tap area sizing, and icon sizing tokens for WCAG 2.1 AA compliance. Load when working with focus states, touch targets, or accessibility-related token selection.
 ---
 
 # Accessibility Tokens Guide
 
 **Date**: 2025-12-30
-**Last Reviewed**: 2025-12-30
+**Last Reviewed**: 2026-07-08
 **Purpose**: Complete reference for accessibility-focused tokens including focus indicators, tap areas, and icon sizing
 **Organization**: token-documentation
 **Scope**: cross-project

package/governance/Token-Family-Blend.md

@@ -2,14 +2,13 @@
 id: token-family-blend
 inclusion: manual
 name: Token-Family-Blend
-aliases: blend token work
-description: Blend token family — color modification utilities (darken, lighten, saturate, desaturate) producing opaque colors. Load when working with hover/pressed/disabled/focus color states or theme-aware color blending.
+description: Blend token family — color modification utilities (darken, lighten, saturate, desaturate) producing opaque colors. Load when working with hover/pressed/focus color states or theme-aware color blending.
 ---
 
 # Blend Tokens Guide
 
 **Date**: 2025-12-29
-**Last Reviewed**: 2026-05-06
+**Last Reviewed**: 2026-07-15
 **Purpose**: Complete reference for blend tokens with utility functions and theme-aware patterns
 **Organization**: token-documentation
 **Scope**: cross-project
@@ -27,7 +26,9 @@ The DesignerPunk blend token system provides a mathematically consistent foundat
 - **Opaque Color Results**: Blend operations produce new opaque colors, not transparent overlays
 - **Cross-Platform Consistency**: Same blend calculations produce identical results (±1 RGB) across Web, iOS, and Android
 - **Theme-Aware**: Blend utilities work correctly with both light and dark themes
-- **Semantic Meaning**: Semantic blend tokens express design intent (hover, pressed, disabled, focus)
+- **Semantic Meaning**: Semantic blend tokens express design intent (hover, pressed, focus)
+
+> **Deprecation note (2026-07-15)**: `blend.disabledDesaturate` and the `disabledColor()`/`disabledBlend()` convenience wrappers are **DEPRECATED**. DesignerPunk does not support disabled states (Button-CTA disabled-state adjudication, ruled REMOVE — the philosophy holds corpus-wide): if an action is unavailable, do not render the component. The deprecated surfaces remain for backward compatibility and are scheduled for removal in the next major version of `@3fn/core`. The generic `desaturate()` utilities are NOT deprecated.
 
 ---
 
@@ -54,7 +55,7 @@ Blend tokens can be applied in four directions:
 | `darker` | Overlay black at specified opacity | Hover/pressed states on light backgrounds |
 | `lighter` | Overlay white at specified opacity | Hover/pressed states on dark backgrounds, icon optical balance |
 | `saturate` | Increase color saturation in HSL space | Focus states, emphasis |
-| `desaturate` | Decrease color saturation in HSL space | Disabled states |
+| `desaturate` | Decrease color saturation in HSL space | Muted, de-emphasized colors |
 
 ---
 
@@ -68,7 +69,7 @@ Semantic blend tokens provide contextual meaning for common color modification u
 | `blend.hoverLighter` | blend200 | lighter | 8% | Hover feedback on dark backgrounds |
 | `blend.pressedDarker` | blend300 | darker | 12% | Pressed state feedback |
 | `blend.focusSaturate` | blend200 | saturate | 8% | Focus state with increased saturation |
-| `blend.disabledDesaturate` | blend300 | desaturate | 12% | Disabled state with decreased saturation |
+| `blend.disabledDesaturate` | blend300 | desaturate | 12% | **DEPRECATED 2026-07-15** — no disabled states in DesignerPunk; removal at next major |
 | `blend.containerHoverDarker` | blend100 | darker | 4% | Subtle container/surface hover |
 | `color.icon.opticalBalance` | blend200 | lighter | 8% | Icon optical weight compensation |
 
@@ -107,7 +108,7 @@ import {
 | `hoverColor(baseColor)` | darkerBlend | 8% (blend200) |
 | `pressedColor(baseColor)` | darkerBlend | 12% (blend300) |
 | `focusColor(baseColor)` | saturate | 8% (blend200) |
-| `disabledColor(baseColor)` | desaturate | 12% (blend300) |
+| `disabledColor(baseColor)` | desaturate | **DEPRECATED 2026-07-15** — removal at next major |
 | `iconColor(baseColor)` | lighterBlend | 8% (blend200) |
 
 **Usage Example**:
@@ -125,7 +126,6 @@ class ButtonCTA extends HTMLElement {
     // Calculate state colors
     this._hoverColor = blendUtils.hoverColor(primaryColor);
     this._pressedColor = blendUtils.pressedColor(primaryColor);
-    this._disabledColor = blendUtils.disabledColor(primaryColor);
   }
 }
 ```
@@ -168,7 +168,7 @@ extension Color {
     /// Focus state color (8% more saturated)
     func focusBlend() -> Color
     
-    /// Disabled state color (12% less saturated)
+    /// DEPRECATED 2026-07-15 — no disabled states in DesignerPunk; removal at next major
     func disabledBlend() -> Color
     
     /// Icon optical balance (8% lighter)
@@ -189,7 +189,6 @@ struct ButtonCTA: View {
         .background(isPressed ? primaryColor.pressedBlend() : 
                     isHovered ? primaryColor.hoverBlend() : 
                     primaryColor)
-        .foregroundColor(isDisabled ? primaryColor.disabledBlend() : primaryColor)
     }
 }
 ```
@@ -216,7 +215,7 @@ fun Color.desaturate(amount: Float): Color
 fun Color.hoverBlend(): Color    // 8% darker
 fun Color.pressedBlend(): Color  // 12% darker
 fun Color.focusBlend(): Color    // 8% more saturated
-fun Color.disabledBlend(): Color // 12% less saturated
+fun Color.disabledBlend(): Color // DEPRECATED 2026-07-15 — removal at next major
 fun Color.iconBlend(): Color     // 8% lighter
 ```
 
@@ -266,7 +265,6 @@ class ButtonCTA extends HTMLElement {
     const blendUtils = getBlendUtilities();
     this._hoverColor = blendUtils.hoverColor(primaryColor);
     this._pressedColor = blendUtils.pressedColor(primaryColor);
-    this._disabledColor = blendUtils.disabledColor(primaryColor);
     this._iconColor = blendUtils.iconColor(onPrimaryColor);
   }
   
@@ -348,7 +346,6 @@ const iconStyle = { filter: 'brightness(1.08)' };
 const blendUtils = getBlendUtilities();
 const hoverColor = blendUtils.hoverColor(primaryColor);      // darkerBlend 8%
 const pressedColor = blendUtils.pressedColor(primaryColor);  // darkerBlend 12%
-const disabledColor = blendUtils.disabledColor(primaryColor); // desaturate 12%
 const iconColor = blendUtils.iconColor(onPrimaryColor);      // lighterBlend 8%
 ```
 
@@ -357,7 +354,6 @@ const iconColor = blendUtils.iconColor(onPrimaryColor);      // lighterBlend 8%
 ```typescript
 const blendUtils = getBlendUtilities();
 const focusColor = blendUtils.focusColor(primaryColor);      // saturate 8%
-const disabledColor = blendUtils.disabledColor(primaryColor); // desaturate 12%
 ```
 
 ### Container Component
@@ -414,7 +410,6 @@ Use semantic blend tokens for standard interaction states:
 | Hover (dark bg) | `blend.hoverLighter` | `lighterBlend(color, 0.08)` |
 | Pressed | `blend.pressedDarker` | `pressedColor()` |
 | Focus | `blend.focusSaturate` | `focusColor()` |
-| Disabled | `blend.disabledDesaturate` | `disabledColor()` |
 | Container hover | `blend.containerHoverDarker` | `darkerBlend(color, 0.04)` |
 | Icon optical | `color.icon.opticalBalance` | `iconColor()` |
 
@@ -433,6 +428,13 @@ const emphasisColor = blendUtils.darkerBlend(color, 0.16); // blend400 = 16%
 
 ### Anti-Patterns to Avoid
 
+**❌ Don't style disabled states**:
+```typescript
+// WRONG: DesignerPunk does not support disabled states (adjudicated 2026-07-15).
+// If an action is unavailable, do not render the component.
+const disabledColor = blendUtils.disabledColor(primaryColor);
+```
+
 **❌ Don't use opacity for state colors**:
 ```typescript
 // WRONG: Opacity creates transparency, not new colors
@@ -481,7 +483,7 @@ blend500 = base × 5 = 0.04 × 5 = 0.20 (20%)
 | blend.hoverLighter | blend200 | 8% |
 | blend.pressedDarker | blend300 | 12% |
 | blend.focusSaturate | blend200 | 8% |
-| blend.disabledDesaturate | blend300 | 12% |
+| blend.disabledDesaturate (deprecated) | blend300 | 12% |
 | blend.containerHoverDarker | blend100 | 4% |
 | color.icon.opticalBalance | blend200 | 8% |
 

package/governance/Token-Family-Blur.md

@@ -2,7 +2,6 @@
 id: token-family-blur
 inclusion: manual
 name: Token-Family-Blur
-aliases: blur token work
 description: Unified blur token family — single primitive scale for shadow edge softness, glow radial spread, and surface/backdrop blur. Load when working with shadows, glows, translucent surfaces, or any blur effect.
 ---
 

package/governance/Token-Family-Border.md

@@ -2,14 +2,13 @@
 id: token-family-border
 inclusion: manual
 name: Token-Family-Border
-aliases: border token work
 description: Border token family — border width tokens with doubling progression and numeric naming. Load when working with border widths, dividers, or outline styles.
 ---
 
 # Border Tokens Guide
 
 **Date**: 2025-12-30
-**Last Reviewed**: 2025-12-30
+**Last Reviewed**: 2026-07-08
 **Purpose**: Complete reference for border width tokens with numeric naming convention and mathematical relationships
 **Organization**: token-documentation
 **Scope**: cross-project

package/governance/Token-Family-Color.md

@@ -2,7 +2,6 @@
 id: token-family-color
 inclusion: manual
 name: Token-Family-Color
-aliases: color token work
 description: Color token family — OKLCH channel-primitive architecture, palette structure, semantic color tokens, neutral partition, blend model, theme support, and WCAG compliance. Load when working with color tokens, color selection, theme variants, or color-related accessibility.
 ---
 

package/governance/Token-Family-Glow.md

@@ -2,14 +2,13 @@
 id: token-family-glow
 inclusion: manual
 name: Token-Family-Glow
-aliases: glow token work
 description: Glow token family — radial emphasis and energy effects with zero-offset blur, opacity, and color primitives. Load when working with glow effects, emphasis indicators, or interactive energy states.
 ---
 
 # Glow Token Usage Documentation
 
 **Date**: 2025-10-24
-**Last Reviewed**: 2025-12-30
+**Last Reviewed**: 2026-07-08
 **Purpose**: Glow token reference and usage guide
 **Organization**: token-documentation
 **Scope**: cross-project

package/governance/Token-Family-Layering.md

@@ -2,7 +2,6 @@
 id: token-family-layering
 inclusion: manual
 name: Token-Family-Layering
-aliases: layering z-index token work
 description: Layering token family — z-index (web/iOS) and elevation (Android) tokens for element stacking order. Load when working with overlays, modals, tooltips, or any stacking context decisions.
 ---
 

package/governance/Token-Family-Motion.md

@@ -2,14 +2,13 @@
 id: token-family-motion
 inclusion: manual
 name: Token-Family-Motion
-aliases: motion easing token work
 description: Motion token family — animation duration, easing curves, and scale primitives for consistent transitions. Load when working with animations, transitions, micro-interactions, or motion timing.
 ---
 
 # Motion Token Usage Documentation
 
 **Date**: 2025-12-06
-**Last Reviewed**: 2025-12-30
+**Last Reviewed**: 2026-07-08
 **Purpose**: Motion token reference and usage guide
 **Organization**: token-documentation
 **Scope**: cross-project

package/governance/Token-Family-Opacity.md

@@ -2,7 +2,6 @@
 id: token-family-opacity
 inclusion: manual
 name: Token-Family-Opacity
-aliases: opacity token work
 description: Opacity token family — transparency tokens with 8% base increment system and 14-token percentage-based scale (opacity000–opacity100). Load when working with transparency effects, disabled states, overlays, or visual hierarchy through opacity.
 ---
 

package/governance/Token-Family-Radius.md

@@ -2,14 +2,13 @@
 id: token-family-radius
 inclusion: manual
 name: Token-Family-Radius
-aliases: radius token work
 description: Radius token family — corner rounding tokens on 8-unit baseline grid with strategic flexibility exceptions. Load when working with border-radius, rounded corners, or pill/circle shapes.
 ---
 
 # Radius Tokens Guide
 
 **Date**: 2025-12-30
-**Last Reviewed**: 2025-12-30
+**Last Reviewed**: 2026-07-08
 **Purpose**: Complete reference for radius tokens with numeric naming convention and mathematical relationships
 **Organization**: token-documentation
 **Scope**: cross-project

package/governance/Token-Family-Responsive.md

@@ -2,14 +2,13 @@
 id: token-family-responsive
 inclusion: manual
 name: Token-Family-Responsive
-aliases: responsive token work
 description: Responsive token family — breakpoint and density tokens for adaptive interfaces. Load when working with responsive layouts, viewport breakpoints, or density-based scaling.
 ---
 
 # Responsive Tokens Guide
 
 **Date**: 2025-12-30
-**Last Reviewed**: 2025-12-30
+**Last Reviewed**: 2026-07-08
 **Purpose**: Complete reference for breakpoint and density tokens enabling responsive design across platforms
 **Organization**: token-documentation
 **Scope**: cross-project

package/governance/Token-Family-Shadow.md

@@ -2,14 +2,13 @@
 id: token-family-shadow
 inclusion: manual
 name: Token-Family-Shadow
-aliases: shadow token work
 description: Shadow token family — directional depth effects with compositional offset, blur, opacity, and color primitives. Load when working with elevation, depth, card shadows, or spatial hierarchy.
 ---
 
 # Shadow Token Usage Documentation
 
 **Date**: 2025-10-24
-**Last Reviewed**: 2025-12-30
+**Last Reviewed**: 2026-07-08
 **Purpose**: Shadow token reference and usage guide
 **Organization**: token-documentation
 **Scope**: cross-project

package/governance/Token-Family-Sizing.md

@@ -2,7 +2,6 @@
 id: token-family-sizing
 inclusion: manual
 name: Token-Family-Sizing
-aliases: sizing token work
 description: Sizing token family — component dimensions (width, height, box size). Separate from spacing (gaps). Load when working with component sizes, avatar dimensions, button sizes, or any component dimensional value.
 ---
 

package/governance/Token-Family-Spacing.md

@@ -2,14 +2,13 @@
 id: token-family-spacing
 inclusion: manual
 name: Token-Family-Spacing
-aliases: spacing token work
 description: Spacing token family — layout and component spacing on 8-unit baseline grid with strategic flexibility exceptions. Load when working with padding, margins, gaps, or any spatial layout decisions.
 ---
 
 # Spacing Tokens Guide
 
 **Date**: 2025-11-26
-**Last Reviewed**: 2025-12-30
+**Last Reviewed**: 2026-07-08
 **Purpose**: Complete reference for spacing tokens with numeric naming convention and mathematical relationships
 **Organization**: token-documentation
 **Scope**: cross-project

package/governance/Token-Family-Typography.md

@@ -2,14 +2,13 @@
 id: token-family-typography
 inclusion: manual
 name: Token-Family-Typography
-aliases: typography token work
 description: Typography token family — compositional typography tokens combining fontSize, lineHeight, fontFamily, fontWeight, and letterSpacing. Load when working with text styles, font selection, or typographic hierarchy.
 ---
 
 # Typography Tokens Guide
 
 **Date**: 2025-12-09
-**Last Reviewed**: 2025-12-30
+**Last Reviewed**: 2026-07-08
 **Purpose**: Complete reference for typography tokens with font family usage and weight mapping guidance
 **Organization**: token-documentation
 **Scope**: cross-project

package/governance/Token-Governance.md

@@ -625,15 +625,15 @@ This gate exists to prevent ungoverned growth of the modifier pattern. The opaci
 
 ```
 # Get this document
-get_document_full({ path: ".kiro/steering/Token-Governance.md" })
+get_document_full({ path: "token-governance" })
 
 # Get specific sections
-get_section({ path: ".kiro/steering/Token-Governance.md", heading: "Token Selection Matrix" })
-get_section({ path: ".kiro/steering/Token-Governance.md", heading: "Token Usage Governance" })
-get_section({ path: ".kiro/steering/Token-Governance.md", heading: "Token Creation Governance" })
-get_section({ path: ".kiro/steering/Token-Governance.md", heading: "Prior Acknowledgment" })
-get_section({ path: ".kiro/steering/Token-Governance.md", heading: "Decision Examples" })
-get_section({ path: ".kiro/steering/Token-Governance.md", heading: "Token Creation Guides" })
+get_section({ path: "token-governance", heading: "Token Selection Matrix" })
+get_section({ path: "token-governance", heading: "Token Usage Governance" })
+get_section({ path: "token-governance", heading: "Token Creation Governance" })
+get_section({ path: "token-governance", heading: "Prior Acknowledgment" })
+get_section({ path: "token-governance", heading: "Decision Examples" })
+get_section({ path: "token-governance", heading: "Token Creation Guides" })
 ```
 
 ---
@@ -645,7 +645,7 @@ get_section({ path: ".kiro/steering/Token-Governance.md", heading: "Token Creati
 - [Rosetta System Principles](rosetta-system-principles) — Mathematical foundations
 - [Token Quick Reference](token-quick-reference) — Token documentation routing
 - [Token Category Pattern Guide](../specs/token-system/token-category-pattern-guide.md) — Detailed primitive/semantic creation patterns
-- [Core Goals](core-goals) — Project principles including token-first approach
+- [Core Goals](../.kiro/steering/core-goals.md) — Project principles including token-first approach
 - [Design Authority](../specs/051-semantic-token-naming-restructure/design-outline.md) — Semantic token naming restructure design
 
 ### DTCG Integration