feat: probe/teach agent split — explicit phase markers, position-only plan map

Diagnosis (2026-09-11 user testing, minimal-effort GLM): sessions stuck on
'plan' forever. Two causes: (1) the three-phase view read the stored tree's
currentNodeId, which nothing ever writes post author-once (2026-09-03) — a
structural dead seam; (2) the teacher stochastically left quiz.nodeId
untagged, and done-by-quiz-result semantics would have falsely completed
nodes anyway.

The redesign (docs/probe-teach-split.md) abolishes derived occupancy in
favor of explicit events:

- Two agents over one transcript: createProberAgent (quiz without a
  nodeId field, ask, probe_done) and createTeacherAgent (full toolset,
  plan_init onward). The chat-handler construction branch keys on a
  probe_done part in the transcript. MODELS.prober added.
- probe_done: server-side seam tool — carries the learner assessment
  (strands + free-form edge read), refuses while a question is open or
  the probe is already concluded, and queues a handoff steer through the
  generalized wake pipeline (steers now dedupe by id, not jobId; job
  finalization only for job steers). The teacher auto-wakes and authors
  the plan; the learner sees the assessment via the probe-done card.
- phases: probe ends at a concluded probe_done, plan ends at a
  successful plan_init — strictly sequential, no skipping, no legacy
  compatibility (data wiped at the pivot per doctrine).
- Plan map = position, not completion: derivePlanStatuses reads only
  tagged quiz CALLS (state/outcome feed nothing); current = latest
  tagged node with consecutive duplicates collapsed, visited = earlier
  distinct stays (a revisit stays in both — current wins at render).
  PlanTree is structure-only; currentNodeId/doneNodeIds and the dead
  mutation helpers are gone. No fallback current.
- Prompts split per agent (prompts/prober/, prompts/teacher/ over the
  trimmed shared base); graph-context injection removed entirely
  (shelved, docs/probe-teach-split.md §5); knowledge-graph context no
  longer reaches either agent.
- Plan blocks are full-only snapshots at plan_init (neighborhood
  machinery retired; the persistent DAG window is the future UI wave);
  usage capture unchanged.

Gates: tsc clean, 294/294 tests (phases/plan-tree/plan-blocks/question-
tools rewritten to the new semantics; probe-done + handoff-wake tests
added), lint, build. Live GLM smoke PASS: prober concluded with an honest
assessment, teacher auto-woke, authored a 10-node plan with the block
attached, then tagged checks on slope-instinct → secant derived current/
visited exactly as designed; grading honest both ways (driver off-by-one
proved a wrong answer grades false).

src/core/contracts/chat.ts

@@ -124,12 +124,15 @@ export interface TurnUsage {
  * small container, the current node glowing — clearly a fragment, not the
  * whole plan. Clicking either opens the full plan in a popup. */
 export interface PlanBlockData {
-	kind: "full" | "neighborhood";
+	/** Only "full" survives (the 2026-09-11 pivot): the plan renders IN
+	 *  FLOW once, at authoring. The neighborhood fragments are retired —
+	 *  position derives live from the transcript (the persistent DAG
+	 *  window is the successor). */
+	kind: "full";
 	at: string;
 	/** The current node at snapshot time (the glow target; null = none). */
 	current: string | null;
-	/** Included nodes: all of them (full) or the one-level-up/one-level-down
-	 * neighborhood of `current` (neighborhood). Statuses are the snapshot's,
+	/** All nodes of the authored tree. Statuses are the snapshot's,
 	 * derived at emission time — the block never re-derives at render. */
 	nodes: Array<{ id: string; title: string; status: PlanNodeStatus }>;
 	edges: Array<{ from: string; to: string }>;
@@ -141,9 +144,9 @@ export interface PlanBlockData {
  *  them in listChats. Liveness (`busy`) is NOT record-derived — the API
  *  route merges it in (see ChatListItem).
  *
- *  Phase semantics (three phases, data-only): probe = no plan yet, plan =
- *  tree exists but no node occupied, teach = a node is occupied
- *  (core/phases.ts phaseOfTree).
+ *  Phase semantics (three phases, event-driven — docs/probe-teach-split.md
+ *  §4): probe ends at the concluded probe_done, plan ends at the successful
+ *  plan_init; derived from the transcript (core/phases.ts phaseAt3).
  */
 export interface ChatSummary {
 	id: string;