dev-improve-archlisted

# Dev Improve Arch Domain scan → friction inventory → ranked improvements → approve one at a time. ## Step 1 — Domain Scan Read the module without judging it. Understand it as it is. - What is the module's responsibility? - What patterns does it use? (classes, functions, hooks, services, etc.) - What are its dependencies — inbound (callers) and outbound (deps)? - How old is the code? (`git log --oneline -- {path} | tail -5`) - What has changed most recently? (`git log --oneline -10 -- {path}`) Do not propose changes yet. ## Step 2 — Friction Inventory List every source of friction you observe. One item per line: ``` FRICTION: {description} TYPE: complexity / coupling / duplication / naming / missing-abstraction / over-abstraction / performance IMPACT: high / medium / low EFFORT: high / medium / low ``` Examples: - "UserService has 12 methods mixing auth logic with profile logic" - "DB queries duplicated across 4 different files" - "Function names don't match what the functions actually do" ## Step 3 — Rank For each friction item, compute a priority score: ``` Priority = (Impact × 2) + (1 / Effort) ``` Sort highest to lowest. Present the top 5. ## Step 4 — Propose One Improvement Present only the highest-priority improvement with a concrete plan: ``` IMPROVEMENT: {name} PROBLEM: {what's wrong now} SOLUTION: {what it looks like after} FILES AFFECTED: {list} RISKS: {what could break} ROLLBACK: {how to undo if it goes wrong} ESTIMATED EFFORT: {hours / days} ``` D