@unified-product-graph/core 0.37.0 → 0.39.0

package/dist/index.d.cts

@@ -2264,6 +2264,13 @@ declare const UPG_EDGE_CATALOG: {
         source_type: string;
         target_type: string;
     };
+    feature_area_groups_design_component: {
+        forward_verb: string;
+        reverse_verb: string;
+        classification: "hierarchy";
+        source_type: string;
+        target_type: string;
+    };
     outcome_delivered_by_feature: {
         forward_verb: string;
         reverse_verb: string;
@@ -2896,6 +2903,14 @@ declare const UPG_EDGE_CATALOG: {
         source_type: string;
         target_type: string;
     };
+    design_token_derives_from_design_token: {
+        forward_verb: string;
+        reverse_verb: string;
+        classification: "causal";
+        source_type: string;
+        target_type: string;
+        cross_product_eligible: true;
+    };
     design_component_follows_design_pattern: {
         forward_verb: string;
         reverse_verb: string;
@@ -2923,6 +2938,7 @@ declare const UPG_EDGE_CATALOG: {
         classification: "hierarchy";
         source_type: string;
         target_type: string;
+        cross_product_eligible: true;
     };
     prototype_annotated_with_annotation: {
         forward_verb: string;
@@ -14345,8 +14361,28 @@ interface DesignComponentProperties {
  * }
  */
 interface DesignTokenProperties {
-    /** Category */
-    category?: 'color' | 'spacing' | 'typography' | 'radius' | 'motion';
+    /**
+     * What kind of value this token holds. Aligned to the Design Tokens
+     * Community Group `$type` vocabulary so a DTCG export maps across without
+     * translation; the five original UPG values are kept, `color` and `spacing`
+     * being the ones DTCG spells the same and `typography`, `radius`, `motion`
+     * being groupings a design system names in its own terms.
+     *
+     * @remarks
+     * DTCG mapping for the values that are not one-to-one: a `radius` token is a
+     * DTCG `dimension`, a `motion` token is usually a `duration` or a
+     * `cubicBezier`, and a `typography` token is a composite over `fontFamily` /
+     * `fontWeight` / `dimension`. Both spellings are accepted: an estate that
+     * speaks DTCG writes the `$type` name, one that speaks UPG's original five
+     * keeps writing them, and neither has to translate at the boundary.
+     *
+     * Extended at 0.39.0 from a measured estate (163 DTCG primitives) whose
+     * `shadow`, `dimension` and `opacity` tokens had no category to land on. The
+     * enum was documented but unenforced then; `validate_graph`'s
+     * `property_enum_drift` class (same release) is what makes it real, which is
+     * why the vocabulary had to be right before the check arrived.
+     */
+    category?: 'color' | 'spacing' | 'typography' | 'radius' | 'motion' | 'dimension' | 'fontFamily' | 'fontWeight' | 'duration' | 'cubicBezier' | 'number' | 'shadow' | 'gradient' | 'border' | 'transition' | 'strokeStyle' | 'opacity';
     /** Resolved value */
     value: string;
     /** CSS custom property name */
@@ -26999,7 +27035,7 @@ declare function checkHeaderSealText(text: string): UPGHeaderSealReport;
  * it stamps the `upg_version` field of every `.upg` file written by the SDK.
  * The `check:version-lockstep` gate enforces this at release time.
  */
-declare const UPG_VERSION: "0.37.0";
+declare const UPG_VERSION: "0.39.0";
 /**
  * The `.upg` JSON document format version. Written to the `upg_version` field.
  * Evolves independently from `UPG_VERSION` (the catalogue version).

package/dist/index.d.ts

@@ -2264,6 +2264,13 @@ declare const UPG_EDGE_CATALOG: {
         source_type: string;
         target_type: string;
     };
+    feature_area_groups_design_component: {
+        forward_verb: string;
+        reverse_verb: string;
+        classification: "hierarchy";
+        source_type: string;
+        target_type: string;
+    };
     outcome_delivered_by_feature: {
         forward_verb: string;
         reverse_verb: string;
@@ -2896,6 +2903,14 @@ declare const UPG_EDGE_CATALOG: {
         source_type: string;
         target_type: string;
     };
+    design_token_derives_from_design_token: {
+        forward_verb: string;
+        reverse_verb: string;
+        classification: "causal";
+        source_type: string;
+        target_type: string;
+        cross_product_eligible: true;
+    };
     design_component_follows_design_pattern: {
         forward_verb: string;
         reverse_verb: string;
@@ -2923,6 +2938,7 @@ declare const UPG_EDGE_CATALOG: {
         classification: "hierarchy";
         source_type: string;
         target_type: string;
+        cross_product_eligible: true;
     };
     prototype_annotated_with_annotation: {
         forward_verb: string;
@@ -14345,8 +14361,28 @@ interface DesignComponentProperties {
  * }
  */
 interface DesignTokenProperties {
-    /** Category */
-    category?: 'color' | 'spacing' | 'typography' | 'radius' | 'motion';
+    /**
+     * What kind of value this token holds. Aligned to the Design Tokens
+     * Community Group `$type` vocabulary so a DTCG export maps across without
+     * translation; the five original UPG values are kept, `color` and `spacing`
+     * being the ones DTCG spells the same and `typography`, `radius`, `motion`
+     * being groupings a design system names in its own terms.
+     *
+     * @remarks
+     * DTCG mapping for the values that are not one-to-one: a `radius` token is a
+     * DTCG `dimension`, a `motion` token is usually a `duration` or a
+     * `cubicBezier`, and a `typography` token is a composite over `fontFamily` /
+     * `fontWeight` / `dimension`. Both spellings are accepted: an estate that
+     * speaks DTCG writes the `$type` name, one that speaks UPG's original five
+     * keeps writing them, and neither has to translate at the boundary.
+     *
+     * Extended at 0.39.0 from a measured estate (163 DTCG primitives) whose
+     * `shadow`, `dimension` and `opacity` tokens had no category to land on. The
+     * enum was documented but unenforced then; `validate_graph`'s
+     * `property_enum_drift` class (same release) is what makes it real, which is
+     * why the vocabulary had to be right before the check arrived.
+     */
+    category?: 'color' | 'spacing' | 'typography' | 'radius' | 'motion' | 'dimension' | 'fontFamily' | 'fontWeight' | 'duration' | 'cubicBezier' | 'number' | 'shadow' | 'gradient' | 'border' | 'transition' | 'strokeStyle' | 'opacity';
     /** Resolved value */
     value: string;
     /** CSS custom property name */
@@ -26999,7 +27035,7 @@ declare function checkHeaderSealText(text: string): UPGHeaderSealReport;
  * it stamps the `upg_version` field of every `.upg` file written by the SDK.
  * The `check:version-lockstep` gate enforces this at release time.
  */
-declare const UPG_VERSION: "0.37.0";
+declare const UPG_VERSION: "0.39.0";
 /**
  * The `.upg` JSON document format version. Written to the `upg_version` field.
  * Evolves independently from `UPG_VERSION` (the catalogue version).