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

package/dist/commands/mesh-coordinator.d.ts

@@ -1,4 +1,4 @@
-import type { ProviderModule, MeshCoordinatorMcpConfigFormat } from '../providers/contracts.js';
+import type { MeshCoordinatorMcpConfigFormat, MeshCoordinatorSystemPromptInjection, ProviderModule } from '../providers/contracts.js';
 export interface MeshCoordinatorMcpServerLaunch {
     command: string;
     args: string[];
@@ -25,6 +25,7 @@ export type MeshCoordinatorSetup = {
     command: string;
     requiresRestart: boolean;
     instructions: string;
+    mcpServer: MeshCoordinatorMcpServerLaunch;
 } | {
     kind: 'unsupported';
     reason: string;
@@ -42,3 +43,86 @@ export interface ResolveMeshCoordinatorSetupOptions {
 }
 export declare function createHermesManualMeshCoordinatorSetup(meshId: string, workspace: string): MeshCoordinatorSetup;
 export declare function resolveMeshCoordinatorSetup(options: ResolveMeshCoordinatorSetupOptions): MeshCoordinatorSetup;
+/**
+ * Apply a provider's declared system-prompt injection rule, mutating `cliArgs`
+ * and `launchEnv` in place and writing any required workspace context file.
+ *
+ * Replaces the previous hard-coded `if (cliType === 'claude-cli') ... else if
+ * (cliType === 'hermes-cli') ...` branches in router.ts. Adding a new CLI is
+ * now provider.v1.json data, not a router edit.
+ *
+ * Failures are non-fatal: log and continue with whatever was applied so the
+ * coordinator session still launches, just without the prompt for that
+ * provider. A missing/unknown rule means "skip injection" — safe by default
+ * (the previous fallback unconditionally pushed --append-system-prompt onto
+ * every non-Claude CLI, which crashed agy on launch).
+ */
+export interface CoordinatorInjectionEffect {
+    /** Absolute path the daemon wrote a wrapper-blocked file to. Only set for
+     *  context_file injection. R48 schedules a strip after launch so workers
+     *  don't see the wrapper on disk; R47's unregister cleanup uses it as a
+     *  fallback if the timer never fires (process crash, etc). */
+    contextFilePath?: string;
+}
+export declare function applyMeshCoordinatorSystemPromptInjection(systemPrompt: string, injection: MeshCoordinatorSystemPromptInjection | undefined, ctx: {
+    cliArgs: string[];
+    launchEnv: Record<string, string>;
+    workspace: string;
+    cliType: string;
+}): CoordinatorInjectionEffect;
+/**
+ * Strip the daemon's wrapper block from a context_file we previously wrote.
+ *
+ * Used in two places:
+ *   1. R48 inject-then-remove: ~5s after spawn, after agy/gemini have read
+ *      the file into their in-memory system-prompt cache. Removing it from
+ *      disk at that point doesn't affect the running coordinator but keeps
+ *      worker sessions (or fresh non-coordinator launches) in the same
+ *      workspace from picking up our wrapper.
+ *   2. R47 unregister fallback: if the timer never fires (process crash,
+ *      kill -9), coordinator-registry.unregisterMeshCoordinator runs the
+ *      same logic when its entry is dropped.
+ *
+ * Idempotent: missing file is fine, missing sentinels are fine, returns
+ * silently. Leaves user-authored content outside the sentinels intact.
+ * Deletes the file outright if our wrapper was the only content.
+ */
+export declare function stripCoordinatorWrapperFile(filePath: string): void;
+export interface PtyExecResult {
+    exitCode: number | null;
+    signal: number | null;
+    output: string;
+    timedOut: boolean;
+}
+export interface MeshCoordinatorRegistrationStep {
+    command: string;
+    args: string[];
+    required: boolean;
+    label: 'remove_existing' | 'register';
+}
+/**
+ * Codex rejects `mcp add` when a server with the same name already exists.
+ * Replace that entry before registering so transport/mesh changes do not leave
+ * a fresh coordinator attached to stale MCP launch arguments.
+ */
+export declare function buildMeshCoordinatorRegistrationPlan(cliType: string, serverName: string, registrationCommand: string): MeshCoordinatorRegistrationStep[];
+/**
+ * Run a one-shot CLI command under a real PTY and collect its output.
+ *
+ * Some provider mcp-registration commands (`agy mcp add`, future bubbletea
+ * TUIs) refuse to run without `/dev/tty`. Daemon-side `execFileSync` runs
+ * pipe-only, so those commands fail with errors like
+ *   `bubbletea: error opening TTY: open /dev/tty: device not configured`
+ * and silently skip the registration, leaving the launched session
+ * without the adhdev-mesh MCP tools — which is exactly what we saw with
+ * agy coordinators.
+ *
+ * Wrapping the registration through node-pty gives the child a real PTY,
+ * so the bubbletea check passes. We close stdin immediately and just
+ * collect stdout until the process exits or the timeout fires.
+ */
+export declare function execUnderPty(command: string, args: string[], options?: {
+    cwd?: string;
+    env?: Record<string, string>;
+    timeoutMs?: number;
+}): Promise<PtyExecResult>;

package/dist/commands/router-aggregate-status.d.ts

@@ -0,0 +1,24 @@
+/**
+ * Aggregate mesh-status cache — extracted from router.ts (behavior-preserving code move).
+ *
+ * These functions were `DaemonCommandRouter` methods; they now take the router
+ * instance as `self`. The class keeps thin delegating wrappers
+ * (getCachedAggregateMeshStatus / rememberAggregateMeshStatus are bound into
+ * HighFamilyContext — intra-cluster calls therefore go through `self.` so instance
+ * dispatch is preserved). No log string, error message, refusal condition, or
+ * result shape changed — only physical location + `this.` → `self.`.
+ *
+ * The group is self-contained: it reads only `self.aggregateMeshStatusCache` and
+ * imported mesh-node-identity / mesh-work-queue helpers. It does NOT touch the
+ * inline-mesh cache cluster, so the move is a pure lift.
+ */
+import type { DaemonCommandRouter } from './router.js';
+export declare function cloneJsonValue<T>(value: T): T;
+export declare function hydrateCachedAggregateMeshStatusFromInline(self: DaemonCommandRouter, snapshot: any, mesh: any, options?: {
+    requireDirectPeerTruth?: boolean;
+}): any;
+export declare function getCachedAggregateMeshStatus(self: DaemonCommandRouter, meshId: string, mesh?: any, options?: {
+    requireDirectPeerTruth?: boolean;
+    allowStalePending?: boolean;
+}): any | null;
+export declare function rememberAggregateMeshStatus(self: DaemonCommandRouter, meshId: string, snapshot: any, refreshReason: string): any;

package/dist/commands/router-mesh-session-owner.d.ts

@@ -0,0 +1,59 @@
+/**
+ * Remote mesh-session owner resolution — extracted from router.ts (behavior-preserving code move).
+ *
+ * These functions were `DaemonCommandRouter` methods; they now take the router
+ * instance as `self`. resolveRemoteMeshSessionOwnerDaemonId stays reachable as a
+ * public method (the [Z] session-scoped forward in executeDaemonCommand and the
+ * mesh-session-scoped-remote-forward test call it), so the class keeps a thin
+ * delegating wrapper. No log string, error message, refusal condition, or result
+ * shape changed — only physical location + `this.` → `self.`.
+ *
+ * The group is read-only: it reads self.deps.statusInstanceId, the cached inline-mesh
+ * nodes, and the aggregate-status snapshot nodes. It never mutates router state.
+ */
+import type { DaemonCommandRouter } from './router.js';
+/**
+ * Resolve the REMOTE worker daemonId that owns a given session, when the session
+ * belongs to a mesh node hosted on a DIFFERENT daemon than this coordinator.
+ *
+ * The coordinator does not host remote-worker session instances in its own
+ * instanceManager/sessionRegistry — only their cached mesh-node metadata. A
+ * dashboard-issued session-scoped command (invoke_provider_script / resolve_action /
+ * set_mode / …) lands on the coordinator with a targetSessionId the coordinator can't
+ * find locally, and without forwarding it dies as "Live session not found". send_chat
+ * happens to survive (its target resolves to the worker by another route), but the
+ * controlbar commands do not — so the controlbar buttons appear to do nothing.
+ *
+ * Mirror the existing node-level remote-forward pattern (fast_forward_mesh_node etc.):
+ * scan the candidate mesh nodes for the one hosting the targetSessionId, and return its
+ * daemonId when that daemonId is a remote daemon (i.e. not this coordinator's own
+ * statusInstanceId). Returns undefined for a locally-hosted session (no forward — execute
+ * locally as before) or when ownership can't be resolved.
+ *
+ * The candidate set spans BOTH the cached inline-mesh nodes and the live aggregate
+ * mesh-status snapshots. The inline cache reliably carries only each node's single primary
+ * session (cachedStatus.activeSession), so a worker hosting more than one session exposes its
+ * non-primary sessions only on the aggregate snapshot nodes (status.activeSessions /
+ * activeSessionDetails, built from live session records). collectMeshNodeHostedSessionIds does
+ * the wider plural-shape scan so a controlbar/modal command targeting a non-primary remote
+ * session still resolves its owner — the singular readCachedInlineMeshActiveSessions semantics
+ * other consumers depend on stay untouched.
+ *
+ * CANCEL-STOP-RELAY: the session-id cache scan above only matches when the coordinator's
+ * cached status snapshot already lists the worker's session id in a recognized active-sessions
+ * shape. A worktree-clone worker session whose id form/timing differs from the cached snapshot
+ * (or is simply not yet reflected) misses the scan, so a stop that carries the authoritative
+ * owning nodeId (mesh_queue_cancel knows assignedNodeId) used to silently fail to forward.
+ * `ownerNodeIdHint` adds a deterministic fallback: when the session-id scan misses, resolve the
+ * owner daemonId by matching the node by id (meshNodeIdMatches — same form-tolerant compare the
+ * rest of the router uses, no new raw compare). The same self-loopback guard applies to both
+ * paths, so a coordinator-hosted node is still never force-forwarded to a remote form of itself.
+ */
+export declare function resolveRemoteMeshSessionOwnerDaemonId(self: DaemonCommandRouter, sessionId: string, ownerNodeIdHint?: string): string | undefined;
+/**
+ * Candidate nodes for remote-session owner resolution: the cached inline-mesh nodes (which
+ * carry each node's primary session) plus the nodes from every cached aggregate mesh-status
+ * snapshot (which carry each node's full live session list). getCachedInlineMeshNodes()
+ * returns a fresh array, so appending the aggregate nodes never mutates cached state.
+ */
+export declare function collectMeshSessionOwnerCandidateNodes(self: DaemonCommandRouter): any[];

package/dist/commands/router-refine.d.ts

@@ -0,0 +1,151 @@
+import type { DaemonCommandRouter, CommandRouterResult } from './router.js';
+import { MeshRefineAsyncJobStatus, MeshRefineBatchJobHandle, MeshRefineBatchJobStatus, MeshRefineJobHandle, RefineContext, RefineStageOutcome } from '../mesh/mesh-refine-gates.js';
+export declare function buildRefineJobKey(self: DaemonCommandRouter, meshId: string, nodeId: string): string;
+export declare function buildRefineJobHandle(self: DaemonCommandRouter, args: {
+    meshId: string;
+    nodeId: string;
+    node?: any;
+    status?: MeshRefineAsyncJobStatus;
+    startedAt?: string;
+    completedAt?: string;
+    jobId?: string;
+    interactionId?: string;
+    retryOfJobId?: string;
+    coordinatorDaemonId?: string;
+}): MeshRefineJobHandle;
+/**
+ * Slim the terminal-stage refine result down to the fields a coordinator needs to
+ * decide next-step, dropping the heavy per-command / per-entry detail.
+ *
+ * The full `CommandRouterResult` (with `validationSummary.commandsRun[]` carrying
+ * per-command stdout/stderr, `rejectedCommands`, `suggestions`, `suggestedConfig`,
+ * the full `patchEquivalence`, and `submoduleReachability.entries[]`/`.unreachable[]`)
+ * routinely exceeds 70KB and overflows the coordinator token limit when it rides on a
+ * `mesh_wait_events` payload. The full detail is still persisted verbatim to the ledger
+ * (`appendRefineJobLedger`) and `terminalRefineJobs`, so slimming only the EVENT loses
+ * nothing — the coordinator can pull the full record on demand via
+ * `evidence.ledgerCommand` / `taskHistoryKind`.
+ */
+export declare function slimRefineEventResult(result: Record<string, unknown>): Record<string, unknown>;
+export declare function queueRefineJobEvent(self: DaemonCommandRouter, event: 'refine:accepted' | 'refine:completed' | 'refine:failed', handle: MeshRefineJobHandle, result?: Record<string, unknown>): void;
+export declare function appendRefineJobLedger(self: DaemonCommandRouter, kind: 'task_dispatched' | 'task_completed' | 'task_failed', handle: MeshRefineJobHandle, result?: Record<string, unknown>): Promise<void>;
+/**
+ * On daemon restart, scan all mesh ledgers for refine jobs that were dispatched
+ * but never completed/failed (i.e. the daemon died mid-job).  Re-queue each one
+ * so the job runs to completion automatically without coordinator intervention.
+ */
+export declare function resumePendingRefineJobsOnStartup(self: DaemonCommandRouter): Promise<void>;
+/**
+ * Synchronous refinery for a single worktree node — the gate pipeline that
+ * validates, preflights (patch-equivalence / submodule-reachability /
+ * no-op), merges, aligns submodules, cleans up the worktree node and
+ * (optionally) pushes. The body is a flat sequence of stage methods; each
+ * stage either returns a terminal CommandRouterResult (gate failure or a
+ * successful already-merged short-circuit) or `continue` with the extended
+ * context. Behavior — stage order, every early-exit, and every result shape —
+ * is identical to the previous single inlined body.
+ */
+export declare function executeMeshRefineNodeSynchronously(self: DaemonCommandRouter, meshId: string, nodeId: string, args: any): Promise<CommandRouterResult>;
+/**
+ * resolve_refs stage: resolve the mesh / worktree node / source node /
+ * repoRoot, then the worktree branch, base branch, fetched base head and
+ * branch head. Seeds the RefineContext consumed by every later stage.
+ */
+export declare function refineResolveRefsStage(self: DaemonCommandRouter, meshId: string, nodeId: string, args: any, refineStages: Array<Record<string, unknown>>): Promise<RefineStageOutcome>;
+/**
+ * validation stage: run the refinery validation gate (typecheck / test /
+ * lint / build per node config) and block on failure or when no allowlisted
+ * command was available. On pass, stores the summary on the context.
+ */
+export declare function refineValidationStage(self: DaemonCommandRouter, ctx: RefineContext): Promise<RefineStageOutcome>;
+/**
+ * patch_equivalence stage: preflight that the worktree branch's cumulative
+ * patch is equivalent to base+branch. On a "behind base" branch, auto-rebase
+ * once and re-check; on an empty merge-tree with real branch changes, treat as
+ * already-merged-via-another-path and short-circuit to cleanup. Mutates the
+ * context's branchHead (after rebase) and patchEquivalence (rebased gate).
+ */
+export declare function refinePatchEquivalenceStage(self: DaemonCommandRouter, ctx: RefineContext): Promise<RefineStageOutcome>;
+/**
+ * submodule_reachability stage: verify every submodule gitlink commit that
+ * would land via the merge is reachable from its configured remote main
+ * branch (optionally auto-publishing when policy allows). Blocks the merge
+ * when any commit is unreachable. Stores the result on the context.
+ */
+export declare function refineSubmoduleReachabilityStage(self: DaemonCommandRouter, ctx: RefineContext): Promise<RefineStageOutcome>;
+/**
+ * effective_diff stage (no-op guard): block a silent no-op merge where the
+ * branch produces no effective root-tree diff against base — typically a
+ * submodule that has commits but whose root-level gitlink (pointer) bump was
+ * never committed, so the merge would land nothing real on main.
+ */
+export declare function refineEffectiveDiffStage(self: DaemonCommandRouter, ctx: RefineContext): Promise<RefineStageOutcome>;
+/**
+ * merge + finalize stage: perform the --no-ff merge, align submodule
+ * checkouts after merge, clean up (remove) the worktree node per policy,
+ * append the refinery ledger entry, and (unless approval is required) push the
+ * base branch. Always terminal — produces the final CommandRouterResult.
+ */
+export declare function refineMergeAndFinalizeStage(self: DaemonCommandRouter, ctx: RefineContext): Promise<RefineStageOutcome>;
+/**
+ * Batch refinery: converge multiple sibling worktree nodes onto the base branch
+ * in one sequential pipeline, absorbing the rebase + patch-equivalence churn that
+ * arises when several siblings touch the same submodule.
+ *
+ * Reuses executeMeshRefineNodeSynchronously per node — every node goes through the
+ * exact same validation / patch-equivalence / submodule-reachability / merge / cleanup
+ * gates, including its built-in auto-rebase onto fresh origin/<base>. Because each
+ * node fetches origin/<base> at the start of its own refine, a node merged earlier in
+ * the batch advances the base, and the next node's refine auto-rebases onto it before
+ * re-running patch-equivalence. No force-push, no reset — conflicting nodes are
+ * isolated as blocked_review while the rest of the batch proceeds.
+ */
+export declare function batchRefineMeshNodes(self: DaemonCommandRouter, meshId: string, requestedNodeIds: string[] | undefined, args: any): Promise<CommandRouterResult>;
+/**
+ * Convergence core shared by the synchronous batch entry and the async batch job.
+ * Refines each node in order: the per-node refine pipeline fetches origin/<base>
+ * fresh, so each merged sibling advances the base before the next node's auto-rebase
+ * + patch-equivalence re-check. A blocked/failed node is isolated; the batch
+ * continues with the remaining nodes. Does NOT touch the per-node merge logic — it
+ * only sequences calls to executeMeshRefineNodeSynchronously and aggregates outcomes.
+ */
+export declare function runMeshRefineBatchConvergence(self: DaemonCommandRouter, meshId: string, orderedNodes: any[], ordering: {
+    order: string[];
+    rationale?: unknown;
+}, args: any): Promise<CommandRouterResult>;
+export declare function buildRefineBatchJobKey(self: DaemonCommandRouter, meshId: string): string;
+export declare function buildRefineBatchJobHandle(self: DaemonCommandRouter, args: {
+    meshId: string;
+    nodeIds: string[];
+    order: string[];
+    status?: MeshRefineBatchJobStatus;
+    startedAt?: string;
+    completedAt?: string;
+    jobId?: string;
+    interactionId?: string;
+    coordinatorDaemonId?: string;
+}): MeshRefineBatchJobHandle;
+/**
+ * Emit a batch Refinery terminal/accepted event through the SAME pending-event +
+ * forward mechanism single-node refine uses (queueRefineJobEvent), so the
+ * coordinator's existing refine:accepted/completed/failed handling and message
+ * renderer apply unchanged. The aggregate per-node results ride along in `result`.
+ */
+export declare function queueRefineBatchJobEvent(self: DaemonCommandRouter, event: 'refine:accepted' | 'refine:completed' | 'refine:failed', handle: MeshRefineBatchJobHandle, result?: Record<string, unknown>): void;
+export declare function appendRefineBatchJobLedger(self: DaemonCommandRouter, kind: 'task_dispatched' | 'task_completed' | 'task_failed', handle: MeshRefineBatchJobHandle, result?: Record<string, unknown>): Promise<void>;
+export declare function finishMeshRefineBatchJob(self: DaemonCommandRouter, handle: MeshRefineBatchJobHandle, orderedNodes: any[], ordering: {
+    order: string[];
+    rationale?: unknown;
+}, args: any): Promise<void>;
+/**
+ * Async entry for the batch Refinery execute path. Mirrors startMeshRefineJob:
+ * resolves the plan synchronously (so target/ordering errors and the dry-run shape
+ * stay synchronous), then for execute=true registers an in-flight batch job, returns
+ * {async:true, status:'accepted', batch:true, ...plan} immediately, and runs the
+ * convergence loop in the background — emitting the same terminal refine event.
+ * Idempotent: a batch already in flight for this mesh returns the running handle
+ * with duplicate:true rather than spawning a second background job.
+ */
+export declare function startMeshRefineBatchJob(self: DaemonCommandRouter, meshId: string, requestedNodeIds: string[] | undefined, args: any): Promise<CommandRouterResult>;
+export declare function finishMeshRefineJob(self: DaemonCommandRouter, handle: MeshRefineJobHandle, args: any): Promise<void>;
+export declare function startMeshRefineJob(self: DaemonCommandRouter, meshId: string, nodeId: string, args: any): Promise<CommandRouterResult>;

package/dist/commands/router-worktree-cleanup.d.ts

@@ -0,0 +1,133 @@
+import type { DaemonCommandRouter } from './router.js';
+import type { RepoMeshSessionCleanupMode } from '../repo-mesh-types.js';
+export declare function sessionMatchesMeshNode(self: DaemonCommandRouter, record: any, node: any, nodeId: string, sessionIds?: Set<string>): boolean;
+/**
+ * Best-effort recursive removal of a managed worktree directory.
+ *
+ * The git-registry de-registration is the safety-critical step of worktree
+ * teardown; a leftover directory must never gate dropping the node from the
+ * mesh. On Windows, `fs.rmSync` can throw EINVAL/EPERM/EBUSY on submodule
+ * gitlink (`.git`) files, long paths, junctions, or while a just-stopped
+ * delegate session is still releasing a handle/cwd on the directory. This
+ * helper absorbs those errors (never throws), with bounded retries + backoff
+ * to give handles time to release, and reports whether residue remains.
+ */
+export declare function bestEffortRemoveWorktreeDir(self: DaemonCommandRouter, dir: string): Promise<{
+    removed: boolean;
+    residue: boolean;
+    error?: string;
+}>;
+/**
+ * Non-destructive precheck mirroring every REFUSAL condition in
+ * {@link cleanupLocalWorktreeNode} — missing workspace / source-repo / branch
+ * metadata, unexpected (non-managed) path, branch mismatch — PLUS the
+ * dirty-worktree guard that `removeWorktree(requireClean)` enforces
+ * (`git status --porcelain`). It performs ZERO destructive actions: no
+ * `git worktree remove`, no `git worktree prune`, no directory deletion.
+ *
+ * remove_mesh_node calls this BEFORE any session cleanup so that a refusal
+ * (the common one being a dirty worktree) does not first stop/delete the
+ * delegated session and orphan it — the original ordering bug. Success/skip
+ * cases that the real cleanup handles idempotently (worktree path already
+ * gone, git-de-registered residue) are NOT refusals and return `{ ok: true }`.
+ *
+ * `force:true` skips the dirty guard, preserving `removeWorktree`'s
+ * `requireClean: !force` semantics. This is a read-only superset check; the
+ * authoritative `requireClean` guard inside `removeWorktree` is intentionally
+ * kept as a second line of defense against a precheck→execute race.
+ */
+export declare function precheckLocalWorktreeRemovable(self: DaemonCommandRouter, args: {
+    mesh: any;
+    node: any;
+    nodeId: string;
+    force?: boolean;
+}): Promise<{
+    ok: true;
+} | {
+    ok: false;
+    code: string;
+    error: string;
+    recoveryHint: string;
+}>;
+export declare function cleanupLocalWorktreeNode(self: DaemonCommandRouter, args: {
+    mesh: any;
+    node: any;
+    nodeId: string;
+    force?: boolean;
+}): Promise<{
+    success: true;
+    skipped?: boolean;
+    removedPath?: string;
+    repoRoot?: string;
+    reason?: string;
+    fallback?: string;
+    forced?: boolean;
+    convergence?: Record<string, unknown>;
+    recovered?: boolean;
+    residue?: boolean;
+    residueWarning?: string;
+    residueError?: string;
+    branchRefDeleted?: boolean;
+    branchRefReason?: string;
+    branchRefForced?: boolean;
+    branchRefWarning?: string;
+} | {
+    success: false;
+    code: string;
+    error: string;
+    recoveryHint: string;
+    convergence?: Record<string, unknown>;
+}>;
+export declare function getWorktreeForceCleanupConvergence(self: DaemonCommandRouter, args: {
+    repoRoot: string;
+    workspace: string;
+    node: any;
+}): Promise<{
+    allow: boolean;
+    status?: string;
+    source?: string;
+    ref?: string;
+    error?: string;
+}>;
+export declare function isCompletedHostedSession(self: DaemonCommandRouter, record: any): boolean;
+export declare function recordIntentionalMeshSessionStop(self: DaemonCommandRouter, args: {
+    meshId: string;
+    nodeId: string;
+    node: any;
+    sessionId: string;
+    mode: RepoMeshSessionCleanupMode;
+    source: 'mesh_cleanup_sessions' | 'mesh_remove_node' | 'magi_session_cleanup';
+    action: 'stop_session' | 'delete_session_force';
+}): Promise<void>;
+export declare function cleanupMeshSessions(self: DaemonCommandRouter, args: {
+    meshId: string;
+    nodeId: string;
+    node: any;
+    mode: RepoMeshSessionCleanupMode;
+    sessionIds?: string[];
+    dryRun?: boolean;
+    source?: 'mesh_cleanup_sessions' | 'mesh_remove_node' | 'magi_session_cleanup';
+    /**
+     * MAGI auto-cleanup safety gate: a map of sessionId → the queue task id that
+     * session must have been AUTO-LAUNCHED for (record meta autoLaunchedForQueueTaskId).
+     * When set, a matched explicit session is only acted on if its record carries that
+     * exact marker. A reused idle session (no marker), the coordinator session, a
+     * re-assigned session, or any session whose marker points at a DIFFERENT task is
+     * skipped (reason 'auto_launch_marker_mismatch') — so MAGI never kills a session it
+     * didn't itself spawn for this fan-out. Only consulted alongside explicit sessionIds.
+     */
+    requireAutoLaunchedForTaskIds?: Record<string, string>;
+    /**
+     * Opt-in orphan reclaim (default false). See SESSION-ACCUMULATION-LEAK.
+     * When true, a workspace-only live_runtime session (no node binding) OR a
+     * live_runtime session bound to a node absent from `liveMeshNodeIds` is
+     * stopped instead of skipped by the conservative shared-daemon guard. A
+     * session whose meshNodeId is STILL in `liveMeshNodeIds` (active sibling)
+     * is never reclaimed — that is the shared-daemon safety this preserves.
+     */
+    reclaimOrphans?: boolean;
+    liveMeshNodeIds?: string[];
+}): Promise<{
+    success: boolean;
+    [key: string]: unknown;
+}>;