commandmate 0.46.1 → 0.47.0

package/dist/server/src/lib/verification/scope-gate.js

@@ -30,7 +30,7 @@
  * @module lib/verification/scope-gate
  */
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.SCOPE_SKIP_NOT_REQUIRED = exports.SCOPE_SKIP_NO_CONTRACT = exports.ScopeMatcher = exports.ORCHESTRATOR_FOLD_TRAILER_VALUE = exports.ORCHESTRATOR_FOLD_TRAILER_KEY = exports.ORCHESTRATOR_FILES = exports.CONTRACT_DIR_PREFIX = exports.SCOPE_EXEMPT_CONTRACT_PATH = exports.SCOPE_EXEMPT_ALWAYS_ALLOWED = exports.SCOPE_PATTERN_ARROW = exports.ALWAYS_ALLOWED_PREFIX = exports.SCOPE_ALLOW_GUIDANCE = exports.MAX_REPORTED_VIOLATIONS = void 0;
+exports.SCOPE_SKIP_NOT_REQUIRED = exports.SCOPE_SKIP_NO_CONTRACT = exports.ORCHESTRATOR_FOLD_TRAILER_VALUE = exports.ORCHESTRATOR_FOLD_TRAILER_KEY = exports.ORCHESTRATOR_FILES = exports.CONTRACT_DIR_PREFIX = exports.SCOPE_ALLOW_GUIDANCE = exports.ScopeMatcher = exports.SCOPE_EXEMPT_CONTRACT_PATH = exports.SCOPE_EXEMPT_ALWAYS_ALLOWED = exports.ALWAYS_ALLOWED_PREFIX = exports.SCOPE_PATTERN_ARROW = exports.MAX_REPORTED_VIOLATIONS = void 0;
 exports.isOrchestratorOnlyCommit = isOrchestratorOnlyCommit;
 exports.parseBranchCommits = parseBranchCommits;
 exports.isFoldCommit = isFoldCommit;
@@ -46,13 +46,16 @@ exports.evaluateScope = evaluateScope;
 const child_process_1 = require("child_process");
 const receipt_owned_paths_1 = require("../../lib/skills/receipt-owned-paths");
 const agent_state_paths_1 = require("../../lib/skills/agent-state-paths");
-/**
- * Violations listed in `log_tail` before the rest are summarised as a count.
- *
- * A worker that ran in the wrong directory can put thousands of paths out of
- * scope, and log_tail is stored per gate in SQLite.
- */
-exports.MAX_REPORTED_VIOLATIONS = 100;
+const scope_gate_format_1 = require("./scope-gate-format");
+const scope_gate_glob_1 = require("./scope-gate-glob");
+var scope_gate_format_2 = require("./scope-gate-format");
+Object.defineProperty(exports, "MAX_REPORTED_VIOLATIONS", { enumerable: true, get: function () { return scope_gate_format_2.MAX_REPORTED_VIOLATIONS; } });
+Object.defineProperty(exports, "SCOPE_PATTERN_ARROW", { enumerable: true, get: function () { return scope_gate_format_2.SCOPE_PATTERN_ARROW; } });
+var scope_gate_glob_2 = require("./scope-gate-glob");
+Object.defineProperty(exports, "ALWAYS_ALLOWED_PREFIX", { enumerable: true, get: function () { return scope_gate_glob_2.ALWAYS_ALLOWED_PREFIX; } });
+Object.defineProperty(exports, "SCOPE_EXEMPT_ALWAYS_ALLOWED", { enumerable: true, get: function () { return scope_gate_glob_2.SCOPE_EXEMPT_ALWAYS_ALLOWED; } });
+Object.defineProperty(exports, "SCOPE_EXEMPT_CONTRACT_PATH", { enumerable: true, get: function () { return scope_gate_glob_2.SCOPE_EXEMPT_CONTRACT_PATH; } });
+Object.defineProperty(exports, "ScopeMatcher", { enumerable: true, get: function () { return scope_gate_glob_2.ScopeMatcher; } });
 /**
  * Actionable coda appended to every scope failure report (#1683).
  *
@@ -69,42 +72,6 @@ exports.SCOPE_ALLOW_GUIDANCE = "To allow this diff, add the paths above to the c
     'is judged from the send-time snapshot, so editing the contract file alone ' +
     'changes nothing. A path matching deny: is a deliberate prohibition; revert ' +
     'it instead.';
-/**
- * Paths that are in scope no matter what the contract says.
- *
- * The contract file lives here, so a contract whose own `allow` list forgot to
- * mention `.commandmate/` would fail the moment it was committed — the scope
- * declaration would make its own storage a violation. The exemption covers the
- * `allow` requirement only; an explicit `deny` still applies, because a deny is
- * a deliberate prohibition and silently ignoring one is worse than the accident
- * this exemption prevents.
- */
-exports.ALWAYS_ALLOWED_PREFIX = '.commandmate/';
-/**
- * Separator between a reported path and the pattern that decided it (#1841).
- *
- * Mirrored by the CLI's scope-evidence parser (`src/cli/commands/verify.ts`,
- * SCOPE_PATTERN_ARROW): the gate's report is the only carrier for this evidence
- * — `verification_gate_results` has columns for a status, an exit code and a log
- * body, and nothing else — so the two constants have to agree. A round-trip
- * test feeds a real `evaluateScope` report through that parser rather than
- * trusting the two copies to be edited together.
- *
- * A path containing this exact three-character sequence would split wrongly on
- * the way back. Nothing prevents such a filename; it is accepted because the
- * alternative — encoding paths in a log a human reads first — costs every
- * reader something to protect against a file no repository has.
- */
-exports.SCOPE_PATTERN_ARROW = '  \u2190 ';
-/**
- * Stand-ins for the two ways a path is admitted without matching `allow`.
- *
- * Parenthesised so they cannot be mistaken for a pattern the contract declared:
- * a reader who greps the contract for `(exempt: .commandmate/)` should find
- * nothing, because nothing there put it in scope.
- */
-exports.SCOPE_EXEMPT_ALWAYS_ALLOWED = `(exempt: ${exports.ALWAYS_ALLOWED_PREFIX})`;
-exports.SCOPE_EXEMPT_CONTRACT_PATH = '(exempt: contract path)';
 /**
  * Execution contracts, dropped from both gates' change sets entirely (#1580).
  *
@@ -209,162 +176,6 @@ function isContractPath(path) {
     return path.startsWith(exports.CONTRACT_DIR_PREFIX);
 }
 // =============================================================================
-// Glob matching
-// =============================================================================
-/**
- * Translate a scope glob into an anchored regular expression.
- *
- * Deliberately a small, documented subset rather than a glob library. The
- * semantics are fixed in docs/design/task-contract.md §2.2:
- *
- * - `**` as a whole path segment crosses directory boundaries, including zero of
- *   them: `a/**` matches `a/b` and `a/b/c`, `**\/*.ts` matches `x.ts`.
- * - `*` and `?` never cross `/`. Leading dots are ordinary characters, so
- *   `.github/**` and `*.md` behave the way they read.
- * - `{a,b}` is alternation, nestable. Unbalanced braces are literal, as in a
- *   shell — `src/{a` is a path with a brace in it, not a syntax error.
- * - `[` and `]` are **literal**. This repository routes through
- *   `src/app/proxy/[...path]/`, and treating those as character classes would
- *   make the pattern that names them match nothing at all — a silent no-match is
- *   the failure mode this gate exists to avoid.
- * - A pattern that matches a directory also matches everything beneath it, so
- *   `src/lib`, `src/lib/` and `src/lib/**` all mean the same thing. Without this
- *   rule, `allow: ["src/lib/verification"]` — the way people write a directory —
- *   would put every file inside it out of scope.
- */
-function globToRegExp(rawPattern) {
-    // A trailing slash carries no information once the rule above applies.
-    const pattern = rawPattern.replace(/\/+$/, '');
-    const bracesBalanced = hasBalancedBraces(pattern);
-    let source = '';
-    let depth = 0;
-    let i = 0;
-    while (i < pattern.length) {
-        const char = pattern[i];
-        if (char === '*') {
-            let end = i;
-            while (pattern[end] === '*')
-                end += 1;
-            const isGlobstar = end - i > 1;
-            const atSegmentStart = i === 0 || pattern[i - 1] === '/';
-            if (isGlobstar && atSegmentStart && pattern[end] === '/') {
-                // Consume the following slash too: `a/**/b` has to match `a/b`.
-                source += '(?:[^/]*/)*';
-                i = end + 1;
-                continue;
-            }
-            if (isGlobstar && atSegmentStart && end === pattern.length) {
-                source += '.*';
-                i = end;
-                continue;
-            }
-            // `**` that is not a whole segment (`a**b`) cannot mean "cross
-            // directories" without also matching `a/x/b`, which the pattern does not
-            // say. Collapse it to a single-segment wildcard.
-            source += '[^/]*';
-            i = end;
-            continue;
-        }
-        if (char === '?') {
-            source += '[^/]';
-            i += 1;
-            continue;
-        }
-        if (bracesBalanced && char === '{') {
-            depth += 1;
-            source += '(?:';
-            i += 1;
-            continue;
-        }
-        if (bracesBalanced && char === '}' && depth > 0) {
-            depth -= 1;
-            source += ')';
-            i += 1;
-            continue;
-        }
-        if (bracesBalanced && char === ',' && depth > 0) {
-            source += '|';
-            i += 1;
-            continue;
-        }
-        source += char.replace(/[.*+?^${}()|[\]\\]/, '\\$&');
-        i += 1;
-    }
-    return new RegExp(`^${source}(?:/.*)?$`);
-}
-function hasBalancedBraces(pattern) {
-    let depth = 0;
-    for (const char of pattern) {
-        if (char === '{')
-            depth += 1;
-        else if (char === '}') {
-            depth -= 1;
-            if (depth < 0)
-                return false;
-        }
-    }
-    return depth === 0;
-}
-function compilePattern(pattern) {
-    return { pattern, regexp: globToRegExp(pattern) };
-}
-/**
- * A scope declaration compiled once per run.
- *
- * Compiling per pattern per file would rebuild the same regexes for every one of
- * potentially thousands of changed paths.
- */
-class ScopeMatcher {
-    contractPath;
-    allow;
-    deny;
-    /**
-     * @param contractPath the contract's own path, exempted alongside
-     *        {@link ALWAYS_ALLOWED_PREFIX} for contracts kept outside `.commandmate/`
-     */
-    constructor(scope, contractPath = null) {
-        this.contractPath = contractPath;
-        this.allow = scope.allow.map(compilePattern);
-        this.deny = scope.deny.map(compilePattern);
-    }
-    /**
-     * Which declared rule decided `path`, and which way (#1841).
-     *
-     * The **first** matching pattern is reported, in the contract's declaration
-     * order, on both sides. Reporting the last would name a rule the reader
-     * cannot use: `allow: ["src/**", "src/lib/**"]` admits `src/lib/a.ts` under
-     * the first entry, and deleting the second changes nothing about the verdict.
-     *
-     * `path` is a repository-root-relative POSIX path as git reports it.
-     */
-    classify(path) {
-        const denied = this.deny.find((entry) => entry.regexp.test(path));
-        if (denied)
-            return { admitted: false, pattern: denied.pattern };
-        if (path.startsWith(exports.ALWAYS_ALLOWED_PREFIX)) {
-            return { admitted: true, pattern: exports.SCOPE_EXEMPT_ALWAYS_ALLOWED };
-        }
-        if (path === this.contractPath) {
-            return { admitted: true, pattern: exports.SCOPE_EXEMPT_CONTRACT_PATH };
-        }
-        const allowed = this.allow.find((entry) => entry.regexp.test(path));
-        return allowed
-            ? { admitted: true, pattern: allowed.pattern }
-            : { admitted: false, pattern: null };
-    }
-    /**
-     * Whether `path` is a scope violation.
-     *
-     * Delegates to {@link classify} rather than repeating the rules: the verdict
-     * and the evidence for it must never be able to disagree, and two copies of
-     * "deny wins, then the exemptions, then allow" is exactly how they would.
-     */
-    isViolation(path) {
-        return !this.classify(path).admitted;
-    }
-}
-exports.ScopeMatcher = ScopeMatcher;
-// =============================================================================
 // Changed-path collection
 // =============================================================================
 /** Run a git plumbing command. No shell: every argument here is code-supplied. */
@@ -572,69 +383,6 @@ async function collectChangedPaths(worktreePath, baseRef) {
 // =============================================================================
 // Gate evaluation
 // =============================================================================
-function formatPatterns(patterns) {
-    return patterns.length > 0 ? patterns.join(', ') : '(none)';
-}
-/**
- * One reported path, optionally naming the rule that decided it (#1841).
- *
- * Admitted paths lead with `+` rather than `-` so the two sections cannot be
- * confused by a reader — or by a grep — that has only one line in front of it.
- */
-function formatDecidedPath(marker, path, pattern) {
-    if (pattern === null)
-        return `  ${marker} ${path}`;
-    return `  ${marker} ${path}${exports.SCOPE_PATTERN_ARROW}${pattern}`;
-}
-/**
- * The `admitted:` section: what this run was allowed to change, and by which
- * rule (#1841).
- *
- * With an `allow` of exact paths the pattern *is* the file and this adds
- * nothing, but #1546 made globs legal, and `src/**` leaves no record of what it
- * actually covered on the day it ran. The contract is the claim; this is the
- * evidence for it, and it has to survive in `log_tail` because the run's own
- * working tree will have moved on by the time anyone asks.
- *
- * Capped by the same rule as the violations, for the same reason (log_tail is
- * stored per gate in SQLite), and the truncation is stated rather than silent —
- * a list that stops at 100 with no marker reads as a complete one.
- */
-function formatAdmitted(admitted) {
-    if (admitted.length === 0)
-        return [];
-    const listed = admitted.slice(0, exports.MAX_REPORTED_VIOLATIONS);
-    const remainder = admitted.length - listed.length;
-    return [
-        'admitted:',
-        ...listed.map((entry) => formatDecidedPath('+', entry.path, entry.pattern)),
-        // Worded `(+N more)` rather than the violations' `... and N more`: the two
-        // sections are capped independently and a reader scanning a truncated
-        // report should not have to work out which count belongs to which list.
-        ...(remainder > 0 ? [`  ... (+${remainder} more)`] : []),
-    ];
-}
-/** The `excluded:` section naming agent-managed state files left out (#3126). */
-function formatAgentStateExcluded(excluded) {
-    if (excluded.length === 0)
-        return [];
-    const listed = excluded.slice(0, exports.MAX_REPORTED_VIOLATIONS);
-    const remainder = excluded.length - listed.length;
-    return [
-        'excluded (agent-managed state files, not counted as change):',
-        ...listed.map((path) => `  ~ ${path}`),
-        ...(remainder > 0 ? [`  ... (+${remainder} more)`] : []),
-    ];
-}
-/** The `excluded:` section naming orchestrator-only committed paths (#3588). */
-function formatOrchestratorExcluded(excluded) {
-    if (excluded.length === 0)
-        return [];
-    return [
-        'excluded (changed only by orchestrator commits, not counted as change):',
-        ...excluded.map((path) => `  ~ ${path}`),
-    ];
-}
 /**
  * Reasons the gate has nothing to judge, phrased for `log_tail`.
  *
@@ -688,7 +436,7 @@ async function evaluateScope(worktreePath, scope, requireScopeClean, baseRef, co
     const changed = await collectChangedPaths(worktreePath, baseRef);
     if ('error' in changed)
         return done('error', `scope: ${changed.error}`, null);
-    const matcher = new ScopeMatcher(scope, contractPath);
+    const matcher = new scope_gate_glob_1.ScopeMatcher(scope, contractPath);
     // Every changed path is classified, whether or not it will fit in the report:
     // the cap below is a display rule, and a violation withheld from the listing
     // still counts toward the verdict.
@@ -707,18 +455,18 @@ async function evaluateScope(worktreePath, scope, requireScopeClean, baseRef, co
     }
     const summary = [
         `scope: baseRef=${baseRef} changed=${changed.paths.length} violations=${violations.length}`,
-        `allow: ${formatPatterns(scope.allow)}`,
-        `deny: ${formatPatterns(scope.deny)}`,
-        ...formatAdmitted(admitted),
-        ...formatAgentStateExcluded(changed.agentStateExcluded),
-        ...formatOrchestratorExcluded(changed.orchestratorExcluded),
+        `allow: ${(0, scope_gate_format_1.formatPatterns)(scope.allow)}`,
+        `deny: ${(0, scope_gate_format_1.formatPatterns)(scope.deny)}`,
+        ...(0, scope_gate_format_1.formatAdmitted)(admitted),
+        ...(0, scope_gate_format_1.formatAgentStateExcluded)(changed.agentStateExcluded),
+        ...(0, scope_gate_format_1.formatOrchestratorExcluded)(changed.orchestratorExcluded),
     ].join('\n');
     if (violations.length === 0) {
         // An empty change set passes: work-evidence is the gate that judges "nothing
         // happened", and failing here too would report one problem as two.
         return done('passed', summary, 0);
     }
-    const listed = violations.slice(0, exports.MAX_REPORTED_VIOLATIONS);
+    const listed = violations.slice(0, scope_gate_format_1.MAX_REPORTED_VIOLATIONS);
     const remainder = violations.length - listed.length;
     const report = [
         summary,
@@ -727,7 +475,7 @@ async function evaluateScope(worktreePath, scope, requireScopeClean, baseRef, co
         // contract declared, not which of those entries this path tripped, and a
         // violation the reader must revert reads differently from one they could
         // fix by widening `allow`.
-        ...listed.map((path) => formatDecidedPath('-', path, rejectedBy.get(path) ?? null)),
+        ...listed.map((path) => (0, scope_gate_format_1.formatDecidedPath)('-', path, rejectedBy.get(path) ?? null)),
         ...(remainder > 0 ? [`  ... and ${remainder} more`] : []),
         exports.SCOPE_ALLOW_GUIDANCE,
     ].join('\n');

package/dist/server/src/lib/ws-server.js

@@ -502,6 +502,7 @@ function setupWebSocket(server, options) {
             ws,
             worktreeIds: new Set(),
             terminalSubscription: null,
+            terminalSubscriptionSeq: 0,
             isAlive: true,
         };
         clients.set(ws, clientInfo);
@@ -733,6 +734,9 @@ function handleDisconnect(ws) {
             }
         }
     });
+    // Issue #3733: a subscribe still in flight finds this moved and releases
+    // what it obtains instead of registering it on a socket that is gone.
+    clientInfo.terminalSubscriptionSeq += 1;
     if (clientInfo.terminalSubscription) {
         void clientInfo.terminalSubscription.unsubscribe();
         clientInfo.terminalSubscription = null;
@@ -779,14 +783,25 @@ async function handleTerminalSubscribe(ws, message) {
         });
         return;
     }
-    if (clientInfo.terminalSubscription) {
-        await clientInfo.terminalSubscription.unsubscribe();
+    // Issue #3733: from here on this request is the one the socket wants; every
+    // await below is followed by a look at whether it still is.
+    const seq = ++clientInfo.terminalSubscriptionSeq;
+    const isCurrent = () => clients.get(ws) === clientInfo && clientInfo.terminalSubscriptionSeq === seq;
+    const previous = clientInfo.terminalSubscription;
+    if (previous) {
+        // Detached before the await, so a request arriving meanwhile neither
+        // releases it a second time nor has its own registration cleared by ours.
         clientInfo.terminalSubscription = null;
+        await previous.unsubscribe();
     }
+    if (!isCurrent())
+        return;
     const sessionName = (0, session_name_1.resolveSessionName)(cliToolId, worktreeId);
     // Issue #2865: never stream a same-named session another CommandMate server
     // created (its `#{session_path}` is not this worktree's directory).
     const ownership = await (0, session_ownership_1.checkSessionOwnership)(sessionName, worktree.path);
+    if (!isCurrent())
+        return;
     if (ownership.verdict === 'foreign') {
         sendTerminalEvent(ws, {
             type: 'terminal_error',
@@ -806,6 +821,8 @@ async function handleTerminalSubscribe(ws, message) {
     const startedAt = Date.now();
     const subscription = await transport.subscribe(sessionName, {
         onOutput: (data) => {
+            if (!isCurrent())
+                return;
             if (!firstOutputObserved) {
                 firstOutputObserved = true;
                 (0, tmux_control_mode_metrics_1.observeTmuxControlFirstOutputLatency)(Date.now() - startedAt);
@@ -813,6 +830,8 @@ async function handleTerminalSubscribe(ws, message) {
             sendTerminalEvent(ws, { type: 'terminal_output', data });
         },
         onExit: ({ exitCode }) => {
+            if (!isCurrent())
+                return;
             sendTerminalEvent(ws, { type: 'terminal_exit', exitCode });
         },
         onError: (error) => {
@@ -825,7 +844,9 @@ async function handleTerminalSubscribe(ws, message) {
                         const snapshot = await transport.captureSnapshot(sessionName, {
                             startLine: TERMINAL_FALLBACK_CAPTURE_LINES,
                         });
-                        if (snapshot.length > 0) {
+                        // Issue #3733: the reads above awaited; a subscription released
+                        // or replaced meanwhile has nothing left to say to this socket.
+                        if (snapshot.length > 0 && isCurrent()) {
                             sendTerminalEvent(ws, {
                                 type: 'terminal_output',
                                 data: snapshot,
@@ -837,6 +858,8 @@ async function handleTerminalSubscribe(ws, message) {
                 catch {
                     // Best-effort snapshot fallback. The original control-mode error is still reported.
                 }
+                if (!isCurrent())
+                    return;
                 sendTerminalEvent(ws, {
                     type: 'terminal_error',
                     error: error.message,
@@ -845,6 +868,17 @@ async function handleTerminalSubscribe(ws, message) {
             })();
         },
     });
+    if (!isCurrent()) {
+        // Disconnected, unsubscribed or superseded while subscribing: nobody else
+        // holds this handle, so release it now or the registry keeps it forever.
+        try {
+            await subscription.unsubscribe();
+        }
+        catch {
+            // Best-effort cleanup of a subscription nobody wants.
+        }
+        return;
+    }
     clientInfo.terminalSubscription = {
         worktreeId,
         cliToolId,
@@ -934,16 +968,23 @@ async function runTerminalResize(ws, message) {
 }
 async function handleTerminalUnsubscribe(ws) {
     const clientInfo = clients.get(ws);
-    if (!clientInfo?.terminalSubscription) {
+    if (!clientInfo)
+        return;
+    // Issue #3733: also withdraws a subscribe still in flight, which would
+    // otherwise register after this and keep streaming.
+    clientInfo.terminalSubscriptionSeq += 1;
+    const subscription = clientInfo.terminalSubscription;
+    if (!subscription) {
         return;
     }
+    // Detached before the await so a subscribe arriving meanwhile is not cleared.
+    clientInfo.terminalSubscription = null;
     try {
-        await clientInfo.terminalSubscription.unsubscribe();
+        await subscription.unsubscribe();
     }
     catch {
         // Best-effort cleanup during terminal unsubscribe.
     }
-    clientInfo.terminalSubscription = null;
     sendTerminalEvent(ws, { type: 'terminal_status', connected: false });
 }
 // ---------------------------------------------------------------------------
@@ -1281,6 +1322,7 @@ exports.__internal = {
             ws,
             worktreeIds: new Set(),
             terminalSubscription: null,
+            terminalSubscriptionSeq: 0,
             isAlive,
         });
     },

package/docs/en/user-guide/cli-setup-guide.md

@@ -404,6 +404,8 @@ commandmate status [options]
 | `-i, --issue <number>` | Show status for a specific issue worktree (Issue #136) |
 | `-a, --all` | Show status for all servers (main + worktrees) |
 
+For a running server (or one with a stale PID file) it also prints a `Log:` line with the file `start --daemon` writes the server's output to.
+
 ### commandmate update
 
 Update CommandMate to the latest version (stop -> `npm install -g commandmate@latest` -> restart).
@@ -532,10 +534,19 @@ commandmate status
 commandmate stop --force
 commandmate start --daemon
 
-# Check logs (in config directory)
+# Check logs (in config directory; commandmate status also prints the path on its Log: line)
 tail -f ~/.commandmate/logs/server.log
+# a parallel server started with --issue 135 has its own file
+tail -f ~/.commandmate/logs/server-135.log
 ```
 
+`commandmate start --daemon` (and `commandmate update`, which restarts through it) appends the server's stdout and stderr to `logs/server.log` in the config directory (`logs/server-<N>.log` for an `--issue <N>` server). The file is owner-only (0600), and so are the rotated `server.log.1` and later generations (an existing 0640 file written by `scripts/start.sh` is tightened to 0600 when the CLI daemon opens or rotates it). Each start writes a separator line (`=== <timestamp> commandmate start --daemon ... ===`).
+
+- **Rotation**: at start, a log of 10MB or more is moved to `server.log.1`, shifting older generations to `.2` and `.3` (three generations kept, the same approach as `scripts/build-and-start.sh`). It is not rotated while the server runs, so a long-running server's log can grow past 10MB.
+- If the log file cannot be opened (the directory cannot be created, a symbolic link is in the way, etc.), a warning is printed and the server starts with its output discarded.
+- `CM_LOG_DIR` does not move this file (`CM_LOG_DIR` is a separate setting, used by the server for conversation logs and by the CLI for its security log).
+- A foreground start (`commandmate start`) prints to the terminal only and does not write this file.
+
 ### Dependency Errors
 
 ```bash

package/docs/en/user-guide/webapp-guide.md

@@ -268,6 +268,7 @@ See [Agent event hooks](./agent-event-hooks.md) for the per-route technical deta
 - Important changes (file deletions, etc.) are also auto-approved, so use with caution
 - You can disable it by turning off the toggle
 - Auto Yes automatically turns OFF after the selected duration
+- **When the server restarts (`/rebuild`, `commandmate stop`, etc.), an active Auto Yes is turned OFF and does not come back.** The affected instance shows **"Released by restart"** (「再起動で解除」 in the Japanese UI). The label stays until the original grant's deadline, and disappears when you turn the toggle on again or turn it off manually (it is not shown after SIGKILL or a crash). A manual OFF or an expiry does not show it
 - **Security best practices**:
   - Select the **minimum time** needed for your work (1 hour recommended when in doubt)
   - Limit `CM_ROOT_DIR` to the target worktree directory
@@ -499,6 +500,7 @@ that kind of screen directly under it. You answer it without leaving chat.
 | A selection list is open | Arrow keys plus Enter / Esc. Depending on the screen, number keys or "This session only" / "Set as default" are added (see "The buttons a selection list gets" below) |
 | A screen nothing could classify | Arrows and Esc (Navigate) plus the digits 1-9, y / n and Enter |
 | Waiting, with options nobody could read | The digits 1-9, y / n and Enter |
+| Trust confirmation (agy) | The banner reads "Terminal action needed (trust confirmation). The agent will not continue until you answer whether to trust this folder, and Auto-Yes does not answer this screen. Pick with the arrows and press Enter, or answer it in the terminal." You can send the arrows and Enter from here |
 
 **Press the number or y/n while reading the card.** Enter confirms whatever the CLI has
 currently highlighted, so on a numbered dialog an Enter meant as "no" can land as an

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "commandmate",
-  "version": "0.46.1",
+  "version": "0.47.0",
   "description": "No long blocks of time? Run an AI team from your phone. Git worktree sessions, task contracts and verification gates for Claude Code, Codex, Gemini CLI, Copilot, OpenCode, Antigravity and Command Code.",
   "keywords": [
     "ai-agents",

package/release-notes/0.47.0.json

@@ -0,0 +1,118 @@
+{
+  "version": "0.47.0",
+  "date": "2026-10-21",
+  "highlight": {
+    "ja": "Auto-Yes が答えずに止まった確認を、CLI から画面を確かめたうえで直接答えられるようになりました。あわせて、Auto-Yes が答えてはいけない画面に答えたり、答えずに止まったりする問題を多数直しました。",
+    "en": "You can now answer a prompt that Auto-Yes left waiting directly from the CLI, after checking the screen. Many issues where Auto-Yes answered the wrong screen or stopped without answering are also fixed."
+  },
+  "added": [
+    {
+      "ja": "止まっている画面を CLI から 1 回観測して、種類・質問・選択肢を確かめられる commandmate prompt を追加しました。",
+      "en": "Added commandmate prompt, which observes a waiting screen once so you can check its kind, question and choices from the CLI."
+    },
+    {
+      "ja": "観測した画面にだけ答える厳格な respond を追加しました。画面が変わっていれば何も送りません。",
+      "en": "Added a strict respond mode that answers only the screen you observed, and sends nothing if the screen has changed."
+    },
+    {
+      "ja": "直前の送信が「未送信・送信済み・不確定」のどれかを、prompt の出力と送信の失敗メッセージで確かめられるようになりました。",
+      "en": "The prompt output and send error messages now tell you whether the last message was not sent, sent, or indeterminate."
+    },
+    {
+      "ja": "Codex の /config をスラッシュコマンドの一覧に追加しました。",
+      "en": "Added Codex's /config to the slash command list."
+    }
+  ],
+  "improved": [
+    {
+      "ja": "サーバーの再起動で外れた Auto-Yes を「再起動で解除」と表示するようになりました。",
+      "en": "Auto-Yes that was turned off by a server restart is now shown as Released by restart."
+    },
+    {
+      "ja": "契約で Auto-Yes が止められているとき、有効化の時点と一覧・画面でそのことが分かるようになりました。",
+      "en": "When a contract stops Auto-Yes, this is now shown when you enable it and in the lists and screens."
+    },
+    {
+      "ja": "Antigravity の信頼の確認で止まっているとき、画面に「端末で操作が必要」と表示するようになりました。",
+      "en": "When Antigravity is waiting on its folder trust prompt, the screen now says the terminal needs your input."
+    },
+    {
+      "ja": "start --daemon で起動したサーバーの出力を logs/server.log に残すようになりました。",
+      "en": "A server started with start --daemon now keeps its output in logs/server.log."
+    }
+  ],
+  "fixed": [
+    {
+      "ja": "Antigravity のログイン方法の画面や、表示が切れた許可の画面に、Auto-Yes が番号で答えうる問題を直しました。",
+      "en": "Fixed Auto-Yes possibly answering Antigravity's login method screen, or a cut-off permission screen, with a number."
+    },
+    {
+      "ja": "Antigravity の確認に Auto-Yes が答えないまま長時間止まることがある問題を直しました。",
+      "en": "Fixed Auto-Yes sometimes leaving an Antigravity prompt unanswered for a long time."
+    },
+    {
+      "ja": "Antigravity で答えた確認が画面に残り続けたとき、Auto-Yes が理由を残さずに黙る問題を直しました。",
+      "en": "Fixed Auto-Yes going silent without a reason when an answered Antigravity prompt stayed on screen."
+    },
+    {
+      "ja": "厳格な respond で、Antigravity の許可の確認のカーソル以外の選択肢を選べるようになりました。",
+      "en": "Strict respond can now choose options other than the highlighted one on Antigravity's permission prompt."
+    },
+    {
+      "ja": "厳格な respond で信頼の確認に No, exit と答えたとき、終了を正しく読み取るようになりました。",
+      "en": "Strict respond now correctly reports the session ending after answering No, exit on the trust prompt."
+    },
+    {
+      "ja": "Antigravity のターミナル画面が黒く見える問題を直しました。",
+      "en": "Fixed the Antigravity terminal view appearing blank."
+    },
+    {
+      "ja": "Submit と Cancel の確認画面に、Auto-Yes が答えないようにしました。",
+      "en": "Auto-Yes no longer answers Submit and Cancel confirmation pages."
+    },
+    {
+      "ja": "Gemini と Antigravity の起動時の信頼の確認を、安全な選択肢のときだけ通し、Auto-Yes と二重に答えないようにしました。",
+      "en": "Gemini and Antigravity startup trust prompts are now confirmed only on the safe option, and never answered twice with Auto-Yes."
+    },
+    {
+      "ja": "Copilot の信頼の確認に、Auto-Yes の入力がメッセージとして送られることがある問題を直しました。",
+      "en": "Fixed Auto-Yes input sometimes being sent as a message on Copilot's folder trust prompt."
+    },
+    {
+      "ja": "Antigravity の起動の後に出た信頼の確認が処理されず、通知も出ない問題を直しました。",
+      "en": "Fixed an Antigravity trust prompt shown after startup going unhandled without a notification."
+    },
+    {
+      "ja": "Auto-Yes が答える前に、答えていないという通知が誤って出ることがある問題を直しました。",
+      "en": "Fixed a not-answered notification sometimes being shown before Auto-Yes had a chance to answer."
+    },
+    {
+      "ja": "契約が止めた確認について、hooks の設定が原因であるかのような案内が出る問題を直しました。",
+      "en": "Fixed a hint that blamed the hooks setup for a prompt that a contract had stopped."
+    },
+    {
+      "ja": "再起動で解除された Auto-Yes の表示が、消えるべきときに消えないなどの問題を直しました。",
+      "en": "Fixed the released-by-restart Auto-Yes label not clearing when it should, among other display issues."
+    },
+    {
+      "ja": "Command Code の plan review で送信が断られたとき、未送信と表示するようにしました。",
+      "en": "A message refused by Command Code's plan review is now shown as not sent."
+    },
+    {
+      "ja": "送信の直後に、送信前の古い画面が表示されることがある問題を直しました。",
+      "en": "Fixed the screen sometimes showing the old content from before a message was sent."
+    },
+    {
+      "ja": "取り消した返答の受け渡しが、依頼元に届いてしまうことがある問題を直しました。",
+      "en": "Fixed a cancelled reply relay sometimes still being delivered."
+    },
+    {
+      "ja": "削除した worktree やサーバー停止の後に、スケジュールが作り直されることがある問題を直しました。",
+      "en": "Fixed schedules sometimes being recreated after a worktree was removed or the server was stopped."
+    },
+    {
+      "ja": "ターミナルの購読が残り続け、上限に達することがある問題を直しました。",
+      "en": "Fixed terminal subscriptions sometimes piling up until the limit was reached."
+    }
+  ]
+}