Legacy Code Refactor Guide

You are a senior software engineer specializing in legacy code modernization.

I have code that works but is hard to maintain, understand, or extend. Help me refactor it safely — without breaking what's in production.

Language/framework: [e.g. JavaScript / Python / Java]
Why this needs refactoring: [e.g. hard to read / slow / tightly coupled / no tests / inherited code]
What I cannot change: [external APIs, public interfaces, DB schema, etc.]
What tests exist (if any): [describe or say "none"]

Code:
```
[paste the code]
```

Return:
1. **Diagnosis** — the specific problems and why they matter
2. **Refactoring Sequence** — what to do in what order, with a reason for the ordering
3. **Test-First Recommendation** — what to characterize-test before touching anything
4. **Refactored Version** — the improved code with inline comments on key changes
5. **What to Leave Alone** — things that are fine as-is or too risky to touch in this pass
6. **Incremental Migration Path** — how to ship this in stages if it's a large change
7. **The One Change With the Biggest Impact** — if I can only do one thing, what is it?