pr-descriptionlisted

# Write a PR title and description If the repository keeps its own PR template (`.github/pull_request_template.md`, or one under `.github/PULL_REQUEST_TEMPLATE/`) or documents a title convention, that wins; use the rest of this skill only for what it leaves open. Otherwise, use this template for 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 **Blast Radius:** <potential ramifications of merge> Closes <ISSUE>. Part of <PARENT-ISSUE>. ``` > **Tracker:** the tracker steps use whatever issue tracker this session can reach (an > issue-tracker MCP server or CLI the host has connected). The issue key format comes from the > project map in `AGENTS.md` or from the ids already in the branch's commits. No tracker? Skip > step 2 and drop the issue id and the closing line everywhere. ## Sections Skip all preambles and keep prose brief. Use the domain language from the project's glossary. ### 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 st