@unified-product-graph/core 0.9.18 → 0.9.19

package/CHANGELOG.md

@@ -7,6 +7,23 @@ This project uses [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
 ---
 
+## [0.9.19] - 2026-06-11
+
+**The tree-pattern catalogue covers every tree-shaped region, and `delivery` finally roots at the roadmap.** `get_tree` now offers 11 patterns (was 8), one per hierarchical region.
+
+### Changed
+- **`delivery` refined.** The 0.9.17 pattern rooted at the product, not the roadmap: its child map listed `product -> roadmap`, which made the product a superset of the roadmap, so the most-nodes anchor rule chose the product even when a roadmap existed. Dropping that slot lets the roadmap win when present; the product is the fallback root (`product -> release`). Added the missing optional children `roadmap_theme -> feature_area`, `release -> changelog`, and `release -> bug`. Default depth is now 3 (a readable overview to the feature tier; `depth` extends into epic and user story).
+
+### Added
+- **Three new tree patterns**, all-optional (browse views, no gap noise):
+  - **`architecture`** (anchor `service`, fallback `bounded_context`): services and the API contracts, endpoints, schemas, queues, deployments, and dependencies they own, grouped by bounded context, with domain aggregates and their members. A DAG: a schema or queue shared by several services renders once, then as a reference.
+  - **`journey`** (anchor `user_journey`, fallback `user_flow`): a journey over time, its phases and steps, the actions within each step, and the screens those steps surface.
+  - **`design_system`** (anchor `design_system`, fallback `design_component`): a design system, its components, their nested sub-components, and the design tokens they consume.
+
+No entity, domain, region, edge, or tool-count change (entities 315, edges 980, local tools 121). The work is in the presentation layer: `UPG_TREE_PATTERNS` (8 to 11) and the pattern lists carried by both servers, the CLI, and the show-tree skill.
+
+---
+
 ## [0.9.18] - 2026-06-11
 
 **The CLI help stops drifting, and an unknown `tree` filter stops lying.** The CLI rendered `--help` from a hand-maintained table divorced from each command's own option definitions, so adding a flag silently left its help stale (that is how `tree --pattern` shipped undocumented in 0.9.17). Separately, `upg tree <unknown>` quietly rendered the whole graph mislabeled as the filter. Both are now structural.

package/dist/index.cjs

@@ -19975,19 +19975,88 @@ var UPG_TREE_PATTERNS = [
   {
     id: "delivery",
     label: "Delivery roadmap",
-    description: "How product work is scheduled and shipped: the roadmap and its themes/items, the releases they schedule, and the features (with optional epic + user story tiers) they deliver.",
+    description: "How product work is scheduled and shipped: the roadmap and its themes/items, the releases they schedule, the features (and the changelog + bugs) those releases deliver, and the feature areas a theme spans. Optional epic + user story tiers appear on request.",
     anchor_type: "roadmap",
-    fallback_anchors: ["product", "release"],
+    // Fallback is the product alone: a graph with no roadmap roots at the
+    // product (product -> release -> feature), reported as anchor_resolved_from:
+    // roadmap. `release` is deliberately NOT a fallback root — a 32-release
+    // forest would out-node the product and shadow it under the most-nodes rule.
+    fallback_anchors: ["product"],
     child_map: {
-      product: [opt("roadmap"), opt("release")],
+      // product holds releases directly (the delivery axis without a roadmap),
+      // but NOT the roadmap: listing roadmap here made the product a superset of
+      // the roadmap, so the most-nodes anchor rule rooted delivery at the product
+      // even when a roadmap existed. Dropping it lets the roadmap win when present.
+      product: [opt("release")],
       roadmap: [opt("roadmap_theme"), opt("roadmap_item"), opt("release")],
-      roadmap_theme: [opt("feature")],
+      roadmap_theme: [opt("feature"), opt("feature_area")],
       roadmap_item: [opt("feature")],
-      release: [opt("feature")],
+      release: [opt("feature"), opt("changelog"), opt("bug")],
       feature: [opt("epic")],
       epic: [opt("user_story")]
     },
-    natural_depth: 5
+    // Default to 3 tiers (roadmap -> theme/item/release -> feature) for a
+    // readable overview on a many-release roadmap; `depth` extends into
+    // epic -> user_story.
+    natural_depth: 3
+  },
+  {
+    id: "architecture",
+    label: "Architecture",
+    description: "The engineering platform: services and the API contracts, endpoints, schemas, queues, deployments, and dependencies they own, grouped by bounded context, with domain aggregates and their members. A DAG (a schema or queue shared by several services renders once, then as a reference).",
+    anchor_type: "service",
+    fallback_anchors: ["bounded_context"],
+    child_map: {
+      bounded_context: [
+        opt("service"),
+        opt("external_api"),
+        opt("data_flow"),
+        opt("integration_pattern"),
+        opt("code_repository"),
+        opt("api_contract"),
+        opt("aggregate"),
+        opt("domain_event")
+      ],
+      service: [
+        opt("api_contract"),
+        opt("api_endpoint"),
+        opt("database_schema"),
+        opt("queue_topic"),
+        opt("deployment"),
+        opt("build_artifact"),
+        opt("library_dependency"),
+        opt("feature_flag")
+      ],
+      aggregate: [opt("domain_entity"), opt("value_object"), opt("command"), opt("read_model"), opt("domain_event")]
+    },
+    natural_depth: 3
+  },
+  {
+    id: "journey",
+    label: "User journey",
+    description: "A user journey over time: its phases and steps, the actions within each step, and the screens those steps surface. Falls back to a user_flow when journeys are not yet mapped.",
+    anchor_type: "user_journey",
+    fallback_anchors: ["user_flow"],
+    child_map: {
+      user_journey: [opt("journey_phase"), opt("journey_step")],
+      journey_phase: [opt("journey_step")],
+      journey_step: [opt("journey_action"), opt("screen")],
+      user_flow: [opt("screen")],
+      screen: [opt("screen_state")]
+    },
+    natural_depth: 3
+  },
+  {
+    id: "design_system",
+    label: "Design system",
+    description: "A design system broken into its components, their nested sub-components (atom to molecule to organism), and the design tokens they consume.",
+    anchor_type: "design_system",
+    fallback_anchors: ["design_component"],
+    child_map: {
+      design_system: [opt("design_component"), opt("design_token")],
+      design_component: [opt("design_component"), opt("design_token")]
+    },
+    natural_depth: 3
   }
 ];
 var UPG_TREE_PATTERNS_BY_ID = Object.fromEntries(
@@ -28300,7 +28369,7 @@ function isCanonical(text) {
 }
 
 // src/index.ts
-var UPG_VERSION = "0.9.18";
+var UPG_VERSION = "0.9.19";
 var UPG_FORMAT_VERSION = "0.4.0";
 var MARKDOWN_FORMAT_VERSION = "0.1";
 var UPG_TYPES = getTypes();