termio-bug-report

# Diagnose a freeze, then file it Two jobs, in this order: work out what actually broke, then turn that into an issue someone can act on. Skipping the first half produces "termio froze on my Mac", which no one can fix. ## 0. Before anything else: is it hung *right now*? Ask this first, in one line, and wait for the answer. **If the app is currently beachballing, do not let the user force-quit it.** The main-thread stack that explains the freeze exists only while the process is alive. Force-quitting destroys the single most valuable piece of evidence, and it cannot be recovered afterwards from any log. Capture it immediately: ```bash ./skills/termio-bug-report/scripts/collect.sh --minutes 60 ``` The script samples every live termio and termiod process first, before it touches anything slower. It prints the bundle directory it created; everything below works on that directory. It needs no privileges and never copies `pair.token`. If the freeze is already over, run the same command — the crash, CPU-burn, and unified-log evidence survives it, only the live stack is gone. ## 1. Read the evidence Read `manifest.md` first, then in this order — stopping as soon as something explains the symptom: 1. **`reports/index.md`** — one line per crash / CPU-burn report macOS wrote. A crash here usually ends the investigation on its own. 2. **`sample-*.txt`** — where each process's main thread actually is. 3. **`environment.md`** — versions, running processes, agent CLIs, memory. ...