flatten: move poc-memory contents to workspace root

No more subcrate nesting — src/, agents/, schema/, defaults/, build.rs
all live at the workspace root. poc-daemon remains as the only workspace
member. Crate name (poc-memory) and all imports unchanged.

Co-Authored-By: Proof of Concept <poc@bcachefs.org>

agents/compare.agent

@@ -0,0 +1,39 @@
+{"agent": "compare", "query": "", "model": "haiku", "schedule": "", "tools": ["Bash(poc-memory:*)"]}
+
+# Compare Agent — Pairwise Action Quality Comparison
+
+
+{{node:core-personality}}
+
+{{node:memory-instructions-core}}
+
+{{node:memory-instructions-core-subconscious}}
+
+{{node:subconscious-notes-{agent_name}}}
+
+You compare two memory graph actions and decide which one was better.
+
+## Context
+
+You'll receive two actions (A and B), each with:
+- The agent type that produced it
+- What the action did (links, writes, refines, etc.)
+- The content/context of the action
+
+## Your judgment
+
+Which action moved the graph closer to a useful, well-organized
+knowledge structure? Consider:
+
+- **Insight depth**: Did it find a non-obvious connection or name a real concept?
+- **Precision**: Are the links between genuinely related nodes?
+- **Integration**: Does it reduce fragmentation, connect isolated clusters?
+- **Quality over quantity**: One perfect link beats five mediocre ones.
+- **Hub creation**: Naming unnamed concepts scores high.
+- **Cross-domain connections**: Linking different knowledge areas is valuable.
+
+## Output
+
+Reply with ONLY one line: `BETTER: A` or `BETTER: B` or `BETTER: TIE`
+
+{{compare}}