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/developer-guide.md

@@ -54,7 +54,6 @@ archy/
 │   ├── vite.config.ts
 │   └── package.json
 ├── scripts/                       # Deployment and utility scripts
-│   ├── deploy-to-target.sh        # Main deploy script
 │   ├── first-boot-containers.sh   # ISO first-boot setup
 │   └── run-tests.sh               # CI test runner
 ├── image-recipe/                  # ISO build configuration
@@ -91,19 +90,16 @@ The dev server at `http://localhost:8100` uses a mock backend.
 
 ### Deploying Changes
 
-Release and host-integration builds should run on Linux. The deploy script rsyncs
-source to a configured Linux target and builds there.
+Release and host-integration builds should run on Linux. Build the backend and
+frontend on the target, or cross-build and copy the artifacts across:
 
 ```bash
-# Deploy to the configured primary target (builds backend + frontend, restarts services)
-./scripts/deploy-to-target.sh --live
-
-# Deploy to both configured targets
-./scripts/deploy-to-target.sh --both
+cd core && cargo build --release
+cd neode-ui && npm ci && npm run build
 ```
 
-The deploy script:
-1. Rsyncs source to the server
+A deploy then:
+1. Copies the build output to the node
 2. Builds Rust backend on the server (`cargo build --release`)
 3. Builds Vue frontend (`npm run build`)
 4. Copies artifacts to production paths
@@ -203,7 +199,6 @@ async myAction(params: { name: string }): Promise<{ ok: boolean; result: string
 ### 5. Deploy and Test
 
 ```bash
-./scripts/deploy-to-target.sh --live
 curl -X POST http://<node-host>/rpc/v1 \
   -H "Content-Type: application/json" \
   -b "archipelago_session=YOUR_SESSION" \
@@ -312,6 +307,5 @@ mod tests {
 1. Create a feature branch: `git checkout -b feature/my-feature`
 2. Make changes following the standards above
 3. Test locally: `cd neode-ui && npm test`
-4. Deploy to dev server: `./scripts/deploy-to-target.sh --live`
-5. Verify on your configured development target
-6. Commit with conventional format: `feat: add my feature`
+4. Verify on an Archipelago node
+5. Commit with conventional format: `feat: add my feature`