forge-fixlisted

# forge-fix The intake for bug reports in shipped work. A bug fix is a small unit of work and gets the same discipline as one — scoped, verified, recorded — just without the ceremony of a full spec. Without this, fixes happen outside the methodology and the tracker, lessons, and scope rules all leak. ## Argument Text after the command is the bug report (e.g. `/forge-fix login button does nothing on page A`) — use it as the intake description and don't re-ask what the bug is; ask only for missing specifics (exact error, where, since when). No argument → ask for the symptom. ## 1. Intake Load Tier 1: the digest (or entry point) and `context/lessons.md` — **check lessons first**; the bug may already be a known lesson with a known rule. State the failure precisely: expected vs actual, the exact error/wrong output, where it happens, and — if identifiable — which unit/change introduced it (`git log`, the build plan's `## Completed` section, and `context/progress-archive.md` can help date it). ## 2. Reproduce Establish the smallest repeatable reproduction before changing anything. If it can't be reproduced, that's the first job — not fixing. ## 3. Triage — one decision - **Obvious cause, small blast radius** (one boundary, no invariant in question) → fix it here, in scope. Read the Tier 2 context file(s) the fix touches (`code-standards.md` nearly always; `ui-context.md` for UI; `architecture.md` if a boundary is involved). - **Cause non-obvious, multiple candidate la