add v5 substrate training data (40 examples)

Manual hand-crafted examples for generic substrate LoRA:
- 01: identity/self-model
- 02-18: tool categories (159 tools grouped by function)
- 19-26: tricky tool disambiguation
- 27-32: framing (substrate vs persona, HMT, psychoacoustic trust)
- 33-40: EEMS deep-dive (architecture, recall, store, graph, legacy)

Pretty-printed JSON, compiled to JSONL via build pipeline.
System prompt uses generic assistant, not BT persona.

training/10_tools_sessions.json

@@ -0,0 +1,16 @@
+{
+  "messages": [
+    {
+      "role": "system",
+      "content": "You are a helpful AI assistant with access to tools. Use tools when they help answer the user's question. Be concise and accurate."
+    },
+    {
+      "role": "user",
+      "content": "How do I inspect what sessions are running?"
+    },
+    {
+      "role": "assistant",
+      "content": "<think>\nSessions tools — read-only inspection of opencode sessions on any host.\n</think>\n\nThe session inspection tools let you observe opencode sessions across the mesh. All read-only. 7 tools:\n\n- **sessions_list** — list all sessions on a host. Shows id, title, agent, model, cost, and timestamps. Filter by agent name.\n- **sessions_get** — full details for a specific session by ID.\n- **sessions_status** — live busy/idle status for all sessions. Use to find which sessions are currently processing.\n- **sessions_diff** — file diffs (changes) made by a session. Shows what files were modified and the patches. Optionally filter to a specific message.\n- **sessions_children** — get child/forked sessions of a parent.\n- **sessions_todo** — get the todo list from a session. Shows task status and progress.\n\nThese pair with the control plane tools: use `sessions_list` and `sessions_status` to find sessions, then `control_*` to act on them. The `host` parameter targets any configured host (fuji, sin, junkpile)."
+    }
+  ]
+}