diagramlisted

Create or update the diagram for: $ARGUMENTS ## Step 1 - Pick the format **why-not-mechanizable:** skill workflow guidance; each step requires understanding the surrounding context (repo, task shape, prior state). Read `rules/diagrams.md` if uncertain. Default to **mermaid** unless one of these triggers fires - then use **drawio**: - Custom shapes, icons, or cloud provider symbols requested `(review-time: see section note)` - Precise grid / column layout (network topology, rack diagrams) `(review-time: see section note)` - More than 2 swimlanes, or nested swimlanes `(review-time: see section note)` - Multi-layer architecture (stacked data/control planes) `(review-time: see section note)` - Color or styling carries semantic weight that mermaid cannot express `(review-time: see section note)` - The user explicitly says "drawio" or "complex" `(review-time: see section note)` If the diagram is borderline, ask the user before committing to drawio. ## Step 2 - Locate the doc - Identify the doc this diagram belongs to. If `docs/` does not exist, ask the user where to put it. `(review-time: see section note)` - Slug the topic from $ARGUMENTS or the parent doc's filename. `(review-time: see section note)` ## Step 3 - Mermaid path 1. Write the mermaid source inline in the target doc using ```` ```mermaid ```` fenced blocks (one block per diagram). `(review-time: see section note)` 2. Match diagram type to purpose: `flowchart` / `sequenceDiagram` / `stateDiagram-v2` / `erDiagra