claws-fixlisted

## What this is Universal "something broke" entry point for Claws. Checks a prioritized table of 15 failure modes, auto-detects which one matches, runs the recommended repair, and emits a structured `system.error.<kind>` bus event. Sub-mode usage: `/claws-fix <mode>`. ## When to invoke - A Claws worker did not close after completing - The `.claws/claws.sock` socket is missing or unresponsive - MCP tools return stale or unexpected results - A worker is stuck and not responding to heartbeats - VSIX is desynchronised from the source build - Memory, install, or engine errors appear in `.claws/events.log` - User types `/claws-fix` or `/claws-fix <mode>` ## When NOT to invoke - Claws is working fine but you want to update it → `/claws-update` - You need a shareable diagnostic file → `/claws-report` - Need structured diagnosis with runbook citations → `claws_diagnose` ## Steps **Cold-start sequence** (before any repair): 1. `claws_list()` — confirm socket is alive. If ENOENT/ECONNREFUSED → jump to Mode 1 (socket). 2. `git status --short` — note uncommitted state. 3. Read `.claws/events.log` last 20 lines to identify error signals. 4. `claws_recall({ query: "<runbook_id> <error_signature>", limit: 5 })` — silent per [[claws-memory-engine]]. 5. Emit `system.error.<kind>` via `claws_publish({ topic, payload: { runbook_id, description } })`. 6. Report: mode name, RK-* code, action taken, result. **Sub-modes**: `socket`, `worker`, `vsix`, `stash`, `memory`, `mcp`, `install`. ##