bug-fix

# Bug Fix ## Required Skills Load these skills based on bug scope (see Steps 2 and 5 for when): 1. `framework:knowledge-priming` -- Load project context (tech stack, architecture, conventions) so fix match real project (always) 2. `framework:context-anchoring` -- Load existing feature context doc when available, capture root cause + repair decisions for future (always) 3. `framework:learning-harvest` -- Load prior operational learnings inform diagnosis; harvest new patterns at session end (always) 4. `framework:collaborative-judgment` -- Surface meaningful repair trade-offs instead of silent patch choice (always) 5. `framework:clean-code` -- Keep fix focused, readable, minimal scope (always) 6. `framework:test-quality` -- Create + validate failing regression test that proves bug exists + fix works (always) 7. `framework:architecture` -- Validate layer placement, dependency direction, correct repair location (conditional) 8. `framework:domain-driven-design` -- Validate invariants, aggregate boundaries, domain behavior when bug involves domain logic (conditional) 9. `framework:secure-coding` -- Validate trust boundaries, input handling, authorization, injection safety when bug touches security-sensitive code (conditional) ## Workflow ### Step 1: Establish Bug Context Start from failure, not proposed fix. - Gather **observed behavior**, **expected behavior**, **reproduction path**, any evidence: failing test, error message, stack trace, log excerpt, request payload, recen...