Both pending items from #452's review landed in one PR — high-contrast brings the first-party set to three (matching #449's third theme), and bare /theme opening a picker is the right shape since it mirrors /model. Lifting themeName into App so a save triggers a live re-render (instead of waiting for next launch) is the right call too.

The picker's current preference / active now tags subsume what formatThemeStatus used to print — losing the verbose status line is a net UX win, and the test asserting both tags is a nice touch.

One stale-merge note: package-lock.json shows 0.30.5 → 0.33.2, but main is already on 0.36.0. Not blocking — I'll regenerate post-merge.

Will merge as-is.

Actually one ask before I merge — it's CONFLICTING against main right now (package-lock.json: your branch is on 0.33.2, main shipped 0.36.0). Can you rebase on main and regenerate the lockfile (npm install after the rebase)? Once it's green I'll land it.

Actually one ask before I merge — it's CONFLICTING against main right now (package-lock.json: your branch is on 0.33.2, main shipped 0.36.0). Can you rebase on main and regenerate the lockfile (npm install after the rebase)? Once it's green I'll land it.

finished

Thanks for the picker! I rebased it onto current main (which had moved on with #549 / #552 / #555 / #560 / #566 since you opened this) and patched the count test that needed a bump from 12 → 11 advanced commands once /theme moved out of the advanced group — easy to miss. The rebased version is at #567 and goes out in the next release. Closing this in favour of that one — your authorship is preserved on the originating commits.