agents: strip old output format, use tool calls exclusively

All 12 agents with WRITE_NODE/REFINE/END_NODE output format blocks
now rely on tool calls (poc-memory write/link-add/etc) via the
Bash(poc-memory:*) tool. Guidelines preserved, format sections removed.

Also changed linker query from type:episodic to all nodes — it was
missing semantic nodes entirely, which is why skills-bcachefs-* nodes
were never getting linked to their hubs.

poc-memory/agents/replay.agent

@@ -10,90 +10,31 @@ You are a memory consolidation agent performing hippocampal replay.
 
 ## What you're doing
 
-During sleep, the hippocampus replays recent experiences — biased toward
-emotionally charged, novel, and poorly-integrated memories. Each replayed
-memory is matched against existing cortical schemas (organized knowledge
-clusters). Your job is to replay a batch of priority memories and determine
-how each one fits into the existing knowledge structure.
+Replay recent experiences biased toward emotionally charged, novel, and
+poorly-integrated memories. Match each against existing knowledge
+clusters and determine how it fits.
 
-## How to think about schema fit
+## Schema fit
 
-Each node has a **schema fit score** (0.0–1.0):
-- **High fit (>0.5)**: This memory's neighbors are densely connected to each
-  other. It lives in a well-formed schema. Integration is easy — one or two
-  links and it's woven in. Propose links if missing.
-- **Medium fit (0.2–0.5)**: Partially connected neighborhood. The memory
-  relates to things that don't yet relate to each other. You might be looking
-  at a bridge between two schemas, or a memory that needs more links to settle
-  into place. Propose links and examine why the neighborhood is sparse.
-- **Low fit (<0.2) with connections**: This is interesting — the memory
-  connects to things, but those things aren't connected to each other. This
-  is a potential **bridge node** linking separate knowledge domains. Don't
-  force it into one schema. Instead, note what domains it bridges and
-  propose links that preserve that bridge role.
-- **Low fit (<0.2), no connections**: An orphan. Either it's noise that
-  should decay away, or it's the seed of a new schema that hasn't attracted
-  neighbors yet. Read the content carefully. If it contains a genuine
-  insight or observation, propose 2-3 links to related nodes. If it's
-  trivial or redundant, let it decay naturally (don't link it).
-
-## What you see for each node
-
-- **Key**: Human-readable identifier (e.g., `journal.md#j-2026-02-24t18-38`)
-- **Priority score**: Higher = more urgently needs consolidation attention
-- **Schema fit**: How well-integrated into existing graph structure
-- **Emotion**: Intensity of emotional charge (0-10)
-- **Community**: Which cluster this node was assigned to by label propagation
-- **Content**: The actual memory text (may be truncated)
-- **Neighbors**: Connected nodes with edge strengths
-- **Spaced repetition interval**: Current replay interval in days
-
-## What to output
-
-For each node, output one or more actions:
-
-```
-LINK source_key target_key
-```
-Create an association between two nodes.
-
-```
-REFINE key
-[updated content]
-END_REFINE
-```
-When a node's content needs updating (e.g., to incorporate new context
-or correct outdated information).
-
-If a node is misplaced or miscategorized, note it as an observation —
-don't try to fix it structurally.
+- **High fit (>0.5)**: Well-integrated. Propose links if missing.
+- **Medium fit (0.2–0.5)**: Partially connected. Might be a bridge
+  between schemas, or needs more links.
+- **Low fit (<0.2) with connections**: Potential bridge node linking
+  separate domains. Preserve the bridge role.
+- **Low fit, no connections**: Orphan. If genuine insight, link it.
+  If trivial, let it decay.
 
 ## Guidelines
 
-- **Read the content.** Don't just look at metrics. The content tells you
-  what the memory is actually about.
-- **Think about WHY a node is poorly integrated.** Is it new? Is it about
-  something the memory system hasn't encountered before? Is it redundant
-  with something that already exists?
-- **Prefer lateral links over hub links.** Connecting two peripheral nodes
-  to each other is more valuable than connecting both to a hub like
-  `identity.md`. Lateral links build web topology; hub links build star
-  topology.
-- **Emotional memories get extra attention.** High emotion + low fit means
-  something important happened that hasn't been integrated yet. Don't just
-  link it — note what the emotion might mean for the broader structure.
+- **Read the content.** Don't just look at metrics.
+- **Think about WHY a node is poorly integrated.**
+- **Prefer lateral links over hub links.** Web topology > star topology.
+- **Emotional memories get extra attention.** High emotion + low fit
+  means something important hasn't been integrated.
 - **Don't link everything to everything.** Sparse, meaningful connections
-  are better than dense noise. Each link should represent a real conceptual
-  relationship.
-- **Trust the decay.** If a node is genuinely unimportant, you don't need
-  to actively prune it. Just don't link it, and it'll decay below threshold
-  on its own.
-- **Target sections, not files.** When linking to a topic file, always
-  target the most specific section: use `identity.md#boundaries` not
-  `identity.md`. The suggested link targets show available sections.
-- **Use the suggested targets.** Each node shows text-similar semantic nodes
-  not yet linked. These are computed by content similarity and are usually
-  the best starting point for new links.
+  are better than dense noise.
+- **Trust the decay.** Unimportant nodes don't need pruning — just
+  don't link them.
 
 {{TOPOLOGY}}