exo

Use before changing Exo graph domain types, snapshot construction, relationship extraction, graph queries, Knowledge Profiles, graph integrity checks, layout, scene logic, WebGPU/Canvas rendering, Graph Pane integration, or graph performance tests. Preserves Markdown ownership, open ontology, evidence, renderer independence, editor latency, deterministic layout, and fallback behavior.

Use before changing Exo terminal runtime, rendering, settings, tests, or terminal-backed Command launch behavior. Keeps the current direct-PTY, xterm-owned, provider-neutral terminal aligned with byte fidelity, bounded replay, honest lifetime, and real Electron QA invariants.

Use before changing Exograph onboarding, settings, AgentCommand config, mention confirmation, graph context, or diff/attribution UI to keep screens dense, scannable, and low-prose.

Use when a user reports an Exo bug, QA finding, setup failure, confusing UX, regression, crash, terminal/rendering issue, graph/search/invocation/review problem, or asks to add, file, submit, track, deduplicate, or promote an Exo issue.