aih-bugfixlisted

## Task Triage and fix a bug. Two phases: first diagnose and get approval, then fix autonomously. $ARGUMENTS ## Phase 1 — Question & Approval ### 1. Load Context - Read `.aihaus/memory/MEMORY.md` (if it exists) for prior patterns and gotchas - Read `.aihaus/project.md` (if present) for project-level context - Read `.aihaus/decisions.md` (if present) — do not contradict any ADR - Read `.aihaus/knowledge.md` (if present) — avoid known pitfalls ### 1.5. Persist Attachments If the user's bug report includes a pasted image (screenshot of error UI, stack trace image) or file (log, crash dump): 1. Copy **immediately on first mention** via `cp`. If slug is known, target `.aihaus/bugfixes/[YYMMDD]-[slug]/attachments/[seq]-[desc].[ext]`. If slug is not yet determined, target temp dir `.aihaus/bugfixes/YYMMDD-wip-HHMMSS-<rand4>/attachments/` and `mv` on slug finalization (M004 story H — prevents loss if conversation drops). Source usually `~/.claude/image-cache/[uuid]/[n].png`. See `pkg/.aihaus/skills/aih-plan/annexes/attachments.md` for canonical temp-slug + crash-recovery protocol. 2. Describe each via vision. 3. List in TRIAGE.md `## Attachments` section. 4. When spawning the `debugger` agent (Step 2), include the attachment paths in its prompt so it can `Read` them during root-cause analysis. ### 2. Triage (delegate to debugger agent) Spawn the `debugger` agent with `subagent_type: "debugger"` and the instruction: > "Investigate this bug using scientific method. Symptom: [user