changeslisted

> **Script path fallback**: qq scripts are invoked as bare commands (e.g. `unity-test.sh`). If "command not found", use `${CLAUDE_PLUGIN_ROOT}/bin/<command>` instead. Respond in the user's preferred language (detect from their recent messages, or fall back to the language setting in CLAUDE.md). Summarize all changes Claude Code made during this conversation. ## Behavior Review the current conversation context and identify all **file changes actually executed** by Claude in this conversation (file modifications made via Edit/Write/Bash tools), then summarize them grouped by logic. **The data source is the conversation context, not git diff.** The user may have gone through multiple rounds of changes in a single conversation — some already committed, some not. Summarize all of them. After producing the summary, if `qq-run-record.py` is available, persist a `changes` run record so controller state can advance: ```bash qq-run-record.py record \ --project . \ --stage changes \ --command qq:changes \ --status checked \ --summary "Conversation change summary captured" \ --capture-local-changes ``` Only do this after the summary is complete. ## Output format ``` ## Summary of changes in this conversation ### <Group 1 title> - What was done - Key files: ... ### <Group 2 title> - ... ### Status - Committed: <list of commit hashes, if any> - Uncommitted: <list of files, if any> - Compilation: passed / not verified - Tests: N/N passed / not run ``` ## Notes - L