fix

# fix ## Purpose Apply code changes. Fix receives a plan, debug finding, or review finding and writes the actual code. It does NOT investigate root causes — that is rune:debug's job. Fix is the action hub: locate, change, verify, report. <HARD-GATE> Never change test files to make tests pass unless the tests themselves are provably wrong (wrong expected value, wrong test setup, testing a removed API). The rule: fix the CODE, not the TESTS. If unsure whether the test is wrong or the implementation is wrong → call `rune:debug` to investigate. </HARD-GATE> ## Triggers - Called by `cook` Phase 4 IMPLEMENT — write code to pass tests - Called by `debug` when root cause found and fix is ready - Called by `review` when bugs found during review - `/rune fix <issue>` — manual fix application - Auto-trigger: after successful debug diagnosis ## Calls (outbound) - `debug` (L2): when root cause unclear before fixing — need diagnosis first - `test` (L2): verify fix with tests after applying changes - `review` (L2): self-review for complex or risky fixes - `verification` (L3): validate fix doesn't break existing functionality - `docs-seeker` (L3): check correct API usage before applying changes - `hallucination-guard` (L3): verify imports after code changes - `scout` (L2): find related code before applying changes - `neural-memory` (L3): after fix verified — capture fix pattern (cause → solution) - `adversary` (L2): on `agent.stuck` after 2+ failed attempts — oracle-mode dispatches st...