engine-upgradelisted

## Steps 1. See where the engine stands — this only checks and changes nothing — by running: `uv run --directory .engine -- python tools/module_manager.py upgrade` (add a specific version at the end to check that one instead of the latest). Show the operator the result exactly as printed — the version they're on and the one available, and the files, settings, and stored-data changes an update would make. Do not summarize or reword it. Then route on what it reports and what the operator wants: - **An update is available and they want it** → the apply path, steps 2–3. - **It reports a consistency problem / an update left unfinished** → the engine is part-way through an update; go to step 4 (finish it or undo it). - **They want to undo an update** (a half-finished one, or one that's already merged) → step 4. - **Up to date, or it couldn't reach the update home** → say so plainly and stop. 2. Before applying, tell the operator plainly what applying does: it downloads the new version and runs its own update steps, then opens the change as a **pull request for your review** — nothing about the running engine changes until you merge it, and merging can be undone by reverting it. If the check flagged a stored-data change with no backup set up, say a backup must be set up first or the update will refuse that step. 3. Only after the operator says to go ahead, apply the update by running: `uv run --directory .engine -- python tools/module_man