commandmate 0.20.0 → 0.21.1

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

@@ -0,0 +1,14 @@
+/**
+ * sync Command - Trigger a server-side worktree re-scan
+ * Issue #1680: worktrees created with `git worktree add` stay invisible to
+ * `commandmate ls` until the GUI sync button is pressed. This command calls the
+ * same endpoint (POST /api/repositories/sync) so worktree creation → dispatch
+ * completes from the CLI alone.
+ */
+import { Command } from 'commander';
+/**
+ * Create the sync command.
+ * [DR1-08] Factory pattern for addCommand() registration.
+ */
+export declare function createSyncCommand(): Command;
+//# sourceMappingURL=sync.d.ts.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"sync.d.ts","sourceRoot":"","sources":["../../../src/cli/commands/sync.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAEH,OAAO,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AAOpC;;;GAGG;AACH,wBAAgB,iBAAiB,IAAI,OAAO,CAmC3C"}

package/dist/cli/commands/sync.js

@@ -0,0 +1,53 @@
+"use strict";
+/**
+ * sync Command - Trigger a server-side worktree re-scan
+ * Issue #1680: worktrees created with `git worktree add` stay invisible to
+ * `commandmate ls` until the GUI sync button is pressed. This command calls the
+ * same endpoint (POST /api/repositories/sync) so worktree creation → dispatch
+ * completes from the CLI alone.
+ */
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.createSyncCommand = createSyncCommand;
+const commander_1 = require("commander");
+const types_1 = require("../types");
+const api_client_1 = require("../utils/api-client");
+const command_helpers_1 = require("../utils/command-helpers");
+/**
+ * Create the sync command.
+ * [DR1-08] Factory pattern for addCommand() registration.
+ */
+function createSyncCommand() {
+    const cmd = new commander_1.Command('sync');
+    cmd
+        .description('Re-scan repositories and sync worktrees to the server (same as the GUI sync button)')
+        .option('--json', 'JSON output (API response as-is)')
+        .option('--token <token>', command_helpers_1.TOKEN_WARNING)
+        .action(async (options) => {
+        try {
+            const client = new api_client_1.ApiClient({ token: options.token });
+            const data = await client.post('/api/repositories/sync');
+            if (options.json) {
+                console.log(JSON.stringify(data, null, 2));
+                return;
+            }
+            console.log(data.message);
+            if (data.deletedCount > 0) {
+                console.log(`Removed ${data.deletedCount} stale worktree(s).`);
+            }
+            for (const warning of data.cleanupWarnings ?? []) {
+                console.error(`Warning: ${warning}`);
+            }
+        }
+        catch (error) {
+            // The route's only 400 is "No repositories configured..." — the server's
+            // wording names the fix (WORKTREE_REPOS / CM_ROOT_DIR), so pass it
+            // through instead of the generic "Bad request" mapping.
+            if (error instanceof api_client_1.ApiError && error.statusCode === 400 && error.payload?.error) {
+                console.error(`Error: ${error.payload.error}`);
+                process.exit(types_1.ExitCode.CONFIG_ERROR);
+            }
+            (0, command_helpers_1.handleCommandError)(error);
+        }
+    });
+    return cmd;
+}

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;;;;;;;;;;;;;;GAcG;AAEH,OAAO,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AAySpC,wBAAgB,iBAAiB,IAAI,OAAO,CA6G3C"}
+{"version":3,"file":"wait.d.ts","sourceRoot":"","sources":["../../../src/cli/commands/wait.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;GAcG;AAEH,OAAO,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AAuXpC,wBAAgB,iBAAiB,IAAI,OAAO,CA6G3C"}

package/dist/cli/commands/wait.js

@@ -34,6 +34,47 @@ const POLL_INTERVAL_MS = 5000;
  * names the state instead of inventing options.
  */
 const SELECTION_LIST_PROMPT_TYPE = 'selection_list';
+/**
+ * How recent `autoYes.lastSuppression` must be to be reported as the reason this
+ * wait is blocked (Issue #1699).
+ *
+ * The record is refreshed on every poll for as long as the suppressed prompt is
+ * on screen, so a fresh timestamp means "this is happening now" while an old one
+ * is a historical suppression of some earlier prompt. The window is generous
+ * against the server's own poll interval — being a few seconds late with a true
+ * report beats staying silent, which is the failure this exists to fix.
+ */
+const SUPPRESSION_FRESH_MS = 60_000;
+/** The suppression currently blocking this session, or null. */
+function activeSuppression(data, now) {
+    const suppression = data.autoYes?.lastSuppression;
+    if (!suppression)
+        return null;
+    const ageMs = now - suppression.at;
+    // A negative age is clock skew between the CLI and the server, not staleness.
+    if (ageMs > SUPPRESSION_FRESH_MS)
+        return null;
+    return { suppression, ageSeconds: Math.max(0, Math.round(ageMs / 1000)) };
+}
+/**
+ * One stderr line naming the policy that is holding this prompt (Issue #1699).
+ *
+ * `wait` used to print only "Waiting for human response...", which reads the
+ * same whether a human was always going to answer or whether Auto-Yes silently
+ * refused to. That ambiguity is what let a deny pattern matching a finished turn
+ * stall two workers unnoticed; the pattern and the reason code belong on screen.
+ */
+function formatSuppressionNotice(suppression, ageSeconds) {
+    const parts = [
+        `reason=${suppression.reason}`,
+        `mode=${suppression.mode ?? 'none'}`,
+        `promptType=${suppression.promptType}`,
+    ];
+    if (suppression.pattern !== undefined) {
+        parts.push(`pattern=${JSON.stringify(suppression.pattern)}`);
+    }
+    return `  auto-yes suppressed this prompt by contract policy: ${parts.join(' ')} (${ageSeconds}s ago)`;
+}
 /**
  * Poll a single worktree until completion, prompt, or timeout.
  */
@@ -82,10 +123,17 @@ async function pollWorktree(client, worktreeId, options) {
             }
             // Prompt detected
             if (data.isPromptWaiting && data.promptData) {
+                // Issue #1699: report a policy suppression on both exits — the human one
+                // keeps polling and would otherwise say nothing about why nobody
+                // answered, and the agent one is read by pipelines that never see stderr.
+                const suppressed = activeSuppression(data, Date.now());
                 // [DR1-03] Prompt detection exit code
                 if (options.onPrompt === 'human') {
                     // Block and continue polling - user handles prompt manually
                     console.error(`Prompt detected on ${worktreeId}. Waiting for human response...`);
+                    if (suppressed) {
+                        console.error(formatSuppressionNotice(suppressed.suppression, suppressed.ageSeconds));
+                    }
                     await sleep(POLL_INTERVAL_MS);
                     continue;
                 }
@@ -97,7 +145,24 @@ async function pollWorktree(client, worktreeId, options) {
                     question: data.promptData.question || '',
                     options: data.promptData.options || [],
                     status: data.promptData.status || 'pending',
+                    ...(data.promptData.approvalTarget !== undefined && {
+                        approvalTarget: data.promptData.approvalTarget,
+                    }),
+                    ...(suppressed && {
+                        autoYesSuppression: {
+                            reason: suppressed.suppression.reason,
+                            mode: suppressed.suppression.mode,
+                            promptType: suppressed.suppression.promptType,
+                            ...(suppressed.suppression.pattern !== undefined && {
+                                pattern: suppressed.suppression.pattern,
+                            }),
+                            ageSeconds: suppressed.ageSeconds,
+                        },
+                    }),
                 };
+                if (suppressed) {
+                    console.error(formatSuppressionNotice(suppressed.suppression, suppressed.ageSeconds));
+                }
                 return { exitCode: types_1.WaitExitCode.PROMPT_DETECTED, output: promptOutput };
             }
             // Issue #1628: an arrow-key menu is the agent blocked on a human just as much
@@ -108,6 +173,12 @@ async function pollWorktree(client, worktreeId, options) {
                 if (options.onPrompt === 'human') {
                     console.error(`Selection list active on ${worktreeId} (${data.sessionStatusReason ?? 'selection_list'}). ` +
                         'Waiting for human response...');
+                    // Issue #1699: the poller parses frames status-detector publishes as
+                    // selection lists, so a policy can be the reason this one is stuck too.
+                    const suppressed = activeSuppression(data, Date.now());
+                    if (suppressed) {
+                        console.error(formatSuppressionNotice(suppressed.suppression, suppressed.ageSeconds));
+                    }
                     await sleep(POLL_INTERVAL_MS);
                     continue;
                 }
@@ -271,7 +342,7 @@ function createWaitCommand() {
         .description('Wait for agent completion (1 worktree per CLI instance recommended)')
         .argument('<worktree-ids...>', 'Worktree ID(s) to wait on')
         .option('--timeout <seconds>', 'Maximum wait time in seconds', parseInt)
-        .option('--on-prompt <mode>', 'Prompt handling: agent (default) or human')
+        .option('--on-prompt <mode>', 'Prompt handling: agent (default) exits 10 with a prompt JSON payload on stdout (read it before re-capturing); human keeps waiting for a human reply')
         .option('--stall-timeout <seconds>', 'Maximum time without output change', parseInt)
         .option('--instance <id>', agent_target_options_1.WAIT_INSTANCE_OPTION_DESCRIPTION)
         .option('--verify', 'After completion, run every verification gate; exit 20 when a gate fails, 21 when there is nothing to verify')

package/dist/cli/docs/agent-operations.d.ts

@@ -5,6 +5,6 @@
  * This content is embedded as a string constant so that it's available
  * even when installed via `npm install -g commandmate` (where docs/ is not included).
  */
-export declare const AGENT_OPERATIONS_GUIDE = "# CLI Agent Operations Guide\n\nOperate agent sessions from the CommandMate CLI.\nThese commands enable coding agents (Claude Code, Codex, etc.) to orchestrate other agents in parallel.\n\n## Prerequisites\n\n- CommandMate server must be running: commandmate start --daemon\n- Target worktrees must be registered (visible in browser UI sidebar)\n- Use CM_PORT env var to connect to a different port (default: 3000)\n- Use CM_AUTH_TOKEN env var for authenticated servers\n\n## Commands\n\n### commandmate ls\n  List worktrees with status.\n\n  commandmate ls                          # Table format (ID, NAME, STATUS, DEFAULT)\n  commandmate ls --json                   # JSON output (for agent consumption)\n  commandmate ls --quiet                  # IDs only, one per line (for piping)\n  commandmate ls --branch <prefix>        # Filter by branch name prefix\n  commandmate ls --id <prefix>            # Filter by worktree id prefix\n\n  Worktree ids are <repo>-<branch> slugs (e.g. anvil-develop). --id / --branch\n  front-match is case-sensitive and does NOT guarantee uniqueness (e.g.\n  --id anvil-develop also matches anvil-develop-2). --branch and --id combine\n  as AND. Use --id to disambiguate the same branch across repositories.\n\n  STATUS values:\n    idle     - Session not started\n    ready    - Session running, waiting for input (task completed)\n    running  - Agent executing a task\n    waiting  - Confirmation prompt active (Yes/No, etc.)\n\n### commandmate send <worktree-id> \"<message>\"\n  Send a message to an agent (async). Starts session automatically if not running.\n\n  Options:\n    --instance <id>        Agent instance ID: <agent> or <agent>-<n> (e.g. claude-2, or codex\n                           for the codex primary instance). The recommended way to name a\n                           target: send / wait / respond / capture / auto-yes all take it.\n    --agent <id>           Ad-hoc CLI tool for an instance the roster does not know:\n                           claude (default), codex, gemini, vibe-local, opencode, copilot, antigravity\n    --register             Register the --instance session into the agent-instance roster\n    --auto-yes             Enable auto-yes before sending\n    --duration <d>         Auto-yes duration: 1h, 3h, 8h (default: 1h)\n    --stop-pattern <p>     Auto-yes stop condition (regex)\n\n  Finding worktree IDs:\n    WT=$(commandmate ls --branch feature/101 --quiet)\n    WT=$(commandmate ls --id anvil- --quiet)   # disambiguate by repo (id prefix)\n    commandmate send \"$WT\" \"Implement this\"\n\n  Targeting a non-default agent (Issue #1638): pass --instance, not --agent. Only\n  --instance is accepted by every command -- 'wait --agent' does not exist -- so a\n  workflow that names the agent on 'send' and nothing on 'wait' waits on the wrong\n  session in silence.\n    commandmate send \"$WT\" \"Implement this\" --instance codex\n    commandmate wait \"$WT\" --instance codex\n\n### commandmate wait <worktree-id...>\n  Block until agent completes or prompt is detected.\n\n  Options:\n    --timeout <seconds>        Maximum wait time\n    --on-prompt <mode>         agent (default) or human\n    --stall-timeout <seconds>  Max time without output change\n    --instance <id>            Agent instance to wait on. There is no --agent here.\n    --verify                   After completion, run every verification gate\n    --require-work             After completion, run only the work-evidence gate\n\n  Exit codes:\n    0   - Completed (agent idle/ready), and verified when --verify was given\n    10  - Prompt detected (--on-prompt agent mode)\n    20  - A verification gate failed (--verify)\n    21  - Nothing to verify: no commits, no uncommitted changes\n    124 - Timeout exceeded\n\n  --on-prompt modes:\n    agent  - Returns exit 10 immediately with prompt JSON on stdout\n    human  - Keeps blocking until human responds via browser UI\n\n  Prompt JSON output (exit 10):\n    {\"worktreeId\":\"...\",\"cliToolId\":\"claude\",\"type\":\"yes_no\",\"question\":\"...\",\"options\":[\"yes\",\"no\"],\"status\":\"pending\"}\n\n  --verify turns \"the agent stopped\" into \"the work passes the repository's own\n  checks\". Verification only runs when completion was detected: a prompt (10) or\n  a timeout (124) is reported as-is and never verified. With several worktrees,\n  gates run one worktree at a time because the server caps concurrent runs.\n\n### commandmate verify <worktree-id>\n  Run the gates declared in .commandmate/verify.yaml against a worktree.\n\n  Options:\n    --gates <id1,id2>     Gate ids to run (default: work-evidence + all declared)\n    --instance <id>       Attribute the run to an agent instance\n    --timeout <seconds>   Stop polling after N seconds (exit 124)\n    --json                Print the run and its gate results as JSON on stdout\n\n  Exit codes:\n    0   - Every gate passed\n    20  - A gate failed, timed out, or errored\n    21  - work-evidence found nothing to verify (no commits, no changes)\n    99  - The run produced no verdict (bad verify.yaml, gates skipped, cancelled)\n    124 - --timeout elapsed while the run was still going\n\n  Output (progress on stderr, verdict on stdout):\n    GATE work-evidence PASS (commits=3, uncommitted=2)\n    GATE lint PASS (exit=0, 12.3s)\n    GATE unit FAIL (exit=1, 45.0s)\n    RESULT failed\n\n  Gates run in the worktree's own directory. Gates are skipped (run status 99,\n  never 0) in the checkout the server itself runs from when verify.yaml sets\n  options.skipInPrimaryCheckout, so a 'build' gate cannot replace the assets the\n  live app is serving.\n\n### commandmate verify history / commandmate verify show <run-id>\n  Read past verification runs. Both are read-only and never start a run, so\n  neither returns 20 or 21 \u2014 those mean \"this tree failed verification\", and a\n  question about history is not a verdict on the current tree.\n\n  commandmate verify history                          # every worktree, newest 50\n  commandmate verify history --worktree <id>          # one worktree\n  commandmate verify history --days 14 --limit 100    # window and page size\n  commandmate verify history --json                   # JSON array on stdout\n  commandmate verify show 42                          # gates + log tails\n  commandmate verify show 42 --json\n\n  history options:\n    --worktree <id>       Restrict to one worktree (default: all)\n    --days <n>            Look back n days, 1..90 (default: no lower bound)\n    --limit <n>           Maximum runs, 1..500 (default: 50)\n\n  One run per line. The leading #<run-id> is what \"verify show\" takes:\n    #42  2026-07-31T04:12:00.000Z  myrepo-feature-101  manual  failed  failed: unit,build\n\n  The listing carries gate verdicts but NOT gate log bodies \u2014 logTail is absent\n  from the JSON, not null. Use \"verify show <run-id>\" when you need the log.\n\n  Exit codes:\n    0   - Read succeeded (also when nothing matched: stderr note, or [] in JSON)\n    2   - Bad argument (--days/--limit out of range, bad worktree or run id)\n    99  - No such run (404), or an unexpected failure\n\n### commandmate respond <worktree-id> \"<answer>\"\n  Respond to an agent's prompt.\n\n  commandmate respond <id> \"yes\"          # Yes/No\n  commandmate respond <id> \"2\"            # Multiple choice (number)\n  commandmate respond <id> \"custom text\"  # Free text\n  commandmate respond <id> \"yes\" --instance codex-2   # Specific instance\n\n  Exit codes:\n    0  - Response sent\n    99 - Prompt already dismissed (prompt_no_longer_active)\n\n### commandmate capture <worktree-id>\n  Get current terminal output.\n\n  commandmate capture <id>                   # Plain text\n  commandmate capture <id> --json            # JSON with status info\n  commandmate capture <id> --instance codex  # Specific instance\n\n### commandmate auto-yes <worktree-id>\n  Control auto-yes (automatic prompt response).\n\n  commandmate auto-yes <id> --enable                    # Enable (default 1h)\n  commandmate auto-yes <id> --enable --duration 3h      # With duration\n  commandmate auto-yes <id> --enable --stop-pattern \"error\"\n  commandmate auto-yes <id> --disable                   # Disable\n  commandmate auto-yes <id> --enable --instance codex-2 # Scoped to one instance\n\n### commandmate instances <worktree-id> [action] [args]\n  Discover and manage a worktree's agent-instance roster (1 agent, multiple sessions).\n\n  commandmate instances <id>                            # List roster + running/auto-yes status\n  commandmate instances <id> --json                     # JSON output\n  commandmate instances <id> add --agent codex          # Add an instance (auto-generates ID, e.g. codex-2)\n  commandmate instances <id> add --agent codex --alias \"Review\" --id codex-3\n  commandmate instances <id> remove <instance-id>       # Remove from roster\n  commandmate instances <id> remove <instance-id> --kill  # Remove and kill its session\n  commandmate instances <id> alias <instance-id> \"New Name\"\n  commandmate instances <id> kill <instance-id>         # Kill only that instance's session\n\n  See \"Multi-Session\" below for the ID convention and roster semantics.\n\n### commandmate skill <subcommand>\n  Manage official Agent Skills. Every subcommand is a thin client over the same\n  APIs the browser UI uses: the CLI never downloads, extracts, writes or deletes\n  anything itself, and never sends a filesystem path, artifact URL, file list or\n  checksum (the API rejects those outright).\n\n  commandmate skill list [--json] [--prerelease]\n  commandmate skill info <skill-id> [--version <v>] [--json]\n  commandmate skill plan <skill-id> --worktree <id> [--version <v>] [--json]\n  commandmate skill install <skill-id> --worktree <id> --version <exact> [--dry-run] [--yes] [--ack-risk <id>@<version>] [--json]\n  commandmate skill uninstall <skill-id> --worktree <id> [--dry-run] [--yes] [--json]\n  commandmate skill status <skill-id> --worktree <id> [--json]\n\n  Confirmation contract (writes = install / uninstall):\n    - A plan is always built and shown first. --dry-run stops there.\n    - Without a TTY, a write REQUIRES --yes. A missing --yes is refused, never\n      assumed: an environment that cannot prompt must not install silently.\n    - A high-risk Skill additionally requires --ack-risk <skill-id>@<version>\n      with the exact id and version. --yes alone never carries a high-risk\n      install, in a TTY or out of one.\n\n  Exit codes:\n    0   success\n    1   the server or the Catalog could not be reached (retryable)\n    2   invalid arguments, unknown Skill or unknown version\n    11  the worktree refused it (local change, conflict, lock, plan drift)\n    12  the write was never confirmed (no --yes, declined, or missing --ack-risk)\n    13  files changed but the operation needs reconciliation\n\n  --json prints the API response body verbatim on stdout; diagnostics, prompts\n  and errors always go to stderr, so a failed --json run leaves stdout empty.\n\n  'skill status' reports one Skill in one worktree, read from the install\n  receipt on disk. There is no per-worktree listing endpoint yet, so <skill-id>\n  is required.\n\n## Multi-Session (1 agent, multiple sessions)\n\n  A worktree can run several sessions of the same CLI tool concurrently. Each\n  session is an \"instance\" identified by an instance ID:\n    <agent>        - the agent's primary instance (e.g. \"claude\")\n    <agent>-<n>    - an additional instance, n >= 2 (e.g. \"claude-2\", \"claude-3\")\n\n  --instance is accepted by send / wait / respond / capture / auto-yes.\n  send --instance auto-starts the session if it is not already running.\n\n  --instance alone is the recommended way to name a target (Issue #1638). It is\n  the only flag all five commands share: --agent is rejected by 'wait'. A\n  rostered instance already carries its CLI tool (Issue #1629), and an instance\n  id that is itself a tool id resolves to that tool's primary instance even\n  without a roster entry, so '--instance codex' needs no --agent.\n\n  --agent remains accepted by send / respond / capture / auto-yes as the\n  supplement for ad-hoc instances the roster does not know -- notably\n  '--register', which cannot infer the tool from an id like codex-3. Passing an\n  --agent that contradicts the roster is an error (exit 2), not an override.\n\n  The roster (visible in the browser UI's Agent panel) is the list of known\n  instances with aliases and display order. Ad-hoc sessions started via\n  'send --instance' do NOT appear in the roster unless registered:\n    commandmate send <id> \"...\" --instance claude-2 --register\n  Without --register, the session still runs and responds to CLI commands,\n  but it will not show up in the UI sidebar/roster until added there or via\n  'commandmate instances <id> add'.\n\n  Per-instance auto-yes: --instance scopes --auto-yes/--duration/--stop-pattern\n  to that specific session, independent of other instances of the same agent.\n\n  commandmate instances <id>                        # discover valid --instance values\n  commandmate send <id> \"task\" --instance codex-2 --auto-yes\n  commandmate wait <id> --instance codex-2 --timeout 600\n  commandmate capture <id> --instance codex-2\n\n## All Exit Codes\n\n  0   SUCCESS          - Completed successfully\n  1   DEPENDENCY_ERROR - Server not running\n  2   CONFIG_ERROR     - Validation error (invalid agent, duration, etc.)\n  10  PROMPT_DETECTED  - Prompt detected during wait\n  20  VERIFY_FAILED    - A verification gate failed (verify, wait --verify)\n  21  NOT_STARTED      - Nothing to verify: no commits, no uncommitted changes\n  99  UNEXPECTED_ERROR - Unexpected error / resource not found / no verdict\n  124 TIMEOUT          - Wait or verification timeout exceeded\n\n  When one 'wait' covers several worktrees, the reported code is the highest\n  priority one observed: 10 > 20 > 21 > 124.\n\n## Troubleshooting\n\n  Server not running:\n    commandmate start --daemon\n    CM_PORT=3011 commandmate ls        # Different port\n\n  Worktree not found:\n    commandmate ls --quiet             # Check registered IDs\n    curl -s -X POST http://localhost:3000/api/repositories/sync  # Sync new worktrees\n\n  Authentication:\n    CM_AUTH_TOKEN=your-token commandmate ls\n";
+export declare const AGENT_OPERATIONS_GUIDE = "# CLI Agent Operations Guide\n\nOperate agent sessions from the CommandMate CLI.\nThese commands enable coding agents (Claude Code, Codex, etc.) to orchestrate other agents in parallel.\n\n## Prerequisites\n\n- CommandMate server must be running: commandmate start --daemon\n- Target worktrees must be registered (visible in browser UI sidebar)\n- Use CM_PORT env var to connect to a different port (default: 3000)\n- Use CM_AUTH_TOKEN env var for authenticated servers\n\n## Commands\n\n### commandmate ls\n  List worktrees with status.\n\n  commandmate ls                          # Table format (ID, NAME, STATUS, DEFAULT)\n  commandmate ls --json                   # JSON output (for agent consumption)\n  commandmate ls --quiet                  # IDs only, one per line (for piping)\n  commandmate ls --branch <prefix>        # Filter by branch name prefix\n  commandmate ls --id <prefix>            # Filter by worktree id prefix\n\n  Worktree ids are <repo>-<branch> slugs (e.g. anvil-develop). --id / --branch\n  front-match is case-sensitive and does NOT guarantee uniqueness (e.g.\n  --id anvil-develop also matches anvil-develop-2). --branch and --id combine\n  as AND. Use --id to disambiguate the same branch across repositories.\n\n  STATUS values:\n    idle     - Session not started\n    ready    - Session running, waiting for input (task completed)\n    running  - Agent executing a task\n    waiting  - Confirmation prompt active (Yes/No, etc.)\n\n### commandmate sync\n  Ask the server to re-scan repositories and sync worktrees to its database\n  (same endpoint as the GUI sync button). Run it after 'git worktree add' so the\n  new worktree appears in 'commandmate ls' without opening the GUI (Issue #1680).\n\n  commandmate sync                        # Prints the server's summary message\n  commandmate sync --json                 # Full API response (worktreeCount,\n                                          # repositoryCount, repositories,\n                                          # deletedCount, cleanupWarnings)\n\n### commandmate send <worktree-id> \"<message>\"\n  Send a message to an agent (async). Starts session automatically if not running.\n\n  Options:\n    --instance <id>        Agent instance ID: <agent> or <agent>-<n> (e.g. claude-2, or codex\n                           for the codex primary instance). The recommended way to name a\n                           target: send / wait / respond / capture / auto-yes all take it.\n    --agent <id>           Ad-hoc CLI tool for an instance the roster does not know:\n                           claude (default), codex, gemini, vibe-local, opencode, copilot, antigravity\n    --register             Register the --instance session into the agent-instance roster\n    --auto-yes             Enable auto-yes before sending (session-wide, no policy\n                           guard -- for unattended runs prefer --contract with an\n                           autoYes policy: mode / denyPatterns)\n    --duration <d>         Auto-yes duration: 1h, 3h, 8h (default: 1h)\n    --stop-pattern <p>     Auto-yes stop condition (regex; matches terminal output,\n                           cannot block commands -- see auto-yes below)\n\n  Finding worktree IDs:\n    WT=$(commandmate ls --branch feature/101 --quiet)\n    WT=$(commandmate ls --id anvil- --quiet)   # disambiguate by repo (id prefix)\n    commandmate send \"$WT\" \"Implement this\"\n\n  Targeting a non-default agent (Issue #1638): pass --instance, not --agent. Only\n  --instance is accepted by every command -- 'wait --agent' does not exist -- so a\n  workflow that names the agent on 'send' and nothing on 'wait' waits on the wrong\n  session in silence.\n    commandmate send \"$WT\" \"Implement this\" --instance codex\n    commandmate wait \"$WT\" --instance codex\n\n### commandmate wait <worktree-id...>\n  Block until agent completes or prompt is detected.\n\n  Options:\n    --timeout <seconds>        Maximum wait time\n    --on-prompt <mode>         agent (default) or human\n    --stall-timeout <seconds>  Max time without output change\n    --instance <id>            Agent instance to wait on. There is no --agent here.\n    --verify                   After completion, run every verification gate\n    --require-work             After completion, run only the work-evidence gate\n\n  Exit codes:\n    0   - Completed (agent idle/ready), and verified when --verify was given\n    10  - Prompt detected (--on-prompt agent mode)\n    20  - A verification gate failed (--verify)\n    21  - Nothing to verify: no commits, no uncommitted changes\n    124 - Timeout exceeded\n\n  --on-prompt modes:\n    agent  - Returns exit 10 immediately with prompt JSON on stdout\n    human  - Keeps blocking until human responds via browser UI\n\n  Prompt JSON output (exit 10):\n    {\"worktreeId\":\"...\",\"cliToolId\":\"claude\",\"type\":\"yes_no\",\"question\":\"...\",\"options\":[\"yes\",\"no\"],\"status\":\"pending\"}\n    The payload IS the prompt -- read it from stdout before falling back to\n    capture. For type \"selection_list\", options is empty by design and the\n    question field carries the reason.\n\n  --verify turns \"the agent stopped\" into \"the work passes the repository's own\n  checks\". Verification only runs when completion was detected: a prompt (10) or\n  a timeout (124) is reported as-is and never verified. With several worktrees,\n  gates run one worktree at a time because the server caps concurrent runs.\n\n### commandmate verify <worktree-id>\n  Run the gates declared in .commandmate/verify.yaml against a worktree.\n\n  Options:\n    --gates <id1,id2>     Gate ids to run (default: work-evidence + all declared)\n    --instance <id>       Attribute the run to an agent instance\n    --timeout <seconds>   Stop polling after N seconds (exit 124)\n    --json                Print the run and its gate results as JSON on stdout\n\n  Exit codes:\n    0   - Every gate passed\n    20  - A gate failed, timed out, or errored\n    21  - work-evidence found nothing to verify (no commits, no changes)\n    99  - The run produced no verdict (bad verify.yaml, gates skipped, cancelled)\n    124 - --timeout elapsed while the run was still going\n\n  Output (progress on stderr, verdict on stdout):\n    GATE work-evidence PASS (commits=3, uncommitted=2)\n    GATE lint PASS (exit=0, 12.3s)\n    GATE unit FAIL (exit=1, 45.0s)\n    RESULT failed\n\n  Gates run in the worktree's own directory. Gates are skipped (run status 99,\n  never 0) in the checkout the server itself runs from when verify.yaml sets\n  options.skipInPrimaryCheckout, so a 'build' gate cannot replace the assets the\n  live app is serving.\n\n### commandmate verify history / commandmate verify show <run-id>\n  Read past verification runs. Both are read-only and never start a run, so\n  neither returns 20 or 21 \u2014 those mean \"this tree failed verification\", and a\n  question about history is not a verdict on the current tree.\n\n  commandmate verify history                          # every worktree, newest 50\n  commandmate verify history --worktree <id>          # one worktree\n  commandmate verify history --days 14 --limit 100    # window and page size\n  commandmate verify history --json                   # JSON array on stdout\n  commandmate verify show 42                          # gates + log tails\n  commandmate verify show 42 --json\n\n  history options:\n    --worktree <id>       Restrict to one worktree (default: all)\n    --days <n>            Look back n days, 1..90 (default: no lower bound)\n    --limit <n>           Maximum runs, 1..500 (default: 50)\n\n  One run per line. The leading #<run-id> is what \"verify show\" takes:\n    #42  2026-07-31T04:12:00.000Z  myrepo-feature-101  manual  failed  failed: unit,build\n\n  The listing carries gate verdicts but NOT gate log bodies \u2014 logTail is absent\n  from the JSON, not null. Use \"verify show <run-id>\" when you need the log.\n\n  Exit codes:\n    0   - Read succeeded (also when nothing matched: stderr note, or [] in JSON)\n    2   - Bad argument (--days/--limit out of range, bad worktree or run id)\n    99  - No such run (404), or an unexpected failure\n\n### commandmate respond <worktree-id> \"<answer>\"\n  Respond to an agent's prompt.\n\n  commandmate respond <id> \"yes\"          # Yes/No\n  commandmate respond <id> \"2\"            # Multiple choice (number)\n  commandmate respond <id> \"custom text\"  # Free text\n  commandmate respond <id> \"yes\" --instance codex-2   # Specific instance\n\n  Exit codes:\n    0  - Response sent\n    99 - Prompt already dismissed (prompt_no_longer_active)\n\n### commandmate capture <worktree-id>\n  Get current terminal output.\n\n  commandmate capture <id>                   # Plain text\n  commandmate capture <id> --json            # JSON with status info\n  commandmate capture <id> --instance codex  # Specific instance\n\n### commandmate auto-yes <worktree-id>\n  Control auto-yes (automatic prompt response).\n\n  commandmate auto-yes <id> --enable                    # Enable (default 1h)\n  commandmate auto-yes <id> --enable --duration 3h      # With duration\n  commandmate auto-yes <id> --enable --stop-pattern \"error\"\n  commandmate auto-yes <id> --disable                   # Disable\n  commandmate auto-yes <id> --enable --instance codex-2 # Scoped to one instance\n\n  --stop-pattern matches new terminal output, not the commands an agent runs.\n  It cannot block a command; a build log that merely prints the pattern\n  (e.g. \"rm -rf\" in an npm script) also triggers it and stops auto-yes.\n  To suppress auto-responses for risky prompts, use the task contract's\n  autoYes.denyPatterns instead (docs/design/task-contract.md).\n\n### commandmate instances <worktree-id> [action] [args]\n  Discover and manage a worktree's agent-instance roster (1 agent, multiple sessions).\n\n  commandmate instances <id>                            # List roster + running/auto-yes status\n  commandmate instances <id> --json                     # JSON output\n  commandmate instances <id> add --agent codex          # Add an instance (auto-generates ID, e.g. codex-2)\n  commandmate instances <id> add --agent codex --alias \"Review\" --id codex-3\n  commandmate instances <id> remove <instance-id>       # Remove from roster\n  commandmate instances <id> remove <instance-id> --kill  # Remove and kill its session\n  commandmate instances <id> alias <instance-id> \"New Name\"\n  commandmate instances <id> kill <instance-id>         # Kill only that instance's session\n\n  See \"Multi-Session\" below for the ID convention and roster semantics.\n\n### commandmate skill <subcommand>\n  Manage official Agent Skills. Every subcommand is a thin client over the same\n  APIs the browser UI uses: the CLI never downloads, extracts, writes or deletes\n  anything itself, and never sends a filesystem path, artifact URL, file list or\n  checksum (the API rejects those outright).\n\n  commandmate skill list [--json] [--prerelease]\n  commandmate skill info <skill-id> [--version <v>] [--json]\n  commandmate skill plan <skill-id> --worktree <id> [--version <v>] [--json]\n  commandmate skill install <skill-id> --worktree <id> --version <exact> [--dry-run] [--yes] [--ack-risk <id>@<version>] [--json]\n  commandmate skill uninstall <skill-id> --worktree <id> [--dry-run] [--yes] [--json]\n  commandmate skill status <skill-id> --worktree <id> [--json]\n\n  Confirmation contract (writes = install / uninstall):\n    - A plan is always built and shown first. --dry-run stops there.\n    - Without a TTY, a write REQUIRES --yes. A missing --yes is refused, never\n      assumed: an environment that cannot prompt must not install silently.\n    - A high-risk Skill additionally requires --ack-risk <skill-id>@<version>\n      with the exact id and version. --yes alone never carries a high-risk\n      install, in a TTY or out of one.\n\n  Exit codes:\n    0   success\n    1   the server or the Catalog could not be reached (retryable)\n    2   invalid arguments, unknown Skill or unknown version\n    11  the worktree refused it (local change, conflict, lock, plan drift)\n    12  the write was never confirmed (no --yes, declined, or missing --ack-risk)\n    13  files changed but the operation needs reconciliation\n\n  --json prints the API response body verbatim on stdout; diagnostics, prompts\n  and errors always go to stderr, so a failed --json run leaves stdout empty.\n\n  'skill status' reports one Skill in one worktree, read from the install\n  receipt on disk. There is no per-worktree listing endpoint yet, so <skill-id>\n  is required.\n\n## Multi-Session (1 agent, multiple sessions)\n\n  A worktree can run several sessions of the same CLI tool concurrently. Each\n  session is an \"instance\" identified by an instance ID:\n    <agent>        - the agent's primary instance (e.g. \"claude\")\n    <agent>-<n>    - an additional instance, n >= 2 (e.g. \"claude-2\", \"claude-3\")\n\n  --instance is accepted by send / wait / respond / capture / auto-yes.\n  send --instance auto-starts the session if it is not already running.\n\n  --instance alone is the recommended way to name a target (Issue #1638). It is\n  the only flag all five commands share: --agent is rejected by 'wait'. A\n  rostered instance already carries its CLI tool (Issue #1629), and an instance\n  id that is itself a tool id resolves to that tool's primary instance even\n  without a roster entry, so '--instance codex' needs no --agent.\n\n  --agent remains accepted by send / respond / capture / auto-yes as the\n  supplement for ad-hoc instances the roster does not know -- notably\n  '--register', which cannot infer the tool from an id like codex-3. Passing an\n  --agent that contradicts the roster is an error (exit 2), not an override.\n\n  The roster (visible in the browser UI's Agent panel) is the list of known\n  instances with aliases and display order. Ad-hoc sessions started via\n  'send --instance' do NOT appear in the roster unless registered:\n    commandmate send <id> \"...\" --instance claude-2 --register\n  Without --register, the session still runs and responds to CLI commands,\n  but it will not show up in the UI sidebar/roster until added there or via\n  'commandmate instances <id> add'.\n\n  Per-instance auto-yes: --instance scopes --auto-yes/--duration/--stop-pattern\n  to that specific session, independent of other instances of the same agent.\n\n  commandmate instances <id>                        # discover valid --instance values\n  commandmate send <id> \"task\" --instance codex-2 --auto-yes\n  commandmate wait <id> --instance codex-2 --timeout 600\n  commandmate capture <id> --instance codex-2\n\n## All Exit Codes\n\n  0   SUCCESS          - Completed successfully\n  1   DEPENDENCY_ERROR - Server not running\n  2   CONFIG_ERROR     - Validation error (invalid agent, duration, etc.)\n  10  PROMPT_DETECTED  - Prompt detected during wait\n  20  VERIFY_FAILED    - A verification gate failed (verify, wait --verify)\n  21  NOT_STARTED      - Nothing to verify: no commits, no uncommitted changes\n  99  UNEXPECTED_ERROR - Unexpected error / resource not found / no verdict\n  124 TIMEOUT          - Wait or verification timeout exceeded\n\n  When one 'wait' covers several worktrees, the reported code is the highest\n  priority one observed: 10 > 20 > 21 > 124.\n\n## Troubleshooting\n\n  Server not running:\n    commandmate start --daemon\n    CM_PORT=3011 commandmate ls        # Different port\n\n  Worktree not found:\n    commandmate ls --quiet             # Check registered IDs\n    commandmate sync                   # Sync new worktrees (e.g. after git worktree add)\n\n  Authentication:\n    CM_AUTH_TOKEN=your-token commandmate ls\n";
 export declare const AGENT_OPERATIONS_SAMPLES = "# CLI Agent Operations - Workflow Samples\n\nCopy and adapt these patterns for your use case.\n\n## 1. Basic: send, wait, capture\n\n  WT=$(commandmate ls --branch feature/101 --quiet)\n  commandmate send \"$WT\" \"Implement Issue #101 with TDD\"\n  commandmate wait \"$WT\" --timeout 600\n  commandmate capture \"$WT\"\n\n## 2. With Auto-Yes (unattended execution)\n\n  WT=$(commandmate ls --branch feature/101 --quiet)\n  commandmate send \"$WT\" \"Implement Issue #101\" --auto-yes --duration 3h\n  commandmate wait \"$WT\" --timeout 1800\n  commandmate auto-yes \"$WT\" --disable    # Disable for safety\n  commandmate capture \"$WT\" --json\n\n## 3. Prompt Response Loop\n\n  WT=$(commandmate ls --branch feature/101 --quiet)\n  commandmate send \"$WT\" \"Refactor this module\"\n\n  while true; do\n    commandmate wait \"$WT\" --timeout 600 --on-prompt agent\n    EXIT_CODE=$?\n\n    if [ $EXIT_CODE -eq 0 ]; then\n      echo \"Done\"\n      break\n    elif [ $EXIT_CODE -eq 10 ]; then\n      commandmate respond \"$WT\" \"yes\"\n    elif [ $EXIT_CODE -eq 124 ]; then\n      echo \"Timeout\"\n      break\n    fi\n  done\n\n  commandmate capture \"$WT\"\n\n## 4. Parallel Worktrees\n\n  WT1=$(commandmate ls --branch feature/101 --quiet)\n  WT2=$(commandmate ls --branch feature/102 --quiet)\n\n  commandmate send \"$WT1\" \"Implement #101\" --auto-yes\n  commandmate send \"$WT2\" \"Implement #102\" --auto-yes --instance codex\n\n  # One --instance covers every worktree id in the call, so worktrees on\n  # different instances need one wait each. Both agents keep running while the\n  # first wait blocks, so this costs no wall clock over a combined wait.\n  # A bare 'wait \"$WT2\"' would watch WT2's DEFAULT agent, not the codex session:\n  # 'wait' has no --agent to correct that with.\n  commandmate wait \"$WT1\" --timeout 1800\n  commandmate wait \"$WT2\" --instance codex --timeout 1800\n\n  commandmate capture \"$WT1\" --json\n  commandmate capture \"$WT2\" --instance codex --json\n\n## 5. Check status before sending\n\n  # Find worktrees and check status\n  commandmate ls --json | python3 -c \"\n  import sys, json\n  for wt in json.load(sys.stdin):\n      if wt['name'].startswith('feature/'):\n          print(f\\\"{wt['id']}  {wt['name']}\\\")\n  \"\n\n## 6. Error handling pattern\n\n  WT=$(commandmate ls --branch feature/101 --quiet)\n\n  if [ -z \"$WT\" ]; then\n    echo \"Error: worktree not found\"\n    exit 1\n  fi\n\n  commandmate send \"$WT\" \"Fix the bug\" --auto-yes\n  commandmate wait \"$WT\" --timeout 600\n  EXIT_CODE=$?\n\n  case $EXIT_CODE in\n    0)   echo \"Success\"; commandmate capture \"$WT\" ;;\n    10)  echo \"Prompt detected\"; commandmate respond \"$WT\" \"yes\" ;;\n    124) echo \"Timeout\"; commandmate capture \"$WT\" --json ;;\n    *)   echo \"Error: exit $EXIT_CODE\" ;;\n  esac\n\n## 7. Multi-Session: run a second Codex session alongside the primary agent\n\n  WT=$(commandmate ls --branch feature/101 --quiet)\n\n  # Discover the roster before picking an --instance value\n  commandmate instances \"$WT\"\n\n  # Register a second Codex instance, then send/wait/capture scoped to it.\n  # Once it is in the roster, --instance alone carries the CLI tool.\n  commandmate instances \"$WT\" add --agent codex --alias \"Review\"\n  commandmate send \"$WT\" \"Review the diff\" --instance codex-2 --auto-yes\n  commandmate wait \"$WT\" --instance codex-2 --timeout 600\n  commandmate capture \"$WT\" --instance codex-2 --json\n\n  # Ad-hoc instance without pre-registering (still runs; register to show in UI).\n  # --agent is required here: codex-3 is not in the roster yet, so nothing else\n  # says which CLI tool to start.\n  commandmate send \"$WT\" \"Quick check\" --agent codex --instance codex-3 --register\n\n  # Clean up when done\n  commandmate instances \"$WT\" remove codex-2 --kill\n\n## 8. Verify the work instead of trusting \"the agent stopped\"\n\n  WT=$(commandmate ls --branch feature/101 --quiet)\n  commandmate send \"$WT\" \"Implement Issue #101 with TDD\" --auto-yes\n\n  # One call: wait for completion, then run every gate in .commandmate/verify.yaml\n  commandmate wait \"$WT\" --timeout 1800 --verify\n  case $? in\n    0)  echo \"Verified\" ;;\n    10) commandmate respond \"$WT\" \"yes\" ;;\n    20) echo \"A gate failed\"; commandmate verify \"$WT\" --json ;;\n    21) echo \"The agent produced nothing\" ;;\n  esac\n\n  # Cheap pre-check: is there any work at all, before paying for the full suite?\n  commandmate wait \"$WT\" --require-work || echo \"no commits and no changes\"\n\n  # Re-run a subset after a fix, without waiting on the agent\n  commandmate verify \"$WT\" --gates lint,unit\n";
 //# sourceMappingURL=agent-operations.d.ts.map

package/dist/cli/docs/agent-operations.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"agent-operations.d.ts","sourceRoot":"","sources":["../../../src/cli/docs/agent-operations.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAEH,eAAO,MAAM,sBAAsB,+icA8RlC,CAAC;AAEF,eAAO,MAAM,wBAAwB,klJAmIpC,CAAC"}
+{"version":3,"file":"agent-operations.d.ts","sourceRoot":"","sources":["../../../src/cli/docs/agent-operations.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAEH,eAAO,MAAM,sBAAsB,u7eAoTlC,CAAC;AAEF,eAAO,MAAM,wBAAwB,klJAmIpC,CAAC"}

package/dist/cli/docs/agent-operations.js

@@ -42,6 +42,16 @@ These commands enable coding agents (Claude Code, Codex, etc.) to orchestrate ot
     running  - Agent executing a task
     waiting  - Confirmation prompt active (Yes/No, etc.)
 
+### commandmate sync
+  Ask the server to re-scan repositories and sync worktrees to its database
+  (same endpoint as the GUI sync button). Run it after 'git worktree add' so the
+  new worktree appears in 'commandmate ls' without opening the GUI (Issue #1680).
+
+  commandmate sync                        # Prints the server's summary message
+  commandmate sync --json                 # Full API response (worktreeCount,
+                                          # repositoryCount, repositories,
+                                          # deletedCount, cleanupWarnings)
+
 ### commandmate send <worktree-id> "<message>"
   Send a message to an agent (async). Starts session automatically if not running.
 
@@ -52,9 +62,12 @@ These commands enable coding agents (Claude Code, Codex, etc.) to orchestrate ot
     --agent <id>           Ad-hoc CLI tool for an instance the roster does not know:
                            claude (default), codex, gemini, vibe-local, opencode, copilot, antigravity
     --register             Register the --instance session into the agent-instance roster
-    --auto-yes             Enable auto-yes before sending
+    --auto-yes             Enable auto-yes before sending (session-wide, no policy
+                           guard -- for unattended runs prefer --contract with an
+                           autoYes policy: mode / denyPatterns)
     --duration <d>         Auto-yes duration: 1h, 3h, 8h (default: 1h)
-    --stop-pattern <p>     Auto-yes stop condition (regex)
+    --stop-pattern <p>     Auto-yes stop condition (regex; matches terminal output,
+                           cannot block commands -- see auto-yes below)
 
   Finding worktree IDs:
     WT=$(commandmate ls --branch feature/101 --quiet)
@@ -92,6 +105,9 @@ These commands enable coding agents (Claude Code, Codex, etc.) to orchestrate ot
 
   Prompt JSON output (exit 10):
     {"worktreeId":"...","cliToolId":"claude","type":"yes_no","question":"...","options":["yes","no"],"status":"pending"}
+    The payload IS the prompt -- read it from stdout before falling back to
+    capture. For type "selection_list", options is empty by design and the
+    question field carries the reason.
 
   --verify turns "the agent stopped" into "the work passes the repository's own
   checks". Verification only runs when completion was detected: a prompt (10) or
@@ -181,6 +197,12 @@ These commands enable coding agents (Claude Code, Codex, etc.) to orchestrate ot
   commandmate auto-yes <id> --disable                   # Disable
   commandmate auto-yes <id> --enable --instance codex-2 # Scoped to one instance
 
+  --stop-pattern matches new terminal output, not the commands an agent runs.
+  It cannot block a command; a build log that merely prints the pattern
+  (e.g. "rm -rf" in an npm script) also triggers it and stops auto-yes.
+  To suppress auto-responses for risky prompts, use the task contract's
+  autoYes.denyPatterns instead (docs/design/task-contract.md).
+
 ### commandmate instances <worktree-id> [action] [args]
   Discover and manage a worktree's agent-instance roster (1 agent, multiple sessions).
 
@@ -290,7 +312,7 @@ These commands enable coding agents (Claude Code, Codex, etc.) to orchestrate ot
 
   Worktree not found:
     commandmate ls --quiet             # Check registered IDs
-    curl -s -X POST http://localhost:3000/api/repositories/sync  # Sync new worktrees
+    commandmate sync                   # Sync new worktrees (e.g. after git worktree add)
 
   Authentication:
     CM_AUTH_TOKEN=your-token commandmate ls

package/dist/cli/program.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"program.d.ts","sourceRoot":"","sources":["../../src/cli/program.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH,OAAO,EAAE,OAAO,EAAU,MAAM,WAAW,CAAC;AA8D5C;;;;;;;GAOG;AACH,wBAAgB,YAAY,IAAI,OAAO,CAkLtC"}
+{"version":3,"file":"program.d.ts","sourceRoot":"","sources":["../../src/cli/program.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH,OAAO,EAAE,OAAO,EAAU,MAAM,WAAW,CAAC;AAgE5C;;;;;;;GAOG;AACH,wBAAgB,YAAY,IAAI,OAAO,CAmLtC"}

package/dist/cli/program.js

@@ -17,6 +17,8 @@ const issue_1 = require("./commands/issue");
 const docs_1 = require("./commands/docs");
 // Issue #518: Agent orchestration commands
 const ls_1 = require("./commands/ls");
+// Issue #1680: Server-side worktree re-scan from the CLI
+const sync_1 = require("./commands/sync");
 const send_1 = require("./commands/send");
 const wait_1 = require("./commands/wait");
 const respond_1 = require("./commands/respond");
@@ -201,6 +203,7 @@ function buildProgram() {
     // Issue #518: Agent orchestration commands [DR1-08] [IA3-07]
     // These commands enable CLI-based agent control for worktree operations.
     program.addCommand((0, ls_1.createLsCommand)());
+    program.addCommand((0, sync_1.createSyncCommand)());
     program.addCommand((0, send_1.createSendCommand)());
     program.addCommand((0, wait_1.createWaitCommand)());
     program.addCommand((0, respond_1.createRespondCommand)());

package/dist/cli/types/api-responses.d.ts

@@ -36,6 +36,16 @@ export interface WorktreeItem {
     }>>;
     agentInstances?: AgentInstance[];
 }
+export interface RepositorySyncResponse {
+    success: boolean;
+    message: string;
+    worktreeCount: number;
+    repositoryCount: number;
+    repositories: string[];
+    deletedCount: number;
+    /** Sanitized, generic warnings only (SEC-MF-001); details stay in server logs. */
+    cleanupWarnings: string[];
+}
 export interface AgentInstance {
     id: string;
     cliTool: string;
@@ -60,6 +70,13 @@ export interface CurrentOutputResponse {
         enabled: boolean;
         expiresAt: number | null;
         stopReason?: string;
+        lastSuppression?: {
+            reason: string;
+            mode: string | null;
+            promptType: string;
+            pattern?: string;
+            at: number;
+        } | null;
     };
     thinking: boolean;
     thinkingMessage: string | null;
@@ -79,12 +96,44 @@ export interface PromptData {
     question: string;
     options?: unknown[];
     status?: string;
+    answer?: string;
+    answeredAt?: string;
+    /** Mirrors: src/types/models.ts PromptAnsweredBy (Issue #1685) */
+    answeredBy?: string;
+    /** Human-facing context block preceding the prompt (Issue #235). */
+    instructionText?: string;
+    /**
+     * What this prompt asks approval for — the surface `autoYes.denyPatterns` are
+     * judged against (Issue #1699). Narrower than `instructionText` on purpose:
+     * the latter is a pane window and carries finished turns.
+     */
+    approvalTarget?: string;
     [key: string]: unknown;
 }
+export interface PromptMessageResponse {
+    id: string;
+    worktreeId: string;
+    role: string;
+    content: string;
+    timestamp: string;
+    messageType: string;
+    promptData?: PromptData;
+    cliToolId?: string;
+    instanceId?: string;
+    archived: boolean;
+}
 export interface PromptResponseResult {
     success: boolean;
     answer: string;
     reason?: string;
+    /** Issue #1681: detail accompanying reason 'unresolvable_answer' */
+    message?: string;
+    /** Issue #1681: how a semantic yes/no or --default answer was resolved */
+    resolved?: {
+        via: 'semantic' | 'default';
+        optionNumber?: number;
+        optionLabel: string;
+    };
 }
 /** wait exit 10 CLI extended output type */
 export interface WaitPromptOutput {
@@ -94,6 +143,25 @@ export interface WaitPromptOutput {
     question: string;
     options: unknown[];
     status: string;
+    /**
+     * What the prompt asks approval for, when the detector could attribute a block
+     * to it (Issue #1699). Present so a caller that reads only this payload can
+     * see what a `deny-pattern` verdict below was actually judged against.
+     */
+    approvalTarget?: string;
+    /**
+     * Set when the contract's autoYes policy withheld an answer for this session
+     * (Issue #1699). Without it, a prompt an operator has to answer by hand is
+     * indistinguishable on stdout from one nobody configured Auto-Yes for — which
+     * is why the #1699 suppression loop went unnoticed for an hour.
+     */
+    autoYesSuppression?: {
+        reason: string;
+        mode: string | null;
+        promptType: string;
+        pattern?: string;
+        ageSeconds: number;
+    };
     [key: string]: unknown;
 }
 export interface DailySummaryGetResponse {
@@ -389,6 +457,139 @@ export interface SkillUninstallPlan {
 export interface SkillUninstallPlanResponse {
     plan: SkillUninstallPlan;
 }
+/** A typed reason an update is refused (Issue #1243). Paths are repository-relative. */
+export interface SkillUpdateBlocker {
+    code: string;
+    path: string | null;
+    /** Underlying per-path finding, when one exists (e.g. a local modification). */
+    detail: string | null;
+}
+/** Mirrors: src/lib/skills/update-plan.ts SkillUpdatePlanDto (subset) [Issue #1243]. */
+export interface SkillUpdatePlan {
+    /** Single-use token apply (#1244) will present unchanged. The CLI never inspects it. */
+    token: string;
+    expiresAt: string;
+    updatable: boolean;
+    blockers: SkillUpdateBlocker[];
+    nextActionKey: string;
+    requiresRiskAcknowledgement: boolean;
+    riskIncreased: boolean;
+    update: {
+        fromVersion: string;
+        toVersion: string;
+        latestVersion: string | null;
+        reasonCode: string;
+        prerelease: boolean;
+    };
+    target: {
+        worktreeId: string;
+        worktreeName: string;
+        repositoryName: string;
+        branch: string | null;
+        headState: string;
+        workingTreeDirty: boolean;
+        /** Repository-relative; the server never serves a machine-absolute path. */
+        installRoot: string;
+        /** Every recorded root the update rewrites, primary first (#1460). */
+        installRoots: string[];
+    };
+    skill: {
+        id: string;
+        name: string;
+        version: string;
+        effectiveRisk: string;
+        riskRationale: string;
+        declaredPermissions: string[];
+        scriptPaths: string[];
+        compatibility: {
+            commandmate: SkillCompatibilityView;
+        };
+    };
+    securityDiff: {
+        risk: {
+            from: {
+                effective: string;
+            };
+            to: {
+                effective: string;
+            };
+            increased: boolean;
+        };
+        permissions: {
+            added: string[];
+            removed: string[];
+        };
+        executables: {
+            added: string[];
+            removed: string[];
+        };
+        scripts: {
+            added: string[];
+            removed: string[];
+        };
+        changelogs: Array<{
+            version: string;
+            changelog: string;
+        }>;
+    };
+    files: Array<{
+        path: string;
+        change: string;
+    }>;
+    stats: {
+        added: number;
+        updated: number;
+        removed: number;
+        unchanged: number;
+        localModified: number;
+        localMissing: number;
+        localUnknown: number;
+        irregular: number;
+    };
+    warnings: string[];
+}
+/** Mirrors: src/app/api/worktrees/[id]/skills/[skillId]/update-plan/route.ts POST response. */
+export interface SkillUpdatePlanResponse {
+    plan: SkillUpdatePlan;
+}
+/**
+ * Mirrors: src/app/api/worktrees/[id]/skills/[skillId]/update/route.ts POST
+ * response [Issue #1244]. `update` is null when a replay finds no index row;
+ * `reload` and `rollback` are absent from the narrower replay body.
+ */
+export interface SkillUpdateResponse {
+    operation: SkillOperationResult;
+    update: {
+        skillId: string;
+        fromVersion?: string;
+        toVersion?: string;
+        /** Present on the replay body instead of fromVersion/toVersion. */
+        version?: string;
+        installRoot: string;
+        installRoots?: string[];
+        pendingRoots?: string[];
+    } | null;
+    reload?: {
+        skillId: string;
+        version: string;
+        installRoot: string;
+        agents: Array<{
+            agent: string;
+            support: string;
+            messageKey: string;
+        }>;
+    };
+    rollback?: {
+        available: boolean;
+        backup: {
+            backupId: string;
+            fromVersion: string;
+            fileCount: number;
+            verified: boolean;
+        };
+        messageKey: string;
+    };
+}
 /** Mirrors: src/app/api/worktrees/[id]/skills/[skillId]/uninstall/route.ts POST response. */
 export interface SkillUninstallResponse {
     operation: SkillOperationResult;