docs: BUILD-LOG Phase 15, CURRENT.md - M13 shipped

BUILD-LOG.md

@@ -337,4 +337,28 @@ Conductor loop proven end-to-end on the stack itself. `main` merged with M8; rel
 
 Session forking verified. `main` merged with M11, tagged `session-fork-v1`; release 0.0.7 active.
 
+---
+
+## Phase 15: Interactive TUI agent + TOOLS.md (M13)
+
+### Entry 15.1 — before
+
+- Timestamp: 2026-09-03
+- Intended action: Add scripts/agent.sh — an interactive TUI launcher (contracts + optional mission + agent identity + named session + optional workspace/tools) — and the pi-adapter interactive branch; remove the fixed compose command; add docs/TOOLS.md as the on-demand reference AGENTS.md routes to; RELEASE -> 0.0.8 (Gitea #35).
+- Reason: The owner's bootstrap model is vanilla pi sessions directed by AGENTS.md, graduating to governed TUI agents — the first the system itself launches.
+- Expected result: TUI agent launches with contracts+identity context; headless paths unchanged; TOOLS.md consolidates the reference.
+
+### Entry 15.2 — after
+
+- Observed: mock plumbing asserts agent name/session/workspace/mission delivery; identity section asserted in generated prompt; headless hello + suites green (24/58/17/14 + verify); 0.0.8 packaged and health-gated activated.
+- Failure or correction:
+  1. Regression: pi adapter rewrite made MOSAIC_AGENT_NAME unconditionally required, breaking headless paths — caught by task suite (empty-stderr exit-nonzero), fixed (optional in headless; identity section simply omitted).
+  2. Regression: unquoted $REQUEST_ARG word-split the request into positional args — fixed with positional-argument building (set -- ... "$@").
+  3. Mission fixture wording (objective named the agent) invited the model to append its name after the marker, tripping the strict gate — fixture tightened; strict gate kept by design.
+- Conductor session env hygiene: sandbox config exports now scoped per-command after a leak broke cross-suite runs.
+
+## Result (M13)
+
+Interactive TUI agent launched and verified; TOOLS.md reference shipped. `main` merged with M13, tagged `interactive-agent-v1`; release 0.0.8 active.
+
 

docs/plans/CURRENT.md

@@ -7,12 +7,12 @@ update this file to the next action). No ambiguity, no re-planning.
 
 ## Next action
 
-Owner review of M12 (conductor auto-apply policy) — then name the next target.
+Owner review of M13 (interactive TUI agent + TOOLS.md) — then name the next target.
 
 ## Queue (ordered, not started)
 
 1. Second real adapter (parked — owner focused on Pi)
-2. Session forking from a common ancestor — SHIPPED in M11; exercise via session demos
+2. Auto-apply policy for worker patches — SHIPPED in M12
 3. UX/DX backlog #31 (grep highlight vs status colors — likely closed by owner's unalias)
 4. Push policy decision: auto-apply commits locally; push remains explicit (documented in CONDUCTOR.md)
 
@@ -28,6 +28,9 @@ Owner review of M12 (conductor auto-apply policy) — then name the next target.
 
 ## Completed log
 
+- 2026-09-03 — M12 conductor auto-apply policy (#34) — committed on main, 17/24/58/14 + verify green; push stays explicit
+- 2026-09-03 — M13 interactive TUI agent + TOOLS.md (#35) — merged, agent.sh TUI launcher + identity injection, 24/58+/17/14 + verify green; release 0.0.8 activated
+
 - 2026-09-03 — M9 mission capability policy (#30) — merged, least-privilege intersection
 - 2026-09-03 — test UX: green OK/red FAIL status colors (#31 adjacent) — terminal-only, pipe-safe
 - 2026-09-03 — M10 run-record retention (#32) — merged, prune keep-N/dry-run/receipt, 49/24/14 + verify green