type PiSdk = typeof import("@earendil-works/pi-coding-agent");
/**
 * The SDK entry of the bundled Pi CLI running this process, if it is one. The
 * published `pi` bin is `dist/bundle/cli.js`; its `dist/bundle/index.js` SDK
 * entry is built from the same chunks the CLI has already evaluated.
 */
export declare function hostBundleSdkEntry(cliPath?: string | undefined): string | undefined;
/**
 * The SDK entry the Pi CLI running this process evaluated: the bundle's entry
 * under the published bin, `dist/index.js` beside an unbundled `dist/cli.js`.
 */
export declare function hostSdkEntry(cliPath?: string | undefined): string | undefined;
/**
 * The host's own SDK. Pi's loader tries a native import first and maps host
 * packages only when that fails, so compiled ESM such as Fabric gets plain Node
 * resolution for every runtime import. Managed installs omit host peers: a bare
 * package import then has nothing on disk to resolve, and where a development
 * peer is on disk it evaluates the separate unbundled SDK inside the bundled
 * CLI: about 1,600 more modules. Besides the startup cost, that CLI enables
 * Node's compile cache, which serializes every one of those modules on exit;
 * with a cold cache that held a Windows child past the worker's exit grace
 * after it had settled. The running CLI's own entry is a module-cache hit
 * instead. The durable worker's resolution hook, mapped hosts (compiled
 * binaries), and embeds supply the package entry.
 */
export declare function loadHostSdk(cliPath?: string | undefined): Promise<PiSdk>;
export {};
//# sourceMappingURL=host-sdk.d.ts.map