## 0.77.3

- **Upgrading is one command, on whichever road installed the deployment.** It was three: fetch a
  tarball by hand, unpack it, then run the installer inside it. Nothing justified the difference,
  and the reason the documentation gave, that upgrades are never automatic, argues against a
  deployment that updates itself rather than against a command an operator types on purpose naming
  the version. The carriers already fetched, verified and handed off to the bundle's own
  `install.py`, which is what reads `STATE` and checks the new bundle against the key this
  deployment pinned; only the verb was hardcoded. A test holds the three roads to the same verbs.