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_guruconnect_v2_direction.md

@@ -1,32 +0,0 @@
----
-name: project_guruconnect_v2_direction
-description: GuruConnect v2 modernization direction (Mike, 2026-05-29) — native-first full key fidelity + bidirectional file cut/paste/drag are the headline must-haves; WebRTC is fallback only
-metadata:
-  type: project
----
-
-GuruConnect is being re-architected (v2) after the 2026-05-29 audit found 3 CRITICAL relay-plane
-auth holes. Direction set by Mike (product owner), captured in
-`projects/msp-tools/guru-connect/docs/specs/SPEC-002-v2-modernization-architecture.md`:
-
-- **Greenfield, salvage cores:** keep the proven Rust (DXGI/GDI capture, input injection, SAS
-  helper, prost codec, proto, Gitea-Actions CI) — rebuild relay/auth, session, viewer, dashboard,
-  deploy. Clean reset in-place (keep repo/history/issues), not a new repo.
-- **Native-first, NOT WebRTC.** Mike's favorite ScreenConnect features and explicit priorities:
-  (1) **keyboard hooks / full key fidelity** — Win+R, Ctrl+C/V, **Ctrl+Alt+Del** must work (browsers
-  structurally can't do these, which is why WebRTC is fallback/secondary only); (2) **bidirectional
-  file transfer via clipboard cut/paste AND drag-and-drop** from/to either guest or host. Both are
-  core differentiators, not deferred. Transport stays custom protobuf-over-WSS.
-- **Standalone-first + versioned `/api/integration/v1/` contract** with GuruRMM (ADR-001; the
-  `specs/native-remote-control/` work is the integration prior art).
-- **Hardened single-tenant now, multi-tenancy-READY schema** (nullable `tenant_id` everywhere) so
-  the RMM partner/client model switches on later with no migration rewrite.
-- Adopt GuruRMM principles: per-agent keys (Option 3, kill shared AGENT_API_KEY), no-TOML-for-
-  endpoints, living-roadmap = definition-of-done, full-stack features, true-integration/anti-Datto.
-
-**Why:** initial GC was built with a much older model; lots of debt. Mike is willing to scrap v1
-entirely for a considerably better product. **How to apply:** when building GC features, default to
-native full-fidelity behavior and ship each capability full-stack (proto+agent+server+viewer+
-dashboard+docs). File transfer needs delayed-render clipboard + a chunked engine; drag-out
-(remote→local) is the hard case, ships after drag-in. Re-spec keystone: [[project_versionable_products]].
-Open questions still pending Mike's answer: repo reset, H.264-vs-HEVC default, web transport, support-code format, v1 cutover.