Changes touching this path

• you cannot build it from source, and the page says so: the Install page stops offering a command no reader can run (#841) `cargo install --git https://github.com/Connor-Miller/loot loot-cli` was labelled as needing read access to a repo that is not public — true, and still a command every reader of a public page is unable to run. Read strictly, #809 first acceptance criterion (no command on the Install page fails against the current release) was not met while it stood. Removed rather than relabelled, because the honest answer is a position and not a caveat: the source is private permanently (ADR 0045), so there IS no build-from-source route, and there is no source archive to fetch either. A labelled command reads as an invitation and pays out an error; a stated position lets a reader decide about loot instead of debugging their own access. What it costs is stated on the page rather than promised away — you are trusting bytes you did not compile — and the counterweight already exists and is now pointed at: every archive carries its SHA-256 in the all-platforms table, and Evidence (#840, which just made those receipts openable anonymously) carries the run output behind each claim. ADR 0045 gains the amendment the ticket asked for, because this is a consequence of that decision nobody had written down: the ADR moved the DOWNLOAD path to R2 and never said what happens to the BUILD path. It also records the only thing that would restore one — #672 crates.io naming call, which makes `cargo install loot-cli` work without the repo being public — and that a source tarball on R2 would be the wrong way to do it, publishing source through a side door of a decision that was about binaries. Verified: zero github.com anywhere in the built Install page, suite 77 passed | 23 skipped, build green. 5b43d681 · dbf3dbe6…

Renames are not followed. loot's tree maps a path to an address, so a rename is a delete and an add. This list is the history of the name, not of the bytes.