updatelisted

# Updating charter One command converges the upgrade. Your job is the conversation around it. ```bash charter update ``` It moves the CLI, asks this harness how its own artifact moves, proves the install took by handing off to the new binary, and reports what the new version brought. **Read its output and relay it** — that text is the report, not a summary of one. It is idempotent: run it without first working out whether there is anything to do. ## Where it stops, and what you do there **The pin.** When this plane already sits on its pin and something newer is published, `update` proposes `charter update --bump` and stops. Moving the pin moves every teammate on their next session, so get an explicit yes before running it. **PyPI.** When `update` ends up with no version from PyPI to check against, it says so. It does not fall back to a version an earlier check cached. It names two possible causes and does not say which one happened, so do not pick one for the person either. On a plane with no pin, or with `--bump`, it exits 1 without moving anything. To install a version you already know, run `charter update --to X.Y.Z`. On a machine on or ahead of its pin it exits 0 and says whether a newer release is published could not be checked. Relay exactly what it says about the pin. Do not call charter current or up to date. **An older release.** On a plane with no pin, when the newest release PyPI reports is older than the charter running, `update` installs nothing and exits