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>

docs/security/BITCOIN-RPC-PROXY-EXPOSURE.md

@@ -1,7 +1,7 @@
 # The Bitcoin RPC proxy that stayed open after it was fixed
 
 **Status:** code fix committed (`f6b5245b`); on-node verification recorded below.
-**Found:** 2026-08-02, archi-dev-box, while verifying `a05956c4` instead of assuming it.
+**Found:** 2026-08-02, a test node, while verifying `a05956c4` instead of assuming it.
 **Severity:** critical on any affected node — unauthenticated control of Bitcoin Core RPC
 through a proxy that injects the node's own credentials.
 
@@ -79,7 +79,7 @@ Deliberately narrow:
   survived. A new regression test pins the whole chain: stale conf in, gate present out,
   container restarted, nothing created.
 
-## What actually closed it on archi-dev-box — and what that does NOT prove
+## What actually closed it on a test node — and what that does NOT prove
 
 Sequence, from file mtimes, container start times and the daemon journal:
 
@@ -104,7 +104,7 @@ Tracked as broken window 15 — **since closed by the controlled test below.**
 
 ## Proving the delivery path on real hardware
 
-Run on archi-dev-box, 2026-08-02 20:00–20:03 EDT, with operator approval. The point was to
+Run on a test node, 2026-08-02 20:00–20:03 EDT, with operator approval. The point was to
 prove the thing the incidental rebuild had made unprovable: that **reconcile itself**
 repairs this state, unaided.