@transitrix/diagrams 1.8.19 → 1.8.20

package/dist/blocks/validate.d.ts

@@ -21,6 +21,22 @@ export interface ValidateGridOptions {
     /** Extra template-level rules to run once the base grid is well-formed. */
     rules?: GridRule[];
 }
+/**
+ * Element-level TYPE registry — IDS_AND_REFERENCES.md §3.1, plus
+ * `VERIFICATION` (§3.7): block diagrams cross-reference the full
+ * hazard → risk-control → requirement → verification chain, and
+ * `VERIFICATION` is the terminal link in that chain.
+ *
+ * `FACTOR` and `ACTIVITY` are kept alongside their canonical replacements
+ * `DRIVER` and `ACTION` — both still-valid grandfathered/deprecated aliases
+ * per §3.1 and §6, not yet forced to migrate.
+ *
+ * `UNIT`/`EMPLOYEE` (replaced by `ACTOR`, removed from canon 2026-05-29) and
+ * `ISSUE` (retired 2026-06-07, no replacement TYPE — see methodology
+ * `docs/decisions/2026-06-07-retire-model-issue-type.md`) are deliberately
+ * not carried forward. `STAGE` was never a canonical TYPE.
+ */
+export declare const REGISTERED_ELEMENT_TYPES: Set<string>;
 export declare function validateNestedBlocks(input: unknown): ValidationResult;
 /** Matrix subset (§4a): validate a `grid:` root document — BL-021..BL-025. */
 export declare function validateGrid(input: unknown, options?: ValidateGridOptions): ValidationResult;

package/dist/blocks/validate.js

@@ -18,23 +18,55 @@ const CANONICAL_ID_RE = /^[A-Z][A-Z0-9_]*(-[A-Z0-9][A-Z0-9_]*)+-\d+$/;
  * dot, so we recognise it separately.
  */
 const CAPABILITY_ID_RE = /^CAPABILITY-[VH]\d+(\.\d+){0,2}$/;
-/** Element-level TYPE registry — IDS_AND_REFERENCES.md §3.1. */
-const REGISTERED_ELEMENT_TYPES = new Set([
+/**
+ * Element-level TYPE registry — IDS_AND_REFERENCES.md §3.1, plus
+ * `VERIFICATION` (§3.7): block diagrams cross-reference the full
+ * hazard → risk-control → requirement → verification chain, and
+ * `VERIFICATION` is the terminal link in that chain.
+ *
+ * `FACTOR` and `ACTIVITY` are kept alongside their canonical replacements
+ * `DRIVER` and `ACTION` — both still-valid grandfathered/deprecated aliases
+ * per §3.1 and §6, not yet forced to migrate.
+ *
+ * `UNIT`/`EMPLOYEE` (replaced by `ACTOR`, removed from canon 2026-05-29) and
+ * `ISSUE` (retired 2026-06-07, no replacement TYPE — see methodology
+ * `docs/decisions/2026-06-07-retire-model-issue-type.md`) are deliberately
+ * not carried forward. `STAGE` was never a canonical TYPE.
+ */
+export const REGISTERED_ELEMENT_TYPES = new Set([
+    'DRIVER',
     'FACTOR',
     'GOAL',
     'CHANGE',
+    'ACTION',
     'ACTIVITY',
     'CAPABILITY',
     'PROCESS',
+    'STEP',
     'PRODUCT',
     'APPLICATION',
     'INTEGRATION',
     'ROLE',
-    'UNIT',
-    'EMPLOYEE',
+    'ACTOR',
+    'LOCATION',
+    'BUSINESS_SERVICE',
     'SCENARIO',
-    'ISSUE',
-    'STAGE',
+    'EQUIPMENT',
+    'NODE',
+    'TECHNOLOGY_SERVICE',
+    'BUSINESS_OBJECT',
+    'RULE',
+    'REGISTRY',
+    'CONSTRAINT',
+    'REQUIREMENT',
+    'STAKEHOLDER',
+    'ASSESSMENT',
+    'HAZARD',
+    'RISK_CONTROL',
+    'TARGET_STATE',
+    'REL',
+    'MILESTONE',
+    'VERIFICATION',
 ]);
 /**
  * Recommended maximum nesting depth (1-indexed). The spec warns at depth 6+;

package/dist/webview/render-activities.d.ts

@@ -12,13 +12,16 @@ export declare const ACTIVITIES_NETWORK_CSS = "\n  .act-node { fill: var(--ts-la
 export declare const ACTIVITIES_NETWORK_DEFS = "<defs>\n  <marker id=\"arrow\" markerWidth=\"8\" markerHeight=\"8\" refX=\"8\" refY=\"3\" orient=\"auto\">\n    <path d=\"M0,0 L0,6 L8,3 z\" class=\"arrow-fill\"/>\n  </marker>\n  <marker id=\"arrow-crit\" markerWidth=\"8\" markerHeight=\"8\" refX=\"8\" refY=\"3\" orient=\"auto\">\n    <path d=\"M0,0 L0,6 L8,3 z\" class=\"arrow-fill-critical\"/>\n  </marker>\n</defs>";
 /**
  * Extra top padding (px) a network-view canvas must add so skip-edge bows
- * (see `blockingNodes`/`bowY` above) never draw above the SVG's y=0 and get
- * clipped. `oyBase` is the canvas's Y offset *before* this padding — the
- * historical `-bounds.y + N_PAD + titleH` both hosts compute — since a bow
- * near the topmost row can reach above the diagram's own node bounds.
- * Callers add the returned value to both `oyBase` and the canvas height.
+ * (see `blockingNodes`/`bowY` above) never rise above the diagram's own node
+ * bounds (`layout.bounds.y`). Node rows shift down by the returned amount to
+ * make room for the bow within the diagram area; the title block — drawn
+ * separately, above that area, at a fixed position independent of this pad —
+ * is left undisturbed, so the bow can never climb into the reserved title
+ * zone (the earlier version floored against the canvas's literal y=0, which
+ * let a tall bow draw straight through the title text sitting between 0 and
+ * the diagram's un-padded top).
  */
-export declare function computeNetworkTopPad(layout: ActivitiesLayout, oyBase: number): number;
+export declare function computeNetworkTopPad(layout: ActivitiesLayout): number;
 /**
  * Canonical Network (PSND) body — the node rects and edge paths that go inside
  * the `<svg>`, shared verbatim by the VS Code preview and the host-neutral

package/dist/webview/render-activities.js

@@ -85,13 +85,16 @@ function bowY(blockers) {
 }
 /**
  * Extra top padding (px) a network-view canvas must add so skip-edge bows
- * (see `blockingNodes`/`bowY` above) never draw above the SVG's y=0 and get
- * clipped. `oyBase` is the canvas's Y offset *before* this padding — the
- * historical `-bounds.y + N_PAD + titleH` both hosts compute — since a bow
- * near the topmost row can reach above the diagram's own node bounds.
- * Callers add the returned value to both `oyBase` and the canvas height.
+ * (see `blockingNodes`/`bowY` above) never rise above the diagram's own node
+ * bounds (`layout.bounds.y`). Node rows shift down by the returned amount to
+ * make room for the bow within the diagram area; the title block — drawn
+ * separately, above that area, at a fixed position independent of this pad —
+ * is left undisturbed, so the bow can never climb into the reserved title
+ * zone (the earlier version floored against the canvas's literal y=0, which
+ * let a tall bow draw straight through the title text sitting between 0 and
+ * the diagram's un-padded top).
  */
-export function computeNetworkTopPad(layout, oyBase) {
+export function computeNetworkTopPad(layout) {
     const nodeMap = new Map(layout.nodes.map((n) => [n.id, n]));
     let pad = 0;
     for (const e of layout.edges) {
@@ -102,7 +105,7 @@ export function computeNetworkTopPad(layout, oyBase) {
         const blockers = blockingNodes(layout.nodes, s, t);
         if (blockers.length === 0)
             continue;
-        const shortfall = -(oyBase + bowY(blockers));
+        const shortfall = layout.bounds.y - bowY(blockers);
         if (shortfall > pad)
             pad = shortfall;
     }
@@ -209,7 +212,7 @@ export function renderActivitiesSvg(doc, options = {}) {
     const cpm = computeCpm(renderDoc.activities ?? []);
     const titleH = title ? 24 : 0;
     const oyBase = -layout.bounds.y + N_PAD + titleH;
-    const topPad = computeNetworkTopPad(layout, oyBase);
+    const topPad = computeNetworkTopPad(layout);
     const w = layout.bounds.width + N_PAD * 2;
     const h = layout.bounds.height + N_PAD * 2 + titleH + topPad;
     const ox = -layout.bounds.x + N_PAD;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@transitrix/diagrams",
-  "version": "1.8.19",
+  "version": "1.8.20",
   "type": "module",
   "description": "Shared rendering, validation, and pure mutations for Transitrix custom diagram formats.",
   "license": "MIT",

package/src/blocks/validate.ts

@@ -45,23 +45,55 @@ const CANONICAL_ID_RE = /^[A-Z][A-Z0-9_]*(-[A-Z0-9][A-Z0-9_]*)+-\d+$/;
  */
 const CAPABILITY_ID_RE = /^CAPABILITY-[VH]\d+(\.\d+){0,2}$/;
 
-/** Element-level TYPE registry — IDS_AND_REFERENCES.md §3.1. */
-const REGISTERED_ELEMENT_TYPES = new Set<string>([
+/**
+ * Element-level TYPE registry — IDS_AND_REFERENCES.md §3.1, plus
+ * `VERIFICATION` (§3.7): block diagrams cross-reference the full
+ * hazard → risk-control → requirement → verification chain, and
+ * `VERIFICATION` is the terminal link in that chain.
+ *
+ * `FACTOR` and `ACTIVITY` are kept alongside their canonical replacements
+ * `DRIVER` and `ACTION` — both still-valid grandfathered/deprecated aliases
+ * per §3.1 and §6, not yet forced to migrate.
+ *
+ * `UNIT`/`EMPLOYEE` (replaced by `ACTOR`, removed from canon 2026-05-29) and
+ * `ISSUE` (retired 2026-06-07, no replacement TYPE — see methodology
+ * `docs/decisions/2026-06-07-retire-model-issue-type.md`) are deliberately
+ * not carried forward. `STAGE` was never a canonical TYPE.
+ */
+export const REGISTERED_ELEMENT_TYPES = new Set<string>([
+  'DRIVER',
   'FACTOR',
   'GOAL',
   'CHANGE',
+  'ACTION',
   'ACTIVITY',
   'CAPABILITY',
   'PROCESS',
+  'STEP',
   'PRODUCT',
   'APPLICATION',
   'INTEGRATION',
   'ROLE',
-  'UNIT',
-  'EMPLOYEE',
+  'ACTOR',
+  'LOCATION',
+  'BUSINESS_SERVICE',
   'SCENARIO',
-  'ISSUE',
-  'STAGE',
+  'EQUIPMENT',
+  'NODE',
+  'TECHNOLOGY_SERVICE',
+  'BUSINESS_OBJECT',
+  'RULE',
+  'REGISTRY',
+  'CONSTRAINT',
+  'REQUIREMENT',
+  'STAKEHOLDER',
+  'ASSESSMENT',
+  'HAZARD',
+  'RISK_CONTROL',
+  'TARGET_STATE',
+  'REL',
+  'MILESTONE',
+  'VERIFICATION',
 ]);
 
 /**

package/src/webview/render-activities.ts

@@ -100,13 +100,16 @@ function bowY(blockers: ActivityLayoutNode[]): number {
 
 /**
  * Extra top padding (px) a network-view canvas must add so skip-edge bows
- * (see `blockingNodes`/`bowY` above) never draw above the SVG's y=0 and get
- * clipped. `oyBase` is the canvas's Y offset *before* this padding — the
- * historical `-bounds.y + N_PAD + titleH` both hosts compute — since a bow
- * near the topmost row can reach above the diagram's own node bounds.
- * Callers add the returned value to both `oyBase` and the canvas height.
+ * (see `blockingNodes`/`bowY` above) never rise above the diagram's own node
+ * bounds (`layout.bounds.y`). Node rows shift down by the returned amount to
+ * make room for the bow within the diagram area; the title block — drawn
+ * separately, above that area, at a fixed position independent of this pad —
+ * is left undisturbed, so the bow can never climb into the reserved title
+ * zone (the earlier version floored against the canvas's literal y=0, which
+ * let a tall bow draw straight through the title text sitting between 0 and
+ * the diagram's un-padded top).
  */
-export function computeNetworkTopPad(layout: ActivitiesLayout, oyBase: number): number {
+export function computeNetworkTopPad(layout: ActivitiesLayout): number {
   const nodeMap = new Map(layout.nodes.map((n) => [n.id, n]));
   let pad = 0;
   for (const e of layout.edges) {
@@ -115,7 +118,7 @@ export function computeNetworkTopPad(layout: ActivitiesLayout, oyBase: number):
     if (!s || !t) continue;
     const blockers = blockingNodes(layout.nodes, s, t);
     if (blockers.length === 0) continue;
-    const shortfall = -(oyBase + bowY(blockers));
+    const shortfall = layout.bounds.y - bowY(blockers);
     if (shortfall > pad) pad = shortfall;
   }
   return pad;
@@ -278,7 +281,7 @@ export function renderActivitiesSvg(doc: ActivityDoc, options: RenderActivitiesO
   const cpm = computeCpm(renderDoc.activities ?? []);
   const titleH = title ? 24 : 0;
   const oyBase = -layout.bounds.y + N_PAD + titleH;
-  const topPad = computeNetworkTopPad(layout, oyBase);
+  const topPad = computeNetworkTopPad(layout);
   const w = layout.bounds.width + N_PAD * 2;
   const h = layout.bounds.height + N_PAD * 2 + titleH + topPad;
   const ox = -layout.bounds.x + N_PAD;