Closes #76 Pre-fix, a user who answered `y` at the all-or-nothing cleanup prompt ("What would you like to do?") saw nothing deleted if their terminal session's input stream ended before they re-answered for every candidate — the per-version loop fired unconditionally for every version in `toOffer` because `cfg.PerVersion` defaults to `true` from `cfg.Cleanup.Prompt`'s config default, the `default:` branch of `promptPerVersion` returned `false` for empty / non-`y` input, and every version landed in `result.Skipped` with no visible error. User reported live: answered `y` at the cleanup prompt during a real `nodeup upgrade`, then `fnm list` afterward still showed the old versions — no deletion occurred, with no surface indication of why. Fix: confirmation is now sticky at the level the user chose to operate at. Three classes of higher-level confirmation set `cfg.PerVersion = false` for the per-version loop: 1. `decision.deleteAll` — `y`/`yes` at the all-or-nothing prompt. 2. `decision.deleteOne` — a specific version typed at the all-or-nothing prompt (the user's choice IS the per-version confirmation). 3. `AutoDeleteAll` (without `ForcePerVersion`) — set by `--cleanup`, `--yes`, or `cfg.Cleanup.Auto`. The user's pre-flight opt-in counts; the per-version prompt is redundant. The `ForcePerVersion` downgrade from #58 is the only path that keeps `cfg.PerVersion = true` after Step 1b, because it represents an inability to safely exclude the active version from the candidate set — when `Manager.Current()` errors, we fall back to per-version y/N to avoid mass-deletion. All three `TestCleanupPrompt_ForcePerVersion*` tests confirm this preservation. `TestCleanupPrompt_PerVersionConfirm` and `TestCleanupPrompt_SpecificVersion` (the tests that pinned the buggy double-prompt behavior) are rewritten to assert the new correct behavior. `TestCleanupPrompt_DeleteAllSkipsPerVersionPrompt` is the explicit regression test for #76 — two candidates, only `y\n` supplied, both must be deleted and no "Delete v" prompt may appear in the output. CHANGELOG: ### Fixed entry under [Unreleased]. Co-Authored-By: puku-ai-2.8 <noreply@puku.sh>

Commits

Commits on Jul 3, 2026

fix(cli): make post-upgrade cleanup confirmation sticky, no silent override