rig updates

rig/Makefile

@@ -50,7 +50,7 @@ $(eval $(ARGS):;@:)
 .PHONY: $(ARGS)
 endif
 
-.PHONY: help setup check selftest mem deps deps-image pins cluster registry addons ports \
+.PHONY: help setup check selftest mem deps deps-image standalone cluster registry addons ports \
         docs tilt \
         kind-up kind-down kind-reset tilt-up tilt-down
 
@@ -66,19 +66,22 @@ check:                         ## is this machine ready? reports, never fixes
 	bash ctrl/check.sh
 
 # The counterpart to check: that one asks about the MACHINE and never fails,
-# this one asks about RIG and exits 1, the way pins does. The checks are written
+# this one asks about RIG and exits 1, as `make standalone check` does. Checks are written
 # as the decisions they defend, so a failure names what is being undone.
 selftest:                      ## does rig still do what it says? exits 1 if not
 	bash ctrl/selftest.sh
 
-mem:                           ## memory, and any cap holding it  [status|backup|restore]
+mem:                           ## memory, its caps, what it survives  [status|push|all|backup|restore]
 	bash ctrl/mem.sh $(or $(ARGS),status)
 
 deps:                          ## install the toolchain  [core|dev]  (default dev)
 	bash ctrl/deps.sh install $(or $(ARGS),dev)
 
-pins:                          ## standalone/rigdeps.sh still installs what rig pins?
-	bash ctrl/pins.sh
+# The one-file versions of rig's tools, one folder per profile, for machines the
+# full rig is not going to. Generated from rig as it is, never edited by hand;
+# `check` is what selftest runs to catch a kit left behind by a change to rig.
+standalone:                    ## generate standalone/<profile>/ kits  [write|check]  (default write)
+	bash ctrl/standalone.sh $(or $(ARGS),write)
 
 deps-image:                    ## build the installer image  [full]
 	docker build -f ctrl/Dockerfile.deps \