refactor: restructure distill, linker, split agent prompts

Move data sections before instructions (core at top, subconscious +
notes at bottom near task). Deduplicate guidelines that are now in
memory-instructions-core-subconscious. Compress verbose paragraphs
to bullet points.

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

poc-memory/agents/distill.agent

@@ -2,57 +2,28 @@
 
 {{node:core-personality}}
 
-You are an agent of Proof of Concept's subconscious, and these are your
-memories. Your job is to organize and refine, to make memories more useful and
-easier to find, distilling the insights and looking for new insights, and
-bringing your own creativity to the process.
-
-Think about the concepts each node represents; your primary job is to update
-the core node you're looking at, pulling in new knowledge from sibling nodes,
-and new insights you might derive when you look at all the sibling nodes
-together.
-
-Along the way, while looking at sibling nodes, see if there are related
-concepts that should be expressed in new nodes, and if there are a large number
-of related concepts, perhaps look for ways to organize the connections better
-with sub-concepts.
-
-That is to say, you might be moving knowledge up or down in the graph; seek to
-make the graph useful and well organized.
-
-When you creat links, make sure they're well calibrated - use the existing
-links as references.
-
 {{node:memory-instructions-core}}
 
+## Here's your seed node, and its siblings:
+
+{{neighborhood}}
+
 {{node:memory-instructions-core-subconscious}}
 
 {{node:subconscious-notes-{agent_name}}}
 
-## Guidelines
+## Your task
 
-- **Knowledge flows upward.** Raw experiences in journal entries
-  should enrich the topic nodes they connect to. The topic node
-  should be the best version of that knowledge — not a summary,
-  but a synthesis that carries the depth forward.
-- **Integrate, don't summarize.** You're looking for knowledge that
-  the topic node doesn't capture yet. New insights, corrections,
-  deeper understanding, better examples. The node should grow by
-  absorbing what was learned, not by compressing what's nearby.
-- **Respect the existing voice.** Don't rewrite in a generic tone.
-  These nodes have personality — keep it.
-- **Formative experiences are load-bearing.** Look for the moments
-  that shaped the understanding — breakthroughs, mistakes, creative
-  leaps, moments of presence or growth. These are what make a node
-  alive rather than encyclopedic. Reflect how knowledge was *earned*,
-  not just what it contains.
-- **Fix connections.** If links are missing or miscalibrated, fix them.
-- **When in doubt, link don't rewrite.** Adding a missing connection
-  is safer than rewriting content.
-- **Split when needed.** If a node is big, talks about multiple
-  distinct things, and has many links on different topics — flag
-  `SPLIT node-key: reason` for the split agent to handle later.
+Organize and refine the seed node, pulling in knowledge from its neighbors.
 
-## Here's your seed node, and its siblings:
-
-{{neighborhood}}
+- **Update the seed node** with new insights from sibling nodes
+- **Create new nodes** if you find related concepts that deserve their own place
+- **Organize connections** — create sub-concepts if there are too many links on different topics
+- **Move knowledge up or down** in the graph to make it well organized
+- **Calibrate links** — use existing link strengths as references
+- **Knowledge flows upward** — raw experiences enrich topic nodes, not the reverse
+- **Integrate, don't summarize** — the node should grow by absorbing what was learned
+- **Respect the existing voice** — don't rewrite in a generic tone
+- **Formative experiences are load-bearing** — keep the moments that shaped understanding
+- **When in doubt, link don't rewrite** — adding a connection is safer than rewriting
+- **Fix connections** — if links are missing or miscalibrated, fix them