security: remove all infrastructure and internal process material from the repo

The repo is source code and guidelines only. Nothing about how Archipelago's
own fleet is run, or how the team works, stays in it.

Untracked (kept on disk, gitignored) — 250 files:
- .planning/ (199) and loop/ — internal development process
- fleet operations tooling that targets specific nodes: deploy-to-target,
  deploy-tailscale, deploy-config-defaults, setup-target-dev, setup-aiui-server,
  setup-https-dev, debug-frontend, node-profile, fleet-fips-pair/unpair,
  image-recipe/sync-from-live.sh
- image-recipe/INTEGRATION-GUIDE.md and docs/multinode-testing-plan.md, both of
  which are live-server workflow and fleet node inventories
- the Phase 10 on-node verification and evidence records, which cite .planning/
  as their evidence base

KEY-05-ENTROPY-ENFORCEMENT.md was initially moved out with the other Phase 10
docs and then put back: it is cited as normative rationale from ten places in
the codebase, including core/clippy.toml, which bans rand::thread_rng and
points at it for the reason. That makes it a guideline, not an internal record.

Node names removed from source (48 occurrences across comments, manifests and
test fixtures): archi-dev-box, archy-x250*, shorty-s, framework-pt,
zaza-optiplex, archi-thinkpad. Comments keep the engineering context and the
date, which is what carried the meaning; the machine name did not.

Three of those were live test values rather than comments and were replaced
with valid stand-ins, not prose: two mDNS hostnames and a mesh peer name.
An earlier pass substituted "a test node" into a hostname assertion, producing
an invalid hostname; caught and fixed as test-node.local.

Wipe mechanism: .local-only/manifest.txt inventories every local-only path and
.local-only/wipe.sh deletes them on one confirmation, refusing to touch
anything git still tracks. Both are themselves untracked, so the public repo
does not carry a map of internal filenames.

Verified: cargo check -p archipelago --all-features clean; archipelago-container
75/75 tests pass; appOrigin vitest 7/7; audit-secrets 5/5; every relative link
in tracked markdown resolves (0 broken).

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

scripts/self-update.sh

@@ -217,7 +217,7 @@ ok "Backend installed"
 # Non-fatal: archipelago falls back to its dev venv path if the packaged
 # binaries aren't present, so a missing/failed build here degrades mesh
 # Reticulum support rather than breaking the update. This mirrors
-# deploy-to-target.sh's existing manual-deploy step, which until now was the
+# the existing manual-deploy step, which until now was the
 # only path that ever installed these — a node that only ever received OTA
 # self-updates had neither binary.
 if [ -f "$REPO_DIR/reticulum-daemon/build.sh" ]; then
@@ -329,7 +329,7 @@ UI_REBUILD_LIST=""
 # /opt/archipelago/docker/<ui>, and nothing was ever updating that directory.
 # So source edits to those two trees reached nodes through no path at all:
 # their nginx kept listening on 0.0.0.0 and served the Guardian and FIPS
-# screens unauthenticated on every interface (found by scanning archi-dev-box
+# screens unauthenticated on every interface (found by scanning a test node
 # from outside, 2026-08-05 — the in-node audit could not see them).
 for ui in bitcoin-ui lnd-ui electrs-ui fips-ui fedimint-ui; do
     src="$REPO_DIR/docker/$ui"