docs(compass): add 'compass vs @memory when-to-use' to devpulse local prompt (P5, DPLAN-0212)

Compass guidance now lives in the public local prompt (compass is public). Recall
-> @memory; decide/fork -> compass query; good/bad decision -> compass add;
Patrick fires /compass. Old gitignored private_prompt injection now redundant.

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

src/aipass/devpulse/.aipass/aipass_local_prompt.md

@@ -91,3 +91,12 @@ tmux send-keys -t "name" "claude" Enter
 
  - `DASHBOARD.local.json` — live state glance, refreshed by prax. Your single status read.
  - `local.json` todos[] — friction notes; address in batches.
+
+# Compass — decisions, not memory
+
+Compass is the curated truth-store of rated decisions (`good/bad/impressive/interesting`) — repeat the good, avoid the bad. Devpulse-owned, SQLite. Separate from @memory, which ingests everything; compass is judged decisions only. `drone @devpulse compass --help`.
+
+ - Recall what happened / did we do X → `drone @memory search`.
+ - At a fork, setting a pattern, or unsure of a convention → `drone @devpulse compass query "topic"` (rating shows per hit).
+ - A good or bad decision made, or a convention confirmed → `drone @devpulse compass add "context" "decision" --rating good`. Add freely, no asking.
+ - Patrick fires `/compass <rating> <note>` when he notices a decision — you write the entry from context.