Every version, and what it changed for you.

Archis can keep itself up to date.

Before you upgrade — Nothing to do. Automatic updates are off until you say otherwise: chi init asks the next time you run it, and an installation that has never been asked never installs anything on its own. Set CHI_AUTO_UPDATE=0 to force it off everywhere, whatever the answer was.

• NewArchis will now install new releases by itself, if you tell it to. Until this release the only thing a newer version could do was mention itself once a day and wait for you to get round to chi update — which mattered more than it sounds, because a coding agent talking to an Archis that is a release behind its own index does not degrade gently: it gets an error where it expected your code, and falls back to reading files one at a time. chi init now asks the question once, and chi update --auto on or --auto off changes the answer whenever you like. chi update itself is unchanged, and still there for the times you want the new version now rather than tomorrow.
• NewIt is deliberately timid about when it does that. It checks at most once a day, and only ever at the end of a command that has already finished — so an update can never turn a command that worked into one that failed, and if the download fails you keep the version you had and get told. It stays out of CI entirely, stays quiet whenever the output is being piped into something rather than read by a person, and leaves long-running servers alone rather than swapping the binary underneath an editor that is holding it open. Every download is checked against its published checksum and signature before it replaces anything, exactly as chi update does.