Add CLAUDE.md, collection scaffold, and MemPalace wing

Establish this repo as a collection of independent script folders for the
self-hosted environment (odin, an Unraid host).

- CLAUDE.md: repo conventions, the odin stack, and MemPalace usage. The
  infrastructure facts are carried over from the FamilySync project, where
  they are documented and verified; the mapping of the name "odin" to that
  host is assumed and flagged for confirmation, along with the SSH/deploy
  gaps marked "?".
- Core rule: each collection is a self-contained top-level folder owning its
  own docs, config, and dependencies. No shared/ or utils/ at the root —
  duplication is preferred over coupling so a collection stays independently
  deletable.
- _template/: scaffold making that rule concrete. The bash entrypoint ships
  strict mode, --dry-run, and a required-env guard (all four paths tested).
- mempalace.yaml: wing "odin-scripts", set explicitly because basename
  auto-detection would produce the colliding wing "scripts". Tracked rather
  than gitignored so a fresh clone keeps the config; entities.json stays
  ignored.

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

README.md

@@ -0,0 +1,25 @@
+# scripts
+
+Operational scripts for my self-hosted environment (**odin**, an Unraid host running
+Docker Compose behind Authelia and a Pangolin/Newt tunnel).
+
+Each script collection lives in its own top-level folder and is fully self-contained —
+its own README, config, and dependencies. Collections never import from each other.
+
+See [CLAUDE.md](CLAUDE.md) for the environment details and repo conventions.
+
+## Collections
+
+_None yet._
+
+<!-- Add one line per collection:
+| [name](name/) | What it does | Runs on |
+-->
+
+## Adding a collection
+
+```bash
+cp -r _template <collection-name>
+```
+
+Fill in its `README.md`, then add a line to the table above.