@diagrammo/dgmo 0.15.1 → 0.17.0

package/dist/pert.d.cts

@@ -12,7 +12,7 @@ interface DgmoError {
     code?: string;
 }
 
-/** A single entry inside a tag group: `Value(color)` */
+/** A single entry inside a tag group: `Value color` */
 interface TagEntry {
     value: string;
     color: string;
@@ -248,7 +248,7 @@ interface ParsedPert {
     groups: PertGroup[];
     /**
      * Tag groups declared at the top of the diagram (`tag Priority as p
-     * High(red), Low(green)`). Drive node fill via `resolveTagColor()`.
+     * High red, Low green`). Drive node fill via `resolveTagColor()`.
      * Empty when no `tag` blocks are declared.
      */
     tagGroups: TagGroup[];

package/dist/pert.d.ts

@@ -12,7 +12,7 @@ interface DgmoError {
     code?: string;
 }
 
-/** A single entry inside a tag group: `Value(color)` */
+/** A single entry inside a tag group: `Value color` */
 interface TagEntry {
     value: string;
     color: string;
@@ -248,7 +248,7 @@ interface ParsedPert {
     groups: PertGroup[];
     /**
      * Tag groups declared at the top of the diagram (`tag Priority as p
-     * High(red), Low(green)`). Drive node fill via `resolveTagColor()`.
+     * High red, Low green`). Drive node fill via `resolveTagColor()`.
      * Empty when no `tag` blocks are declared.
      */
     tagGroups: TagGroup[];

package/docs/language-reference.md

@@ -59,14 +59,15 @@ These patterns are shared across all or most diagram types.
 
 ```
 tag GroupName as <alias>
-  Value1(color)
-  Value2(color) [default]
+  Value1 color
+  Value2 color
 ```
 
 - `tag` keyword, NO colon
 - Alias: optional postfix `as <alias>` per §2A (universal alias syntax — `[A-Za-z][A-Za-z0-9_]{0,11}`)
-- Inline values also supported: `tag Priority as p Low(green), High(red)`
-- First entry is default unless another is marked `default`
+- Inline values also supported: `tag Priority as p Low green, High red`
+- Color follows the value as a bare trailing token (see §1.5). Capitalize the color word (`Red`, `Yellow`) to keep it as a literal value with no color.
+- First entry is the default — reorder to change
 - Must appear before diagram content
 - Legacy bare shorthand (`tag Priority p`) and `alias` keyword (`tag Priority alias p`) emit `E_TAG_SHORTHAND_REMOVED` per TD-18
 
@@ -85,15 +86,36 @@ EntityName | key: value, key2: value2
 
 ### 1.5 Color Suffixes
 
+Color is set by typing the color name at the end of a label, lowercase. Example: `Done green` colors Done green. Eleven colors exist: `red`, `orange`, `yellow`, `green`, `blue`, `purple`, `teal`, `cyan`, `gray`, `black`, `white`. To use a color word as a literal label, capitalize it: `Red` stays as the word `Red`.
+
+```
+Label color           // bare trailing color token
+Done green            // value=Done, color=green
+Senior Engineer red   // value="Senior Engineer", color=red
+Red                   // value=Red, no color (capitalized → escape hatch)
+```
+
+**The universal rule** — color trails the label:
+
+> Color is the trailing whitespace-delimited token of a label region, when that token (case-sensitive, lowercase) is one of the 11 names above. Otherwise the label region has no color.
+
+The "label region" is everything left after the parser strips off structural terminators it owns: `as <alias>`, `| <pipe metadata>`, numeric values, date ranges, structural brackets. Parsers split those off BEFORE invoking the color rule. So `Tortuga Distillery orange 3000` → `{ label: "Tortuga Distillery", color: "orange", value: 3000 }`: numeric value first, then the color trails the remaining label.
+
+**Where the rule applies**: tag values, kanban columns (`[Done] green`), venn / quadrant items (color before `as`), gantt / timeline eras and markers, data-chart series + rows, sankey nodes + link lines, cycle / pyramid / ring / RACI / boxes-and-lines node labels (shortcut for `| color: <name>` when color is the only metadata).
+
+**Long form preserved for multi-key pipe metadata**:
+
 ```
-Label(colorName)
+Spring | color: green                 // shortcut and long form are equivalent
+Spring | color: green, icon: ❄        // long form REQUIRED when other keys accompany color
 ```
 
-- **Allowed color names (exactly these 10):** `red`, `orange`, `yellow`, `green`, `blue`, `purple`, `teal`, `cyan`, `lightblue`, `gray`
-- Any other value — including hex codes (`#ff0000`), CSS keywords (`black`, `white`, `pink`), or typos — is a parse error and produces an inline diagnostic in the editor (with a "did you mean?" suggestion when close to a known name)
-- The actual hex value rendered for each name comes from the active palette/theme; users cannot extend or override the allowed list
-- Appears at end of labels, node names, tag values, series names
-- Color is stripped from display text
+**Accepted tradeoffs**:
+
+- **No typo diagnostics**: `Done grren` is a 2-word label with no color, no warning.
+- **Case-sensitivity is the escape hatch**: `Red`, `Yellow`, `Green` stay as labels.
+- **No edge color** on flowchart, state, sitemap. Sankey links DO accept a trailing color word after the numeric value.
+- **11-name palette is a frozen public contract**: adding a 12th color is itself a breaking change.
 
 ### 1.6 Indentation
 
@@ -104,12 +126,12 @@ Label(colorName)
 
 ```
 [Group Name]
-[Group Name](color)
+[Group Name] color
 [Group Name] | key: value
 ```
 
 - Bracket-enclosed name
-- Optional color suffix
+- Optional trailing-token color (kanban columns, scatter categories, era/marker labels)
 - Optional pipe metadata (outside brackets)
 - Indented content below belongs to the group
 
@@ -162,7 +184,7 @@ A -日本語-> B
 A -🎉-> B
 
 // punctuation is literal — no markdown interpretation
-A -(parenthetical)-> B      // label = "(parenthetical)"  (NOT a color)
+A -(parenthetical)-> B      // label = "(parenthetical)"
 A -*emphasis*-> B           // label = "*emphasis*"       (NOT bold)
 A -`code`-> B               // label = "`code`"           (NOT a code span)
 
@@ -185,23 +207,21 @@ A -Makes calls-> B | tech: HTTP   // preferred: technology on target metadata
 - **Plain text only**: no markdown interpretation. `*foo*` renders as `*foo*`, not italicized. `[label](url)` renders as literal `[label](url)`, not a hyperlink. Clickable URLs belong in notes, not in in-arrow labels.
 - **HTML-safe**: all renderers emit label text as a DOM text node. `<script>alert(1)</script>` renders as literal text — the entire label is a sequence of codepoints, not a markup fragment.
 
-#### Color suffix (flowchart and state only)
+#### Edge color is not a feature
+
+Edges on flowchart, state, and sitemap diagrams have NO color slot. `A -(red)-> B` is a literal label with text `(red)`; `A -yes-> B` and `A -no-> B` no longer auto-color the arrow. Arrows render with the default theme color, period. To color a *node*, use tags (§1.3).
+
+Sankey link lines DO accept a trailing-token color, because the link itself carries data:
 
 ```
-A -(red)-> B         // colored edge, no label
-A -(notacolor)-> B   // label = "(notacolor)" (fall-through)
-A -(red) uses-> B    // label = "(red) uses" (combined form not supported)
-A -red-> B           // label = "red" (bare word is always a label)
+Sugar Plantations -> Tortuga Distillery 3000 red    // link is colored red
 ```
 
-A parenthesized palette color is only recognized when the entire label between the opening `-` and the arrow token is exactly `(colorName)` and `colorName` is one of the 11 names in §1.5. Any other content falls through to the label. To combine a color and a label, use the post-colon or pipe-metadata form instead.
-
 #### Migrating from pre-gauntlet syntax
 
-Two legacy forms changed with this spec:
+One legacy form changed with this spec:
 
 1. **C4 trailing `[technology]` sugar is removed.** A C4 arrow like `-Makes calls [HTTPS]-> API` used to extract `HTTPS` as the technology annotation. The full `Makes calls [HTTPS]` is now the label. Use the post-colon or pipe form for technology: `-Makes calls-> API | tech: HTTPS`.
-2. **Bare palette color suffixes are a literal label.** `A -red-> B` on flowchart/state used to be accepted as a bare color suffix in some surfaces. It is now always a label with text `red`. To color an edge, use the `-(red)->` parens form.
 
 No code migration is required for in-arrow label character escaping — any label that was valid before remains valid, with one exception: if your label happened to contain the literal substring `->` or `~>`, the parser now rejects it with `E_ARROW_SUBSTRING_IN_LABEL`. Move those labels to the post-colon form.
 
@@ -243,7 +263,7 @@ quote.
 
 ### 2.3 Examples
 
-- `Auth Service is a service` — bare multi-word, no quoting needed
+- `Auth Database is a database` — bare multi-word, no quoting needed
 - `"first name" varchar` — quote when name contains a reserved char (the `:` ER type separator)
 - `"Order | Items"` — quote the pipe
 - `class "Customer Service"` — bare multi-word also accepts in class
@@ -269,6 +289,7 @@ These are intentionally outside the universal rule:
 - `I_NAME_MERGED` (warning) — two source-distinct names normalize to the same key with different displayed forms
 - `E_NAME_RESERVED_CHAR` (error) — bare name contains a reserved char without quoting
 - `E_AKA_REMOVED` (error) — removed `aka` keyword used in sequence participant declaration
+- `E_PARTICIPANT_TYPE_REMOVED` (error) — sequence `is a X` declaration used a removed type keyword (`service`, `frontend`, `networking`, `gateway`, `external`)
 
 ---
 
@@ -282,7 +303,7 @@ tag-shorthand and venn `alias` keyword forms with a uniform rule.
 
 ```
 sequence
-Alice is a service as a
+Alice is an actor as a
 Bob is a database as b
 a -hello-> b
 b -ack-> a
@@ -290,8 +311,8 @@ b -ack-> a
 
 ```
 venn
-Swordsmanship(red) as sw
-Navigation(blue) as nav
+Swordsmanship red as sw
+Navigation blue as nav
 sw + nav Sea Raiders
 ```
 
@@ -304,7 +325,7 @@ tag Concern as c
 
 - **Token shape**: `[A-Za-z][A-Za-z0-9_]{0,11}` — letter start,
   letters/digits/underscore, length 1–12. **Case-sensitive**.
-- **Modifier order on declarations**: `<name> [(color)] [is a type] as <alias> [| key: value, …]`.
+- **Modifier order on declarations**: `<name> [color] [is a type] as <alias> [| key: value, …]`.
 - **Strict ordering**: aliases must be declared on or before first use.
 - **Flat global namespace**: one alias literal has exactly one binding per source.
 - **Aliases are NEVER UNH-normalized** — exact-match short-codes only.
@@ -328,7 +349,7 @@ rarely benefit. Aliases should aid comprehension, not obscure it.
 |-----|-----|
 | `tag Priority p` (bare shorthand) | `tag Priority as p` |
 | `tag Priority alias p` (explicit) | `tag Priority as p` |
-| `Swordsmanship(red) alias sw` (venn) | `Swordsmanship(red) as sw` |
+| `Swordsmanship red alias sw` (venn) | `Swordsmanship red as sw` |
 
 ### 2A.6 Error Codes
 
@@ -356,43 +377,38 @@ Name is a <type> [position N]
 Name | key: value
 ```
 
-Types: `service`, `database`, `actor`, `queue`, `cache`, `gateway`, `external`, `networking`, `frontend`
+Types: `actor`, `database`, `cache`, `queue` (plus default — the plain rectangle, used when `is a` is omitted).
+
+Type names in `is a X` are **case-insensitive** (`is a Actor`, `is an ACTOR`, `is an actor` all parse the same). The keywords `service`, `frontend`, `networking`, `gateway`, and `external` were removed in 0.16.0 and now emit `E_PARTICIPANT_TYPE_REMOVED`; drop the override and the participant renders as the default rectangle.
+
+A participant *named* with a removed-type keyword (e.g. `service -> User: hi` declares a participant named "service") remains valid. The trim affects only the `is a X` declaration syntax, not name resolution.
 
 **Inference rules** — the parser infers the type (and shape) from the participant name. Only use `is a` when the name does not match or you want to override:
 
 | Inferred Type | Shape | Name Patterns (examples) |
 |--------------|-------|--------------------------|
-| actor | Stick figure | `User`, `Customer`, `Client`, `Admin`, `Agent`, `Person`, `Buyer`, `Seller`, `Guest`, `Visitor`, `Operator`, Alice, Bob, Charlie, `*User`, `*Actor`, `*Analyst`, `*Staff` |
-| service | Rounded rectangle | `*Service`, `*Svc`, `*API`, Lambda, `*Function`, `*Fn`, `*Job`, Cron, Auth, SSO, OAuth, Stripe, Twilio, S3, Vercel, Docker, K8s, Vault, KMS, IAM, LLM, GPT, Claude, `*Pipeline`, `*Engine`, and many `-er`/`-or` suffixes (Scheduler, Handler, Processor, Worker, etc.) |
-| database | Cylinder (vertical) | `*DB`, `Database`, `*Store`, `Storage`, `*Repo`, `SQL`, Postgres, MySQL, Mongo, Dynamo, Aurora, Spanner, Supabase, Firebase, BigQuery, Redshift, Snowflake, Cassandra, Neo4j, ClickHouse, Elastic, OpenSearch, Pinecone, Weaviate, `*Table` |
+| actor | Stick figure | `User`, `Customer`, `Admin`, `Agent`, `Person`, `Buyer`, `Seller`, `Guest`, `Visitor`, `Operator`, `Developer`, Alice, Bob, Charlie, Fan, Purchaser, Reviewer, `*User`, `*Actor`, `*Analyst`, `*Staff` |
+| database | Cylinder (vertical) | `*DB`, `Database`, `Datastore`, `*Store`, `Storage`, `*Repo`, `Repository`, `SQL`, Postgres, MySQL, Mongo, Dynamo, Aurora, Spanner, Supabase, Firebase, BigQuery, Redshift, Snowflake, Cassandra, Neo4j, ClickHouse, Elastic, OpenSearch, Druid, Trino, Pinecone, Weaviate, Qdrant, Milvus, Presto, `*Table` |
 | cache | Dashed cylinder | `*Cache`, Redis, Memcache, KeyDB, Dragonfly, Hazelcast, Valkey |
-| queue | Horizontal cylinder (pipe) | `*Queue`, `*MQ`, SQS, Kafka, RabbitMQ, `EventBus`, `*Bus`, `Topic`, `*Stream`, SNS, PubSub, NATS, Pulsar, Kinesis, EventBridge, Celery, Sidekiq, `*Channel`, `*Broker` |
-| networking | Hexagon | `*Router`, `*Balancer`, `Gateway`, `Proxy`, `LB`, `CDN`, `Firewall`, `WAF`, `DNS`, `Ingress`, Nginx, Traefik, Envoy, Istio, Kong, Akamai, Cloudflare, `*Mesh` |
-| frontend | Monitor (screen + stand) | `*App`, `Application`, `Mobile`, iOS, Android, `Web`, `Browser`, `Frontend`, `*UI`, `Dashboard`, `*CLI`, `Terminal`, React, Vue, Angular, Svelte, NextJS, Electron, Tauri, `*Widget`, `Portal`, `*Console`, SPA, PWA |
-| gateway | Rectangle (same as default) | matched via `is a gateway` only |
-| external | Dashed rectangle | `External`, `*Ext`, `ThirdParty`, `*3P`, `Vendor`, `Webhook`, `Upstream`, `Downstream`, `Callback`, AWS, GCP, Azure |
+| queue | Horizontal cylinder (pipe) | `*Queue`, `*MQ`, SQS, Kafka, RabbitMQ, `EventBus`, `MessageBus`, `*Bus`, `Topic`, `*Stream`, SNS, PubSub, `*Broker`, NATS, Pulsar, Kinesis, EventBridge, CloudEvents, Celery, Sidekiq, EventHub, `*Channel` |
 | default | Rectangle | Everything else (no `is a` needed) |
 
 **Inference handles it (skip `is a`):**
 ```
-AuthService          // service (matches *Service)
 PostgresDB           // database (matches *DB)
 Redis                // cache (exact match)
 User                 // actor (exact match)
 Kafka                // queue (exact match)
-API Gateway          // networking (matches Gateway)
-WebApp               // frontend (matches *App)
-Stripe               // service (exact match)
 ```
 
 **Inference would miss (use `is a`):**
 ```
-Payments is a service       // "Payments" matches no rule
-Vault is a database         // "Vault" infers as service, but you want database
+Vault is a database         // "Vault" matches no rule, but you want database
 Notifications is a queue    // "Notifications" matches no rule
-Analytics is a frontend     // "Analytics" matches no rule
 ```
 
+Names that previously inferred to a removed type — `AuthService`, `WebApp`, `Cloudflare`, `API Gateway`, `Stripe`, `Webhook` — now fall through to default (plain rectangle). That is the intended outcome of the trim: the visual differentiation is gone because the underlying distinction did not pull its weight.
+
 ### 2.2 Participant Groups
 
 ```
@@ -644,7 +660,7 @@ flowchart [Title]
 | Subroutine | `[[Label]]` | `[[Validate]]` |
 | Document | `[Label~]` | `[Report~]` |
 
-- Color suffix: `(Start(green))`
+- Node coloring: use tags (§1.3) — flowchart nodes have no color suffix
 
 ### 4.3 Arrows
 
@@ -652,8 +668,6 @@ flowchart [Title]
 |------|--------|
 | Unlabeled | `->` |
 | Labeled | `-label->` |
-| Colored | `-(color)->` |
-| Labeled + colored | `-label(color)->` |
 
 - Color inference: `yes/success/ok/true` infers green; `no/fail/error/false` infers red
 
@@ -695,7 +709,7 @@ state [Title]
 
 ```
 StateName
-StateName(color)
+StateName color
 [*]                    // initial/final pseudostate
 ```
 
@@ -705,13 +719,12 @@ StateName(color)
 |------|--------|
 | Unlabeled | `Idle -> Active` |
 | Labeled | `Idle -submit-> Processing` |
-| Colored | `Idle -(blue)-> Active` |
 
 ### 5.4 Groups
 
 ```
 [Group Name]
-[Group Name](color)
+[Group Name] color
 ```
 
 ### 5.5 Options
@@ -742,7 +755,7 @@ CEO
   CFO
 ```
 
-- Color suffix: `Alice(blue)`
+- Node coloring: per-node indented metadata `\n  color: blue` (deferred to a follow-up spec; tag groups inside org also work)
 - Pipe metadata: `Alice | role: CEO, t: Exec`
 
 ### 6.3 Metadata (Indented, Colon REQUIRED)
@@ -863,7 +876,7 @@ er [Title]
 
 ```
 users
-users(blue)
+users blue
 users | domain: Core
 ```
 
@@ -986,7 +999,7 @@ Columns represent workflow stages and must flow left-to-right from least-done to
 
 ```
 [Column Name]
-[Column Name](color) | wip: 3
+[Column Name] color | wip: 3
 ```
 
 ### 10.3 Cards (Indented Under Columns)
@@ -1118,14 +1131,14 @@ Top-level directive (not nested under `holiday`).
 
 **Flat form:**
 ```
-era 2026-04-06 -> 2026-04-10 Conference (purple)
+era 2026-04-06 -> 2026-04-10 Conference purple
 ```
 
 **Block form:**
 ```
 era
-  2026-04-06 -> 2026-04-10 Conference (purple)
-  2026-06-01 -> 2026-06-05 Sprint Review (blue)
+  2026-04-06 -> 2026-04-10 Conference purple
+  2026-06-01 -> 2026-06-05 Sprint Review blue
 ```
 
 ### 12.6 Markers
@@ -1139,7 +1152,7 @@ marker 2026-03-27 Board Review
 ```
 marker
   2026-03-27 Board Review
-  2026-06-15 Release (green)
+  2026-06-15 Release green
 ```
 
 ### 12.7 Groups (Swimlanes)
@@ -1322,21 +1335,21 @@ era 1716 -> 1718 Nassau Republic
 ```
 era
   1716 -> 1718 Nassau Republic
-  1718 -> 1720 Woodes Rogers Era (orange)
+  1718 -> 1720 Woodes Rogers Era orange
 ```
 
 ### 14.4 Markers
 
 **Flat form:**
 ```
-marker 1718-07 Woodes Rogers arrives (orange)
+marker 1718-07 Woodes Rogers arrives orange
 ```
 
 **Block form:**
 ```
 marker
-  1718-07 Woodes Rogers arrives (orange)
-  1720-01 End of Golden Age (red)
+  1718-07 Woodes Rogers arrives orange
+  1720-01 End of Golden Age red
 ```
 
 ### 14.5 Groups
@@ -1365,11 +1378,11 @@ Q1 400, 700, 300, 500  ⚠  tolerated; use spaces
 
 ```
 series                            ✅  preferred
-  Cloud Platform (blue)
-  Legacy Suite (red)
-  Mobile App (green)
+  Cloud Platform blue
+  Legacy Suite red
+  Mobile App green
 
-series Cloud (blue), Legacy (red) ⚠  tolerated; prefer the block
+series Cloud blue, Legacy red ⚠  tolerated; prefer the block
 ```
 
 Parsers accept either form. The rules above are authoring guidance.
@@ -1381,8 +1394,8 @@ Parsers accept either form. The rules above are authoring guidance.
 **Series** — follows Rule B (prefer the indented block):
 ```
 series
-  Cloud Platform (blue)
-  Legacy Suite (red)
+  Cloud Platform blue
+  Legacy Suite red
 ```
 
 Short one-line form is tolerated: `series Revenue` or `series A B`.
@@ -1391,7 +1404,7 @@ Short one-line form is tolerated: `series Revenue` or `series A B`.
 ```
 Label 100
 Label 100 200 300
-Label(color) 100
+Label color 100        // trailing color before numeric values
 Q1 400 700 300 500
 ```
 
@@ -1425,7 +1438,7 @@ Each chart honors the subset of flags that has a renderable atom on it:
 
 **Eras (line/area only):**
 ```
-era Day 1 -> Day 3 Rough Seas (red)
+era Day 1 -> Day 3 Rough Seas red
 ```
 
 ### 15.2 Scatter / Bubble Charts
@@ -1438,7 +1451,7 @@ Name x y size
 
 **Categories:**
 ```
-[Caribbean](red)
+[Caribbean] red
   Blackbeard 90 8500
 ```
 
@@ -1477,8 +1490,8 @@ x-label Distance
 y-label Height
 x 0 to 250
 
-15 degrees(blue): -0.001*x^2 + 0.27*x
-45 degrees(red): -0.003*x^2 + 0.75*x
+15 degrees blue: -0.001*x^2 + 0.27*x
+45 degrees red: -0.003*x^2 + 0.75*x
 ```
 
 The colon between name and expression is **required** — both sides can contain spaces, so colon is the unambiguous delimiter.
@@ -1490,8 +1503,8 @@ The colon between name and expression is **required** — both sides can contain
 
 **Tree structure (indented, space-separated):**
 ```
-Sugar Plantations(green)
-  Tortuga Distillery(orange) 3000
+Sugar Plantations green
+  Tortuga Distillery orange 3000
   Nassau Distillery 2500
 ```
 
@@ -1544,7 +1557,7 @@ Roberts 12 52
   ```
 - Data rows: `Label value1 value2` — follows §15 Rule A (space-separated; commas between values tolerated for back-compat but not idiomatic)
 - Thousands commas within values supported (e.g., `1,000`)
-- Color annotations: `Label (color) value1 value2`
+- Color annotations: `Label color value1 value2` (trailing color word before numeric values)
 - Minimum 2 periods required
 
 ### 16.2 Wordcloud
@@ -1567,7 +1580,7 @@ navigation 88
 ```
 arc Pirate Alliances
 
-[Caribbean](red)
+[Caribbean] red
   Blackbeard -> Bonnet 8
   Blackbeard -> Vane 5
 
@@ -1582,15 +1595,15 @@ order group
 ```
 venn Skill Overlap
 
-Swordsmanship(red) as sw
-Navigation(blue) as nav
-Leadership(green) as lead
+Swordsmanship red as sw
+Navigation blue as nav
+Leadership green as lead
 
 sw + nav Sea Raiders
 sw + nav + lead Legendary Pirates
 ```
 
-- Set declaration: `Name(color) as <alias>` — uses the universal alias syntax (§2A)
+- Set declaration: `Name [color] as <alias>` — color is an optional trailing token BEFORE `as` (universal alias syntax, §2A)
 - Intersections: `Set1 + Set2 Label` — label follows the last set reference (no colon)
 - Legacy `Name(color) alias X` emits `E_VENN_ALIAS_KEYWORD_REMOVED` per TD-18
 
@@ -1601,10 +1614,10 @@ quadrant Crew Assessment
 x-label Low Skill, High Skill
 y-label Low Loyalty, High Loyalty
 
-top-right Promote (green)
-top-left Train (yellow)
-bottom-left Maroon (red)
-bottom-right Watch Closely (purple)
+top-right Promote green
+top-left Train yellow
+bottom-left Maroon red
+bottom-right Watch Closely purple
 
 Quartermaster 0.9 0.95
 Navigator 0.85 0.8

package/docs/migration-sequence-color-to-tags.md

@@ -27,7 +27,7 @@ tag: Role
   Gateway(blue)
   Storage(green)
 
-API is a service | role: Gateway
+API | role: Gateway
 DB is a database | role: Storage
 ```
 

package/gallery/fixtures/area.dgmo

@@ -2,9 +2,9 @@ area Memory Usage Over Time
 x-label Hour
 y-label GB
 
-era 12am -> 9am Night (blue)
-era 9am -> 6pm Day (green)
-era 6pm -> 11pm Evening (purple)
+era 12am -> 9am Night blue
+era 9am -> 6pm Day green
+era 6pm -> 11pm Evening purple
 
 12am 2.1
 3am 1.8

package/gallery/fixtures/bar-stacked.dgmo

@@ -3,11 +3,11 @@ x-label Month
 y-label Tickets
 
 series
-  Critical (red)
-  High (orange)
-  Medium (yellow)
-  Low (green)
-  Info (blue)
+  Critical red
+  High orange
+  Medium yellow
+  Low green
+  Info blue
 
 January 8 24 45 62 31
 February 12 19 51 58 28

package/gallery/fixtures/boxes-and-lines.dgmo

@@ -1,7 +1,7 @@
 boxes-and-lines E-Commerce Platform
 
-tag Team t Backend(blue), Frontend(green), Platform(purple)
-tag Priority p High(red), Medium(orange), Low(gray)
+tag Team t Backend blue, Frontend green, Platform purple
+tag Priority p High red, Medium orange, Low gray
 
 active-tag Team
 hide priority:Low

package/gallery/fixtures/c4-full.dgmo

@@ -1,16 +1,16 @@
 c4 Online Bookstore — C4 Architecture
 
 tag Technology as tech
-  React(blue)
-  Node(green)
-  Python(orange)
-  PostgreSQL(purple)
+  React blue
+  Node green
+  Python orange
+  PostgreSQL purple
 
 tag Team as t
-  Frontend(blue)
-  Backend(green)
-  Platform(teal)
-  Data(purple)
+  Frontend blue
+  Backend green
+  Platform teal
+  Data purple
 
 Customer is a person | t: Frontend
   description: Browses and purchases books online

package/gallery/fixtures/class-full.dgmo

@@ -4,7 +4,7 @@ Drawable [interface]
   + draw(): void
   + resize(w: number, h: number): void
 
-Shape implements Drawable [abstract] (purple)
+Shape implements Drawable [abstract] purple
   # x: number
   # y: number
   + area(): number
@@ -20,7 +20,7 @@ Rectangle extends Shape
   - height: number
   + getDiagonal(): number
 
-Color [enum] (yellow)
+Color [enum] yellow
   Red
   Green
   Blue

package/gallery/fixtures/doughnut.dgmo

@@ -1,8 +1,8 @@
 doughnut Cloud Spending by Service
 
-Compute (blue) 34
-Storage (cyan) 22
-Database (green) 18
-Networking (orange) 12
-AI/ML (purple) 8
-Other (gray) 6
+Compute blue 34
+Storage cyan 22
+Database green 18
+Networking orange 12
+AI/ML purple 8
+Other gray 6

package/gallery/fixtures/flowchart-colors.dgmo

@@ -1,5 +1,5 @@
 flowchart Color Demo
 
-(Start(green)) -> [Parse Input] -> <Valid?(blue)>
-  -yes(green)-> [Process(teal)] -> (Success(green))
-  -no(red)-> [Error Handler(red)] -> /Log Error(orange)/ -> (Failure(red))
+(Start) -> [Parse Input] -> <Valid?>
+  -yes-> [Process] -> (Success)
+  -no-> [Error Handler] -> /Log Error/ -> (Failure)

package/gallery/fixtures/function.dgmo

@@ -3,6 +3,6 @@ x-label x
 y-label f(x)
 
 x -6 to 6
-f(x) (blue) sin(x)
-g(x) (red) x^2 / 10
-h(x) (green) cos(x) * 2
+f(x) blue: sin(x)
+g(x) red: x^2 / 10
+h(x) green: cos(x) * 2