@diagrammo/dgmo 0.96.0 → 0.98.0

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 whiteboard** take the tag group but no `active-tag` line — declare the group and stop there; on event-line and family 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 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 and whiteboard** take the tag group but no `active-tag` line — declare the group and stop there; on event-line 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.
@@ -125,6 +125,7 @@ Valid markup is the floor, not the goal. A good diagram reads at a glance. Apply
 | `family`          | family tree / genealogy: unions (couples), children, remarriage, adoption, GEDCOM-style metadata                                                              |
 | `bracket`         | single-elimination tournament bracket: winners auto-advance; seed the field for a day-0 skeleton or list results casually; two sides mirror to a championship |
 | `kanban`          | task-board columns                                                                                                                                            |
+| `swot`            | SWOT analysis: strengths, weaknesses, opportunities, threats in four fixed panels on helpful/harmful and internal/external axes                               |
 | `gantt`           | project scheduling with task dependencies and milestones                                                                                                      |
 | `pert`            | project network with three-point estimates and critical path                                                                                                  |
 | `swimlane`        | cross-functional process flow with lanes, phases and gateways (BPMN-style)                                                                                    |
@@ -214,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, 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).
+**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, bracket, family, swot 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
 
@@ -745,6 +746,8 @@ tag Security as sec
 
 Trailing `==` is optional.
 
+- **Fold a section** with a bare `collapsed` flag (or `collapsed: true`) after the divider: `== Checkout == collapsed`. The messages under it fold away until the next divider. `== collapsed ==` is a section named "collapsed".
+
 ### 2.5 Notes
 
 ```
@@ -772,6 +775,7 @@ Content formatting:
 - Links: `[text](url)` and bare URLs (auto-truncated in display)
 - The note ends where the indentation does — there is **no `end` terminator** (a bare `end` line is rejected).
 - Body lines join into one paragraph — a blank line or a trailing `\` keeps a break (§1.11).
+- **Fold a multi-line note** with a bare `collapsed` flag (or `collapsed: true`) at the end of its opening line: `note right of API collapsed`. It draws only the first body line, with the collapse bar. The flag counts only on a line followed by an indented body, so `note right of DB collapsed` with no body is a note that reads "collapsed".
 
 ### 2.6 Structural Blocks
 
@@ -791,7 +795,7 @@ parallel label
 ```
 
 - `parallel` requires a label
-- `else` is bare. A second condition is `else if <condition>`; `else <label>` is an error (`'else' does not take a label`)
+- `else` is bare. A second condition is `else if <condition>`; `else <label>` means the same and draws as `else if <label>`
 - Blocks nest via indentation
 - **No `end`/terminator keyword** — a block closes by dedenting (like multi-line notes). `end` and `activate`/`deactivate` are not dgmo syntax (a bare `end` line is rejected); activation is controlled by the `activations` option (§2.7), not per-message keywords.
 - **Tags apply to participants, not messages** — there is no per-message tag/color. Color a participant by category with `<Participant> <tagAlias>: <Value>` after declaring a `tag <Name> as <alias>` group (§1.3). Message text is just the arrow label.
@@ -1251,7 +1255,7 @@ Blackbeard
     Powder Monkey
 ```
 
-**Colon form only** — org has no bare trailing `collapsed` flag (mindmap/gantt/kanban do), because an org label is a person's name and a trailing bare word cannot be told from part of one. Only the literal `true` collapses; the key is reserved, so it never becomes part of a label and never draws as an attribute row. Honoured by every render path, so a folded chart survives save, export, share link and embed; applied before `focus`.
+**Colon form only on a person** — a person's line takes no bare trailing `collapsed` flag (mindmap/gantt/kanban do), because an org label is a person's name and a trailing bare word cannot be told from part of one. A `[Team]` header does take it (`[Gun Deck] collapsed`), since the `]` ends the name. Only the literal `true` collapses; the key is reserved, so it never becomes part of a label and never draws as an attribute row. Honoured by every render path, so a folded chart survives save, export, share link and embed; applied before `focus`.
 
 ### 6.5 Options
 
@@ -1635,6 +1639,8 @@ All permutations supported: node→group, group→node, group→group. Brackets
   Pricing Auth: Public
 ```
 
+**Collapse:** a bare `collapsed` flag at the end of a page line or a `[Container]` line (`Products collapsed`, `[Shop] collapsed`; legacy `collapsed: true`) starts it folded. Every render path draws the fold with the collapse bar and a hidden-page count. Only a page with children or a container with pages folds.
+
 ### 11.5 Node Descriptions
 
 ```
@@ -2008,6 +2014,7 @@ Henry Turner + Carina Smyth m: 1751
 - **Unknown/private person:** a bare `?` renders a faint, solid-bordered, name-only placeholder card; each `?` is a distinct person.
 - **`generations`** (option): draws a left gutter of Roman-numeral generation labels (`Gen I`, `Gen II`, …) plus subtle zebra shading behind alternating generations.
 - **`highlight <name>`** (directive): dims everyone outside that person's bloodline (ancestors + descendants + spouses stay lit).
+- **`active-tag <Group>`** (option): picks which tag group colours the cards when there are two or more (the built-in Sex group counts); `active-tag none` turns colouring off.
 - **Sex → color:** `sex: m` → blue, `sex: f` → purple, unset → gray (25% tint). An explicit `tag`/inline color overrides the sex color.
 - The union split cuts `m:` metadata first, THEN splits `+` within the name region — so a `+` inside a quoted name (`"Anne + Jack"`) or a metadata value never mis-splits. Per-side `key: value` metadata on a union line is not supported — declare the person standalone.
 
@@ -2147,6 +2154,8 @@ Nested groups (max depth 2):
 
 Group metadata cascades to children (node metadata overrides). Nodes already declared above can be referenced inside groups to assign membership.
 
+A bare `collapsed` flag on the group line (`[AWS] collapsed`, or `[AWS] color: blue, collapsed`; legacy `collapsed: true`) starts the group folded: it draws as one pill with a member count and the collapse bar, and its edges end on the pill.
+
 ### 13.5 Group-Targeted Edges
 
 Node-to-group and group-to-group edges use bracket syntax `[Group Name]`:
@@ -2356,6 +2365,8 @@ marker
   1718-07 Woodes Rogers arrives
 ```
 
+A bare `collapsed` flag on the lane line (`[Royal Navy] collapsed`, `[Royal Navy] blue collapsed`; legacy `collapsed: true`) starts the lane folded to one summary row with the collapse bar. Lanes fold only in the grouped swimlane layout.
+
 ### 14.6 Options (Space-Separated, NO Colon)
 
 ```
@@ -3507,6 +3518,8 @@ persona Captain Mara
 
 Phases are `[Bracket]` headers at indent 0. Steps live indented under them. Phases are optional — omit them for a continuous flat flow.
 
+A bare `collapsed` flag on the phase line (`[Research] collapsed`; legacy `collapsed: true`) starts the phase folded to a narrow column with the collapse bar. Nothing else may follow a phase header.
+
 ```
 [Research]
   Compare specs score: 4
@@ -4438,6 +4451,8 @@ Phase headers accept a trailing-token color for per-phase styling:
 
 The phase bar tints to a soft mix of the color over the background. Phases without a color fall back to the neutral gray bar.
 
+A bare `collapsed` flag on the phase line (`[Departure] collapsed`, `[Departure] teal collapsed`; legacy `collapsed: true`) starts the phase folded: its task rows hide and the band keeps its summary chips and the collapse bar.
+
 ### Display vs source ordering
 
 Markers in cells are always **rendered in canonical alphabet order** (`R A C I`, `R A S C I`, `D A C I`) regardless of source order. Source casing and order are preserved in the file; mutations operate on source order to keep round-trips byte-stable except for the cell that changed.
@@ -4668,6 +4683,77 @@ The one directive is `url`. There are no elements, no indentation and no colons.
 
 ---
 
+## 25B. SWOT Analysis
+
+<!-- TYPE:swot -->
+
+<!-- TIPS start -->
+
+**Styling tips:** Keep items to a few words, and let the section colours stand: a tag group earns its place only when the items sort into kinds, such as priority or owner. Declare the sections in any order; they always draw S W / O T.
+
+<!-- TIPS end -->
+
+### 25B.1 Declaration
+
+```
+swot [Title]
+```
+
+A SWOT analysis names four fixed panels: **strengths** and **weaknesses** are internal, **opportunities** and **threats** are external; strengths and opportunities help, weaknesses and threats harm. The panels always draw as a 2×2 in the order S W / O T, whatever order the source uses. At phone width the chart stays 2×2 and scales as a whole.
+
+### 25B.2 Sections and items
+
+```
+swot Tortuga Rum Co.
+tag Priority as p
+  High red
+  Low gray
+active-tag Priority
+x-label Helpful, Harmful
+y-label Internal, External
+
+strengths
+  Oldest still on the island p: Low
+  Crew of 40 sworn tasters
+    Trained in three ports
+weaknesses Soft spots yellow
+  One barrel supplier p: High
+opportunities
+  Navy rum ration contract
+threats
+  Royal Navy blockade
+```
+
+- **Section line**, indent 0: `strengths|weaknesses|opportunities|threats [Label] [color]`. The keyword is case-insensitive. The label defaults to Strengths, Weaknesses, Opportunities, Threats; the colour defaults to green, yellow, blue, red. Sections are keywords, never `[brackets]`.
+- **Item line**: indented under a section. Text is literal, so colons and commas stay (`Cost: 20% below rivals, margins thin`) unless the key is a declared tag alias (`p: High`). A colour word ending an item stays in the text (`Margins are in the red`). A leading `- ` is removed.
+- **Detail line**: indented one level under an item; drawn smaller and muted. There is one detail level.
+- A missing or empty section still draws its panel, with a muted "None listed".
+- Long text wraps and the panel grows; nothing is truncated. A row takes its tallest panel's height, and the two columns stay equal.
+
+### 25B.3 Options
+
+| Option              | Effect                                                                                                                                                                                                    |
+| ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `tag`, `active-tag` | A tag recolours an item's dot, tints its row faintly in the tag colour, and adds the legend. An untagged item keeps its section's colour and no tint, and the header bands always keep the section colour |
+| `x-label A, B`      | Column headers: a filled band over each column, in small caps. Default `Helpful, Harmful`                                                                                                                 |
+| `y-label A, B`      | Row headers: a filled rail beside each row, rotated, in small caps. Default `Internal, External`                                                                                                          |
+| `no-axes`           | Hide the axis labels. Wins over `x-label` and `y-label`                                                                                                                                                   |
+| `no-tint-items`     | Don't tint tagged rows; the dot alone carries the tag                                                                                                                                                     |
+| `no-legend`         | Hide the tag legend                                                                                                                                                                                       |
+| `palette`           | Draw in a built-in palette                                                                                                                                                                                |
+
+The TOWS strategy cross-matrix, scores or weights are not part of this chart.
+
+### 25B.4 Diagnostics
+
+| Code                       | Fires on                                                                                                   |
+| -------------------------- | ---------------------------------------------------------------------------------------------------------- |
+| `E_SWOT_UNKNOWN_SECTION`   | an unknown word at indent 0, including `[Strengths]` and `strength`; the message names the nearest keyword |
+| `E_SWOT_DUPLICATE_SECTION` | the same section twice                                                                                     |
+| `E_SWOT_ORPHAN_ITEM`       | an item before any section                                                                                 |
+| `E_SWOT_TOO_DEEP`          | nesting below the detail level                                                                             |
+| `W_SWOT_EMPTY_SECTION`     | a missing or empty section; its panel still draws                                                          |
+
 ## 26. Colon Usage Summary
 
 ### Constructs Where Colons Are REQUIRED
@@ -4769,16 +4855,16 @@ API description: Main gateway
 
 Some constructs _look_ universal but are scoped to specific chart types. Don't transplant them across charts.
 
-| Construct                                     | Scope                                                                                                                             |
-| --------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
-| Bare `collapsed` trailing flag (§1.8)         | sequence, infra, gantt, kanban, mindmap, pert, state, c4, event-line (eras), block, wireframe. Legacy: `collapsed: true` metadata |
-| Same-line / indented metadata on declarations | all chart types except flowchart, state, data charts (§1.4)                                                                       |
-| Trailing-keyword flag list                    | wireframe only (§19)                                                                                                              |
-| `progress: <N>` key                           | gantt only (§13)                                                                                                                  |
-| `score: <N>` + `emotion: <Word>` keys         | journey-map only (§22)                                                                                                            |
-| `description: <text>` shorthand for layers    | pyramid, ring (§23, §24)                                                                                                          |
-| `milestone` keyword                           | **removed** — use `<name> 0` (§13A)                                                                                               |
-| `\|` operator as metadata delimiter           | **removed** (§1.4). Surviving uses: wireframe `{A \| B}` braces, in-arrow `A -file\|name-> B`, quoted `"Order \| Items"`          |
+| Construct                                     | Scope                                                                                                                                                                                                                                                                                       |
+| --------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Bare `collapsed` trailing flag (§1.8)         | sequence (groups, sections, multi-line notes), infra, gantt, kanban, mindmap, pert, state, event-line (eras), block, wireframe, sitemap, boxes-and-lines, timeline (lanes), journey-map, raci. c4 parses it but draws nothing (c4 folds by drill level). Legacy: `collapsed: true` metadata |
+| Same-line / indented metadata on declarations | all chart types except flowchart, state, data charts (§1.4)                                                                                                                                                                                                                                 |
+| Trailing-keyword flag list                    | wireframe only (§19)                                                                                                                                                                                                                                                                        |
+| `progress: <N>` key                           | gantt only (§13)                                                                                                                                                                                                                                                                            |
+| `score: <N>` + `emotion: <Word>` keys         | journey-map only (§22)                                                                                                                                                                                                                                                                      |
+| `description: <text>` shorthand for layers    | pyramid, ring (§23, §24)                                                                                                                                                                                                                                                                    |
+| `milestone` keyword                           | **removed** — use `<name> 0` (§13A)                                                                                                                                                                                                                                                         |
+| `\|` operator as metadata delimiter           | **removed** (§1.4). Surviving uses: wireframe `{A \| B}` braces, in-arrow `A -file\|name-> B`, quoted `"Order \| Items"`                                                                                                                                                                    |
 
 ### 26.4 Quoted Names + Aliases — Pick One
 

package/gallery/fixtures/swot-relabel.dgmo

@@ -0,0 +1,19 @@
+swot Coopérative du Rhum
+no-axes
+x-label Atouts, Risques
+y-label Interne, Externe
+
+// The source order is deliberately T O W S; the panels stay S W / O T.
+threats Menaces
+  Blocus de la marine royale, qui ferme le port principal pendant toute la saison des alizés
+opportunities Opportunités teal
+  Contrat de ration de rhum pour la marine
+  Ouverture d'une route commerciale vers les îles du sud
+  Demande croissante en Europe
+weaknesses Faiblesses
+  Un seul fournisseur de tonneaux
+strengths Forces
+  La plus ancienne distillerie de l'île
+  Quarante goûteurs assermentés, formés dans trois ports différents et capables de reconnaître un millésime à l'odeur
+    Formation reprise chaque hiver
+  Recette gardée depuis 1680

package/gallery/fixtures/swot-tags.dgmo

@@ -0,0 +1,16 @@
+swot Tortuga Rum Co.
+tag Priority as p
+  High red
+  Low gray
+active-tag Priority
+x-label Helpful, Harmful
+y-label Internal, External
+
+strengths
+  Oldest still on the island p: Low
+  Crew of 40 sworn tasters
+    Trained in three ports
+weaknesses Soft spots yellow
+  One barrel supplier p: High
+opportunities
+  Navy rum ration contract

package/gallery/fixtures/swot.dgmo

@@ -0,0 +1,13 @@
+swot Tortuga Rum Co.
+
+strengths
+  Oldest still on the island
+  Crew of 40 sworn tasters
+weaknesses
+  One barrel supplier
+  Cost: 20% above rivals, margins thin
+opportunities
+  Navy rum ration contract
+threats
+  Royal Navy blockade
+  Margins are in the red

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@diagrammo/dgmo",
-  "version": "0.96.0",
+  "version": "0.98.0",
   "description": "DGMO diagram markup language — parser, renderer, and color system",
   "license": "MIT",
   "author": "Diagrammo LLC",

package/dist/chunk-R2K5L4UA.js

@@ -1,49 +0,0 @@
-import {
-  EDGE_DASH
-} from "./chunk-XCKNFFKM.js";
-import {
-  measureText
-} from "./chunk-KAO7JL4I.js";
-
-// src/utils/card.ts
-function renderNodeCard(container, opts) {
-  const rect = container.append("rect").attr("x", 0).attr("y", 0).attr("width", opts.width).attr("height", opts.height).attr("rx", opts.rx).attr("fill", opts.fill).attr("stroke", opts.stroke).attr("stroke-width", opts.strokeWidth);
-  if (opts.dashed) {
-    rect.attr("stroke-dasharray", EDGE_DASH);
-  }
-  const labelLines = opts.labelLines;
-  if (labelLines && labelLines.length > 1) {
-    const lineH = opts.labelFontSize * 1.2;
-    const midY = opts.headerHeight / 2;
-    const startY = midY - (labelLines.length - 1) * lineH / 2;
-    for (let li = 0; li < labelLines.length; li++) {
-      container.append("text").attr("x", opts.width / 2).attr("y", startY + li * lineH).attr("text-anchor", "middle").attr("dominant-baseline", "central").attr("fill", opts.labelColor).attr("font-size", opts.labelFontSize).attr("font-weight", "bold").text(labelLines[li]);
-    }
-  } else {
-    container.append("text").attr("x", opts.width / 2).attr("y", opts.headerHeight / 2).attr("dominant-baseline", "central").attr("text-anchor", "middle").attr("fill", opts.labelColor).attr("font-size", opts.labelFontSize).attr("font-weight", "bold").text(labelLines?.[0] ?? opts.label);
-  }
-  const meta = opts.meta;
-  if (!meta || meta.rows.length === 0) return;
-  container.append("line").attr("x1", 0).attr("y1", opts.headerHeight).attr("x2", opts.width).attr("y2", opts.headerHeight).attr("stroke", meta.separatorColor).attr("stroke-opacity", 0.3).attr("stroke-width", 1);
-  const keyX = meta.keyX ?? 10;
-  const maxKeyWidth = Math.max(
-    ...meta.rows.map(([key]) => measureText(`${key}: `, meta.fontSize))
-  );
-  const valueX = keyX + maxKeyWidth;
-  const metaStartY = opts.headerHeight + meta.separatorGap + meta.fontSize;
-  for (let i = 0; i < meta.rows.length; i++) {
-    const [displayKey, value] = meta.rows[i];
-    const rowY = metaStartY + i * meta.lineHeight;
-    container.append("text").attr("x", keyX).attr("y", rowY).attr("fill", meta.textColor).attr("font-size", meta.fontSize).text(`${displayKey}: `);
-    container.append("text").attr("x", valueX).attr("y", rowY).attr("fill", meta.textColor).attr("font-size", meta.fontSize).text(value);
-  }
-}
-function renderCollapseBar(container, opts) {
-  container.append("clipPath").attr("id", opts.clipId).append("rect").attr("width", opts.width).attr("height", opts.height).attr("rx", opts.rx);
-  container.append("rect").attr("x", opts.inset).attr("y", opts.height - opts.barHeight).attr("width", opts.width - opts.inset * 2).attr("height", opts.barHeight).attr("fill", opts.fill).attr("clip-path", `url(#${opts.clipId})`).attr("class", opts.className);
-}
-
-export {
-  renderNodeCard,
-  renderCollapseBar
-};

package/dist/collapse-TCVK3RPO.js

@@ -1,8 +0,0 @@
-import {
-  collapseSitemapTree
-} from "./chunk-UNCCZ3NU.js";
-import "./chunk-BS7SV7C3.js";
-import "./chunk-YLJ4XMA6.js";
-export {
-  collapseSitemapTree
-};

package/dist/dgmo-router-EPBQKQW2.js

@@ -1,100 +0,0 @@
-import {
-  CHART_TYPE_DESCRIPTIONS,
-  chartTypeParsers,
-  getAllChartTypes,
-  getRenderCategory,
-  isExtendedChartType,
-  knownChartTypeIds,
-  parseDgmo
-} from "./chunk-MVUNMJKO.js";
-import "./chunk-P2GNNEMN.js";
-import "./chunk-K2WXMXI2.js";
-import "./chunk-EPB3UEMD.js";
-import "./chunk-EOYPX6SF.js";
-import "./chunk-FBK32S4D.js";
-import "./chunk-5ARANBIE.js";
-import "./chunk-P3PSLC2K.js";
-import "./chunk-SQBCNEJB.js";
-import "./chunk-B7BSRVNC.js";
-import "./chunk-SIABEREK.js";
-import "./chunk-35A3J4Z5.js";
-import "./chunk-VVTCUIPN.js";
-import "./chunk-B2YVZ3QU.js";
-import "./chunk-SCYVGPLI.js";
-import "./chunk-VLI6AWS3.js";
-import "./chunk-GM2SLMQW.js";
-import "./chunk-YSGOXZBB.js";
-import "./chunk-ITDF3MWD.js";
-import "./chunk-AUXUNV73.js";
-import "./chunk-YFIUABSF.js";
-import "./chunk-QQJUTGQH.js";
-import "./chunk-2CW5ZTNH.js";
-import "./chunk-KQAPFIYF.js";
-import "./chunk-EZ6BI5LL.js";
-import "./chunk-A2RUBBVT.js";
-import "./chunk-I2I2FKAK.js";
-import "./chunk-URRAWU5D.js";
-import "./chunk-3DPOIW3W.js";
-import "./chunk-QEU6VM4O.js";
-import "./chunk-RGFVHYDP.js";
-import "./chunk-BD4O4D2A.js";
-import "./chunk-DWMQ24JR.js";
-import "./chunk-XSVWUOUZ.js";
-import "./chunk-IU7XKZA6.js";
-import "./chunk-H7AXCRO7.js";
-import "./chunk-OAZ6BIIB.js";
-import {
-  looksLikeC4,
-  looksLikeGantt,
-  parseDgmoChartType
-} from "./chunk-I3ZRIMR7.js";
-import "./chunk-U6N547QA.js";
-import "./chunk-DPNSDCR3.js";
-import "./chunk-JCC3B2GS.js";
-import "./chunk-WLGOIMTI.js";
-import "./chunk-YVIPJGFG.js";
-import "./chunk-34JOHSVE.js";
-import "./chunk-2SKMEL7V.js";
-import "./chunk-H7RQG4PH.js";
-import "./chunk-TIVMAITN.js";
-import "./chunk-TPCP2UOI.js";
-import "./chunk-NXMESY4J.js";
-import "./chunk-EQW6HOP4.js";
-import "./chunk-MKSTL6DR.js";
-import "./chunk-CYTFO2LF.js";
-import "./chunk-MAYTYF5S.js";
-import "./chunk-C3Z4DX3V.js";
-import "./chunk-IYULMRBE.js";
-import "./chunk-M4ZUIW3J.js";
-import "./chunk-GXCDD6NG.js";
-import "./chunk-FMAVHTYB.js";
-import "./chunk-N7VMGZCU.js";
-import "./chunk-HH3DHNQA.js";
-import "./chunk-NOTA6TEI.js";
-import "./chunk-67N26CER.js";
-import "./chunk-7WEYXYLC.js";
-import "./chunk-QKPOIJBT.js";
-import "./chunk-ICLB27PZ.js";
-import "./chunk-D7DGLJ7N.js";
-import "./chunk-4WW3SGMH.js";
-import "./chunk-3UR4F7FE.js";
-import "./chunk-LGUFJ7Y2.js";
-import "./chunk-FUYEXLAN.js";
-import "./chunk-Z6QFHH4D.js";
-import "./chunk-KAO7JL4I.js";
-import "./chunk-6GXLAKUH.js";
-import "./chunk-3J7O3CU6.js";
-import "./chunk-BYU54C3S.js";
-import "./chunk-YLJ4XMA6.js";
-export {
-  CHART_TYPE_DESCRIPTIONS,
-  chartTypeParsers,
-  getAllChartTypes,
-  getRenderCategory,
-  isExtendedChartType,
-  knownChartTypeIds,
-  looksLikeC4,
-  looksLikeGantt,
-  parseDgmo,
-  parseDgmoChartType
-};

package/dist/dimensions-DBCRBZIU.js

@@ -1,21 +0,0 @@
-import {
-  mapContentAspect,
-  mapExportDimensions
-} from "./chunk-FHX373L5.js";
-import "./chunk-EMGNCG5C.js";
-import "./chunk-AXLF3KRE.js";
-import "./chunk-KMU65FYM.js";
-import "./chunk-VLC6WNRD.js";
-import "./chunk-JILEYZ2V.js";
-import "./chunk-LGUFJ7Y2.js";
-import "./chunk-FUYEXLAN.js";
-import "./chunk-UOCWYLYT.js";
-import "./chunk-KAO7JL4I.js";
-import "./chunk-6GXLAKUH.js";
-import "./chunk-3J7O3CU6.js";
-import "./chunk-BYU54C3S.js";
-import "./chunk-YLJ4XMA6.js";
-export {
-  mapContentAspect,
-  mapExportDimensions
-};

package/dist/flowchart-renderer-PPS2GTTD.js

@@ -1,40 +0,0 @@
-import {
-  renderFlowchart,
-  renderFlowchartForExport
-} from "./chunk-LRHPBWOY.js";
-import "./chunk-26EVL454.js";
-import "./chunk-5GU6C5WB.js";
-import "./chunk-VNAPEZX2.js";
-import "./chunk-XBJJP2HN.js";
-import "./chunk-5G4DOOX2.js";
-import "./chunk-VGAMBOOC.js";
-import "./chunk-THTYCJGF.js";
-import "./chunk-WTTIODDV.js";
-import "./chunk-IN7XI6NO.js";
-import "./chunk-EPDBWATV.js";
-import "./chunk-CYRB2JTN.js";
-import "./chunk-24YPR5EH.js";
-import "./chunk-R5L5E3TC.js";
-import "./chunk-VLC6WNRD.js";
-import "./chunk-XCKNFFKM.js";
-import "./chunk-H7RQG4PH.js";
-import "./chunk-TIVMAITN.js";
-import "./chunk-NXMESY4J.js";
-import "./chunk-N7VMGZCU.js";
-import "./chunk-HH3DHNQA.js";
-import "./chunk-NOTA6TEI.js";
-import "./chunk-67N26CER.js";
-import "./chunk-7WEYXYLC.js";
-import "./chunk-QKPOIJBT.js";
-import "./chunk-ICLB27PZ.js";
-import "./chunk-FUYEXLAN.js";
-import "./chunk-UOCWYLYT.js";
-import "./chunk-KAO7JL4I.js";
-import "./chunk-6GXLAKUH.js";
-import "./chunk-3J7O3CU6.js";
-import "./chunk-BYU54C3S.js";
-import "./chunk-YLJ4XMA6.js";
-export {
-  renderFlowchart,
-  renderFlowchartForExport
-};

package/dist/layout-3J72UULM.js

@@ -1,15 +0,0 @@
-import {
-  layoutOrg
-} from "./chunk-O2HNVNKO.js";
-import "./chunk-XCKNFFKM.js";
-import "./chunk-LGUFJ7Y2.js";
-import "./chunk-FUYEXLAN.js";
-import "./chunk-UOCWYLYT.js";
-import "./chunk-KAO7JL4I.js";
-import "./chunk-6GXLAKUH.js";
-import "./chunk-3J7O3CU6.js";
-import "./chunk-BYU54C3S.js";
-import "./chunk-YLJ4XMA6.js";
-export {
-  layoutOrg
-};

package/dist/layout-IXQNVRBE.js

@@ -1,15 +0,0 @@
-import {
-  layoutSitemap
-} from "./chunk-EM5SA7NC.js";
-import "./chunk-XCKNFFKM.js";
-import "./chunk-LGUFJ7Y2.js";
-import "./chunk-FUYEXLAN.js";
-import "./chunk-UOCWYLYT.js";
-import "./chunk-KAO7JL4I.js";
-import "./chunk-6GXLAKUH.js";
-import "./chunk-3J7O3CU6.js";
-import "./chunk-BYU54C3S.js";
-import "./chunk-YLJ4XMA6.js";
-export {
-  layoutSitemap
-};

package/dist/layout-VDCJOZSH.js

@@ -1,11 +0,0 @@
-import {
-  layoutSwimlane
-} from "./chunk-ERT7XDQW.js";
-import "./chunk-VGAMBOOC.js";
-import "./chunk-WTTIODDV.js";
-import "./chunk-IN7XI6NO.js";
-import "./chunk-KAO7JL4I.js";
-import "./chunk-YLJ4XMA6.js";
-export {
-  layoutSwimlane
-};

package/dist/parser-HM6FEX5K.js

@@ -1,14 +0,0 @@
-import {
-  extractSymbols,
-  parseBody
-} from "./chunk-IU7XKZA6.js";
-import "./chunk-H7AXCRO7.js";
-import "./chunk-LGUFJ7Y2.js";
-import "./chunk-FUYEXLAN.js";
-import "./chunk-3J7O3CU6.js";
-import "./chunk-BYU54C3S.js";
-import "./chunk-YLJ4XMA6.js";
-export {
-  extractSymbols,
-  parseBody
-};

package/dist/renderer-2MCV75JQ.js

@@ -1,41 +0,0 @@
-import {
-  renderERDiagram,
-  renderERDiagramForExport
-} from "./chunk-IKXQ6NVR.js";
-import "./chunk-3W73ZP6W.js";
-import "./chunk-VNAPEZX2.js";
-import "./chunk-5G4DOOX2.js";
-import "./chunk-VGAMBOOC.js";
-import "./chunk-THTYCJGF.js";
-import "./chunk-WTTIODDV.js";
-import "./chunk-IN7XI6NO.js";
-import "./chunk-CYRB2JTN.js";
-import "./chunk-24YPR5EH.js";
-import "./chunk-R5L5E3TC.js";
-import "./chunk-VLC6WNRD.js";
-import "./chunk-XCKNFFKM.js";
-import "./chunk-PGD6CNWO.js";
-import "./chunk-JILEYZ2V.js";
-import "./chunk-MAYTYF5S.js";
-import "./chunk-GXCDD6NG.js";
-import "./chunk-FMAVHTYB.js";
-import "./chunk-N7VMGZCU.js";
-import "./chunk-HH3DHNQA.js";
-import "./chunk-NOTA6TEI.js";
-import "./chunk-67N26CER.js";
-import "./chunk-7WEYXYLC.js";
-import "./chunk-QKPOIJBT.js";
-import "./chunk-ICLB27PZ.js";
-import "./chunk-3UR4F7FE.js";
-import "./chunk-LGUFJ7Y2.js";
-import "./chunk-FUYEXLAN.js";
-import "./chunk-UOCWYLYT.js";
-import "./chunk-KAO7JL4I.js";
-import "./chunk-6GXLAKUH.js";
-import "./chunk-3J7O3CU6.js";
-import "./chunk-BYU54C3S.js";
-import "./chunk-YLJ4XMA6.js";
-export {
-  renderERDiagram,
-  renderERDiagramForExport
-};