commandmate 0.26.1 → 0.27.0

package/dist/cli/commands/send.js

@@ -203,21 +203,6 @@ function createSendCommand() {
                 console.error(`Error: stop-pattern exceeds maximum length of ${api_client_1.MAX_STOP_PATTERN_LENGTH} characters.`);
                 process.exit(types_1.ExitCode.CONFIG_ERROR);
             }
-            // Issue #576/#588/#989: Validate --model option via shared validator (DR1-003)
-            if (options.model) {
-                // --model requires --agent copilot or --agent antigravity
-                if (!options.agent || (options.agent !== 'copilot' && options.agent !== 'antigravity')) {
-                    console.error('Error: --model option requires --agent copilot or --agent antigravity');
-                    process.exit(types_1.ExitCode.CONFIG_ERROR);
-                }
-                const modelValidation = options.agent === 'antigravity'
-                    ? (0, model_validation_1.validateAntigravityModelName)(options.model)
-                    : (0, model_validation_1.validateCopilotModelName)(options.model);
-                if (!modelValidation.valid) {
-                    console.error(`Error: Invalid model name: ${modelValidation.reason}`);
-                    process.exit(types_1.ExitCode.CONFIG_ERROR);
-                }
-            }
             // Issue #1608: every option that can be judged from its own value is
             // judged here, before the first side effect. --duration used to be the
             // exception: enableAutoYes() validated it, and that runs after
@@ -234,6 +219,27 @@ function createSendCommand() {
             const agent = options.instance
                 ? await (0, instances_1.resolveInstanceCliTool)(client, worktreeId, options.instance, options.agent)
                 : options.agent;
+            // Issue #576/#588/#989: Validate --model option via shared validator (DR1-003).
+            // Issue #1925: judged against the RESOLVED agent, not against --agent.
+            // `--instance copilot-2 --model gpt-5` names a copilot session in the
+            // only way the roster understands, and this check used to reject it for
+            // not repeating `--agent copilot` — the tool-dependent option was being
+            // validated before the tool was known (design §4 D5 決定 3). Still ahead
+            // of every side effect: resolution only reads.
+            if (options.model) {
+                if (agent !== 'copilot' && agent !== 'antigravity') {
+                    console.error('Error: --model option requires --agent copilot or --agent antigravity'
+                        + ' (or an --instance registered as one)');
+                    process.exit(types_1.ExitCode.CONFIG_ERROR);
+                }
+                const modelValidation = agent === 'antigravity'
+                    ? (0, model_validation_1.validateAntigravityModelName)(options.model)
+                    : (0, model_validation_1.validateCopilotModelName)(options.model);
+                if (!modelValidation.valid) {
+                    console.error(`Error: Invalid model name: ${modelValidation.reason}`);
+                    process.exit(types_1.ExitCode.CONFIG_ERROR);
+                }
+            }
             // Issue #1545: resolve the contract before anything with a side effect,
             // so an invalid contract cannot leave auto-yes enabled for a message
             // that was never sent.

package/dist/cli/commands/status.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"status.d.ts","sourceRoot":"","sources":["../../../src/cli/commands/status.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAGH,OAAO,EAA2C,aAAa,EAAE,MAAM,UAAU,CAAC;AA4GlF;;;;GAIG;AACH,wBAAsB,aAAa,CAAC,OAAO,GAAE,aAAkB,GAAG,OAAO,CAAC,IAAI,CAAC,CAsF9E"}
+{"version":3,"file":"status.d.ts","sourceRoot":"","sources":["../../../src/cli/commands/status.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAGH,OAAO,EAA2C,aAAa,EAAE,MAAM,UAAU,CAAC;AA+IlF;;;;GAIG;AACH,wBAAsB,aAAa,CAAC,OAAO,GAAE,aAAkB,GAAG,OAAO,CAAC,IAAI,CAAC,CA2F9E"}

package/dist/cli/commands/status.js

@@ -15,6 +15,7 @@ const daemon_1 = require("../utils/daemon");
 const env_setup_1 = require("../utils/env-setup");
 const package_info_1 = require("../utils/package-info");
 const input_validators_1 = require("../utils/input-validators");
+const version_probes_1 = require("../../lib/detection/version-probes");
 const logger = new logger_1.CLILogger();
 /**
  * Print the running daemon's version and, when it differs from the installed CLI, a warning.
@@ -32,6 +33,36 @@ function printVersionInfo(status) {
             'Restart the server ("commandmate stop && commandmate start") to run the current version.');
     }
 }
+/**
+ * Warn when this build's detection rules were read off an older CLI than the one
+ * installed (Issue #1929, design §4 D2).
+ *
+ * `status` is the diagnostic command and an operator-initiated one-off, so
+ * unlike the `capture` polling path it may await the probes — the design draws
+ * exactly that line ("露出面ごとに待つ / 待たない を分ける"). Measured cost is
+ * the slowest single `--version` (~0.9s on the reference machine) because they
+ * run concurrently, and every probe is bounded by its own timeout.
+ *
+ * Silent when nothing is stale, so the existing output is unchanged on a machine
+ * whose CLIs match — a skew nobody can act on is not worth a line. Never throws:
+ * a broken probe must not turn `commandmate status` into a failure.
+ */
+async function printDetectorFreshness() {
+    try {
+        const stale = (await (0, version_probes_1.getDetectorFreshness)()).filter((row) => row.stale);
+        if (stale.length === 0)
+            return;
+        console.log('');
+        console.log('Detector rules verified against an older CLI:');
+        for (const row of stale) {
+            console.log(`  ${row.tool}: installed ${row.installed}, rules read off ${row.verifiedAgainst}`);
+        }
+        console.log('  Detection may misread this tool; see docs/design/multi-agent-state-architecture.md.');
+    }
+    catch {
+        // A version probe is a hint. Losing it changes nothing about server status.
+    }
+}
 /**
  * Show status for a single server (main or issue-specific)
  */
@@ -94,6 +125,9 @@ async function showAllStatus() {
     catch {
         // pids directory may not exist yet
     }
+    // Once for the whole listing: the probe cache is process-level, so repeating
+    // it per server would print the same skew N times for one measurement.
+    await printDetectorFreshness();
     console.log('');
 }
 /**
@@ -165,6 +199,10 @@ async function statusCommand(options = {}) {
         if (allowedIps) {
             console.log(`IP ACL:  ${allowedIps}`);
         }
+        // Issue #1929: the other authenticated surface §4 D2 exposes detector
+        // staleness on (the first is `capture --json`). Only reached on a running
+        // server, where a detection skew is something the operator can act on.
+        await printDetectorFreshness();
         console.log('');
         process.exit(types_1.ExitCode.SUCCESS);
     }

package/dist/cli/commands/wait.d.ts

@@ -19,5 +19,31 @@
  * Infrastructure errors use ExitCode (1, 2, 99)
  */
 import { Command } from 'commander';
+/**
+ * Structured event types that mean "a turn is under way" (Issue #1839).
+ *
+ * Mirrors AGENT_EVENT_TYPES in src/lib/hooks/agent-event-types.ts; duplicated
+ * rather than imported because the CLI bundle keeps its own copy of the API
+ * shapes (see api-responses.ts).
+ *
+ * `notification` is deliberately absent, and that is the one measured deviation
+ * from the design sketched in Issue #1839. The Issue proposed accepting
+ * `stop` **or** `idle_prompt` as the end of a turn; the live capture of
+ * 2026-08-20 (see docs/design/upstream-fault-turn-boundary-1839.md) shows
+ * Claude 2.1.236 emitting `Notification(idle_prompt)` 62 s into a turn that
+ * ran nothing at all, because the composer had been idle for a minute. Reading
+ * it as a turn boundary would have re-created the false completion this gate
+ * exists to stop, one minute later. Only `Stop` ends a turn.
+ *
+ * Exported for the cross-layer pin in
+ * `tests/unit/session/status-contract-1926.test.ts`. The server opens a turn on
+ * the same three events (`src/lib/session/provisional-turn.ts`
+ * TURN_ACTIVITY_EVENTS), and since Issue #1930 `adoptTurnStart` reads that
+ * turn's `openedAt` rather than this set — so a set that drifted would change
+ * this gate silently. The set is still read here for the pre-#1930 fallback
+ * path, and the CLI cannot import the server module (`tsconfig.cli.json` sets
+ * `"paths": {}`), so the test is the only thing holding the two together.
+ */
+export declare const TURN_OPENING_EVENT_TYPES: ReadonlySet<string>;
 export declare function createWaitCommand(): Command;
 //# sourceMappingURL=wait.d.ts.map

package/dist/cli/commands/wait.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"wait.d.ts","sourceRoot":"","sources":["../../../src/cli/commands/wait.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;GAmBG;AAEH,OAAO,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AAsqBpC,wBAAgB,iBAAiB,IAAI,OAAO,CA8G3C"}
+{"version":3,"file":"wait.d.ts","sourceRoot":"","sources":["../../../src/cli/commands/wait.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;GAmBG;AAEH,OAAO,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AA6DpC;;;;;;;;;;;;;;;;;;;;;;;;GAwBG;AACH,eAAO,MAAM,wBAAwB,EAAE,WAAW,CAAC,MAAM,CAIvD,CAAC;AAy5BH,wBAAgB,iBAAiB,IAAI,OAAO,CAmJ3C"}