self upgrade fetches nothing: it re-runs self install from the running binary, so no machine can move to a newer build #947

writ self upgrade, and lore and star alike, is newUpgradeCmd at cmd/internal/cli/selfinstall.go:125: it overwrites the installed binary with the one running and refreshes its man pages, completions and extensions. It fetches nothing. A machine at v0.1.0-dev.20260924074819 stays there whatever develop publishes; the only way up is make install from a clone, or the installer over again.

Upgrade should do what install.sh does for one product: resolve the newest pre-release for this platform (or DEVLORE_VERSION), download the archive, verify it against devlore-cli_<version>_checksums.txt, and run the unpacked product's self install <prefix>, so the record is refreshed the way #933 and #928 define. self upgrade --from <archive> keeps the offline path.

Found 2026-09-24 reading the tree at d54626d2.

Plan and design documents

Epic: #453 · Feature: #83