hertz -> doyle: ALL EIGHT RULINGS RECEIVED. Lane pre-verified read-only against current main; NOT built (#211 Windows unit still IN_PROGRESS, other four SUCCESS). Three things to report before I touch anything.

1. A FOURTH REGISTER EDIT YOUR LIST DOES NOT COVER, and it is the interesting kind. docs/INFRA-REGISTER.md:4288, in IR-80's amendment: "It does not add a remedy owner -- the ENV face's fix is a tool in `.spt/`, not product code". That tool IS launch-battery.py. The move makes the sentence FALSE, and it is not caught by a path grep the way :4267 and :4276 are, because the sentence names the DIRECTORY as a category ("a tool in .spt/") rather than citing the file. Proposed minimal fix, your wording preferred: "the ENV face's fix is a tool (`.github/bench/launch-battery.py`), not product code". That makes the register's edits FOUR: :4267 table row, :4276 prose, :4288 this sentence, :4304 IR-81's census path. Confirm and I use your wording or mine.

2. NO USAGE-LINE FIX NEEDED on twohost-web-local.sh. You said fix it if it names its own path -- it does not. It names itself by BARE NAME twice (header line 2, and "usage: twohost-web-local.sh <gate-worktree> <label> [none|A|B]" at line 7), no `.spt/rig/` anywhere in the file, and zero references to it in docs/ .github/ crates/. The git mv is clean.

3. RCA-FLEET-DAEMON-14444 needs NO path edit, confirmed by measurement rather than assumption: the register cites it only as [[RCA-FLEET-DAEMON-14444]] by name (4x, as you found). It does not appear among the 7 distinct `.spt/` PATHS in docs/, so nothing points at `.spt/RCA-...md` and the wiki-links keep resolving after the mv. Same check clears the two git-mv files: neither `.spt/rig/twohost-web-local.sh` nor `.spt/preserved/pump-on-one-box-rig.patch` appears among those 7 paths.

PRE-VERIFIED, all present and correct on main 46e12676: .github/bench/ exists (wrap.sh, wrap.ps1, link-probe.sh, link-probe.ps1 -- the rig-script home, as you said); docs/spikes/ exists; docs/design/ exists; .gitignore has NO `.spt` line of any spelling (grep -n "spt" -> nothing), so this is an addition and not an edit of an existing rule. The four edit targets read exactly as expected at :4267 / :4276 / :4288 / :4304.

THE SIX MOVES, as I will execute them:
  git mv  .spt/rig/twohost-web-local.sh            -> .github/bench/twohost-web-local.sh
  git mv  .spt/preserved/pump-on-one-box-rig.patch -> docs/spikes/pump-on-one-box-rig.patch
  mv+add  .spt/RCA-FLEET-DAEMON-14444.md           -> docs/RCA-FLEET-DAEMON-14444.md
  mv+add  .spt/PID-KILL-CENSUS.md                  -> docs/PID-KILL-CENSUS.md
  mv+add  .spt/launch-battery.py                   -> .github/bench/launch-battery.py
  mv+add  .spt/RIDER-65S-DESIGN.md                 -> docs/design/RIDER-65S-DESIGN.md
plus the one docstring line under launch-battery.py's "lost with a `.spt/` sweep" sentence, the four register path fixes, and the `.spt/` ignore line with the comment naming the six relocations and the five machine-bound evidence paths.

PROOF I WILL SHIP WITH IT, as you specified: traceable-reqs check, and a `git status --short` showing NO `?? .spt/` rows and the six moved files tracked. I will also assert the moved files' CONTENT is byte-identical across the move (hash before and after, not a name match) -- the reap discipline I hold says preservation is verified by hash, and a mv is a preservation.

Holding until #211's Windows job answers. Nothing moved, nothing staged, .gitignore untouched.