@unified-product-graph/core 0.22.2 → 0.23.0

package/README.md

@@ -7,7 +7,7 @@
 
 The TypeScript core for the **Unified Product Graph (UPG)**, an open specification that gives product tools a shared vocabulary for entities, edges, and frameworks.
 
-320 entity types across 37 domains. 1039 typed edges. 46 canonical framework definitions, with more added as each is reviewed.
+320 entity types across 37 domains. 1041 typed edges. 46 canonical framework definitions, with more added as each is reviewed.
 
 ## Install
 

package/dist/index.cjs

@@ -1684,6 +1684,17 @@ var UPG_EDGE_CATALOG = {
   bug_affects_feature: { forward_verb: "affects", reverse_verb: "affected_by", classification: "cross-domain", source_type: "bug", target_type: "feature" },
   roadmap_item_references_feature: { forward_verb: "references", reverse_verb: "referenced_by", classification: "cross-domain", source_type: "roadmap_item", target_type: "feature" },
   feature_decomposes_into_task: { forward_verb: "decomposes_into", reverse_verb: "implements", classification: "hierarchy", source_type: "feature", target_type: "task" },
+  // Epic-level mirrors of the feature→task / feature→bug hierarchy (feedback
+  // df99026a). A `feature` is the flat planning root, but an `epic` is a body of
+  // work under it, and real imported ticket sets (Linear/Jira) carry bugs and
+  // pure engineering tasks that belong to ONE epic, not the feature as a whole.
+  // Without these, such tickets had to be mislabelled `user_story` (the only
+  // epic child) to keep the epic grouping. These are additive twins of the
+  // feature-level edges (same verbs/classification), so `pickCanonicalEdge` /
+  // `resolveContainmentEdge('epic', 'task'|'bug')` and the adapter import path
+  // resolve them with no further wiring.
+  epic_decomposes_into_task: { forward_verb: "decomposes_into", reverse_verb: "implements", classification: "hierarchy", source_type: "epic", target_type: "task" },
+  epic_affected_by_bug: { forward_verb: "affected_by", reverse_verb: "affects", classification: "hierarchy", source_type: "epic", target_type: "bug" },
   task_has_subtask: { forward_verb: "has_subtask", reverse_verb: "is_subtask_of", classification: "hierarchy", source_type: "task", target_type: "task" },
   // ── Planning cadence (0.20.0) ────────────────────────────────────────────────
   // The cadence axis. E1 self-nests the interval (a program-increment contains
@@ -3987,7 +3998,10 @@ var UPG_VALID_CHILDREN = {
   // task_implements_user_story edge.
   feature: ["epic", "bug", "task"],
   feature_area: ["feature", "feature_area"],
-  epic: ["user_story"],
+  // epic owns user_story (the templated promise) and, mirroring feature, may
+  // also directly contain bug/task — heterogeneous imported tickets that belong
+  // to one epic rather than the feature as a whole (feedback df99026a).
+  epic: ["user_story", "bug", "task"],
   user_story: ["acceptance_criterion"],
   task: ["task"],
   // planning_cycle (0.20.0): the cadence axis self-nests (a program-increment
@@ -10972,7 +10986,7 @@ var UPG_PROPERTY_SCHEMA = {
   },
   // DashboardProperties: Dashboard entity.
   dashboard: {
-    tool: { type: "string", enum: ["looker", "amplitude", "mixpanel", "posthog", "custom"], description: "Analytics tool hosting this dashboard" },
+    tool: { type: "string", enum: ["looker", "amplitude", "mixpanel", "posthog", "omni", "custom"], description: "Analytics tool hosting this dashboard" },
     url: { type: "string", description: "URL to the live dashboard", modifier: "volatile" },
     audience: { type: "string", description: "Intended audience for this dashboard" },
     element_count: { type: "number", description: "Number of widgets or panels on the dashboard", modifier: "derived" },
@@ -23131,6 +23145,12 @@ var PRODUCT_SPEC_GUIDE = {
       entity_types: ["feature_area", "feature", "epic", "user_story", "task"],
       edge_chain: ["feature_area_contains_feature", "feature_decomposed_into_epic", "epic_specified_by_user_story", "task_implements_user_story"]
     },
+    {
+      name: "Epic Work Items",
+      description: "A bug or a pure engineering/infra task that belongs to one specific epic (not the feature as a whole) attaches directly to that epic, mirroring how task and bug attach at the feature level. Use this when importing a real tracker (Linear/Jira) whose tickets are heterogeneous: keep genuine stories as user_story, but let bugs, spikes, and engineering tasks nest under their epic with their true type instead of being mislabelled to preserve the grouping.",
+      entity_types: ["epic", "task", "bug"],
+      edge_chain: ["epic_decomposes_into_task", "epic_affected_by_bug"]
+    },
     {
       name: "Planning Cadence",
       description: "The cadence axis. Create a planning_cycle (a sprint, iteration, quarter, or PI), nest finer cycles inside a coarse one, schedule the stories that flow through it, and scope the objectives the cycle serves. Scheduling and scoping are deliberate links, not containment: a story keeps its feature/epic parent.",
@@ -29947,7 +29967,7 @@ function isCanonical(text) {
 }
 
 // src/index.ts
-var UPG_VERSION = "0.22.2";
+var UPG_VERSION = "0.23.0";
 var UPG_FORMAT_VERSION = "0.4.0";
 var MARKDOWN_FORMAT_VERSION = "0.1";
 var UPG_TYPES = getTypes();