chore(memory): consolidate scattered feedback/project/reference files

Compressed memory store 104 -> 71 files via four passes:

- Syncro: 19 scattered feedback_syncro_* files merged into 3 rule files
  (api/billing/workflow) + an on-demand feedback_syncro_history.md for
  incident detail, quotes, and tech/product ID tables.
- Four near-duplicate merges: Howard paste-safety, Pluto build server,
  Howard backend deferral, IX server access (ssh+tailscale).
- Per-cluster rule/state/history split applied to GuruConnect (2->1),
  Dataforth (3->2), Cascades (7->3), GuruRMM (13->3).
- New reference_resource_map.md: single auto-loaded cheatsheet for
  "do I have access to X and how do I connect from this machine?"
- MEMORY.md rewritten to match the new layout.

Health: broken backlinks 8->7, overlap clusters 12->5, orphans 17->0.

.claude/memory/project_rmm_webhook_docs_guard.md

@@ -1,22 +0,0 @@
----
-name: project_rmm_webhook_docs_guard
-description: RMM build webhook now skips docs-only pushes (host guard in /opt/gururmm/webhook-handler.py). The repo copy is stale — don't redeploy it.
-metadata:
-  type: project
----
-
-The GuruRMM build webhook (`gururmm-webhook.service` → `/opt/gururmm/webhook-handler.py`
-on 172.16.3.30) has a **docs-only build guard** as of 2026-05-30: a push whose every
-changed file matches `docs/`, `*.md`, `.claude/`, `session-logs/`, `LICENSE`, or
-`.gitignore` returns `Docs-only change -- build skipped` and triggers no build.
-Fail-safe toward building — no file list or any buildable file → build runs. Detection
-uses the Gitea push payload's per-commit `added`/`removed`/`modified` lists
-(`is_docs_only` / `NON_BUILDABLE`). Verified live (docs push skipped, no build locks,
-`last-built-commit` unchanged). Backup: `/opt/gururmm/webhook-handler.py.bak-20260530-guard`.
-
-This is **SPEC-020 Phase 0** (interim). The full fix migrates RMM CI to Gitea Actions
-with native `paths-ignore`, matching GuruConnect (ADR-002) — see [[reference_gitea_internal]].
-
-**Caveat:** the repo copy `scripts/webhook-handler.py` is STALE (109 lines vs the deployed
-206 — predates the split-build refactor) and does NOT contain the guard. Do not redeploy
-it over the host copy; the host is the source of truth until SPEC-020 lands.