prlisted

Use this template for writing the PR body: ```markdown ## Summary <diagram, diff-sketch, or tree> ## Evidence - **Before:** <screenshot/output/failing test run> **After:** <screenshot/output/passing test run> ## Merge danger **Door:** <one-way or two-way> <optional: description> **Blast radius:** <one-word description> <optional: potential ramifications of merge> ``` ## Sections Skip all preambles and keep prose brief. Use the user's domain language from the glossary (`docs/agents/domain.md` gives the layout; by default `GLOSSARY.md`). ### Summary Pick the smallest view that makes the key point clear. - Show logic or an algorithm as pseudocode: ```text on(save) if content is unchanged return cached result write new content return fresh result ``` - Show runtime control flow as a call tree: ```text submitForm createSession persistPrompt launchAgent navigateToSession ``` - Show UI structure as a component tree, including state and module boundaries that matter: ```tsx <SessionPage> // apps/example/src/routes/session.tsx useSessionEvents() <SessionToolbar> <RunSkillButton /> // packages/ui ``` - Show file responsibility or a broad refactor as a shallow file tree: ```text src/ ├── commands/ # parses user actions ├── sessions/ # owns session state └── transport/ # sends API requests ``` - Show component interaction, control flow, or data flow with Mermaid: ```mermaid sequenceDiagram participan