Private
Public Access
install.sh and upgrade.sh deploy git tags, not branch tips, but the docs still described git pull/clone-and-run. Add a "Releases" section explaining the v<year>.<month>.<day> tagging convention and that a tag must exist before the first production install, update the manual upgrade steps to match what upgrade.sh actually does (fetch tags, checkout latest), and mention the /health/ endpoint upgrade.sh verifies against. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>