create-yss-spec 2.1.5 → 2.1.6

package/template/.trae/skills/drawio/references/docs/canonical-graph-projection.md

@@ -1,54 +0,0 @@
-# Canonical Graph Projection
-
-Use `CanonicalGraphProjection v1` for adapters that need stable external identity, important comparison attributes, or declared/live matching. Simple Mermaid and CSV adapters may continue returning the canonical YAML spec directly.
-
-For Terraform, Kubernetes, Compose, SQL DDL, OpenAPI, and CI parser routes,
-see [Declared Config Importers](./config-importers.md).
-For source dependency and inheritance routes, see
-[Code Importers](./code-importers.md).
-
-## Boundary
-
-```text
-untrusted source
-  -> parser-owned raw projection candidate
-  -> finalizeGraphProjection
-  -> projectGraphToSpec
-  -> validateSpec
-  -> vendored JavaScript ELK
-  -> canonical renderer and validateXml
-```
-
-Parsers only extract structure. They do not place nodes, emit Draw.io XML, invoke Desktop, or call Graphviz. `graph-projection.schema.json` describes the finalized projection written after validation and identity enrichment.
-
-## Stable Identity
-
-Each node and module carries `{ scheme, key }`. Edges receive an identity derived from their endpoint identities, relation, and stable discriminator. The shared factory owns normalization for Terraform, Kubernetes, Compose, code modules, OpenAPI operations, CI jobs, SQL tables, groups, and edges.
-
-Canonical renderer IDs are deterministic SHA-256 projections of `scheme + NUL + key`. They match the existing YAML ID pattern but do not replace the full identity. Display labels, input order, absolute checkout paths, capture timestamps, styles, and mutable runtime instance names do not participate.
-
-Parallel edges with the same endpoints and relation require a source-derived discriminator. Never add traversal-order suffixes and never use a label as the default match key.
-
-## Projection Contract
-
-A finalized projection contains:
-
-- `version: 1`;
-- relative, sanitized `source` provenance;
-- identity-keyed `nodes`, `edges`, and `modules`;
-- allowlisted shallow `attributes` without secrets, raw source blocks, environment values, or absolute paths;
-- non-fatal `info` or `warning` diagnostics.
-
-Unknown versions, duplicate identities, dangling edges, raw Draw.io styles, non-allowlisted attributes, sensitive fields, and ambiguous parallel edges fail explicitly. Reusable modules throw stable error codes rather than exiting the process.
-
-## Canonical YAML And Sidecars
-
-`projectGraphToSpec` keeps full identity metadata on canonical nodes, edges, and modules while assigning renderer-safe IDs. `meta.adapter` records the projection version and sanitized source provenance. The same fields survive `.spec.yaml` and `.arch.json` round-trips; raw projection attributes are deliberately excluded from `.arch.json`.
-
-Legacy YAML without `meta.adapter` remains valid and does not require identity metadata. When `meta.adapter` is present, every canonical node, edge, and module must retain its identity.
-
-## Layout And Evidence
-
-Set `meta.layout: hierarchical` and use the vendored JavaScript ELK pre-pass. Graphviz `dot` and `tred` are not default dependencies. A future optional Graphviz path requires a separate evidence-backed design.
-
-Deterministic schema, identity, ELK, and XML checks are command evidence. They do not count as Desktop or visual-model execution; unavailable provider/model runs remain `missing evidence`.

package/template/.trae/skills/drawio/references/docs/code-importers.md

@@ -1,53 +0,0 @@
-# Code Importers
-
-Code importers turn a bounded local project directory into a finalized
-`CanonicalGraphProjection v1`, then use canonical YAML validation, JavaScript
-ELK, rendering, and XML validation. They do not execute source code, invoke
-Graphviz, or call Python package managers, `go`, `cargo`, or `rustc`.
-
-## CLI
-
-```powershell
-node scripts/cli.js src/python output.drawio --input-format python-imports --validate
-node scripts/cli.js src/python output.drawio --input-format python-classes --validate
-node scripts/cli.js src/web output.drawio --input-format js-imports --validate
-node scripts/cli.js src/go output.drawio --input-format go-imports --validate
-node scripts/cli.js src/rust output.drawio --input-format rust-imports --validate
-```
-
-The input must be a local directory. Stdin is not supported. Scanning is
-sorted, does not follow symlinks, skips cache/vendor/build directories, and is
-bounded to 500 files, 1 MiB per file, and 4 MiB of selected source.
-
-## Parser Scope
-
-- Python 3.11+ uses an isolated stdlib `ast` worker for imports and top-level
-  class inheritance. It uses a fixed script, bounded JSON stdin/stdout, a
-  10-second timeout, `shell: false`, fixed cwd, and a minimal environment.
-- JavaScript/TypeScript uses exact-pinned `es-module-lexer@2.3.1` for ESM
-  static, side-effect, export-from, and string-literal dynamic imports.
-- Go uses exact-pinned `tree-sitter@0.21.1` and
-  `tree-sitter-go@0.23.4` for `import_spec` nodes. A minimal `go.mod` grammar
-  supplies one module path; no Go toolchain is used.
-- Rust uses exact-pinned `tree-sitter@0.21.1` and
-  `tree-sitter-rust@0.23.0` for `crate/self/super` use trees. No Rust
-  toolchain is used.
-
-The Node parser packages are exact-pinned optional dependencies and are loaded
-only by their routes. Missing bindings return `OPTIONAL_DEPENDENCY_MISSING`.
-They are MIT licensed; Tree-sitter packages include native bindings and need
-Node 20 install coverage.
-
-## Stable Identity And Limitations
-
-Module identity is language plus canonical project-relative POSIX path. Go
-package identity uses the package directory (`_root` for root). Python class
-identity extends its module identity with the top-level qualified class name.
-Absolute checkout roots, labels, and traversal order never identify nodes.
-
-CJS, TypeScript path aliases and monorepo/package resolution, Go workspace and
-replace semantics, and Rust workspace, multiple crate roots, cfg, `#[path]`,
-inline modules, and edition-ambiguous bare paths are not resolved. Unsupported internal references
-fail instead of silently dropping an edge; ignored non-relative dependencies
-produce aggregate diagnostics. Large repository corpora, Desktop, visual
-model, Graphviz, and conditional-build evidence remain `missing evidence`.

package/template/.trae/skills/drawio/references/docs/config-importers.md

@@ -1,68 +0,0 @@
-# Declared Config Importers
-
-Declared config importers normalize infrastructure and workflow sources into
-`CanonicalGraphProjection v1`, then use the existing canonical YAML,
-JavaScript ELK, renderer, and XML validation path. They do not execute provider
-CLIs, contact a cluster or database, call Graphviz, or write raw Draw.io style.
-
-## CLI
-
-```powershell
-node scripts/cli.js infra/main.tf output.drawio --input-format terraform --module-address module.app --validate
-node scripts/cli.js k8s/app.yaml output.drawio --input-format kubernetes --scope prod --validate
-node scripts/cli.js compose.yaml output.drawio --input-format compose --project shop --validate
-node scripts/cli.js db/schema.sql output.drawio --input-format sql --dialect postgres --validate
-node scripts/cli.js api/openapi.yaml output.drawio --input-format openapi --validate
-node scripts/cli.js .github/workflows/ci.yml output.drawio --input-format github-actions --validate
-node scripts/cli.js .gitlab-ci.yml output.drawio --input-format gitlab-ci --validate
-```
-
-For stdin CI input, pass `--workflow <repo-relative-path>`. Kubernetes always
-requires a stable logical `--scope`. Compose accepts top-level `name`; use
-`--project` when declared and live sources need an explicit shared override.
-
-## Optional HCL And SQL Parser
-
-Terraform and SQL need Python 3.9+ plus pinned parser packages:
-
-```powershell
-python -m pip install -r scripts/adapters/python/requirements.txt
-```
-
-The worker is optional and isolated. Missing Python or packages returns
-`OPTIONAL_DEPENDENCY_MISSING` for Terraform/SQL without preventing other CLI
-formats from loading. The worker reads bounded JSON from stdin, returns
-sanitized records on stdout, and never returns raw HCL/SQL bodies.
-
-Current pins and licenses:
-
-| Package | Version | License | Use |
-| --- | --- | --- | --- |
-| `python-hcl2` | `8.1.2` | MIT | Terraform HCL AST |
-| `sqlglot` | `30.12.0` | MIT | SQL DDL AST |
-
-Large multi-module HCL and multi-dialect SQL corpora remain `missing evidence`
-until executed. Do not describe small fixtures as complete dialect support.
-
-## Stable Identity And Relations
-
-- Terraform: module-qualified managed-resource address; `references` and
-  `depends-on` edges. Data/provider/local blocks are diagnostics.
-- Kubernetes: scope/namespace/kind/name. Unknown CRD scope needs an explicit
-  `kindScopes` API override; Secret data never enters attributes.
-- Compose: project/service plus separate named network/volume identities.
-- SQL: dialect/schema/table; FK discriminator uses constraint and column tuple.
-- OpenAPI: uppercase method plus case-preserving normalized path; summary and
-  operationId are display/comparison attributes only.
-- CI: provider/repo-relative workflow/job key; display names never identify a
-  job.
-
-Terraform, Kubernetes, and Compose export shared identity input builders and
-important attribute allowlists. Live adapters must import these exports rather
-than reproduce their string logic.
-
-## Evidence Boundary
-
-Deterministic fixtures, worker commands, JavaScript ELK, and XML validation are
-command evidence. Provider CLI, Desktop, Graphviz comparison, large corpora,
-and visual-model execution remain independent evidence states.

package/template/.trae/skills/drawio/references/docs/design-system/README.md

@@ -1,204 +0,0 @@
-# Draw.io Design System
-
-A unified design system providing consistent visual language for AI-generated draw.io diagrams.
-
----
-
-## Quick Start
-
-```yaml
-meta:
-  theme: tech-blue    # Select theme
-  layout: horizontal  # Layout direction
-
-nodes:
-  - id: api
-    label: API Gateway
-    type: service     # Auto-selects rounded rectangle
-
-  - id: db
-    label: User Database
-    type: database    # Auto-selects cylinder
-
-edges:
-  - from: api
-    to: db
-    type: data        # Dashed line with arrow
-    label: Query
-```
-
----
-
-## Core Concepts
-
-### Workflow Profiles
-
-Use profiles to choose the validation posture:
-
-| Profile | Best For |
-|---------|----------|
-| `default` | Standard diagrams |
-| `academic-paper` | IEEE figures, thesis diagrams, paper-ready exports |
-| `engineering-review` | Dense architecture and network diagrams |
-
-### 8px Grid System
-
-All positions, sizes, and spacing are multiples of 8px for professional alignment.
-
-| Spacing | Value | Usage |
-|---------|-------|-------|
-| Node margin | 32px | Minimum space between nodes |
-| Container padding | 24px | Space inside modules |
-| Canvas padding | 32px | Edge to content |
-
-### Themes
-
-7 built-in themes for different use cases:
-
-| Theme | Use Case |
-|-------|----------|
-| **Tech Blue** | Software architecture, DevOps |
-| **Academic** | IEEE papers, grayscale print |
-| **Nature** | Environmental, lifecycle |
-| **Dark Mode** | Presentations, slides |
-| **Architecture Dark** | Role-coded system/microservice/cloud architecture |
-| **Academic Color** | Academic papers, research (color print/digital) |
-| **High Contrast** | WCAG AA accessible, maximum readability |
-
-### Replication Color Modes
-
-When redrawing from an uploaded image, keep theme selection and color extraction separate:
-
-| Mode | Default? | Behavior |
-|------|----------|----------|
-| `preserve-original` | Yes | Keep the source background and dominant palette, writing explicit style overrides for high-confidence colors. |
-| `theme-first` | No | Use the selected theme as the primary palette and only keep source colors as hints/reference metadata. |
-
-Replicated specs should usually include `meta.source: replicated` and a `meta.replication` block so later edits can tell which colors came from the image and which colors are theme fallbacks.
-
-### Text and Label Fidelity
-
-For ordinary generated diagrams, labels usually live inside their shapes. For screenshot or reference-image replication, text placement can carry meaning and should be preserved explicitly:
-
-- use `type: text` for standalone titles, captions, callouts, legends, and explanatory notes;
-- use `type: formula` for dedicated formula annotations, with official math delimiters;
-- use `bounds: {x, y, width, height}` when exact text-box geometry matters (`bounds` is top-left based);
-- use `position: {x, y}` for center-point placement of ordinary nodes;
-- use `labelOffset: {x, y}` on edges to keep labels 12-20px off the connector instead of sitting on top of the line.
-
-### Semantic Shapes
-
-Automatic shape selection based on node type:
-
-| Type | Shape |
-|------|-------|
-| `service` | Rounded rectangle |
-| `database` | Cylinder |
-| `decision` | Diamond |
-| `terminal` | Stadium/Pill |
-| `queue` | Parallelogram |
-| `user` | Ellipse |
-| `document` | Document |
-| `formula` | Rectangle |
-| `text` | Standalone text box |
-
-### Typed Connectors
-
-Visual hierarchy through connector semantics:
-
-| Type | Style | Usage |
-|------|-------|-------|
-| `primary` | Solid 2px | Main flow |
-| `data` | Dashed 2px | Data/async |
-| `optional` | Dotted 1px | Weak relation |
-
----
-
-## Documentation
-
-| Topic | Description |
-|-------|-------------|
-| [tokens.md](tokens.md) | Color, spacing, typography tokens |
-| [themes.md](themes.md) | Built-in themes & customization |
-| [shapes.md](shapes.md) | Semantic shape vocabulary |
-| [connectors.md](connectors.md) | Connector types & routing |
-| [icons.md](icons.md) | Cloud provider & DevOps icons |
-| [formulas.md](formulas.md) | LaTeX/MathJax integration |
-| [specification.md](specification.md) | YAML specification format |
-
----
-
-## Example: Microservices Architecture
-
-```yaml
-meta:
-  theme: tech-blue
-  layout: horizontal
-
-modules:
-  - id: frontend
-    label: Frontend
-  - id: backend
-    label: Backend
-  - id: data
-    label: Data Layer
-
-nodes:
-  - id: web
-    label: Web App
-    type: service
-    module: frontend
-    
-  - id: api
-    label: API Gateway
-    type: service
-    module: backend
-    icon: aws.api-gateway
-    
-  - id: users
-    label: User Service
-    type: service
-    module: backend
-    
-  - id: db
-    label: PostgreSQL
-    type: database
-    module: data
-
-edges:
-  - from: web
-    to: api
-    type: primary
-    
-  - from: api
-    to: users
-    type: primary
-    
-  - from: users
-    to: db
-    type: data
-    label: CRUD
-```
-
----
-
-## Design Principles
-
-1. **Content in Components, Except When Position Matters**: Prefer embedding ordinary labels in nodes, but treat standalone text, formula annotations, captions, callouts, and edge labels as first-class elements during replication when their separate position carries meaning.
-   > 普通图中优先把文字写入形状组件；复刻图时，如果标题、说明、公式或边标签的独立位置本身有意义，就把它们作为一等文本元素处理。
-2. **KISS**: Simple, predictable styling
-3. **DRY**: Reusable tokens and themes
-4. **Consistency**: Same semantic = same visual
-5. **Accessibility**: High contrast, print-safe options
-
----
-
-## Migration from A-H Format
-
-The legacy A-H format is replaced by YAML specification. See [specification.md](specification.md) for migration guide.
-
-| Before (A-H) | After (YAML) |
-|--------------|--------------|
-| Free-text sections | Structured fields |
-| Implicit styling | Explicit themes |
-| No validation | JSON Schema |

package/template/.trae/skills/drawio/references/docs/design-system/color-guide.md

@@ -1,255 +0,0 @@
-# Theme and Palette Selection Guide
-
-A guide to choose diagram structure styling and category colors independently.
-(主题与配色组选择指南 — 分别决定排版风格与类别颜色。)
-
----
-
-## Decision Tree (3 Steps to Choose a Theme)
-
-```
-Step 1: Final use case? (最终用途？)
-  ├── Print / Publication (印刷 / 出版)
-  │   ├── Color print / Digital PDF → academic-color ⭐
-  │   └── Strict grayscale (IEEE submission) → academic
-  └── Digital / Screen display → Continue to Step 2
-
-Step 2: Target audience? (目标受众？)
-  ├── Technical / Engineering → tech-blue (default)
-  ├── Academic / Research → academic-color
-  ├── Presentation / Slides → dark
-  └── Environmental / Ecology → nature
-
-Step 3: Special requirements? (特殊要求？)
-  ├── High contrast (accessibility) → academic or tech-blue
-  ├── Dark background projector → dark
-  └── Other → Use Step 2 result
-```
-
----
-
-## Theme and Palette Are Independent
-
-Theme and palette are independent, orthogonal dimensions:
-
-- `meta.theme` owns typography, spacing, shape treatment, connector line styles, modules, and canvas.
-- `meta.palette` optionally replaces semantic/category fill, stroke, text, and default connector colors.
-- Content-neutral `text` and `formula` nodes always keep theme styling; a palette never recolors them.
-- Omitting `meta.palette` keeps existing theme behavior unchanged.
-
-```yaml
-meta:
-  theme: academic
-  palette: okabe-ito
-```
-
-This combines academic typography and line treatment with Okabe-Ito category colors. Switching only the palette does not change fonts, spacing, shapes, or routing.
-
-### Palette Decision Tree
-
-```text
-Was a palette explicitly named?
-  yes -> apply it directly; do not ask
-  no  -> does the request mention palette/color choice, colorblind safety,
-         grayscale or black-and-white printing, or multi-category distinction?
-           yes -> ask once with 3-4 relevant palette choices
-           no  -> omit meta.palette and keep the theme defaults
-
-Replicate route?
-  yes -> preserve source colors and skip palette selection unless the user
-         explicitly asks to normalize or replace the colors
-```
-
-Use the complete metadata-backed catalog and previews in [`references/examples/palettes/README.md`](../../examples/palettes/README.md). Common starting points:
-
-| Need                                         | Recommended palette |
-| -------------------------------------------- | ------------------- |
-| Accessible academic color                    | `okabe-ito`         |
-| IEEE or thesis black-and-white print         | `ieee-bw`           |
-| Camera-ready color with grayscale separation | `tol-high-contrast` |
-| C4/software architecture                     | `c4-blue`           |
-| AWS/cloud architecture                       | `cloud-aws`         |
-| Familiar draw.io appearance                  | `drawio-classic`    |
-
-### Add a Custom Palette
-
-Copy one bundled JSON definition from `assets/palettes/`, keep the single ordered `entries[]` contract, validate it, and save it as `~/.drawio-skill/palettes/<name>.json`. No code change is required. User definitions override bundled palettes with the same name and emit an info diagnostic. Explicit unknown, malformed, or invalid palettes fail and list available names; they never silently fall back.
-
----
-
-## Theme Quick Reference
-
-| Theme              | Primary   | Secondary | Background | Best For                                                              |
-| ------------------ | --------- | --------- | ---------- | --------------------------------------------------------------------- |
-| **tech-blue**      | `#2563EB` | `#059669` | `#FFFFFF`  | Architecture, DevOps, system design, API docs                         |
-| **academic-color** | `#2563EB` | `#059669` | `#FFFFFF`  | Paper figures, research reports (color print), deep learning diagrams |
-| **academic**       | `#1E1E1E` | `#1E1E1E` | `#FFFFFF`  | IEEE papers, grayscale print, formal publications                     |
-| **dark**           | `#60A5FA` | `#34D399` | `#0F172A`  | Presentation slides, screen display, dark mode                        |
-| **nature**         | `#059669` | `#84CC16` | `#FFFFFF`  | Lifecycle flows, environmental systems, green themes                  |
-
----
-
-## Semantic Color Meanings (Cross-theme Convention)
-
-Different node types follow a unified semantic meaning across themes, even if the specific colors differ:
-(不同节点类型在各主题中遵循统一的语义含义，即便具体颜色有差异。)
-
-| Node Type  | Semantic Meaning           | tech-blue Fill             | Description                                      |
-| ---------- | -------------------------- | -------------------------- | ------------------------------------------------ |
-| `service`  | Main flow / API processing | `#DBEAFE` (light blue)     | Primary processing unit, most common             |
-| `database` | Persistent storage         | `#D1FAE5` (light green)    | Data persistence layer, distinct from services   |
-| `decision` | Conditional / Branch       | `#FEF3C7` (light amber)    | Diamond shape, key flow control point            |
-| `queue`    | Async / Message queue      | `#EDE9FE` (light purple)   | Decoupled communication, async processing        |
-| `terminal` | Flow start / end           | `#F1F5F9` (light gray)     | Marks flow boundaries                            |
-| `user`     | External actor / Role      | `#E0F2FE` (light sky blue) | Person or external system, distinct from service |
-| `document` | File / Report              | `#FFFBEB` (light yellow)   | Output artifact, not a processing unit           |
-| `cloud`    | External network / SaaS    | `#F0FDF4` (light green)    | Third-party or network services                  |
-
-### Agentic / LLM node colors (tech-blue defaults)
-
-| Node Type      | Semantic Meaning                  | tech-blue Fill     | Stroke    |
-| -------------- | --------------------------------- | ------------------ | --------- |
-| `llm`          | LLM / foundation model            | `#EDE9FE` (violet) | `#7C3AED` |
-| `agent`        | Agent / orchestrator              | `#DBEAFE` (blue)   | `#2563EB` |
-| `vector_store` | Vector / embedding store          | `#D1FAE5` (green)  | `#059669` |
-| `memory`       | Short-term memory (dashed border) | `#FEF9C3` (amber)  | `#CA8A04` |
-| `tool`         | Tool / function                   | `#F1F5F9` (slate)  | `#475569` |
-| `gateway`      | API gateway                       | `#FFEDD5` (orange) | `#EA580C` |
-
-These are default/light-theme values. In arch-dark and academic the theme node palette
-overrides them (arch-dark maps to its cyan/emerald/violet roles; academic to grayscale).
-The same concept never carries two competing colors in one theme.
-
----
-
-## Color Override Rules
-
-### Restraint for Infrastructure Diagrams
-
-Keep background fills to a small, intentional set. Use semantic colors for roles and neutral containers for hierarchy; provider icon colors remain their own identity and should not become a second competing role palette. A legend is required whenever color or line style carries meaning that cannot be read from labels alone.
-
-### Prefer Theme Tokens (Strongly Recommended)
-
-Tokens are automatically compatible with theme switching; hardcoded hex values break when themes change:
-(Token 与主题切换自动兼容，硬编码 hex 会在切换主题后失效。)
-
-```yaml
-# Recommended: Use tokens
-nodes:
-  - id: api
-    style:
-      fillColor: $primaryLight # Adjusts automatically with theme
-      strokeColor: $primary
-      fontColor: $text
-
-# Avoid: Hardcoded hex
-nodes:
-  - id: api
-    style:
-      fillColor: "#DBEAFE" # Breaks when switching to dark theme
-```
-
-### Palette Token List
-
-With `meta.palette` selected, category entries are also available as 1-based tokens:
-
-```text
-$paletteN         entry N base color
-$paletteN-fill    entry N materialized fill
-$paletteN-stroke  entry N materialized stroke
-$paletteN-text    entry N materialized text color
-```
-
-An out-of-range palette token warns and falls back to the theme primary color. Palette tokens are invalid when `meta.palette` is absent.
-
-### Theme Token List
-
-```
-Base Colors:
-  $primary          Primary color (blue/green/dark, varies by theme)
-  $primaryLight     Light variant of primary (recommended for fills)
-  $secondary        Secondary color (database nodes default)
-  $secondaryLight   Light variant of secondary
-  $accent           Accent color (decision nodes default)
-  $accentLight      Light variant of accent
-  $background       Canvas background color
-  $surface          Card/module background color
-  $surfaceAlt       Alternate background color
-
-Text & Borders:
-  $text             Primary text color
-  $textMuted        Secondary text color
-  $textInverse      Inverse text (for dark backgrounds)
-  $border           Standard border color
-  $borderStrong     Bold border color
-
-Semantic Colors:
-  $success          Success state (green)
-  $successLight     Light success
-  $warning          Warning state (yellow/orange)
-  $warningLight     Light warning
-  $error            Error state (red)
-  $errorLight       Light error
-  $info             Info hint (blue)
-  $infoLight        Light info
-```
-
----
-
-## Connector Color Rules
-
-| Connector Type  | Line Style                                        | Recommended Use                                  |
-| --------------- | ------------------------------------------------- | ------------------------------------------------ |
-| `primary`       | Solid 2px, filled arrow                           | Main flow, default choice                        |
-| `data`          | Dashed 2px (6 4), filled arrow                    | Data transfer, async communication               |
-| `optional`      | Dotted 1px (2 2), open arrow                      | Optional path, fallback logic                    |
-| `dependency`    | Solid 1px, diamond arrow                          | Dependency, composition                          |
-| `bidirectional` | Solid 1.5px, no arrow                             | Bidirectional association, communication channel |
-| `control`       | Solid 1.5px, filled arrow, orange `#EA580C`       | Trigger / control signal (agentic)               |
-| `memory_read`   | Solid 1.5px, filled arrow, green `#059669`        | Read from store / memory                         |
-| `memory_write`  | Dashed 1.5px (5 3), filled arrow, green `#059669` | Write to store / memory                          |
-| `async`         | Dashed 1.5px (4 2), open arrow, gray `#6B7280`    | Async / non-blocking event                       |
-| `feedback`      | Solid 1.5px, filled arrow, violet `#7C3AED`       | Iterative feedback loop                          |
-
-> Connector colors automatically inherit `$text` (dark); no manual override needed unless special semantic annotation is required.
-> (连接线颜色自动继承 `$text`（深色），无需手动设置除非有特殊语义标注需求。)
->
-> **Theme priority**: The agentic edge colors above are default/light values. Precedence is
-> **explicit edge `style` > theme token > type default** — within arch-dark and academic these
-> types remap to the theme's own palette (arch-dark keeps its role colors; academic falls back
-> to grayscale + dash). When ≥2 arrow semantics appear, add a `meta.legend` (compact single
-> text-node form); see [connectors.md](connectors.md).
-
----
-
-## Color Consistency Checklist
-
-Before generating a YAML spec, verify each item:
-(生成 YAML spec 前，请逐项确认。)
-
-```
-[] Theme explicitly selected (meta.theme is set)
-[] Palette selected only when the request needs one (meta.palette is optional)
-[] Selected palette safety flags match colorblind and print requirements
-[] All custom fillColor uses tokens or valid hex (#RGB or #RRGGBB)
-[] strokeColor and fillColor use matching deep/light token pairs
-   e.g.: fillColor: $primaryLight + strokeColor: $primary
-   e.g.: fillColor: $primaryLight + strokeColor: $error (semantic mismatch)
-[] Decision nodes use $accentLight / $accent for visual distinction from main flow
-[] Connector colors not overridden, keeping default $text color
-[] In dark theme, confirm fontColor uses $textInverse for adequate contrast
-[] Module backgrounds use $surface instead of $background (layer distinction)
-```
-
----
-
-## Common Color Mistakes & Fixes
-
-| Mistake                      | Problem                                                     | Fix                                                   |
-| ---------------------------- | ----------------------------------------------------------- | ----------------------------------------------------- |
-| All nodes same color         | Cannot distinguish node types                               | Use semantic type auto-coloring; don't manually unify |
-| Decision node with blue fill | Confused with service nodes                                 | Use `$accentLight` (amber/yellow) fill instead        |
-| Black text on dark theme     | Insufficient contrast                                       | Add `fontColor: $textInverse`                         |
-| All hardcoded hex values     | Styles break on theme switch                                | Use token references instead                          |
-| Colored connectors           | Visual noise, distracting                                   | Only override connector color for special semantics   |
-| Treating theme as a palette  | Changing colors also changes layout/typography expectations | Keep theme and `meta.palette` as separate choices     |