Make the destructive commands impossible to mistake for a step "Never run these" was a bash block styled exactly like every safe command on the page, sitting right after the cleanup instructions. Someone working down the page and pasting as they go would have run it; the only thing marking it dangerous was a trailing comment. Now a table with the consequence in the wider column, under a heading that reads as a stop sign, with the flags split from the commands so no line in it works if pasted. Spells out that "not attached to a running container" includes every stopped devcontainer's database and credential volumes.
Restructure wiki: consumer guides, runbooks, and a documented split rule Establishes what belongs in the wiki versus the repo: a document that goes stale when this repo's code changes lives in the repo; one that goes stale when an external system changes -- Docker Desktop, GitHub settings, an upstream tool -- or that spans several images lives here. Per-image READMEs therefore stay put, because a tag list has to move in the same commit as its Dockerfile. New consumer-facing pages: - Choosing an Image: decision table across the six images, plus the fixed-toolchain vs bring-your-own-toolchain distinction that matters more than the tool lists. - Image Tags and Rebuild Policy: what :latest means and when it moves, the two tag schemes, which tags are immutable, and the Renovate update policy including the 3-day soak with claude-code exempt. - Troubleshooting: cross-image symptoms only, each citing its issue. Moved from the repo tree (zero coupling to repo code, so nothing is lost by their no longer being reviewed in a PR): - docs/docker-maintenance-cheatsheet.md -> Docker Disk Maintenance - docs/disk-usage.md -> Incident: Docker Disk Exhaustion (2026-09-07) Every page now ends with a Sources section citing the PRs and issues its knowledge came from, and a Last verified date -- wiki pages rot silently and nothing else signals it. Added _Sidebar.md for navigation.