@diagrammo/dgmo 0.10.1 → 0.10.2

package/docs/guide/chart-state.md

@@ -1,171 +0,0 @@
-# State Diagram
-
-```dgmo
-state Order Lifecycle
-
-[*] -> Pending
-
-Pending
-  -submit-> Validating
-
-Validating
-  -approved-> Processing
-  -rejected-> Cancelled
-
-[Fulfillment]
-  Processing
-    -pack-> Shipping
-    -out of stock-> Cancelled
-
-  Shipping
-    -delivered-> Delivered
-    -lost-> Refunded
-
-[Resolution]
-  Delivered
-    -return request-> Returning
-
-  Returning
-    -received-> Refunded
-
-Cancelled -> [*]
-Refunded -> [*]
-Delivered -> [*]
-```
-
-## Overview
-
-State diagrams model states and transitions. Write states as plain text and connect them with `->` arrows. Diagrammo handles the layout automatically. Use `[*]` for start/end pseudostates and indent lines to chain transitions from a parent state.
-
-## Syntax
-
-```
-state Diagram Title
-direction-tb
-
-[*] -> Idle
-Idle -event-> Active
-Active -> [*]
-```
-
-## Settings
-
-| Key            | Description                                     | Default |
-| -------------- | ----------------------------------------------- | ------- |
-| `chart`        | Must be `state`                                 | —       |
-| `title`        | Diagram title                                   | None    |
-| `direction-tb` | Top-to-bottom layout (default is left-to-right) | `TB`    |
-
-## States
-
-Write state names as plain text. States are created automatically when referenced:
-
-```
-Idle -> Active -> Done
-```
-
-### Pseudostates
-
-Use `[*]` for start and end points. They render as filled circles:
-
-```
-[*] -> Idle
-Done -> [*]
-```
-
-## Transitions
-
-Connect states with `->`. Add labels between dashes:
-
-```
-Idle -> Active
-Idle -start-> Active
-Active -finish(green)-> Done
-```
-
-### Indent-Based Source Inference
-
-Indent transitions under a state heading to chain them from that state:
-
-```
-Idle
-  -start-> Active
-  -reset-> Stopped
-Active
-  -> Done
-```
-
-This is equivalent to writing `Idle -start-> Active`, `Idle -reset-> Stopped`, and `Active -> Done`.
-
-### Transition Chains
-
-Chain multiple states on a single line:
-
-```
-[*] -> Idle -> Active -> Done -> [*]
-```
-
-## State Colors
-
-Add a color name in parentheses after a state label:
-
-```
-Active(green) -> Error(red)
-```
-
-## Transition Colors
-
-Add a color in parentheses inside the arrow label:
-
-```
-Idle -go(green)-> Active
-Active -fail(red)-> Error
-```
-
-## Groups
-
-Use bracket syntax `[Name]` to visually group states into regions. States indented under the bracket line belong to the group. The group closes when indentation returns to the bracket's level or below:
-
-```
-state
-
-[Happy Path](green)
-  [*] -> Processing -> Approved -> [*]
-
-[Error Handling](red)
-  Processing -fail-> Rejected -> [*]
-```
-
-Groups render as labeled background boxes with optional colors.
-
-## Comments
-
-```
-// This line is ignored by the parser
-[*] -> Idle
-```
-
-## Complete Example
-
-```dgmo
-state Order of the Jolly Roger
-
-[*] -> Docked
-Docked
-  -set sail-> At Sea
-At Sea
-  -spot treasure-> Treasure Hunt
-  -enemy ship!-> Battle
-Treasure Hunt
-  -found gold-> Celebrating
-  -empty chest-> At Sea
-Battle
-  -victory!-> Plundering
-  -retreat!-> At Sea
-Plundering
-  -> Celebrating
-Celebrating
-  -rum's gone-> At Sea
-  -retire-> Docked
-  -mutiny!-> [*]
-```

package/docs/guide/chart-tech-radar.md

@@ -1,219 +0,0 @@
-# Technology Radar
-
-```dgmo
-tech-radar Pirate Operations Radar — Q2 1718
-
-rings
-  Full Sail
-  Trial Run
-  Spyglass
-  Davy Jones
-
-Tactics | quadrant: top-right
-  Ambush at Dawn | ring: Full Sail, trend: stable
-    Our most reliable boarding tactic. **90% success rate** when
-    approaching from the east with the sun behind us.
-    - Crew morale peaks at dawn — grog hasn't worn off yet
-    - Reduced cannon fire needed: *3 volleys* vs 8 at midday
-  Boarding Parties | ring: Full Sail, trend: stable
-  Decoy Flags | ring: Trial Run, trend: up
-    Flying false colours until within cannon range. Early results
-    are promising — merchant ships drop anchor **40% more often**.
-  Smoke Screens | ring: Trial Run, trend: new
-  Kraken Diplomacy | ring: Spyglass, trend: new
-    Exploring alliances with *sea monsters*. Negotiations ongoing.
-
-Vessels | quadrant: top-left
-  Brigantine | ring: Full Sail, trend: stable
-    Our workhorse. Fast, manoeuvrable, carries **18 cannons**.
-    - Crew capacity: 100 pirates
-    - Top speed: *11 knots* in fair wind
-  Sloop | ring: Full Sail, trend: up
-  War Galleon | ring: Trial Run, trend: up
-    Captured from the Spanish fleet. Massive firepower but
-    **slow to turn** — best for convoy raids, not chases.
-  Longboat | ring: Davy Jones, trend: down
-
-Plunder Targets | quadrant: bottom-left
-  Merchant Convoys | ring: Full Sail, trend: stable
-    Core revenue stream — **78% of total plunder**. East India
-    Company ships running the spice route remain most lucrative.
-  Port Raids | ring: Trial Run, trend: up
-  Rival Pirates | ring: Trial Run, trend: new
-  Royal Treasury Ships | ring: Spyglass, trend: new
-    High risk, astronomical reward. Requires:
-    - Inside information from *corrupt harbourmasters*
-    - At least **3 allied ships** for the blockade
-    - A really good escape plan
-  Whaling Ships | ring: Spyglass, trend: stable
-  Fishing Villages | ring: Davy Jones, trend: down
-    Terrible ROI and **bad for reputation**. The parrot union
-    filed a formal complaint.
-
-Crew Welfare | quadrant: bottom-right
-  Grog Rations | ring: Full Sail, trend: stable
-    Non-negotiable. Cutting grog rations caused the *Great Mutiny of 1716*.
-  Sea Shanty Program | ring: Trial Run, trend: new
-    Hired a shanty master. Crew productivity up **25%** during
-    long voyages. Signature tune: *"Yo Ho Ho and a Bottle of Rum"*.
-  Dental Plan | ring: Spyglass, trend: up
-    Exploring options. Most crew down to **4 teeth** on average.
-    Parley with a Port Royal dentist scheduled for Q3.
-```
-
-## Overview
-
-Technology radars visualize how an organization adopts and evaluates technologies, practices, or strategies. Inspired by the [ThoughtWorks Technology Radar](https://www.thoughtworks.com/radar), each radar arranges items ("blips") into concentric rings indicating adoption stage, grouped by quadrant categories.
-
-Click any quadrant label to drill down into a detail view with expanded blip descriptions. Click the "Blip Legend" toggle to show or hide the numbered reference listing below the radar.
-
-## Syntax
-
-```
-tech-radar Title
-
-rings
-  Ring1
-  Ring2
-
-Quadrant Name | quadrant: position
-  Blip Name | ring: RingName, trend: value
-    Description text (markdown supported)
-```
-
-## Settings
-
-| Key | Description | Default |
-| --- | ----------- | ------- |
-| `chart` | Must be `tech-radar` | — |
-| `title` | Radar title | None |
-
-## Rings
-
-Rings represent adoption stages, ordered from innermost (highest commitment) to outermost (lowest). Declare them in a `rings` block:
-
-```
-rings
-  Adopt
-  Trial
-  Assess
-  Hold
-```
-
-You can use any ring names — the classic Adopt/Trial/Assess/Hold is common but not required.
-
-### Ring Aliases
-
-Rings support aliases for shorter blip references:
-
-```
-rings
-  Adopt alias a
-  Trial alias t
-  Assess alias x
-  Hold alias h
-
-Quadrant | quadrant: top-right
-  Item Name | ring: a, trend: up
-```
-
-## Quadrants
-
-Exactly 4 quadrants are required. Each needs a unique position:
-
-```
-Techniques | quadrant: top-right
-Tools | quadrant: top-left
-Platforms | quadrant: bottom-left
-Languages | quadrant: bottom-right
-```
-
-**Positions:** `top-left`, `top-right`, `bottom-left`, `bottom-right`
-
-### Custom Colors
-
-Override the default quadrant color with `color`:
-
-```
-Tools | quadrant: top-left, color: purple
-```
-
-Default colors: top-left=blue, top-right=green, bottom-left=red, bottom-right=orange.
-
-## Blips
-
-Blips are items placed on the radar. Each is indented under its quadrant and requires a `ring` reference:
-
-```
-  Kubernetes | ring: Adopt
-  Micro Frontends | ring: Trial, trend: up
-```
-
-Ring matching is case-insensitive — `ring: adopt` and `ring: Adopt` both work.
-
-## Trends
-
-The optional `trend` metadata controls the visual indicator on each blip:
-
-| Trend | Indicator | Meaning |
-| ----- | --------- | ------- |
-| `new` | Double circle | Newly added to the radar |
-| `up` | Inward crescent | Moving toward center (higher adoption) |
-| `down` | Outward crescent | Moving away from center (declining) |
-| `stable` | Plain circle | No change since last assessment |
-
-Omitting `trend` renders a plain circle (same as `stable`).
-
-## Descriptions
-
-Further-indented lines below a blip become its description. Descriptions support inline markdown:
-
-```
-  Rust | ring: Assess, trend: new
-    Evaluating for **performance-critical** services.
-    Key benefits: *zero-cost abstractions* and `no GC pauses`.
-    - 12x throughput improvement in image pipeline
-    - See [evaluation doc](https://wiki.example.com/rust)
-```
-
-Descriptions appear in the quadrant detail view and on hover/click in the main radar view.
-
-## Complete Example
-
-```dgmo
-tech-radar Fleet Readiness Radar
-
-rings
-  Battle Ready
-  Sea Trials
-  Scouting
-  Scuttle
-
-Navigation | quadrant: top-right
-  Star Charts | ring: Battle Ready, trend: stable
-  Compass Calibration | ring: Sea Trials, trend: up
-    New lodestone from Madagascar shows **30% better accuracy**.
-  Sextant | ring: Battle Ready, trend: stable
-  Treasure Maps | ring: Scouting, trend: new
-  Celestial Tables | ring: Scouting, trend: new
-
-Armaments | quadrant: top-left
-  Cannon Broadside | ring: Battle Ready, trend: stable
-  Greek Fire | ring: Sea Trials, trend: new
-  Chain Shot | ring: Sea Trials, trend: up
-  Catapult | ring: Scuttle, trend: down
-
-Provisions | quadrant: bottom-left
-  Salted Pork | ring: Battle Ready, trend: stable
-  Citrus Rations | ring: Sea Trials, trend: up
-    Reduced scurvy cases by **80%** in trial crews.
-  Rum Distillation | ring: Scouting, trend: new
-  Hardtack | ring: Scuttle, trend: down
-  Barnacle Soup | ring: Scuttle, trend: down
-
-Morale | quadrant: bottom-right
-  Shore Leave | ring: Battle Ready, trend: stable
-  Sea Shanties | ring: Battle Ready, trend: up
-  Parrot Companions | ring: Scouting, trend: new
-  Plank Walking | ring: Scuttle, trend: down
-```

package/docs/guide/chart-timeline.md

@@ -1,229 +0,0 @@
-# Timeline
-
-```dgmo
-timeline The Golden Age of Piracy (1716–1722)
-scale on
-
-tag Pirate alias p
-  Blackbeard(red)
-  Bonny & Rackham(purple)
-  Roberts(blue)
-
-tag Outcome alias o
-  Victory(green)
-  Defeat(red)
-  Uncertain(yellow) default
-
-tag Theatre alias t
-  Caribbean(teal) default
-  Atlantic(blue)
-  Africa(orange)
-
-era 1716->1718 Nassau Republic
-era 1719->1722 Roberts Era
-
-marker 1718-07 Woodes Rogers arrives (orange)
-marker 1721-08 Roberts reaches peak (teal)
-
-1716->1717 Sails under Hornigold | p: Blackbeard, o: Victory
-1717-11->1718-06 Commands Queen Anne's Revenge | p: Blackbeard, o: Victory, t: Atlantic
-1718-05 Blockades Charleston harbor | p: Blackbeard, o: Victory
-1718-11-22 Killed at Ocracoke | p: Blackbeard, o: Defeat
-1718->1719 Rackham builds crew in Nassau | p: Bonny & Rackham, o: Victory
-1719-03->1720-10? Bonny & Rackham raid together | p: Bonny & Rackham
-1720-11 Rackham hanged at Port Royal | p: Bonny & Rackham, o: Defeat
-1719-06->1720 Raids West African coast | p: Roberts, o: Victory, t: Africa
-1720->1722 Captures 400+ ships | p: Roberts, o: Victory, t: Atlantic
-1722-02-10 Killed at Cape Lopez | p: Roberts, o: Defeat, t: Africa
-```
-
-## Syntax
-
-```
-timeline Chart Title
-sort group
-
-era YYYY->YYYY Era Name
-
-marker YYYY-MM-DD Marker Label (color)
-
-[Group Name](color)
-YYYY->YYYY Span event description
-YYYY-MM-DD Point event description
-```
-
-## Metadata Keys
-
-| Key         | Description                                                                                           | Required |
-| ----------- | ----------------------------------------------------------------------------------------------------- | -------- |
-| `chart`     | Must be `timeline`                                                                                    | Yes      |
-| `title`     | Chart title displayed above the chart                                                                 | No       |
-| `sort`      | Event ordering: `time` (default), `group`, `tag`, or `tag:GroupName`                                  | No       |
-| `swimlanes` | Show shaded backgrounds per group (boolean; `no-swimlanes` to disable). Works best with `sort group`. | No       |
-
-## Event Format
-
-### Point Events
-
-A single date followed by a description:
-
-```
-1718-11-22 Killed at Ocracoke
-1720-11 Rackham hanged at Port Royal
-```
-
-### Span Events
-
-A date range (start -> end) followed by a description:
-
-```
-1717-11->1718-06 Commands Queen Anne's Revenge
-1720->1722 Captures 400+ ships
-```
-
-### Duration Events
-
-Instead of specifying an end date, you can use a duration:
-
-```
-2026-07-15->30d Film release window
-2026-06-01->2w Festival run
-2026-01->6m Award season
-2026->2y Franchise arc
-```
-
-Supported duration units:
-
-| Unit | Meaning |
-| ---- | ------- |
-| `d`  | Days    |
-| `w`  | Weeks   |
-| `m`  | Months  |
-| `y`  | Years   |
-
-Decimals are supported (up to 2 places):
-
-```
-2026-01->1.25y Fifteen months (1 year + 3 months)
-2026-01->0.5y Half year (6 months)
-2026-01-01->1.5m Six weeks (1 month + 15 days)
-```
-
-The end date is calculated automatically and preserves the precision of the start date.
-
-### Uncertain End Dates
-
-Use `->?` to indicate an uncertain or approximate end date. The bar will fade out over the last 20%:
-
-```
-2026-07-15->?3m Project Alpha
-2026-01->?1.5y Long-term initiative
-```
-
-This visually communicates that the end date is an estimate rather than a fixed deadline.
-
-### Date Precision
-
-Dates support three levels of precision:
-
-- Year: `1718`
-- Year-Month: `1718-05`
-- Year-Month-Day: `1718-11-22`
-
-## Eras
-
-Background shaded regions that span a time range:
-
-```
-era 1716->1718 Nassau Republic
-era 1719->1722 Roberts Era
-```
-
-## Markers
-
-Notable moments displayed as a dashed vertical line with a diamond indicator:
-
-```
-marker 1718-11-22 Blackbeard Killed (red)
-marker 1720-11 Trial at Port Royal (orange)
-```
-
-Markers are not associated with groups and appear above all events. They're useful for highlighting key dates that span across all timeline tracks.
-
-## Groups
-
-Use `[Group Name](color)` headers to organize events into colored tracks:
-
-```
-[Blackbeard](red)
-1716->1717 Sails under Hornigold
-1718-11-22 Killed at Ocracoke
-
-[Roberts](blue)
-1719-06->1720 Raids West African coast
-1722-02-10 Killed at Cape Lopez
-```
-
-## Tag Groups
-
-Tag groups let you color and organize events by metadata categories like team, priority, or status — independent of the timeline's structural groups.
-
-### Declaring Tag Groups
-
-```
-tag Team
-  Engineering(blue)
-  Design(green)
-  QA(orange)
-```
-
-Each entry has a name and a color. You can add `default` to an entry to apply it to untagged events when the group is active:
-
-```
-tag Priority
-  High(red)
-  Medium(yellow) default
-  Low(gray)
-```
-
-### Tagging Events
-
-Add `| key: value` metadata after any event line:
-
-```
-2024-01->2024-06 Build API | Team: Engineering
-2024-03->2024-05 UX Review | Team: Design, Priority: High
-```
-
-Multiple tags can be separated by commas.
-
-### Tag-Based Swimlanes
-
-Use `sort: tag` or `sort: tag:GroupName` to arrange events into swimlanes by tag value:
-
-```dgmo
-timeline Project Roadmap
-sort tag:Team
-
-tag Team
-  Engineering(blue)
-  Design(green)
-  QA(orange)
-
-tag Priority
-  High(red)
-  Medium(yellow)
-  Low(gray)
-
-2024-01->2024-06 Build API | Team: Engineering, Priority: High
-2024-03->2024-05 UX Review | Team: Design, Priority: Medium
-2024-04->2024-07 Integration Tests | Team: QA, Priority: High
-2024-02->2024-04 Design System | Team: Design, Priority: Low
-```
-
-- `sort tag` — uses the first declared tag group for swimlanes
-- `sort tag:GroupName` — uses a specific tag group (aliases work: `sort tag:t` resolves to `sort tag:Team`)
-
-### Interactive Legend
-
-When tag groups are declared, a legend appears above the chart. Click a tag group pill to activate it — events are colored by that group's values. The swimlane tag group controls the spatial layout; the active tag group controls the coloring. These can be set independently.

package/docs/guide/chart-venn.md

@@ -1,81 +0,0 @@
-# Venn Diagram
-
-```dgmo
-venn Pirate Skill Overlap
-
-Swordsmanship(red) alias sw
-Navigation(blue) alias nav
-Leadership(green) alias lead
-
-sw + nav Sea Raiders
-nav + lead Voyager Captains
-sw + lead Buccaneer Chiefs
-sw + nav + lead Legendary Pirates
-```
-
-## Syntax
-
-```
-venn Chart Title
-
-<name>(<color>) alias <abbrev>
-
-<A> + <B> Label
-<A> + <B> + <C> Label
-```
-
-## Metadata Keys
-
-| Key     | Description                             | Required |
-| ------- | --------------------------------------- | -------- |
-| `chart` | Must be `venn`                          | Yes      |
-| `title` | Chart title displayed above the diagram | No       |
-
-## Sets
-
-Each set is defined as a name with an optional color and alias. 2 or 3 sets are supported.
-
-```
-Swordsmanship(red) alias sw
-Navigation(blue) alias nav
-Leadership(green) alias lead
-```
-
-### Colors
-
-Colors can be specified in parentheses after the name:
-
-```
-Math(blue) alias m
-Science(orange) alias s
-```
-
-Supports named colors: `red`, `orange`, `yellow`, `green`, `blue`, `purple`, `teal`, `cyan`, `gray`.
-
-### Aliases
-
-Use `alias` to define a short name for intersections:
-
-```
-Swordsmanship(red) alias sw
-Navigation(blue) alias nav
-```
-
-The alias (`sw`, `nav`) is used when defining intersections. The full name is shown in the diagram.
-
-## Intersections
-
-Intersection lines use `+` to reference two or three sets by alias, followed by a label:
-
-```
-sw + nav Sea Raiders
-nav + lead Voyager Captains
-sw + nav + lead Legendary Pirates
-```
-
-- The label follows the last set reference (no colon)
-- Set references use the alias, not the full name
-
-## Constraints
-
-- Minimum 2 sets, maximum 3 sets