@unified-product-graph/core 0.9.9 → 0.9.11

package/CHANGELOG.md

@@ -7,6 +7,40 @@ This project uses [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
 ---
 
+## [0.9.11] - 2026-06-10
+
+**Tooling DX (batch 6, part 2): status pre-flight + anti-pattern visibility.** Two discoverability fixes from the same real portfolio session, plus a self-trip fix.
+
+### Added
+- **`list_status_values(entity_type)`** (tools 118 to 119, on both the local and cloud servers): the valid `status` values a type can hold, as a focused pre-flight lookup so an author no longer learns the set only from a rejected write. Returns lifecycle phases as `{ status, label, terminal }` plus `initial_status` / `terminal_statuses`, or `lifecycle_free: true` with empty `values`. Sourced from `UPG_LIFECYCLES` (exactly what the write validator checks): the low-token sibling of `get_lifecycle`.
+- **Anti-pattern version tracking.** `UPGCuratedAntiPattern` gains an optional `since` field, and `get_spec_version` now reports `anti_patterns: { total, versioned }`. A consumer can see which validators are newer than the version a graph was authored under, so a spec upgrade no longer silently flips a clean graph invalid with no heads-up.
+
+### Changed
+- **A drafted hypothesis is auto-promoted to `active`** when it gains a `hypothesis_requires_experiment_plan` edge (via `create_edge` / `batch_create_edges`). Pairing a hypothesis with a plan is what activates it; this stops the documented structural-spine recipe (hypotheses paired with plans) from self-tripping the `untested-hypothesis-pile-up` anti-pattern. Best-effort: a promotion failure never fails the edge.
+
+No entity, domain, or edge-catalogue count change (tool count 118 to 119).
+
+---
+
+## [0.9.10] - 2026-06-10
+
+**Tooling DX + a born-valid product (batch 6, part 1) + a release-test gate.** Polish from a real multi-graph portfolio session: parity and discoverability fixes, one model correction, and — the headline — the release train now runs the unit suites, after they were found to have been silently red across a release.
+
+### Changed
+- **Product `properties.stage` is canonical.** The stale `UPG_PROPERTY_MIGRATIONS['0.2.13']` lift of a product node's `properties.stage` to top-level `status` is retired: it contradicted the current convention the whole runtime uses (a product node's lifecycle stage lives in `properties.stage`), so a freshly-created product read as `property_drift` against its own validator. A new product is now born valid. Legacy values are still normalised on read by `coerceProductStage`. Decision: `2026-06-10-product-stage-properties-canonical.md`.
+- **`get_nodes` resolves cross-product ids.** A qualified `{product_id}/{node_id}` (the form `list_registry` / `export_edges` / cross-edges return) now reads that product's graph (read-only for non-active products), so a connective pass fetches node content across the portfolio without a `switch_product` sweep. Results carry a `product_id`.
+- **`create_edge` / `batch_create_edges` accept the `p_` product-header** where the in-graph product node is expected, resolving it to the `type:"product"` node (older graphs carry a distinct `n_…` product node).
+- **`did_you_mean` for a mistyped edge type** now falls back to the closest catalogue key by name (edit distance) when the endpoints don't resolve to a canonical pair — so a typo always gets a concrete suggestion.
+- **`batch_create_cross_product_edges` reaches enum parity** with `create_cross_product_edge` (both now derive their type list from one spec source, so the batch tool can no longer lag a release behind — it had been missing `rolls_up_to`).
+- **`batch_register_instance` echoes** `aliased` / `alias_updated` per result, so a bulk sanction pass is visible without a second `portfolio_validate`.
+
+### Fixed
+- **Release-test gate.** The publish train now runs the train packages' unit suites (`gate:tests`) as a hard pre-flight; a red test aborts the train. This closes the gap that let a prior release ship with several silently-red suites — including import adapters that emitted edge types a rename had retired (now corrected), stale compiled test copies, and fixtures referencing retired edges.
+
+No new tools (118) and no entity / domain / edge-catalogue count change.
+
+---
+
 ## [0.9.9] - 2026-06-10
 
 **Structural-integrity forks: validation, AI-prompt, and journey models corrected; duplicate edges collapsed.** A spec-model cut that fixes several long-standing structural mismodels and retires shadow edges. Every renamed or retired edge ships a dual-read migration (`UPG_EDGE_MIGRATIONS['0.9.9']`), so stored graphs upgrade automatically on load. No new tools (118) and no entity-count change; the within-product edge catalogue settles at 975 after the duplicate collapse.

package/dist/index.cjs

@@ -182,6 +182,7 @@ __export(index_exports, {
   resolveEntityType: () => resolveEntityType,
   resolveLabel: () => resolveLabel,
   resolveSlugCollision: () => resolveSlugCollision,
+  ringOrderedDomainIds: () => ringOrderedDomainIds,
   rotateSlug: () => rotateSlug,
   serializeCanonical: () => serializeCanonical,
   validateProductStageStrict: () => validateProductStageStrict,
@@ -7666,22 +7667,18 @@ var UPG_PROPERTY_MIGRATIONS = {
   // graphs typically carry only one of the two; the conflict path is
   // theoretical but documented for predictability.
   "0.2.13": [
-    // 1. Lift properties.stage → status (with value remap to UPGProductStage).
-    {
-      kind: "lift_property_to_top_level",
-      type: "product",
-      from_property: "stage",
-      to: "status",
-      value_map: {
-        // Pre-canonical UPGProductStage aliases from early v0.1 product-node
-        // shape. "idea" was the canonical pre-validation phase before the
-        // 9-stage UPGProductStage shipped; today that's "concept".
-        idea: "concept"
-        // Pass-through: the canonical 9 product stages already exist as
-        // UPGProductStage values and need no remap when surfaced inline.
-      },
-      reason: 'lifecycle phase belongs in top-level `status` per UPGBaseNode contract, not in `properties`. Pre-canonical "idea" alias mapped to canonical `concept` (UPGProductStage[0]).'
-    },
+    // 1. (RETIRED in 0.9.10, batch-6 #33) The product `properties.stage` →
+    //    top-level `status` lift is superseded by UPG-654/661, which
+    //    re-canonicalised a product node's lifecycle stage to
+    //    `properties.stage` — a distinct 9-phase `UPGProductStage` axis,
+    //    separate from the generic top-level `status` other entities use. The
+    //    entire runtime (create_product, get_graph_digest, get_product_context,
+    //    completeness, header-sync) reads and writes `properties.stage`, so
+    //    lifting it to `status` made a freshly-created product read as
+    //    `property_drift` against its own validator (a tool emitting drift its
+    //    validator immediately flags). Legacy "idea"-style values are still
+    //    normalised on READ by `coerceProductStage`, so retiring the lift loses
+    //    no cleanup. Decision: 2026-06-10-product-stage-properties-canonical.md.
     // 2. Rename top-level lifecycle_status → status (with value remap).
     {
       kind: "rename_top_level",
@@ -20474,19 +20471,23 @@ var UPG_DOMAIN_RINGS = [
     id: "define",
     label: "Define",
     description: "What are we building?",
-    domain_ids: ["strategy", "product_spec", "legal", "ux_design", "design_system", "brand"]
+    // `business_model` lives in the `define` ring (foundational "what are we
+    // building & how it sustains"), not in `grow`. This is an intentional
+    // ring-vs-region divergence: UPG_REGIONS still groups business_model under
+    // `business_gtm_growth` (region membership is a separately-tracked decision).
+    domain_ids: ["strategy", "product_spec", "business_model", "ux_design", "design_system", "brand", "legal"]
   },
   {
     id: "build",
     label: "Build",
     description: "How do we construct it?",
-    domain_ids: ["engineering", "devops", "testing", "security", "accessibility", "data_analytics", "ai", "automation"]
+    domain_ids: ["engineering", "ai", "automation", "data_analytics", "testing", "devops", "security", "accessibility"]
   },
   {
     id: "grow",
     label: "Grow",
     description: "How do we make money?",
-    domain_ids: ["business_model", "growth", "go_to_market", "pricing", "sales", "marketing"]
+    domain_ids: ["pricing", "go_to_market", "sales", "marketing", "growth"]
   },
   {
     id: "operate",
@@ -20498,9 +20499,27 @@ var UPG_DOMAIN_RINGS = [
     id: "extend",
     label: "Extend",
     description: "How do we scale?",
-    domain_ids: ["team_org", "program_mgmt", "localisation", "ecosystem", "compliance"]
+    domain_ids: ["team_org", "program_mgmt", "ecosystem", "localisation", "compliance"]
   }
 ];
+function assertRingsPartitionDomains() {
+  const ringDomainIds = UPG_DOMAIN_RINGS.flatMap((r) => [...r.domain_ids]);
+  const canonical = new Set(UPG_DOMAINS.map((d) => d.id));
+  const ringSet = new Set(ringDomainIds);
+  const duplicates = ringDomainIds.filter((id, i) => ringDomainIds.indexOf(id) !== i);
+  const unknown = [...ringSet].filter((id) => !canonical.has(id));
+  const unassigned = [...canonical].filter((id) => !ringSet.has(id));
+  if (duplicates.length || unknown.length || unassigned.length) {
+    const parts = [];
+    if (unassigned.length) parts.push(`domains in no ring: [${unassigned.join(", ")}]`);
+    if (unknown.length) parts.push(`ring domains not in UPG_DOMAINS: [${unknown.join(", ")}]`);
+    if (duplicates.length) parts.push(`domains in multiple rings: [${[...new Set(duplicates)].join(", ")}]`);
+    throw new Error(
+      `UPG_DOMAIN_RINGS must partition UPG_DOMAINS exactly: ${parts.join("; ")}. Slot every domain into exactly one ring in domain-rings.ts.`
+    );
+  }
+}
+assertRingsPartitionDomains();
 function getRingForDomain(domainId) {
   return UPG_DOMAIN_RINGS.find((ring) => ring.domain_ids.includes(domainId));
 }
@@ -20508,6 +20527,9 @@ function getDomainsInRing(ringId) {
   const ring = UPG_DOMAIN_RINGS.find((r) => r.id === ringId);
   return ring ? [...ring.domain_ids] : [];
 }
+function ringOrderedDomainIds() {
+  return UPG_DOMAIN_RINGS.flatMap((ring) => [...ring.domain_ids]);
+}
 
 // src/intelligence/domain-guides.ts
 var USER_GUIDE = {
@@ -24071,6 +24093,7 @@ var UPG_ANTI_PATTERNS = [
   // RelationshipCheck (edge presence/absence) and are promoted here.
   {
     id: "insights-without-evidence",
+    since: "0.9.7",
     name: "Insights without evidence",
     description: "The graph has insight entities but none are backed by a primary-evidence link: no observation yields them (`observation_yields_insight`), no survey response evidences them (`survey_response_evidences_insight`), and no quote is attached (`insight_evidenced_by_quote`). An insight with no evidence behind it is an opinion wearing a research label.",
     structured_condition: {
@@ -24114,6 +24137,7 @@ var UPG_ANTI_PATTERNS = [
   },
   {
     id: "feature-requests-without-provenance",
+    since: "0.9.7",
     name: "Feature requests without provenance",
     description: "The graph has feature_request entities but none trace back to a source: no feedback program collects them (`feedback_program_collects_feature_request`), no customer feedback becomes one (`customer_feedback_becomes_feature_request`), and none originate from a behavioural segment (`feature_request_from_behavioral_segment`). A request with no provenance cannot be weighed against who asked or how many.",
     structured_condition: {
@@ -27174,7 +27198,7 @@ function isCanonical(text) {
 }
 
 // src/index.ts
-var UPG_VERSION = "0.9.9";
+var UPG_VERSION = "0.9.11";
 var UPG_FORMAT_VERSION = "0.4.0";
 var MARKDOWN_FORMAT_VERSION = "0.1";
 var UPG_TYPES = getTypes();
@@ -27401,6 +27425,7 @@ var UPG_META_COUNT = UPG_ENTITY_META.length;
   resolveEntityType,
   resolveLabel,
   resolveSlugCollision,
+  ringOrderedDomainIds,
   rotateSlug,
   serializeCanonical,
   validateProductStageStrict,