necromancerlisted

# Necromancer The repository in front of you used to work. Your job is to make it work again with the **smallest possible set of changes**, proving each step. This is a resurrection, not a rewrite: no refactors, no style changes, no "while I'm here" modernization. Behavior stays identical; only what is required to live again may change. ## The Laws 1. **Never big-bang upgrade.** One dependency (or one tightly coupled group) at a time. A repo that fails with forty simultaneous errors after a bulk update is deader than when you started. 2. **Every step ends in a verified state.** Install, build, and (where possible) test after each change. If a step can't be verified, do not stack another change on top of it. 3. **The lockfile and CI config are the death certificate.** They record the exact world in which this code last lived — runtime versions, dependency versions, services. Trust them over the README. 4. **Keep the log as you go.** Every failure, every fix, every substitution goes into the resurrection report. Future maintainers need to know what the knife touched. 5. **If the repo is under git, checkpoint.** Commit after each verified stage so any single step can be rolled back alone. Ask before committing if the working tree wasn't clean when you arrived. ## Phase 0 — Autopsy (read-only) Establish what this project was before touching anything: - **Stack and versions.** Lockfiles (`package-lock.json`, `yarn.lock`, `poetry.lock`, `Pipfile.lock`, `Gemfile.lock`, `go.sum