@adhdev/daemon-core 0.9.82-rc.333 → 0.9.82-rc.335

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

@@ -182,6 +182,7 @@ export declare class ProviderCliAdapter implements CliAdapter {
         force?: boolean;
     }): Promise<void>;
     forceSendMessage(text: string): Promise<void>;
+    private waitForForceSubmitSettle;
     private enqueuePendingOutboundMessage;
     private shouldQueuePendingOutboundMessage;
     private schedulePendingOutboundFlush;

package/dist/commands/router.d.ts

@@ -86,6 +86,16 @@ type MeshRefineSubmoduleConflictHint = {
     }>;
     nextSteps: string[];
 };
+/**
+ * A spawn-resolution failure is when the executable itself could not be found by
+ * the OS spawn boundary — `spawn <cmd> ENOENT` — as opposed to the command
+ * running and exiting non-zero. On win32 this is the .cmd-shim case: libuv's
+ * spawn search appends only .com/.exe, so a bare `npm`/`npx`/`tsc` (which are
+ * .cmd shims) ENOENTs even though it is installed. It carries no stderr, so it
+ * must be detected by error.code/syscall, not by string-matching output.
+ */
+export declare function isSpawnResolutionError(error: any): boolean;
+export declare function describeSpawnError(error: any, command: string, spawnResolutionFailed: boolean): string;
 export declare function runMeshRefinePatchEquivalenceGate(repoRoot: string, baseHead: string, branchHead: string): Promise<MeshRefinePatchEquivalenceSummary>;
 export type MeshWorktreePatchContainmentSummary = {
     /** True only when merging worktreeHead into ref introduces no new patch. */