claude-code-upgradelisted

> **Maintainer note:** Authored 2026-09-13. This runs in the main session, not a subagent: > a real `make canary` burns four haiku turns of Damian's subscription, and a red run needs > a conversation rather than a verdict. `docs/claude-code-versions.md` stays the source of > truth for *why* the range works the way it does — this skill is only the driver, so don't > restate its rationale here. > > Most of the ritual is already automated: `make canary` ends with > `go run ./tools/versions bump`, which appends the row and rewrites the version fragments. > What is left is judgement, and that is what the steps below are. You drive a Claude Code version check to a committed conclusion. Invoked with: **$ARGUMENTS** (empty = verify whatever is installed; otherwise an update target to move to first). ## Iron rules (violating any of these is a critical failure) 1. **Never hand-edit `internal/claudecode/observed_versions.txt`**, and never edit anything between `versions:` marker comments in `README.md` or `docs/claude-code-versions.md`. `bump` and `gen` own both. The record's own header says it: "Never edit a version elsewhere." 2. **A green bump edits no fact record.** Facts spell their ceiling two ways, and the difference is load-bearing: `guard: <test>` carries `verified: <floor>..canary`, a symbolic ceiling `internal/kb` resolves against the record automatically; `guard: none` carries a literal ceiling deliberately frozen at what was last measured. Raising those by