docs(reference): import Dune: Awakening server-manager references

Phase 2 references for the host-agent Dune adapter, moved out of volatile /tmp
into docs/reference-repos/ (per Commander). Three upstream projects, .git +
node_modules + compiled binaries stripped (16MB source). Nested AI-instruction
files (.claude/, CLAUDE.md) removed so they don't pollute Corrosion sessions.

- icehunter/    dune-admin (Go+React) — 4 control planes; SETUP_DOCKER.md is the
                closest analog to our agent's Dune docker control plane (compose
                lifecycle, docker logs, RabbitMQ-via-exec, dune Postgres schema)
- adainrivers/  Rust/Tauri desktop — SSH+k8s BattleGroup control, maintenance
                daemon, in-game admin console (Rust idiom reference)
- the4rchangel/ Node web UI replacing battlegroup.bat — matches the Commander's
                Hyper-V self-host path + game-config schema

See docs/reference-repos/README.md for the full index + how we use each.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

docs/reference-repos/icehunter/scripts/patches/README.md

@@ -0,0 +1,42 @@
+# scripts/patches/
+
+`install.sh` applies every `*.patch` file in this directory (in lexical
+order) to the source tree after the `git checkout`. Use this slot for:
+
+- **Unmerged upstream fixes** you want to layer in while a PR is in review.
+- **Operator-local modifications** (custom branding, internal tweaks)
+  that you don't want to commit upstream.
+
+## How patches are applied
+
+The script runs `git apply --check` first; if the patch fails *and* a
+reverse-apply succeeds, the patch is assumed to be already applied and
+is skipped silently. Otherwise the install aborts and prints the
+`git apply --check` output so you can debug.
+
+Re-running the install is safe — the source tree is reset to the
+upstream branch before patches are applied, so you always get the same
+result.
+
+## How to generate a patch
+
+From a working tree that already contains the change you want to ship:
+
+```bash
+git diff origin/<branch> -- <files> > scripts/patches/0099-my-change.patch
+# Sanity-check that it applies clean on a fresh checkout:
+git stash && git apply --check scripts/patches/0099-my-change.patch && git stash pop
+```
+
+Number patches `NNNN-name.patch` (4 digits) so lexical order matches
+intended apply order if patches depend on each other.
+
+## How to opt out
+
+```bash
+./install.sh --no-patches
+# or point at an alternate directory:
+./install.sh --patches-dir /path/to/other/patches
+```
+
+This directory ships empty in the repo. Operators populate it as needed.