/**
 * Builds the agent-session guest bundle.
 *
 * The guest is Lobu's own code, not organization-supplied source, so it is
 * bundled once per worker process and reused for every turn. It goes through
 * the SAME `ISOLATE_LANE_BUILD_OPTIONS` a connector does — one set of esbuild
 * options, one eligibility rule — plus import-scoped adapters for Pi's file
 * tools and the provider SDKs this lane never selects.
 *
 * Why the aliases are exactly these three: `@google/genai` resolves to its Node
 * build and drags google-auth-library, gaxios, ws, node-fetch, agent-base,
 * https-proxy-agent, proxy-agent, debug and supports-color in with it, and
 * `@aws-sdk/client-bedrock-runtime` drags the Bedrock path. Stubbing those two
 * roots removes every Node builtin from the bundle but one: pi-ai reads
 * `/proc/self/environ` through `node:fs` when it detects Bun with an empty
 * `process.env`. That single importer loses `fs`; every other module keeps it,
 * so a bare `require('fs')` anywhere else still survives into the bundle and
 * `assertIsolateEligible` still rejects it.
 */
export declare function buildAgentGuest(): Promise<string>;
/**
 * The guest bundle for this process. Built on the first turn and kept: it is
 * the same bytes for every agent, and rebuilding it per turn would cost about a
 * second of the turn's own budget.
 */
export declare function agentGuestBundle(): Promise<string>;
//# sourceMappingURL=bundle.d.ts.map