@adhdev/daemon-core 0.9.82-rc.49 → 0.9.82-rc.490

package/dist/cli-adapters/provider-cli-shared.d.ts

@@ -1,6 +1,7 @@
 import type { ProviderResumeCapability } from '../providers/contracts.js';
 import type { ChatMessageKind } from '../providers/chat-message-normalization.js';
 import type { ChatBubbleState } from '../types.js';
+import type { InteractivePrompt } from '../providers/types/interactive-prompt.js';
 import { sanitizeSpawnEnv } from './spawn-env.js';
 export interface CliChatMessage {
     role: string;
@@ -26,8 +27,63 @@ export interface CliSessionStatus {
         message: string;
         buttons: string[];
     } | null;
+    /**
+     * Monotonic counter identifying which approval *entry* the current modal
+     * belongs to. Bumped by the FSM on every fresh waiting_approval entry.
+     * Consumers (e.g. auto-approval) use it to distinguish a genuinely new
+     * approval from the same approval re-observed across TUI paint flaps —
+     * two distinct approvals can carry identical message/button text, so the
+     * seq is the only reliable discriminator.
+     */
+    approvalEntrySeq?: number;
+    /**
+     * The approval entry seq that the engine's last resolveModal() handled. When
+     * `lastResolvedEntrySeq >= approvalEntrySeq` (and approvalEntrySeq > 0) it is positive
+     * evidence that the current/latest approval entry was resolved through ADHDev (auto-approve
+     * fire, dashboard / mesh_approve, or dev-cli-debug — all route through resolveModal). The
+     * completion finalization gate uses this to avoid confirming a waiting_approval→idle
+     * transition for which no resolution actually occurred (a false idle: the spec's text-based
+     * approval→idle rule tripped while the modal is still on screen).
+     */
+    lastResolvedEntrySeq?: number;
+    activeInteractivePrompt?: InteractivePrompt | null;
+    pendingOutboundCount?: number;
+    pendingOutboundMessages?: Array<{
+        id: string;
+        role: 'user';
+        content: string;
+        queuedAt: number;
+        source: string;
+    }>;
     errorMessage?: string;
     errorReason?: string;
+    providerSessionId?: string;
+    /**
+     * Spec/FSM adapters only (SpecCliAdapter): true once the driver has observed
+     * its first non-initial idle state — the prompt is genuinely drawn. The
+     * legacy ProviderCliAdapter never sets it (undefined). CliProviderInstance
+     * uses it to re-arm the queue-claim agent:ready on the first genuine ready,
+     * independent of the boot-time starting→idle one-shot (which is consumed too
+     * early for specs whose initial state already reports status 'idle', e.g.
+     * antigravity-cli — without the re-arm the worker never claims its queued
+     * task and the coordinator relaunch-loops).
+     */
+    fsmReadySeen?: boolean;
+    /**
+     * Timestamp (ms) of the most recent raw PTY output chunk. Advances on every
+     * byte the process emits, including tool/build output that produces no
+     * parsed assistant text. Liveness watchdogs use this to distinguish a real
+     * stall (no output at all) from an active turn whose assistant buffer is
+     * momentarily static while a tool runs.
+     */
+    lastOutputAt?: number;
+    /**
+     * Timestamp (ms) of the most recent *visible* terminal screen change.
+     * Stricter than lastOutputAt — only advances when the rendered screen
+     * content actually differs, so repeated keepalive bytes do not register as
+     * progress. Preferred liveness signal for the no-progress watchdog.
+     */
+    lastScreenChangeAt?: number;
     bufferState?: {
         responseBuffer?: {
             truncated: boolean;
@@ -59,6 +115,9 @@ export interface ParsedSession {
         buttons: string[];
     } | null;
     parsedStatus: string | null;
+    errorMessage?: string;
+    errorReason?: string;
+    providerSessionId?: string;
     transcriptAuthority?: 'provider' | 'daemon';
     coverage?: 'full' | 'tail' | 'current-turn';
 }
@@ -112,6 +171,10 @@ export interface CliScriptInput {
     rawBuffer: string;
     recentBuffer: string;
     screenText: string;
+    workspace?: string;
+    workingDir?: string;
+    providerSessionId?: string;
+    historySessionId?: string;
     screen: CliScreenSnapshot;
     bufferScreen: CliScreenSnapshot;
     recentScreen: CliScreenSnapshot;
@@ -121,6 +184,7 @@ export interface CliScriptInput {
     promptText?: string;
     settings?: Record<string, any>;
     args?: Record<string, any>;
+    spawnAt?: number;
 }
 export interface CliStatusInput {
     tail: string;
@@ -158,16 +222,26 @@ export interface CliProviderModule {
     binary: string;
     approvalKeys?: Record<number, string>;
     sendDelayMs?: number;
+    /** Wall-clock budget (ms) for a single provider script invocation. Default 50. Range 1..5000.
+     *  Exceeding the budget records `timedOut: true` on the invocation trace and emits a
+     *  throttled WARN — it does NOT abort the script (Node CJS can't interrupt sync code). */
+    scriptCallBudgetMs?: number;
     sendKey?: string;
     submitStrategy?: 'wait_for_echo' | 'immediate';
     /** Require the typed prompt to be visible on the PTY screen before sending Enter. */
     requirePromptEchoBeforeSubmit?: boolean;
     /** Allow sending another prompt while the CLI is still generating so users can intervene mid-turn. */
     allowInputDuringGeneration?: boolean;
+    /** When true, only transition to idle after the parsed transcript includes a final standard assistant message. */
+    requiresFinalAssistantBeforeIdle?: boolean;
+    /** When true, allow providers to augment stale snapshot data before parse. Reserved for future use. */
+    augmentStaleSnapshot?: boolean;
     /** When provider-owned, daemon treats provider parser output as canonical transcript authority. */
     transcriptAuthority?: 'provider' | 'daemon';
     /** Full context lets provider-owned parsers canonicalize retained history instead of daemon prefix stitching. */
     transcriptContext?: 'full' | 'tail';
+    /** v1 declarative tui block — used by CliScriptRunner to synthesize SDK helpers (declarativeDetectStatus, declarativeParseApproval). */
+    tui?: Record<string, unknown>;
     scripts?: CliScripts;
     spawn: {
         command: string;

package/dist/cli-adapters/pty-write-chunking.d.ts

@@ -0,0 +1,34 @@
+export declare const WIN32_PTY_WRITE_CHUNK_CHARS = 1024;
+export declare const WIN32_PTY_WRITE_CHUNK_GAP_MS = 8;
+/** Split `text` into chunks of at most `size` UTF-16 units without ever cutting
+ *  between a high and low surrogate (which would corrupt an astral char — emoji,
+ *  etc. — on the UTF-8 PTY write). */
+export declare function chunkPreservingSurrogates(text: string, size: number): string[];
+/** True when a body of `length` UTF-16 units should be paced into multiple
+ *  chunks on win32 rather than written in a single PTY write. */
+export declare function shouldChunkWin32Write(length: number): boolean;
+/**
+ * Drive a paced, surrogate-safe chunked write of `text` over a `write(chunk)`
+ * sink, calling `onChunkWritten` after each chunk (e.g. to advance an input-
+ * activity timestamp) and `onDone` once the final chunk is out. The optional
+ * `setTimer` lets the caller own the timer handle (so it can be cleared on
+ * shutdown) and supply a custom scheduler in tests; it defaults to setTimeout.
+ *
+ * Bodies at or below the chunk threshold are written in a SINGLE write — the
+ * common case — so this is a no-op pacing wrapper for normal-sized prompts.
+ *
+ * Returns the chunks that will be written (useful for assertions/logging).
+ */
+export interface PacedWin32WriteOptions {
+    write: (chunk: string) => void;
+    onChunkWritten?: () => void;
+    onDone?: () => void;
+    /** Schedule the next chunk; must return a handle the caller can clear.
+     *  Defaults to setTimeout. */
+    setTimer?: (fn: () => void, delayMs: number) => ReturnType<typeof setTimeout>;
+    /** Store the pending timer handle so the caller can clear it on shutdown. */
+    onTimer?: (handle: ReturnType<typeof setTimeout> | null) => void;
+    chunkChars?: number;
+    gapMs?: number;
+}
+export declare function writeWin32Paced(text: string, opts: PacedWin32WriteOptions): string[];

package/dist/cli-adapters/raw-terminal-io.d.ts

@@ -0,0 +1,37 @@
+import { type SessionHostEndpoint, type SessionHostRequest, type SessionHostResponse, type SessionTerminalSnapshot, type SessionTerminalState } from '@adhdev/session-host-core';
+type LowercaseLetter = 'a' | 'b' | 'c' | 'd' | 'e' | 'f' | 'g' | 'h' | 'i' | 'j' | 'k' | 'l' | 'm' | 'n' | 'o' | 'p' | 'q' | 'r' | 's' | 't' | 'u' | 'v' | 'w' | 'x' | 'y' | 'z';
+type FunctionKey = 'f1' | 'f2' | 'f3' | 'f4' | 'f5' | 'f6' | 'f7' | 'f8' | 'f9' | 'f10' | 'f11' | 'f12';
+type BaseNamedKey = 'enter' | 'escape' | 'tab' | 'backspace' | 'up' | 'down' | 'left' | 'right' | 'home' | 'end' | 'pageup' | 'pagedown' | 'space' | FunctionKey;
+type ShiftNamedKey = BaseNamedKey | LowercaseLetter | `ctrl+${LowercaseLetter}` | `alt+${LowercaseLetter}`;
+export type NamedKey = BaseNamedKey | `ctrl+${LowercaseLetter}` | `alt+${LowercaseLetter}` | `shift+${ShiftNamedKey}`;
+export declare function namedKeyToAnsi(key: NamedKey | string): string;
+export declare function namedKeysToAnsi(keys: readonly (NamedKey | string)[]): string;
+export interface RawTerminalSessionHostClient {
+    connect(): Promise<void>;
+    request<T = unknown>(request: SessionHostRequest): Promise<SessionHostResponse<T>>;
+    close(): Promise<void>;
+}
+export interface RawTerminalAttachmentOptions {
+    endpoint?: SessionHostEndpoint;
+    sessionId: string;
+    mode?: 'read' | 'write';
+    clientId?: string;
+    client?: RawTerminalSessionHostClient;
+}
+export declare class RawTerminalAttachment {
+    readonly sessionId: string;
+    private readonly clientId;
+    private readonly mode;
+    private readonly client;
+    private closed;
+    private constructor();
+    static attach(options: RawTerminalAttachmentOptions): Promise<RawTerminalAttachment>;
+    readSnapshot(): Promise<SessionTerminalSnapshot>;
+    readScreenText(): Promise<string>;
+    readState(): Promise<SessionTerminalState>;
+    writeInput(text: string): Promise<void>;
+    writeKeys(keys: readonly (NamedKey | string)[]): Promise<void>;
+    close(): Promise<void>;
+}
+export declare function withRawTerminalAttachment<T>(options: RawTerminalAttachmentOptions, operation: (attachment: RawTerminalAttachment) => Promise<T>): Promise<T>;
+export {};

package/dist/cli-adapters/resolve-executable.d.ts

@@ -0,0 +1,69 @@
+/**
+ * Pick the best launch target from `where`'s match list on win32.
+ *
+ * `where npm` on a typical install returns BOTH the extensionless Unix wrapper
+ * (e.g. `C:\Program Files\nodejs\npm`, a bash shell script) AND the `npm.cmd`
+ * shim. The extensionless wrapper is NOT a win32 executable — handing it to a
+ * spawn boundary ENOENTs (errno -4058). So:
+ *   1. Prefer a directly-launchable `.exe`/`.com`.
+ *   2. Otherwise take a `.cmd`/`.bat` shim (absolute → works for ConPTY, and for
+ *      execFile once wrapped via buildWin32ExecFileSpawn).
+ *   3. NEVER fall back to an extensionless match — return null so the caller can
+ *      try other resolution strategies (global-bin scan) rather than emit a
+ *      path that cannot be exec'd.
+ */
+export declare function selectWin32ExecutableMatch(matches: string[]): string | null;
+/**
+ * Resolve a launch command to an absolute executable path on Windows.
+ *
+ * node-pty's ConPTY backend resolves a bare/relative command against the
+ * *calling process's* `Path` env var and — critically — does NOT apply PATHEXT.
+ * So a provider command like `claude` never matches `claude.exe` and the native
+ * layer throws `File not found:` (empty), which crashes the daemon. We resolve
+ * it to an absolute `.exe` here (in the daemon process, which has the full PATH)
+ * before the command ever reaches node-pty.
+ *
+ * No-op on non-Windows and when the command is already an existing absolute path
+ * or cannot be resolved (caller keeps the original behaviour).
+ */
+export declare function resolveWin32Executable(command: string): string;
+/**
+ * Quote one argument for a cmd.exe command line using the standard
+ * CommandLineToArgvW rules (the same algorithm Node uses internally): wrap in
+ * double quotes only when needed, double up the backslashes that precede a
+ * quote, and escape embedded quotes. We do per-argument quoting ourselves
+ * (rather than `{ shell: true }`) because Node's shell mode joins argv with bare
+ * spaces and applies NO quoting — any argument containing a space (a path, a
+ * test name) would split. Inputs here are repo-mesh validation/bootstrap command
+ * tokens (trusted config, not network data), so argv-quoting for spaces/quotes
+ * is sufficient; we deliberately do not attempt full cmd.exe metacharacter
+ * (& | < > ^ %) escaping.
+ */
+export declare function quoteWin32CmdArg(arg: string): string;
+export interface Win32ExecFileSpawn {
+    file: string;
+    args: string[];
+    /** Set when the args are pre-quoted for cmd.exe and must not be re-quoted. */
+    windowsVerbatimArguments?: boolean;
+}
+/**
+ * Build child_process.execFile/spawn parameters for an already-resolved command.
+ *
+ * On win32 a `.cmd`/`.bat` shim (what `npm`/`npx`/`tsc`/`vitest` resolve to)
+ * cannot be launched by execFile directly — modern Node refuses it (CVE-2024-27980
+ * mitigation) and CreateProcess cannot exec a batch file. So wrap it in
+ * `cmd.exe /d /s /c "<quoted command line>"` with `windowsVerbatimArguments` so
+ * our own per-argument quoting is preserved. `.exe`/`.com` (and every non-win32
+ * platform, and any already-cmd.exe target) pass through unchanged — this is a
+ * strict no-op off win32, guarding against regressions on linux/macOS.
+ */
+export declare function buildWin32ExecFileSpawn(resolvedCommand: string, args: string[]): Win32ExecFileSpawn;
+/**
+ * Convenience: resolve a bare command to an absolute win32 path AND build the
+ * execFile spawn parameters (cmd.exe-wrapping a .cmd/.bat shim). Returns the
+ * resolved command alongside the spawn spec so callers can still surface the
+ * resolved path in diagnostics.
+ */
+export declare function resolveWin32ExecFileSpawn(command: string, args: string[]): Win32ExecFileSpawn & {
+    resolvedCommand: string;
+};

package/dist/cli-adapters/terminal-backends/ghostty-vt-backend.d.ts

@@ -1,13 +1,16 @@
-import type { TerminalViewportBackend, TerminalViewportBackendOptions, TerminalViewportBackendPreference } from './types.js';
-export declare function resolveTerminalBackendPreference(): TerminalViewportBackendPreference;
-export declare function isGhosttyVtBackendAvailable(): boolean;
+import type { TerminalViewportBackend, TerminalViewportBackendOptions } from './types.js';
 export declare class GhosttyVtTerminalBackend implements TerminalViewportBackend {
     readonly kind: "ghostty-vt";
     private terminal;
+    private rows;
+    private disposed;
     constructor(options: TerminalViewportBackendOptions);
     resize(rows: number, cols: number): void;
     write(data: string): void;
+    private formatLines;
+    private static trimBlankEnds;
     getText(): string;
+    getTextWithScrollback(): string;
     getCursorPosition(): {
         col: number;
         row: number;

package/dist/cli-adapters/terminal-backends/types.d.ts

@@ -1,5 +1,4 @@
-export type TerminalViewportBackendKind = 'xterm' | 'ghostty-vt';
-export type TerminalViewportBackendPreference = TerminalViewportBackendKind | 'auto';
+export type TerminalViewportBackendKind = 'ghostty-vt';
 export type TerminalViewportBackendOptions = {
     rows: number;
     cols: number;
@@ -10,6 +9,15 @@ export interface TerminalViewportBackend {
     resize(rows: number, cols: number): void;
     write(data: string): void;
     getText(): string;
+    /**
+     * Like getText() but includes scrollback history (the lines that have
+     * scrolled above the visible viewport). Used by content-pattern matching
+     * (e.g. approval/modal button extraction) that must stay correct when a
+     * tall prompt — a big diff or long explanation — pushes part of the
+     * prompt box above the viewport. NOT for cursor-relative / stable_ms
+     * conditions, whose row indices are viewport-relative.
+     */
+    getTextWithScrollback(): string;
     getCursorPosition(): {
         col: number;
         row: number;

package/dist/cli-adapters/terminal-screen.d.ts

@@ -1,29 +1,22 @@
 /**
- * PTY screen snapshot abstraction.
- *
- * Terminal viewport backend selection.
- *
- * Runtime preference is backend-agnostic:
- * - prefer ghostty-vt when available (or when explicitly requested)
- * - fall back to xterm when ghostty-vt is unavailable
+ * PTY screen snapshot abstraction — ghostty-vt backend.
  */
-import type { TerminalViewportBackendKind, TerminalViewportBackendPreference } from './terminal-backends/types.js';
+import type { TerminalViewportBackendKind } from './terminal-backends/types.js';
 export declare function getTerminalBackendRuntimeStatus(): {
     backend: TerminalViewportBackendKind;
-    preference: TerminalViewportBackendPreference;
-    ghosttyAvailable: boolean;
 };
 export declare class TerminalScreen {
     readonly backendKind: TerminalViewportBackendKind;
     private rows;
     private cols;
-    private readonly preference;
     private terminal;
     constructor(rows?: number, cols?: number);
     reset(rows?: number, cols?: number): void;
     resize(rows: number, cols: number): void;
     write(data: string): void;
     getText(): string;
+    /** Full buffer including scrollback history (see backend doc). */
+    getTextWithScrollback(): string;
     getCursorPosition(): {
         col: number;
         row: number;

package/dist/commands/chat-commands-debug-bundle.d.ts

@@ -0,0 +1,14 @@
+/**
+ * Chat Commands — get_chat_debug_bundle: sanitize, summarize and store a
+ * diagnostic snapshot of the current read_chat / provider / session state.
+ */
+import type { CommandResult, CommandHelpers } from './handler.js';
+interface DebugSanitizeOptions {
+    maxDepth?: number;
+    maxArrayLength?: number;
+    maxObjectKeys?: number;
+    maxStringLength?: number;
+}
+export declare function sanitizeDebugBundleValue(value: unknown, options?: DebugSanitizeOptions, depth?: number, keyHint?: string): unknown;
+export declare function handleGetChatDebugBundle(h: CommandHelpers, args: any): Promise<CommandResult>;
+export {};

package/dist/commands/chat-commands-read.d.ts

@@ -0,0 +1,23 @@
+/**
+ * Chat Commands — read side: handleReadChat, handleChatHistory and the
+ * native-history / source-resolution / normalization helpers they use.
+ */
+import type { CommandResult, CommandHelpers } from './handler.js';
+/**
+ * Test-only: clear the in-memory read-pin map and re-arm cold-start hydration so
+ * each test starts from a clean pin state. The on-disk mirror is isolated per
+ * test process via ADHDEV_CONFIG_DIR (test/helpers/setup-env.ts); this resets the
+ * module-level cache that would otherwise leak a pin across tests sharing the
+ * worker. Not part of the runtime contract.
+ */
+export declare function __resetProviderSessionPinsForTest(): void;
+/**
+ * Test-only: read the in-memory read-pin (the mesh-session → conversation-uuid
+ * bind recorded by recordBoundProviderSessionId and mirrored to state.json
+ * sessionProviderSessionPins). Lets the antigravity-coordinator-pin tests assert
+ * that an owner-confirmed workspace-latest read recorded the pin — and that a
+ * non-owner-confirmed read did NOT. Not part of the runtime contract.
+ */
+export declare function __getProviderSessionPinForTest(meshSessionId: string): string | undefined;
+export declare function handleChatHistory(h: CommandHelpers, args: any): Promise<CommandResult>;
+export declare function handleReadChat(h: CommandHelpers, args: any): Promise<CommandResult>;

package/dist/commands/chat-commands-scope.d.ts

@@ -0,0 +1,39 @@
+/**
+ * Chat Commands — read_chat node workspace scope guard.
+ */
+import type { CommandHelpers } from './handler.js';
+/**
+ * read_chat node scope verdict. One physical daemon hosts a base node plus several
+ * worktree nodes; mesh_read_chat always dispatches read_chat with the requested
+ * node's workspace (`args.workspace`). When the resolved target session actually
+ * lives in a DIFFERENT worktree, returning its transcript — or worse, letting the
+ * native-history-by-workspace fallback splice sibling worktree turns into the
+ * reply — makes the coordinator believe one session received every worktree's
+ * work. This guard refuses a CONFIRMED cross-workspace read instead of mixing.
+ *
+ * Conservative by design (mirrors the WTCLAIM fix-B "unknown → allow" rule): only
+ * a session id that resolves to a known workspace which is unequal to a known
+ * intended workspace blocks. When either side is unknown — no targetSessionId, no
+ * args.workspace, an unregistered session, the coordinator self-session, or a
+ * plain dashboard read that never passes a node workspace — the read proceeds
+ * untouched, so base-node and same-daemon coordinator reads never regress.
+ */
+export declare function evaluateReadChatNodeWorkspaceScope(args: {
+    targetSessionId?: string;
+    intendedWorkspace?: string;
+    sessionWorkspace?: string;
+}): {
+    scoped: false;
+} | {
+    scoped: true;
+    intended: string;
+    actual: string;
+};
+/**
+ * Resolve the target session's ACTUAL workspace from the most authoritative source
+ * available on this daemon: the session registry record (stamped at register
+ * time), then the live CLI adapter's working directory, then the bound instance
+ * state. Returns '' when nothing knows the session's workspace — the caller treats
+ * that as "unknown" and does not block.
+ */
+export declare function resolveTargetSessionActualWorkspace(h: CommandHelpers, targetSessionId: string): string;

package/dist/commands/chat-commands-shared.d.ts

@@ -0,0 +1,33 @@
+/**
+ * Chat Commands — shared private helpers used by more than one handler group.
+ *
+ * These were module-local helpers/consts/interfaces in chat-commands.ts. They
+ * are exported here only so the split read/write/debug/scope sub-modules can
+ * import them; they are NOT part of the public chat-commands surface (except
+ * READ_CHAT_PROVIDER_EVAL_TIMEOUT_MS and buildSendInputSignature, which the
+ * chat-commands barrel re-exports).
+ */
+import type { CommandHelpers } from './handler.js';
+import type { CliAdapter } from '../cli-adapter-types.js';
+import { type InputEnvelope, type ProviderModule } from '../providers/contracts.js';
+import type { ProviderInstance } from '../providers/provider-instance.js';
+import type { ChatMessage } from '../types.js';
+import type { SessionTransport } from '../shared-types.js';
+export declare const READ_CHAT_PROVIDER_EVAL_TIMEOUT_MS = 25000;
+export interface ApprovalSelectableInstance extends ProviderInstance {
+    recordApprovalSelection?(buttonText: string): void;
+}
+export interface RuntimeChatMessageMerger extends ProviderInstance {
+    mergeRuntimeChatMessages?(messages: ChatMessage[]): ChatMessage[];
+    recordAcknowledgedUserInput?(input: InputEnvelope | string): void;
+}
+export declare function getCurrentProviderType(h: CommandHelpers, fallback?: string): string;
+export declare function getCurrentManagerKey(h: CommandHelpers): string;
+export declare function getTargetedCliAdapter(h: CommandHelpers, args: any, providerType?: string): CliAdapter | null;
+export declare function getTargetInstance(h: CommandHelpers, args: any): ApprovalSelectableInstance | null;
+export declare function getTargetTransport(h: CommandHelpers, provider?: ProviderModule): SessionTransport | null;
+export declare function isCliLikeTransport(transport: SessionTransport | null): boolean;
+export declare function isExtensionTransport(transport: SessionTransport | null): boolean;
+export declare function buildSendInputSignature(input: InputEnvelope): string;
+export declare function parseMaybeJson(value: any): any;
+export declare function getChatMessageSignature(message: ChatMessage | null | undefined): string;

package/dist/commands/chat-commands-write.d.ts

@@ -0,0 +1,14 @@
+/**
+ * Chat Commands — write side: handleSendChat, handleListChats, handleNewChat,
+ * handleSwitchChat, handleSetMode, handleChangeModel, handleSetThoughtLevel,
+ * handleResolveAction and the send/mode/model helpers they use.
+ */
+import type { CommandResult, CommandHelpers } from './handler.js';
+export declare function handleSendChat(h: CommandHelpers, args: any): Promise<CommandResult>;
+export declare function handleListChats(h: CommandHelpers, args: any): Promise<CommandResult>;
+export declare function handleNewChat(h: CommandHelpers, args: any): Promise<CommandResult>;
+export declare function handleSwitchChat(h: CommandHelpers, args: any): Promise<CommandResult>;
+export declare function handleSetMode(h: CommandHelpers, args: any): Promise<CommandResult>;
+export declare function handleChangeModel(h: CommandHelpers, args: any): Promise<CommandResult>;
+export declare function handleSetThoughtLevel(h: CommandHelpers, args: any): Promise<CommandResult>;
+export declare function handleResolveAction(h: CommandHelpers, args: any): Promise<CommandResult>;

package/dist/commands/chat-commands.d.ts

@@ -1,27 +1,14 @@
 /**
  * Chat Commands — readChat, sendChat, listChats, newChat, switchChat,
  *                 setMode, changeModel, setThoughtLevel, resolveAction, chatHistory
+ *
+ * This module is a re-export barrel. The implementation was split into focused
+ * sub-modules (chat-commands-shared / -scope / -debug-bundle / -read / -write)
+ * as a pure move; the public export surface here is unchanged. handler.ts does
+ * `import * as Chat from './chat-commands.js'` and keeps working unchanged.
  */
-import type { CommandResult, CommandHelpers } from './handler.js';
-import { type InputEnvelope } from '../providers/contracts.js';
-export declare const READ_CHAT_PROVIDER_EVAL_TIMEOUT_MS = 25000;
-export declare function buildSendInputSignature(input: InputEnvelope): string;
-interface DebugSanitizeOptions {
-    maxDepth?: number;
-    maxArrayLength?: number;
-    maxObjectKeys?: number;
-    maxStringLength?: number;
-}
-export declare function sanitizeDebugBundleValue(value: unknown, options?: DebugSanitizeOptions, depth?: number, keyHint?: string): unknown;
-export declare function handleGetChatDebugBundle(h: CommandHelpers, args: any): Promise<CommandResult>;
-export declare function handleChatHistory(h: CommandHelpers, args: any): Promise<CommandResult>;
-export declare function handleReadChat(h: CommandHelpers, args: any): Promise<CommandResult>;
-export declare function handleSendChat(h: CommandHelpers, args: any): Promise<CommandResult>;
-export declare function handleListChats(h: CommandHelpers, args: any): Promise<CommandResult>;
-export declare function handleNewChat(h: CommandHelpers, args: any): Promise<CommandResult>;
-export declare function handleSwitchChat(h: CommandHelpers, args: any): Promise<CommandResult>;
-export declare function handleSetMode(h: CommandHelpers, args: any): Promise<CommandResult>;
-export declare function handleChangeModel(h: CommandHelpers, args: any): Promise<CommandResult>;
-export declare function handleSetThoughtLevel(h: CommandHelpers, args: any): Promise<CommandResult>;
-export declare function handleResolveAction(h: CommandHelpers, args: any): Promise<CommandResult>;
-export {};
+export { READ_CHAT_PROVIDER_EVAL_TIMEOUT_MS, buildSendInputSignature } from './chat-commands-shared.js';
+export { evaluateReadChatNodeWorkspaceScope } from './chat-commands-scope.js';
+export { sanitizeDebugBundleValue, handleGetChatDebugBundle } from './chat-commands-debug-bundle.js';
+export { handleChatHistory, handleReadChat, __resetProviderSessionPinsForTest, __getProviderSessionPinForTest } from './chat-commands-read.js';
+export { handleSendChat, handleListChats, handleNewChat, handleSwitchChat, handleSetMode, handleChangeModel, handleSetThoughtLevel, handleResolveAction, } from './chat-commands-write.js';

package/dist/commands/cli-manager.d.ts

@@ -6,7 +6,7 @@
  */
 import type { ProviderInstanceManager } from '../providers/provider-instance-manager.js';
 import { ProviderLoader } from '../providers/provider-loader.js';
-import { type ProviderModule, type ProviderResumeCapability } from '../providers/contracts.js';
+import { type MeshCoordinatorDelegatedWorkerIsolation, type ProviderModule, type ProviderResumeCapability } from '../providers/contracts.js';
 import type { CliAdapter } from '../cli-adapter-types.js';
 import type { PtyTransportFactory } from '../cli-adapters/pty-transport.js';
 import type { SessionRegistry } from '../sessions/registry.js';
@@ -38,6 +38,16 @@ export interface CliTransportFactoryParams {
     cliArgs?: string[];
     providerSessionId?: string;
     attachExisting?: boolean;
+    /**
+     * Launch-time record meta (meshNodeId / meshNodeFor / launchedByCoordinator /
+     * autoLaunchedForQueueTaskId). Defense-in-depth for SESSION-ACCUMULATION-LEAK:
+     * a session-host factory impl SHOULD seed the create_session record with this
+     * so the node binding is present the instant the record exists, rather than
+     * relying solely on the post-spawn updateRuntimeMeta round-trip. Optional and
+     * additive — factory impls that ignore it keep the prior behavior; the
+     * post-spawn WTDISPATCH stamp in register() still runs as the primary path.
+     */
+    initialMeta?: Record<string, unknown>;
 }
 export interface HostedCliRuntimeDescriptor {
     runtimeId: string;
@@ -51,6 +61,14 @@ export interface HostedCliRuntimeDescriptor {
     cliArgs?: string[];
     providerSessionId?: string;
     managedBy?: string;
+    /**
+     * Real spawn time (ms epoch) of the underlying session-host runtime — a PAST
+     * timestamp recorded when the runtime first started. Threaded through so an
+     * attach can restore the native-history session-floor to the runtime's actual
+     * birth instead of collapsing spawnedAtMs to 0. Undefined when unrecoverable
+     * (genuine post-restart-unknown), in which case the caller keeps the 0 fallback.
+     */
+    startedAtMs?: number;
 }
 type CliLaunchMode = 'new' | 'resume' | 'manual';
 type CliSessionBinding = {
@@ -62,18 +80,57 @@ type CliStartOptions = {
     resumeSessionId?: string;
     settingsOverride?: Record<string, any>;
     extraEnv?: Record<string, string>;
+    /** BRAIN-ROUTING thinking axis: standard level ('low'|'medium'|'high') applied
+     *  at launch via the provider's thinkingLaunchArgs (CLI) or setConfigOption
+     *  ('thought_level', ACP). Best-effort — ignored by providers with no support. */
+    initialThinkingLevel?: string;
 };
 export interface CoordinatorDelegatedCliLaunchOptionsInput {
     cliType: string;
     workspace: string;
     cliArgs?: string[];
     env?: Record<string, string>;
+    isolation?: MeshCoordinatorDelegatedWorkerIsolation;
 }
 export interface CoordinatorDelegatedCliLaunchOptions {
     cliArgs: string[];
     env: Record<string, string>;
 }
+/**
+ * Decide the session-registry spawnedAtMs (the native-history session-floor) for a
+ * newly registered CLI instance.
+ *
+ * - Fresh launch (attachExisting=false): now (nowMs). A real live spawn floor
+ *   isolates a fresh session's own store and holds prior-session leak protection.
+ * - Attach WITH a recoverable record startedAt (a PAST timestamp): that startedAt.
+ *   Restoring a hosted runtime (coordinator / MAGI replica / hermes / claude /
+ *   codex) after a daemon restart, the real spawn time is in the past. Using it
+ *   restores each session's per-session birth-floor so co-located antigravity
+ *   runtimes resolve their OWN conversation (ownerConfirmed) instead of the
+ *   floor-less newest-by-mtime path that let a replica claim the coordinator's conv.
+ * - Attach with NO recoverable startedAt: 0 — disables the floor for this session
+ *   (recent_window_ms still bounds the look-back). NEVER use nowMs here: nowMs is in
+ *   the FUTURE relative to existing transcripts and would push the floor past every
+ *   transcript file, losing them (the ANTIGRAVITY-FINAL-MESSAGE-TAIL-GAP regression).
+ */
+export declare function resolveHostedSpawnedAtMs(attachExisting: boolean, attachStartedAtMs: number | undefined, nowMs: number): number;
 export declare function buildCoordinatorDelegatedCliLaunchOptions(input: CoordinatorDelegatedCliLaunchOptionsInput): CoordinatorDelegatedCliLaunchOptions;
+/**
+ * Expand a provider's `modelLaunchArgs` template with the requested model, mirroring
+ * expandResumeArgs. `{{model}}` → the trimmed model string. Returns undefined when
+ * there is no template or no model (a model request without a template is a no-op —
+ * see startSession, where the caller logs the skip). MAGI kind-panel model axis.
+ */
+export declare function expandModelLaunchArgs(template: string[] | undefined, model: string | undefined): string[] | undefined;
+/**
+ * Expand a provider's `thinkingLaunchArgs` template with the requested thinking
+ * level, parallel to expandModelLaunchArgs. The standard level ('low'|'medium'|
+ * 'high') is first mapped through the provider's `thinkingLevelMap` (a level absent
+ * from the map passes through unchanged), then substituted into every `{{level}}`
+ * token. Returns undefined when there is no template or no level (best-effort; a
+ * thinking request without a template is a no-op). BRAIN-ROUTING thinking axis.
+ */
+export declare function expandThinkingLaunchArgs(template: string[] | undefined, level: string | undefined, levelMap: Partial<Record<string, string>> | undefined): string[] | undefined;
 export declare function supportsExplicitSessionResume(resume?: ProviderResumeCapability): boolean;
 export declare function resolveCliSessionBinding(provider: ProviderModule | undefined, normalizedType: string, cliArgs?: string[], requestedResumeSessionId?: string): CliSessionBinding;
 export declare class DaemonCliManager {
@@ -112,6 +169,19 @@ export declare class DaemonCliManager {
         key: string;
     } | null;
     private findAdapterBySessionId;
+    /**
+     * WTCLAIM (B): resolve the adapter for a mesh dispatch that named a node
+     * (meshContext.nodeId) but carried no explicit session. Matches by the
+     * instance's bound mesh node id (settings.meshNodeId, falling back to the
+     * sticky meshLastNodeId) first, then by the node workspace (workingDir).
+     *
+     * Unlike findAdapter's step-2 fuzzy fallback, this NEVER degrades to a
+     * provider-only first-match: on a daemon hosting BOTH a base node and a
+     * cloned worktree node (same daemonId), that fuzzy match could land a
+     * worktree-targeted task on the base session. Returns null when no session
+     * is bound to this node so the caller fails closed.
+     */
+    private findMeshNodeAdapter;
     handleCliCommand(cmd: string, args: any): Promise<CommandResult | null>;
 }
 export {};