clean rig

rig/BOOTSTRAP.md

@@ -97,7 +97,7 @@ build has a Makefile target today. **On a genuinely bare machine, run it by
 hand:**
 
 ```bash
-make deps-image                          # builds rig-deps:deps
+make deps image                          # builds rig-deps:deps
 mkdir -p ~/.local/bin
 docker run --rm \
   -v /:/host:ro \
@@ -141,7 +141,7 @@ If something else on this machine already provides `kubectl`, the installer says
 by name rather than shadowing it quietly. `OUT_BIN=$PWD/def/bin` installs
 somewhere private instead.
 
-**Two variants worth knowing before you need them.** `make deps-image full` bakes
+**Two variants worth knowing before you need them.** `make deps image full` bakes
 every pinned binary into the image at build time (`DEPS_SOURCE=baked`), so
 `docker save` gives you the entire installer as one file to carry into an
 air-gapped network. And `DEPS_SOURCE=artifactory` with `DEPS_ARTIFACTORY_URL`
@@ -156,16 +156,14 @@ the first-time path.
 ## Prove the machine before blaming the project
 
 ```bash
-make setup
+make check
 make cluster up
 kubectl get nodes
 ```
 
-`make setup` re-runs every check as a group. It is idempotent and it deliberately
-does not abort on the first failure — a setup script that dies at step two hides
-the fact that steps four and five were also going to fail. Run now, it should be
-`ok` and `done` all the way down, and that is the point: it is the scoreboard,
-not the installer.
+`make check` re-runs every check — host, docker, toolchain, memory, ports — and
+changes nothing. Run now, it should end with nothing left to do by hand, and that
+is the point: it is the scoreboard, not the installer.
 
 `make cluster up` builds rig's built-in defaults — one node, no addons,
 boots fast. You do not need it to develop anything, but you do want to know that