claude-multi-session 2.6.0 → 2.7.0

package/bin/setup.js

@@ -125,6 +125,8 @@ The tool automatically:
 Returns a structured pass/fail report with recommendation.
 PROCEED ONLY IF the report says ALL CHECKS PASSED.
 
+**ENFORCED:** \`team_spawn\` will return an error if \`phase_gate\` was not called between spawn batches. The first batch (Phase 0) is free; every subsequent batch requires a passing \`phase_gate\` call first.
+
 Count your phases upfront. If you have N phases, fill in this checkpoint exactly N-1 times (between every adjacent pair of phases). Skipping verification for later phases is the #1 cause of test failures.
 
 Only intervene in workers when a session is BLOCKED or FAILED.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-multi-session",
-  "version": "2.6.0",
+  "version": "2.7.0",
   "description": "Multi-session orchestrator for Claude Code CLI — spawn, control, pause, resume, and send multiple inputs to Claude Code sessions programmatically",
   "main": "src/index.js",
   "bin": {

package/src/mcp-server.js

@@ -76,6 +76,10 @@ let pipelineEngine = null;
 let snapshotEngine = null;
 let currentTeamName = null;
 
+// Phase gate enforcement state — tracks gate calls vs spawn batches per team
+// team -> { gateCount: number, spawnBatchCount: number, lastSpawnTime: number }
+const _gateState = new Map();
+
 /**
  * Get or create Team Hub instances for a given team
  * This function lazily creates the instances on first use
@@ -1748,6 +1752,31 @@ async function handleTeamSpawn(args) {
     const teamName = args.team || 'default';
     const { teamHub } = getTeamInstances(teamName);
 
+    // Gate enforcement: require phase_gate between spawn batches
+    const state = _gateState.get(teamName) || { gateCount: 0, spawnBatchCount: 0, lastSpawnTime: 0 };
+    const now = Date.now();
+
+    // Detect new spawn batch (>5s since last spawn = new batch)
+    const isNewBatch = (now - state.lastSpawnTime) > 5000;
+    if (isNewBatch) {
+      state.spawnBatchCount++;
+    }
+    state.lastSpawnTime = now;
+    _gateState.set(teamName, state);
+
+    // Rule: spawnBatchCount must be <= gateCount + 1
+    // (first batch is free, every subsequent batch needs a gate)
+    if (state.spawnBatchCount > state.gateCount + 1) {
+      return errorResult(
+        `PHASE GATE REQUIRED: You have spawned ${state.spawnBatchCount - 1} batch(es) of workers ` +
+        `but only called phase_gate ${state.gateCount} time(s). ` +
+        `Call phase_gate() to verify the previous phase completed before spawning more workers.\n\n` +
+        `Example:\n` +
+        `phase_gate({ phase_completing: "Phase N", phase_starting: "Phase N+1", ` +
+        `expected_artifacts: ["..."] })`
+      );
+    }
+
     // Join the team roster
     teamHub.joinTeam(args.name, {
       role: args.role || 'team member',
@@ -2769,6 +2798,14 @@ function handlePhaseGate(args) {
     // Overall pass/fail
     report.passed = report.checks.every(c => c.passed);
 
+    // Track gate pass for spawn enforcement
+    if (report.passed) {
+      const state = _gateState.get(teamName) || { gateCount: 0, spawnBatchCount: 0, lastSpawnTime: 0 };
+      state.gateCount++;
+      _gateState.set(teamName, state);
+      report._gate_generation = state.gateCount;
+    }
+
     // Action recommendation
     if (report.passed) {
       report.recommendation = `ALL CHECKS PASSED. Safe to proceed to ${args.phase_starting}.`;
@@ -2895,6 +2932,9 @@ function handleTeamReset(args) {
     snapshotEngine = null;
     currentTeamName = null;
 
+    // Clear gate enforcement state
+    _gateState.delete(teamName);
+
     summary.message = `Team "${teamName}" has been reset. ${summary.cleared.length} stores cleared.`;
 
     return textResult(JSON.stringify(summary, null, 2));

package/src/prompts.js

@@ -608,6 +608,8 @@ The tool automatically:
 Returns a structured pass/fail report with recommendation.
 PROCEED ONLY IF the report says ALL CHECKS PASSED.
 
+**ENFORCED:** \`team_spawn\` will return an error if \`phase_gate\` was not called between spawn batches. The first batch (Phase 0) is free; every subsequent batch requires a passing \`phase_gate\` call first.
+
 === PHASE COUNTING RULE ===
 At the start of planning, count and list your phases explicitly:
 "Phase 0: [foundation], Phase 1: [routes], Phase 2: [tests], ..."
@@ -919,6 +921,8 @@ IMPORTANT: You are the ORCHESTRATOR. Your job is to PLAN, SPAWN, and MONITOR —
 
 5. **Post-Phase Verification** — After each phase completes, call \`phase_gate()\` which runs ALL verification checks in one call: confirms artifacts exist, validates content, checks workers are idle, and verifies artifact readers. Only proceed when it reports ALL CHECKS PASSED. If you have N phases, verify N-1 times.
 
+**Note:** \`team_spawn\` will return an error if \`phase_gate\` was not called between spawn batches. The first batch (Phase 0) is free; every subsequent batch requires a passing \`phase_gate\` call first.
+
 6. **Collect** — When all workers are idle, check \`artifact_list\` for published outputs and summarize results for the user.
 
 ### Critical Rule: Never Assign the Same File to Two Workers