docs: calibration phase 22 record; CURRENT.md staleness corrected (M16/M17 late-logged, next M18); session registered (#43)

BUILD-LOG.md

@@ -438,3 +438,32 @@ Release self-determination live: the system aligns itself to RELEASE without man
   usurpation (owner, continuity-first); restructure sequenced as M20 phase 1.
 - Live drill: drift 0.0.11 -> 0.0.12 detected, health-gated activate, no
   recursion, verify green.
+
+## Phase 22: Conductor-loop calibration with a live collaborator (#43)
+
+- First full loop through the live-seat path: decompose → dispatch
+  (agent-send.sh, class=actionable) → receipt → line-by-line diff review →
+  suite-gated integration. Worker: ms-test seat (glm-5.3-flash) in the repo
+  cwd, scoped to docs/TOOLS.md, no git.
+- Before (conductor baseline): suites 24/74/14/17 green; TOOLS.md had no
+  tools/ coverage; Maintenance table claimed test-task.sh = 58 cases (stale).
+- After: TOOLS.md gains "Tools (host-side)" (agent-send.sh, agent-watch.sh,
+  unslop-check.js), corrected counts, reading-guide fix; suites 24/74/14/17
+  + verify green post-integration.
+- Masking-failure rule applied: every documented flag/subcommand/exit code
+  independently verified against tool source by the conductor, not taken
+  from the worker's report (all claims checked out).
+- Worker caught a spec gap the conductor missed: the intro reading-guide
+  ("all entry points are scripts/*.sh") became false with the new section;
+  amendment flagged, reviewed, accepted.
+- Process correction: the worker's first reply was typed into the pane
+  without agent-send.sh and never delivered; the protocol resend is the
+  report of record. Comms discipline is load-bearing, not ceremony.
+- CURRENT.md staleness corrected: it still named M16 as next though M16
+  (#38) and M17 (#40–#42, skill-lifecycle-v1, release 0.0.12) had shipped;
+  late entries added to its completed log, next action is now M18.
+
+## Result (calibration)
+
+The conductor loop is proven end to end on a live seat; TOOLS.md covers the
+tools/ tree; suites green at every gate.

docs/SESSIONS.md

@@ -9,3 +9,4 @@ are never rewritten or removed; corrections are new entries.
 | 2026-09-03 | assistant (conductor + worker) | POC through M12: containerized pi proof, config layer, missions/tasks, release model, adapter seam, workspaces/capabilities, named sessions, retention, session forking, conductor auto-apply, roles/ convention | 13 tags; suites 24/58/14 + 17 conductor + verify green; releases 0.0.1–0.0.7; issues #1–#34 closed |
 | 2026-09-03 | assistant (conductor) | User layer: profile updates (pets, family), ms-user skill review/revision (confirmation rules merged, propose-not-apply, missing-file flow, privacy scope, dispatch = all of user/, rule 9 scratch-file constraint), USER.md.bak removed | skills/ms-user/SKILL.md rewritten; ~/.mosaic-dev/user/USER.md updated (Family, Pets); USER.md.bak deleted |
 | 2026-09-03 | assistant | ms-communications skill: inter-agent messaging protocol consolidated from tools/tmux/README.md and agent-send.sh (channel, preamble grammar, flip-on-reply, triage classes, etiquette, receiving protocol, delivery mechanics) | skills/ms-communications/SKILL.md created; unslop-check clean |
+| 2026-09-03 | assistant (conductor) + ms-test collaborator (worker, glm-5.3-flash) | Conductor-loop calibration (#43): decompose → dispatch via agent-send.sh → receipt → line-by-line diff review (claims verified vs tool source) → suite-gated integration; CURRENT.md staleness corrected (M16/M17 late-logged, next action → M18) | docs/TOOLS.md tools/ section + suite-count fix; issue #43 closed; suites 24/74/14/17 + verify green |

docs/plans/CURRENT.md

@@ -7,14 +7,12 @@ update this file to the next action). No ambiguity, no re-planning.
 
 ## Next action
 
-M16 — release self-determination (`release.sh ensure` invoked at launch; post-reset auto-restore; no manual release commands). Owner approved 2026-09-03 — say "next" to execute.
+M18 — seat-role progressive capability restriction (role ceilings ∩ mission ∩ task) — say "next" to execute.
 
 ## Queue (ordered per docs/plans/ROADMAP.md)
 
-1. M17 — ms-tools skill (central tooling documentation; AGENTS.md references it; workers excluded via --no-skills)
-2. M18 — seat-role progressive capability restriction (role ceilings ∩ mission ∩ task)
-3. M19 — harness auth tooling (pi checkpoint: auth status, provider stacking, multi-account investigation)
-4. Deferred by owner: CI runners (Gitea hardware slow); second real adapter; push automation
+1. M19 — harness auth tooling (pi checkpoint: auth status, provider stacking, multi-account investigation)
+2. Deferred by owner: CI runners (Gitea hardware slow); second real adapter; push automation
 
 ## Rules
 
@@ -49,3 +47,6 @@ git history + Gitea issues.
 - 2026-09-03 — M10-era hotfix: retry lineage (#28) + AGENTS.md/SESSIONS.md recovery shim
 - 2026-09-03 — release 0.0.10 packaged and health-gated activated (user context + agent seats live)
 - 2026-09-03 — release 0.0.11 shipped (onboarding + live user context); ROADMAP.md agreed (M16–M19); CI deferred by owner
+- 2026-09-03 — M16 release self-determination (#38; `release.sh ensure` at launch, drift warnings, recursion guard) — logged late: CURRENT.md had gone stale while M16/M17 shipped; ground truth = git history
+- 2026-09-03 — M17 skill lifecycle + ms-* skill set completion (#40–#42; skill-lifecycle-v1); release 0.0.12 packaged, health-gated active — logged late, same staleness correction
+- 2026-09-03 — conductor-loop calibration with live collaborator (#43): dispatch via agent-send.sh → receipt → line-by-line diff review → suite-gated integration; docs/TOOLS.md gains Tools (host-side) section + corrected suite counts