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>

core/container/src/manifest.rs

@@ -557,7 +557,7 @@ pub enum PortAuth {
     /// gated any `session` port regardless of `bind`, which meant a node
     /// whose manifests had not yet been updated saw the daemon publish
     /// Bitcoin's loopback-only RPC on every host address (caught on
-    /// archi-dev-box 2026-08-03, seconds after deploy). Requiring the
+    /// a test node 2026-08-03, seconds after deploy). Requiring the
     /// manifest to say so means the loopback pin and the daemon takeover
     /// ship together, atomically, and a stale manifest fails safe.
     Gated,
@@ -1380,7 +1380,7 @@ impl HostFacts {
     pub fn sample() -> Self {
         Self {
             host_ip: "192.168.1.116".to_string(),
-            host_mdns: "archi-thinkpad.local".to_string(),
+            host_mdns: "test-node.local".to_string(),
             disk_gb: 2000,
             bitcoin_host: "bitcoin-knots".to_string(),
         }
@@ -2306,13 +2306,13 @@ app:
         };
         let facts = HostFacts {
             host_ip: "192.168.1.116".to_string(),
-            host_mdns: "archi-thinkpad.local".to_string(),
+            host_mdns: "test-node.local".to_string(),
             disk_gb: 2000,
             bitcoin_host: "bitcoin-core".to_string(),
         };
 
         let out = c.resolve_derived_env(&facts);
-        assert_eq!(out[0], "FM_API_URL=ws://archi-thinkpad.local:8174");
+        assert_eq!(out[0], "FM_API_URL=ws://test-node.local:8174");
         assert_eq!(out[1], "INFO=192.168.1.116-2000");
         assert_eq!(out[2], "CORE_RPC_HOST=bitcoin-core");
     }

core/container/src/podman_client.rs

@@ -329,7 +329,7 @@ impl PodmanClient {
             // disagree. The earlier attempt put this decision in manifest
             // data instead, and a node whose manifests lagged the binary
             // published Bitcoin's loopback-only RPC across the LAN
-            // (archi-dev-box, 2026-08-03).
+            // (test node, 2026-08-03).
             //
             // A port that already declares a bind is never overridden — that
             // is exactly what keeps `bind: 127.0.0.1` ports host-local and
@@ -343,7 +343,7 @@ impl PodmanClient {
             //   * `bind` is already honoured by every publish path (here and
             //     in package::install), so a manifest edit needs no code.
             //   * inference here would cover only THIS path — proven on
-            //     archi-dev-box, where a recreate went through another one and
+            //     a test node, where a recreate went through another one and
             //     the pin never applied.
             //   * and inferring from an ABSENT field is what republished
             //     Bitcoin's loopback RPC across the LAN, and came within one