@diagrammo/dgmo 0.92.1 → 0.94.0

package/docs/ai-integration.md

@@ -112,7 +112,7 @@ Valid markup is the floor, not the goal. A good diagram reads at a glance. Apply
 - **Always title it.** Every diagram gets a short title on the type-declaration line (`flowchart Checkout Flow`, `sequence Checkout`, `boxes-and-lines Service Map`) so it is self-describing — never leave the bare type keyword alone. Infer a fitting title from the request when the user gives none.
   <!-- TITLE end -->
   <!-- CATEGORIZE start -->
-- **Categorize and color — by default, not only when obvious.** Before drawing, find the axis that sorts the items into kinds and color by it: layer (frontend / backend / data), role (client / service / datastore), trust zone (internal / external / third-party), status (done / active / blocked), owner/team, or read-path vs write-path. Almost every diagram has such an axis — actively look for one rather than leaving everything monochrome. Express it with a **tag group**, never ad-hoc per-node colors: declare `tag <Axis> as t` (the name is a single word — `tag TrustZone as tz` — or quote a multi-word name: `tag "Trust Zone" as tz`), indent the category values (a trailing color is optional — bare values auto-pick a palette color), set `active-tag <Axis>` in the header — after the tag group and before the first element, because a type such as c4 refuses it after content — then assign each item `Node t: <Category>` (see the tag-group syntax in the per-type section below). **Bracket, block, body, event-line, family and sketch** take the tag group but no `active-tag` line — declare the group and stop there; on event-line, family and sketch the line would be drawn as an element. **Class, flowchart, whiteboard, wireframe, raci, cycle, pyramid, ring, sankey, tech-radar, venn, version-control, wordcloud, arc, bar, clock, countdown, funnel, function, goal, heatmap, line, pie, polar-area, quadrant, radar, scatter and slope** take no tag group at all — skip this rule for them. Most report the lines; cycle, pyramid, ring, sankey, venn, version-control and wordcloud read them as content, and flowchart and tech-radar drop them without a word. Only the 11 named palette colors exist, and they re-resolve per palette/theme. Color the grouping so the categories — and the boundaries between them — read at a glance. **Buckets, not name tags — never 1:1.** A tag group must have _fewer_ values than it has members: each color should bucket two or more items so the palette compresses the diagram into a few meaningful kinds (aim for ~2–4 categories, and keep distinct colors well under half the item count). If you find yourself giving nearly every item its own value, you've enumerated, not categorized — merge the singletons up a level until each color groups at least two (a `cache` and a `database` are both `datastore`; a caller and a gateway are both `client`; two microservices are both `service`). One color per item is the same visual noise as random colors — the grouping only earns its place when a color means "these belong together." Leave items uncolored only when they genuinely form a single undifferentiated kind, or the user asked for no color.
+- **Categorize and color — by default, not only when obvious.** Before drawing, find the axis that sorts the items into kinds and color by it: layer (frontend / backend / data), role (client / service / datastore), trust zone (internal / external / third-party), status (done / active / blocked), owner/team, or read-path vs write-path. Almost every diagram has such an axis — actively look for one rather than leaving everything monochrome. Express it with a **tag group**, never ad-hoc per-node colors: declare `tag <Axis> as t` (the name is a single word — `tag TrustZone as tz` — or quote a multi-word name: `tag "Trust Zone" as tz`), indent the category values (a trailing color is optional — bare values auto-pick a palette color), set `active-tag <Axis>` in the header — after the tag group and before the first element, because a type such as c4 refuses it after content — then assign each item `Node t: <Category>` (see the tag-group syntax in the per-type section below). **Bracket, block, body, event-line, family, sketch and whiteboard** take the tag group but no `active-tag` line — declare the group and stop there; on event-line, family and sketch the line would be drawn as an element. **Class, flowchart, wireframe, raci, cycle, pyramid, ring, sankey, tech-radar, venn, version-control, wordcloud, arc, bar, clock, countdown, funnel, function, goal, heatmap, line, pie, polar-area, quadrant, radar, scatter and slope** take no tag group at all — skip this rule for them. Most report the lines; cycle, pyramid, ring, sankey, venn, version-control and wordcloud read them as content, and flowchart and tech-radar drop them without a word. Only the 11 named palette colors exist, and they re-resolve per palette/theme. Color the grouping so the categories — and the boundaries between them — read at a glance. **Buckets, not name tags — never 1:1.** A tag group must have _fewer_ values than it has members: each color should bucket two or more items so the palette compresses the diagram into a few meaningful kinds (aim for ~2–4 categories, and keep distinct colors well under half the item count). If you find yourself giving nearly every item its own value, you've enumerated, not categorized — merge the singletons up a level until each color groups at least two (a `cache` and a `database` are both `datastore`; a caller and a gateway are both `client`; two microservices are both `service`). One color per item is the same visual noise as random colors — the grouping only earns its place when a color means "these belong together." Leave items uncolored only when they genuinely form a single undifferentiated kind, or the user asked for no color.
 <!-- CATEGORIZE end -->
 - **Keep labels short.** A few words per node. Move detail into notes or metadata, never a full sentence inside a label.
 - **Let the defaults show.** Don't add `no-*` opt-outs unless the user asked to hide or disable something — they strip helpful labels, values, and color.

package/docs/language-reference.md

@@ -98,7 +98,7 @@ Valid markup is the floor, not the goal. A good diagram reads at a glance. Apply
 - **Always title it.** Every diagram gets a short title on the type-declaration line (`flowchart Checkout Flow`, `sequence Checkout`, `boxes-and-lines Service Map`) so it is self-describing — never leave the bare type keyword alone. Infer a fitting title from the request when the user gives none.
   <!-- TITLE end -->
   <!-- CATEGORIZE start -->
-- **Categorize and color — by default, not only when obvious.** Before drawing, find the axis that sorts the items into kinds and color by it: layer (frontend / backend / data), role (client / service / datastore), trust zone (internal / external / third-party), status (done / active / blocked), owner/team, or read-path vs write-path. Almost every diagram has such an axis — actively look for one rather than leaving everything monochrome. Express it with a **tag group**, never ad-hoc per-node colors: declare `tag <Axis> as t` (the name is a single word — `tag TrustZone as tz` — or quote a multi-word name: `tag "Trust Zone" as tz`), indent the category values (a trailing color is optional — bare values auto-pick a palette color), set `active-tag <Axis>` in the header — after the tag group and before the first element, because a type such as c4 refuses it after content — then assign each item `Node t: <Category>` (see the tag-group syntax in the per-type section below). **Bracket, block, body, event-line, family and sketch** take the tag group but no `active-tag` line — declare the group and stop there; on event-line, family and sketch the line would be drawn as an element. **Class, flowchart, whiteboard, wireframe, raci, cycle, pyramid, ring, sankey, tech-radar, venn, version-control, wordcloud, arc, bar, clock, countdown, funnel, function, goal, heatmap, line, pie, polar-area, quadrant, radar, scatter and slope** take no tag group at all — skip this rule for them. Most report the lines; cycle, pyramid, ring, sankey, venn, version-control and wordcloud read them as content, and flowchart and tech-radar drop them without a word. Only the 11 named palette colors exist, and they re-resolve per palette/theme. Color the grouping so the categories — and the boundaries between them — read at a glance. **Buckets, not name tags — never 1:1.** A tag group must have _fewer_ values than it has members: each color should bucket two or more items so the palette compresses the diagram into a few meaningful kinds (aim for ~2–4 categories, and keep distinct colors well under half the item count). If you find yourself giving nearly every item its own value, you've enumerated, not categorized — merge the singletons up a level until each color groups at least two (a `cache` and a `database` are both `datastore`; a caller and a gateway are both `client`; two microservices are both `service`). One color per item is the same visual noise as random colors — the grouping only earns its place when a color means "these belong together." Leave items uncolored only when they genuinely form a single undifferentiated kind, or the user asked for no color.
+- **Categorize and color — by default, not only when obvious.** Before drawing, find the axis that sorts the items into kinds and color by it: layer (frontend / backend / data), role (client / service / datastore), trust zone (internal / external / third-party), status (done / active / blocked), owner/team, or read-path vs write-path. Almost every diagram has such an axis — actively look for one rather than leaving everything monochrome. Express it with a **tag group**, never ad-hoc per-node colors: declare `tag <Axis> as t` (the name is a single word — `tag TrustZone as tz` — or quote a multi-word name: `tag "Trust Zone" as tz`), indent the category values (a trailing color is optional — bare values auto-pick a palette color), set `active-tag <Axis>` in the header — after the tag group and before the first element, because a type such as c4 refuses it after content — then assign each item `Node t: <Category>` (see the tag-group syntax in the per-type section below). **Bracket, block, body, event-line, family, sketch and whiteboard** take the tag group but no `active-tag` line — declare the group and stop there; on event-line, family and sketch the line would be drawn as an element. **Class, flowchart, wireframe, raci, cycle, pyramid, ring, sankey, tech-radar, venn, version-control, wordcloud, arc, bar, clock, countdown, funnel, function, goal, heatmap, line, pie, polar-area, quadrant, radar, scatter and slope** take no tag group at all — skip this rule for them. Most report the lines; cycle, pyramid, ring, sankey, venn, version-control and wordcloud read them as content, and flowchart and tech-radar drop them without a word. Only the 11 named palette colors exist, and they re-resolve per palette/theme. Color the grouping so the categories — and the boundaries between them — read at a glance. **Buckets, not name tags — never 1:1.** A tag group must have _fewer_ values than it has members: each color should bucket two or more items so the palette compresses the diagram into a few meaningful kinds (aim for ~2–4 categories, and keep distinct colors well under half the item count). If you find yourself giving nearly every item its own value, you've enumerated, not categorized — merge the singletons up a level until each color groups at least two (a `cache` and a `database` are both `datastore`; a caller and a gateway are both `client`; two microservices are both `service`). One color per item is the same visual noise as random colors — the grouping only earns its place when a color means "these belong together." Leave items uncolored only when they genuinely form a single undifferentiated kind, or the user asked for no color.
 <!-- CATEGORIZE end -->
 - **Keep labels short.** A few words per node. Move detail into notes or metadata, never a full sentence inside a label.
 - **Let the defaults show.** Don't add `no-*` opt-outs unless the user asked to hide or disable something — they strip helpful labels, values, and color.
@@ -215,7 +215,7 @@ tag GroupName as <alias>
 - Must appear before diagram content
 - Bare shorthand is not an alias (TD-18): `tag Priority p` declares a group _named_ "Priority p" — no alias registers, so `p:` assignments silently miss. The parser warns on this shape (spaced name, no alias, alias-shaped trailing word), suggesting `tag Priority as p` or a quoted name
 
-**Diagram types that support tags**: the tag model is near-universal across the structural types — sequence, infra, org, c4, er, kanban, gantt, sitemap, timeline, boxes-and-lines, state (§5.7), pert, swimlane, mindmap, journey-map, event-line, treemap, map, block, sketch, bracket and family all accept `tag <Group> as <alias>` blocks. Check the per-type Options section for the exact directive set; if a type draws a tag legend, it takes tags. **Flowchart, wireframe, raci and class take no tags** — a `tag` block or `active-tag` on any of them is ignored with a warning, because what an element looks like is fixed by what it is (a flowchart's shape, a wireframe's state keywords, a class's trailing colour word) or by the roles (raci).
+**Diagram types that support tags**: the tag model is near-universal across the structural types — sequence, infra, org, c4, er, kanban, gantt, sitemap, timeline, boxes-and-lines, state (§5.7), pert, swimlane, mindmap, journey-map, event-line, treemap, map, block, sketch, bracket, family and whiteboard all accept `tag <Group> as <alias>` blocks (a whiteboard's names its colours — §24Ea). Check the per-type Options section for the exact directive set; if a type draws a tag legend, it takes tags. **Flowchart, wireframe, raci and class take no tags** — a `tag` block or `active-tag` on any of them is ignored with a warning, because what an element looks like is fixed by what it is (a flowchart's shape, a wireframe's state keywords, a class's trailing colour word) or by the roles (raci).
 
 ### 1.4 Same-Line Metadata
 
@@ -4066,6 +4066,19 @@ An `arrow` takes `heads: both` for a head at each end. Arrows and lines take `be
 
 `color:` takes a palette **name**: `ink` (the default, never written — the theme's text colour, near-black on light and near-white on dark), `red`, `green`, `blue`, `teal`, `purple`, `orange`, `yellow`, `cyan`, `gray`. Each takes the palette's own light or dark shade. No hex values. A `note` defaults to `yellow` instead of `ink`, and writes `color:` only when it is not yellow.
 
+A `tag` block gives a colour a **meaning**. Each entry is a name and the colour it names; shapes keep their own `color:`, so the name attaches to the colour, never to a shape:
+
+```
+whiteboard Launch plan
+tag Meaning
+  Blocked red
+  Done green
+rectangle Legal review at: 0 0, size: 160 80, color: red
+rectangle Copy at: 200 0, size: 160 80, color: green
+```
+
+With two or more colours on the board, a legend sits centred above it, below the title, one dot per colour. A colour with an entry shows its name; while no colour is named the legend is drawn faintly, as bare dots. Under two colours there is no legend. `ink` is no colour, and a note in its default yellow does not count. An entry must end with one of the nine colour names, or it is ignored with a warning. Only the first `tag` block is shown.
+
 ### Images
 
 An image whose ref cannot be loaded — a local file that is not there, or a copied fence — draws a plain box at its size labelled _image not uploaded_. It is never an error.
@@ -4654,6 +4667,8 @@ The directive set is **13, all colon-free**: six naming intent the renderer can'
 
 A pointer to a diagram published at Diagrammo Cloud — the file holds no drawing of its own, and whoever opens it sees the publisher's current version. Renders as a reference card until a host resolves it.
 
+**Where the link comes from.** In the Diagrammo app, open the diagram and press Share on the left rail (or ⌘E / Ctrl+E), then "Show on the web" → "Show"; or right-click the diagram in the file list and choose "Show and copy link". Either route copies the link to the clipboard. A diagram that is shown on the web wears an amber globe; pressing the lit amber globe on the left rail copies the link again.
+
 **Do not author one from scratch.** A pointer needs a diagram id only the publisher can hand out, so it arrives by being saved from a shared link. It is not offered in any chart-type picker for that reason.
 
 Two forms. The titled form names the diagram and carries a `url` directive:
@@ -4669,6 +4684,12 @@ The shorthand form is one line, and is what a docs-site fence contains:
 live-link dgm_01M1JBN56CAVS728HPWDACVNMC
 ```
 
+In a docs-site or Obsidian fence the bare link on a line of its own does the same job:
+
+```
+https://online.diagrammo.app/d/dgm_01M1JBN56CAVS728HPWDACVNMC
+```
+
 The id may be the whole share link instead — `live-link ` followed by a paste resolves exactly as the id does:
 
 ```

package/gallery/fixtures/whiteboard.dgmo

@@ -1,4 +1,7 @@
 whiteboard Login ideas
+tag Meaning
+  Open question red
+  Chosen green
 rectangle Sign in at: 60 60, size: 180 70
 ellipse OAuth? at: 345 53, size: 170 84, color: blue
 arrow from: 150 95, to: 430 95, heads: both

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@diagrammo/dgmo",
-  "version": "0.92.1",
+  "version": "0.94.0",
   "description": "DGMO diagram markup language — parser, renderer, and color system",
   "license": "MIT",
   "author": "Diagrammo LLC",
@@ -77,10 +77,6 @@
     "docs/*.md",
     "gallery/fixtures"
   ],
-  "sideEffects": [
-    "./src/palettes/*.ts",
-    "./dist/palettes/*"
-  ],
   "scripts": {
     "codegen": "lezer-generator src/editor/dgmo.grammar -o src/editor/dgmo.grammar.js",
     "fonts": "node scripts/build-fonts.mjs",
@@ -148,7 +144,7 @@
   },
   "pnpm": {
     "overrides": {
-      "undici": "^7.29.1"
+      "undici": "^7.30.1"
     }
   },
   "devDependencies": {

package/dist/chunk-3Y63RFJL.js

@@ -1,75 +0,0 @@
-import {
-  extractColor,
-  measureIndent
-} from "./chunk-TIIZIAGS.js";
-import {
-  makeDgmoError
-} from "./chunk-BYU54C3S.js";
-
-// src/utils/notes/parse.ts
-function parseNoteHeader(rest) {
-  const t = rest.trim();
-  const quoted = t.match(/^"([^"]+)"\s*(.*)$/);
-  if (quoted) {
-    return { ref: quoted[1].trim(), inlineBody: quoted[2].trim() };
-  }
-  const m = t.match(/^(\S+)\s*(.*)$/);
-  if (m) {
-    return { ref: m[1], inlineBody: m[2].trim() };
-  }
-  return { ref: t, inlineBody: "" };
-}
-function collectNoteBody(lines, noteIndex, noteIndent, inlineBody) {
-  const parts = [];
-  if (inlineBody) parts.push(inlineBody);
-  let lastIndex = noteIndex;
-  let endLineNumber = noteIndex + 1;
-  for (let j = noteIndex + 1; j < lines.length; j++) {
-    const raw = lines[j];
-    const trimmed = raw.trim();
-    if (!trimmed) break;
-    if (measureIndent(raw) <= noteIndent) break;
-    parts.push(trimmed);
-    lastIndex = j;
-    endLineNumber = j + 1;
-  }
-  return { body: parts.join("\n"), endLineNumber, lastIndex };
-}
-function tryCollectNote(lines, index, indent, palette, diagnostics) {
-  const trimmed = lines[index].trim();
-  const m = trimmed.match(/^note\s+(.+)$/i);
-  if (!m || /^note\s+->/i.test(trimmed)) return null;
-  const lineNumber = index + 1;
-  const { label: headerNoColor, color } = extractColor(
-    m[1],
-    palette,
-    diagnostics,
-    lineNumber
-  );
-  const { ref, inlineBody } = parseNoteHeader(headerNoColor);
-  const collected = collectNoteBody(lines, index, indent, inlineBody);
-  if (!collected.body.trim()) {
-    diagnostics.push(
-      makeDgmoError(
-        lineNumber,
-        `Note on "${ref}" has no text \u2014 ignored.`,
-        "warning"
-      )
-    );
-    return { lastIndex: collected.lastIndex };
-  }
-  return {
-    note: {
-      ref,
-      body: collected.body,
-      ...color && { color },
-      lineNumber,
-      endLineNumber: collected.endLineNumber
-    },
-    lastIndex: collected.lastIndex
-  };
-}
-
-export {
-  tryCollectNote
-};

package/dist/chunk-5DH3KYFH.js

@@ -1,20 +0,0 @@
-// src/utils/note-box/constants.ts
-var NOTE_MAX_W = 200;
-var NOTE_FOLD = 10;
-var NOTE_PAD_H = 8;
-var NOTE_PAD_V = 6;
-var NOTE_FONT_SIZE = 10;
-var NOTE_LINE_H = 14;
-var NOTE_GAP = 22;
-var NOTE_BULLET_INDENT = 10;
-
-export {
-  NOTE_MAX_W,
-  NOTE_FOLD,
-  NOTE_PAD_H,
-  NOTE_PAD_V,
-  NOTE_FONT_SIZE,
-  NOTE_LINE_H,
-  NOTE_GAP,
-  NOTE_BULLET_INDENT
-};

package/dist/chunk-O753JUEZ.js

@@ -1,67 +0,0 @@
-import {
-  normalizeName
-} from "./chunk-NOTA6TEI.js";
-import {
-  makeDgmoError,
-  suggest
-} from "./chunk-BYU54C3S.js";
-
-// src/utils/notes/resolve.ts
-function resolveNotes(notes, targets, diagnostics) {
-  const byNodeId = /* @__PURE__ */ new Map();
-  if (notes.length === 0) return byNodeId;
-  const byNormLabel = /* @__PURE__ */ new Map();
-  for (const t of targets) {
-    const key = normalizeName(t.label);
-    const arr = byNormLabel.get(key);
-    if (arr) arr.push(t);
-    else byNormLabel.set(key, [t]);
-  }
-  for (const note of notes) {
-    const matches = byNormLabel.get(normalizeName(note.ref));
-    if (!matches || matches.length === 0) {
-      if (diagnostics) {
-        const hint = suggest(
-          note.ref,
-          targets.map((t) => t.label)
-        );
-        diagnostics.push(
-          makeDgmoError(
-            note.lineNumber,
-            `Note references unknown node id "${note.ref}".${hint ? " " + hint : ""}`,
-            "error"
-          )
-        );
-      }
-      continue;
-    }
-    const target = matches[0];
-    if (matches.length > 1 && diagnostics) {
-      diagnostics.push(
-        makeDgmoError(
-          note.lineNumber,
-          `Note ref "${note.ref}" matches ${matches.length} nodes; attaching to the first.`,
-          "warning"
-        )
-      );
-    }
-    if (byNodeId.has(target.id)) {
-      if (diagnostics) {
-        diagnostics.push(
-          makeDgmoError(
-            note.lineNumber,
-            `Multiple notes on node "${target.label}"; keeping the first.`,
-            "warning"
-          )
-        );
-      }
-      continue;
-    }
-    byNodeId.set(target.id, note);
-  }
-  return byNodeId;
-}
-
-export {
-  resolveNotes
-};

package/dist/chunk-RJNZHFNG.js

@@ -1,51 +0,0 @@
-import {
-  NOTE_BULLET_INDENT,
-  NOTE_FOLD,
-  NOTE_FONT_SIZE,
-  NOTE_LINE_H,
-  NOTE_MAX_W,
-  NOTE_PAD_H,
-  NOTE_PAD_V
-} from "./chunk-5DH3KYFH.js";
-import {
-  wrapDescriptionLines
-} from "./chunk-NPWVOFB3.js";
-import {
-  measureText
-} from "./chunk-KAO7JL4I.js";
-
-// src/utils/note-box/metrics.ts
-function normalizeBulletLine(line) {
-  return line.replace(/^\s*[-*]\s+/, "\u2022 ");
-}
-function wrapNoteBody(body, textMaxWidth, fontSize = NOTE_FONT_SIZE) {
-  const sourceLines = body.split("\n").map(normalizeBulletLine);
-  return wrapDescriptionLines(
-    sourceLines,
-    textMaxWidth,
-    (s) => measureText(s, fontSize)
-  );
-}
-function noteBoxSize(body, opts = {}) {
-  const fontSize = opts.fontSize ?? NOTE_FONT_SIZE;
-  const maxW = opts.maxW ?? NOTE_MAX_W;
-  const textMaxWidth = maxW - NOTE_PAD_H * 2;
-  const lines = wrapNoteBody(body, textMaxWidth, fontSize);
-  let maxLineW = 0;
-  for (const line of lines) {
-    const indent = line.kind === "plain" ? 0 : NOTE_BULLET_INDENT;
-    const w = measureText(line.text, fontSize) + indent;
-    if (w > maxLineW) maxLineW = w;
-  }
-  const width = Math.min(
-    maxW,
-    Math.max(80, maxLineW + NOTE_PAD_H * 2 + NOTE_FOLD)
-  );
-  const height = Math.max(1, lines.length) * NOTE_LINE_H + NOTE_PAD_V * 2;
-  return { width, height, lines };
-}
-
-export {
-  wrapNoteBody,
-  noteBoxSize
-};

package/dist/chunk-Z6DXWULM.js

@@ -1,23 +0,0 @@
-// src/utils/safe-href.ts
-var ALLOWED_SCHEMES = ["http", "https", "mailto"];
-var SCHEME_RE = /^([a-z][a-z0-9+.-]*):/i;
-var LEADING_TRIM_RE = /^[\x00-\x20]+/;
-var URL_STRIP_RE = /[\x09\x0A\x0D]/g;
-function safeHref(url) {
-  if (typeof url !== "string") return null;
-  const trimmed = url.replace(URL_STRIP_RE, "").replace(LEADING_TRIM_RE, "");
-  if (trimmed.length === 0) return null;
-  const match = SCHEME_RE.exec(trimmed);
-  if (!match) {
-    return url;
-  }
-  const scheme = match[1].toLowerCase();
-  if (ALLOWED_SCHEMES.includes(scheme)) {
-    return url;
-  }
-  return null;
-}
-
-export {
-  safeHref
-};

package/dist/layout-5USEVQBY.js

@@ -1,25 +0,0 @@
-import {
-  layoutERDiagram
-} from "./chunk-MXAP37W6.js";
-import "./chunk-HXULJZA2.js";
-import "./chunk-X5BUX2GK.js";
-import "./chunk-EJS3K44P.js";
-import "./chunk-FTUMRSGT.js";
-import "./chunk-RJNZHFNG.js";
-import "./chunk-JRWUHLRP.js";
-import "./chunk-5DH3KYFH.js";
-import "./chunk-QT3KDDXK.js";
-import "./chunk-NPWVOFB3.js";
-import "./chunk-S7W75MIM.js";
-import "./chunk-Z6DXWULM.js";
-import "./chunk-ICLB27PZ.js";
-import "./chunk-O753JUEZ.js";
-import "./chunk-NOTA6TEI.js";
-import "./chunk-KAO7JL4I.js";
-import "./chunk-6GXLAKUH.js";
-import "./chunk-3J7O3CU6.js";
-import "./chunk-BYU54C3S.js";
-import "./chunk-YLJ4XMA6.js";
-export {
-  layoutERDiagram
-};

package/dist/layout-J3AGFZZ7.js

@@ -1,10 +0,0 @@
-import {
-  layoutSwimlane
-} from "./chunk-AUS7V54P.js";
-import "./chunk-EJS3K44P.js";
-import "./chunk-QT3KDDXK.js";
-import "./chunk-KAO7JL4I.js";
-import "./chunk-YLJ4XMA6.js";
-export {
-  layoutSwimlane
-};

package/dist/layout-S3RLVPH4.js

@@ -1,25 +0,0 @@
-import {
-  layoutClassDiagram
-} from "./chunk-5EBYPETE.js";
-import "./chunk-HXULJZA2.js";
-import "./chunk-X5BUX2GK.js";
-import "./chunk-EJS3K44P.js";
-import "./chunk-FTUMRSGT.js";
-import "./chunk-RJNZHFNG.js";
-import "./chunk-JRWUHLRP.js";
-import "./chunk-5DH3KYFH.js";
-import "./chunk-QT3KDDXK.js";
-import "./chunk-NPWVOFB3.js";
-import "./chunk-S7W75MIM.js";
-import "./chunk-Z6DXWULM.js";
-import "./chunk-ICLB27PZ.js";
-import "./chunk-O753JUEZ.js";
-import "./chunk-NOTA6TEI.js";
-import "./chunk-KAO7JL4I.js";
-import "./chunk-6GXLAKUH.js";
-import "./chunk-3J7O3CU6.js";
-import "./chunk-BYU54C3S.js";
-import "./chunk-YLJ4XMA6.js";
-export {
-  layoutClassDiagram
-};

package/dist/layout-WRG4APSJ.js

@@ -1,32 +0,0 @@
-import {
-  NODE_LABEL_LINE_HEIGHT,
-  layoutGraph,
-  wrapNodeLabel
-} from "./chunk-5SSTVFPX.js";
-import "./chunk-HXULJZA2.js";
-import "./chunk-X5BUX2GK.js";
-import "./chunk-EJS3K44P.js";
-import "./chunk-FTUMRSGT.js";
-import "./chunk-RJNZHFNG.js";
-import "./chunk-JRWUHLRP.js";
-import "./chunk-5DH3KYFH.js";
-import "./chunk-QT3KDDXK.js";
-import "./chunk-NPWVOFB3.js";
-import "./chunk-S7W75MIM.js";
-import "./chunk-Z6DXWULM.js";
-import "./chunk-ICLB27PZ.js";
-import "./chunk-NXMESY4J.js";
-import "./chunk-3Y63RFJL.js";
-import "./chunk-O753JUEZ.js";
-import "./chunk-NOTA6TEI.js";
-import "./chunk-TIIZIAGS.js";
-import "./chunk-KAO7JL4I.js";
-import "./chunk-6GXLAKUH.js";
-import "./chunk-3J7O3CU6.js";
-import "./chunk-BYU54C3S.js";
-import "./chunk-YLJ4XMA6.js";
-export {
-  NODE_LABEL_LINE_HEIGHT,
-  layoutGraph,
-  wrapNodeLabel
-};

package/dist/{chunk-DGUGE67L.js → chunk-CDYV46JE.js}

@@ -1,9 +1,6 @@
 import {
   buildSwatches
 } from "./chunk-T7NWBVSC.js";
-import {
-  now
-} from "./chunk-3DPOIW3W.js";
 import {
   fixedParts,
   fixedTimeCells,
@@ -14,6 +11,9 @@ import {
   workStatus,
   zoneParts
 } from "./chunk-A2RUBBVT.js";
+import {
+  now
+} from "./chunk-3DPOIW3W.js";
 import {
   FONT_FAMILY
 } from "./chunk-ICLB27PZ.js";

package/dist/{chunk-TKAB3FTK.js → chunk-DRQSB72S.js}

@@ -5,12 +5,17 @@ import {
   renderCollapseBar,
   renderNodeCard
 } from "./chunk-R2K5L4UA.js";
+import {
+  extractExportSvg,
+  runInExportContainer
+} from "./chunk-TOHTKLKE.js";
 import {
   ScaleContext
 } from "./chunk-24YPR5EH.js";
 import {
-  renderIntegratedLegend
-} from "./chunk-NMS5XSLX.js";
+  TITLE_FONT_SIZE,
+  TITLE_FONT_WEIGHT
+} from "./chunk-VLC6WNRD.js";
 import {
   CARD_RADIUS,
   COLLAPSE_BAR_HEIGHT,
@@ -29,22 +34,17 @@ import {
   SEPARATOR_GAP
 } from "./chunk-XCKNFFKM.js";
 import {
-  extractExportSvg,
-  runInExportContainer
-} from "./chunk-TOHTKLKE.js";
+  renderIntegratedLegend
+} from "./chunk-NMS5XSLX.js";
 import {
   getMaxLegendReservedHeight
 } from "./chunk-JILEYZ2V.js";
 import {
-  TITLE_FONT_SIZE,
-  TITLE_FONT_WEIGHT
-} from "./chunk-VLC6WNRD.js";
+  parseOrg
+} from "./chunk-5OTA2PUH.js";
 import {
   FONT_FAMILY
 } from "./chunk-ICLB27PZ.js";
-import {
-  parseOrg
-} from "./chunk-5OTA2PUH.js";
 import {
   resolveTagColor,
   tagAttrKey

package/dist/{chunk-ZKP77MB3.js → chunk-FVTYJUXR.js}

@@ -1,16 +1,16 @@
 import {
   appendArrowheadMarkers
 } from "./chunk-XBJJP2HN.js";
-import {
-  ARROWHEAD_HEIGHT,
-  ARROWHEAD_WIDTH,
-  EDGE_DASH
-} from "./chunk-XCKNFFKM.js";
 import {
   TITLE_FONT_SIZE,
   TITLE_FONT_WEIGHT,
   TITLE_Y
 } from "./chunk-VLC6WNRD.js";
+import {
+  ARROWHEAD_HEIGHT,
+  ARROWHEAD_WIDTH,
+  EDGE_DASH
+} from "./chunk-XCKNFFKM.js";
 import {
   FONT_FAMILY
 } from "./chunk-ICLB27PZ.js";

package/dist/{chunk-MA42PIGJ.js → chunk-H5NVCOEJ.js}

@@ -1,6 +1,10 @@
 import {
   familyCardRows
 } from "./chunk-IVKC4GID.js";
+import {
+  buildCoupleQuotient,
+  rankClasses
+} from "./chunk-QQJUTGQH.js";
 import {
   HEADER_HEIGHT,
   LABEL_FONT_SIZE,
@@ -8,10 +12,6 @@ import {
   META_LINE_HEIGHT,
   SEPARATOR_GAP
 } from "./chunk-XCKNFFKM.js";
-import {
-  buildCoupleQuotient,
-  rankClasses
-} from "./chunk-QQJUTGQH.js";
 import {
   measureText
 } from "./chunk-KAO7JL4I.js";

package/dist/{chunk-BEA4D7OS.js → chunk-IXHWS2HI.js}

@@ -1,12 +1,12 @@
 import {
   inferParticipantType
 } from "./chunk-C3Z4DX3V.js";
-import {
-  parseInArrowLabel
-} from "./chunk-N7VMGZCU.js";
 import {
   tryStripDescriptionKeyword
 } from "./chunk-IYULMRBE.js";
+import {
+  parseInArrowLabel
+} from "./chunk-N7VMGZCU.js";
 import {
   normalizeName
 } from "./chunk-NOTA6TEI.js";

package/dist/{chunk-SOHZDW6N.js → chunk-UXNA2H2V.js}

@@ -1,12 +1,12 @@
 import {
   GRAPH_DX
 } from "./chunk-TIVMAITN.js";
-import {
-  parseInArrowLabel
-} from "./chunk-N7VMGZCU.js";
 import {
   tryStripDescriptionKeyword
 } from "./chunk-IYULMRBE.js";
+import {
+  parseInArrowLabel
+} from "./chunk-N7VMGZCU.js";
 import {
   displayName,
   normalizeName

package/dist/{chunk-NO3UX6AP.js → chunk-V2NQV7VL.js}

@@ -1,12 +1,12 @@
-import {
-  EDGE_DASH,
-  HAIRLINE_DASH
-} from "./chunk-XCKNFFKM.js";
 import {
   TITLE_FONT_SIZE,
   TITLE_FONT_WEIGHT,
   TITLE_Y
 } from "./chunk-VLC6WNRD.js";
+import {
+  EDGE_DASH,
+  HAIRLINE_DASH
+} from "./chunk-XCKNFFKM.js";
 import {
   FONT_FAMILY
 } from "./chunk-ICLB27PZ.js";