Merge titanium's diverged memory tree into the shared historyHEADmain

Titanium and tungsten had grown two separate, unreconciled memory sets
for the same -workspace scope. Ports over 18 titanium-only entries
(12 claudomator files, the fork-scope-creep lesson, the doot Google
Tasks OAuth limitation, the default-subagent-driven-execution
preference, scout's Facebook priority, Hawaii GIS endpoints), merges
two true duplicates into their existing tungsten files rather than
keeping parallel copies (the migration-rename incident -- same
022->023 rename, same commit, titanium's version added the
confirmed-safe-to-patch-prod-directly carve-out tungsten's didn't
have; the APK build OOM note, folded into project_doot_widget_build.md
as a RAM-constrained-host fallback), and marks
doot_future_task_scheduling_ideas.md as historical now that all four
of its backlog items (budgets, labels/projects, buckets, chains) are
built.

1 files changed, 14 insertions, 0 deletions

diff --git a/feedback_facebook_priority.md b/feedback_facebook_priority.md
new file mode 100644
index 0000000..a94fce3
--- /dev/null
+++ b/feedback_facebook_priority.md
@@ -0,0 +1,14 @@
+---
+name: feedback-facebook-priority
+description: Facebook is the priority source in scout — do not de-emphasize it
+metadata: 
+  node_type: memory
+  type: feedback
+  originSessionId: 623a172e-faa7-4586-b07d-6e7f3853e93a
+---
+
+Facebook is the priority source in scout and should never be de-emphasized or treated as secondary.
+
+**Why:** User explicitly stated this when I suggested dropping/downplaying Facebook in favor of Craigslist.
+
+**How to apply:** When working on scout, always treat Facebook as the primary source. Don't suggest removing it, downgrading it, or treating Craigslist-only results as sufficient. Fix Facebook issues rather than working around them.