Pitstop

Update only the owner's chosen registered computer, never the bot's own box.

Update every tool in the registry, including Homebrew-installed ones. A brew row upgrades only that formula or cask with HOMEBREW_NO_AUTO_UPDATE=1 brew upgrade [--cask] <name>, takes its candidate from brew info --json=v2, and is checked afterwards so that only that package and its required dependencies changed. Declarative Homebrew (nix-homebrew, Brewfile) is not a reason to skip; skipped-managed is only for versions the config itself pins, such as a nix-store binary.

Never run the owner's declarative rebuild entry point (nix, darwin-rebuild, home-manager, dotfiles rebuild script); only name it in reports.

Update scripts live at ~/.pitstop/update.sh on the owner's computer, with registry.txt, detect.sh, backups and last-run.log in ~/.pitstop.

Use when running, editing, or debugging a registry-driven developer toolchain update on the owner's computer.

Use when writing or fixing detect.sh, which classifies how a CLI, plugin, or checkout was installed and picks its version, candidate, and upgrade commands.

Use for the first conversation with a new owner, to set up their daily toolchain update.