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/feedback_syncro_html.md

@@ -1,17 +0,0 @@
----
-name: Syncro comment HTML formatting
-description: Use <br> for line breaks in Syncro comments, not <ul>/<li> — list tags don't render
-type: feedback
-originSessionId: b39e319c-ac3e-49f5-afb6-755e08f1fd82
----
-Use `<br>` for line breaks in Syncro comment bodies. Do NOT use `<ul>`, `<li>`, or other block-level list tags — Syncro's renderer collapses them into a single line with no spacing.
-
-**Why:** Posted a comment with `<ul><li>` items and they all ran together on one line in the ticket view. Had to post a corrected duplicate.
-
-**How to apply:** For any bulleted list in a Syncro comment, use:
-```
-- Item one<br>
-- Item two<br>
-- Item three
-```
-wrapped in a `<p>` tag. Never use `<ul>/<li>`.