@byok-sdk/client 0.3.0 → 0.4.0

package/dist/adapters/pi/pi-adapter.d.ts

@@ -1,5 +1,4 @@
-import type { TaskOfferPayload } from '@byok-sdk/protocol';
-import { type RuntimeAdapter, type RuntimeCapabilities, type RuntimeDetectResult, type RuntimeEnvironmentRequirements, type Session, type TaskContext } from '../../types';
+import { type RuntimeAdapter, type RuntimeDetectResult, type RuntimeAdapterPrepareInput, type RuntimeAdapterPrepareResult } from '../../types';
 import { type ResolvedBin } from './resolve-bin';
 import { type SpawnFn } from './rpc-client';
 /**
@@ -31,21 +30,9 @@ export interface PiByokLauncherConfig {
 }
 export declare class PiAdapter implements RuntimeAdapter {
     private readonly options;
-    readonly id = "pi";
-    readonly supportsDispatchSelection = true;
+    readonly descriptor: import("..").RuntimeAdapterDescriptor;
     constructor(options?: PiAdapterOptions);
     detect(): Promise<RuntimeDetectResult>;
-    capabilities(): RuntimeCapabilities;
-    /**
-     * M5: pi authenticates to its ~30 supported providers via env-var API
-     * keys — `detect()`'s own `authPresent` probe above checks this identical
-     * list — so these MUST keep flowing into pi's spawned process or pi auth
-     * breaks entirely. `KNOWN_PROVIDER_ENV_VARS` above is the single source
-     * of truth, reused here rather than duplicated. No `baseNames`: nothing
-     * in this adapter or `rpc-client.ts` reads a pi-specific config-discovery
-     * variable beyond the platform baseline (`daemon/environment.ts`).
-     */
-    environmentRequirements(): RuntimeEnvironmentRequirements;
-    start(task: TaskOfferPayload, ctx: TaskContext): Promise<Session>;
+    prepare(input: RuntimeAdapterPrepareInput): Promise<RuntimeAdapterPrepareResult>;
     private resolveBin;
 }

package/dist/adapters/pi/rpc-client.d.ts

@@ -39,6 +39,9 @@ export declare class PiRpcClient {
     private readonly eventQueue;
     private closed;
     private exitError;
+    private readonly closedPromise;
+    private resolveClosed;
+    private disposalAttempt;
     /** Bounded tail of recent stderr lines — pi discarded this entirely before (nothing ever read `child.stderr`), which is exactly why finding #1 (`Error: Unknown option: --session-id`, exit 1) had to be root-caused by hand instead of reading it off a thrown error. See `buildExitError`. */
     private readonly stderrRing;
     /** Count of pi RPC message types `PiSession` (pi-adapter.ts) has told us have no `AgentEvent` mapping and aren't routine bookkeeping — see `recordUnmappedFrame`. */
@@ -51,6 +54,8 @@ export declare class PiRpcClient {
     }): Promise<PiRpcMessage>;
     /** Every non-response, non-`extension_ui_request` line — the latter is answered directly by this client (see `respondToExtensionUiRequest`) and never enqueued. */
     get events(): AsyncIterable<PiRpcMessage>;
+    /** Local transport diagnostic retained when the process closes; consumers must classify it explicitly. */
+    get terminalError(): Error | undefined;
     /**
      * Record a pi RPC message `type` that `PiSession` (pi-adapter.ts) decided
      * has no `AgentEvent` mapping and isn't routine bookkeeping (see
@@ -61,8 +66,11 @@ export declare class PiRpcClient {
      * a post-mortem on a failed/hung task has it without separate log scraping.
      */
     recordUnmappedFrame(type: string): void;
-    /** Best-effort teardown. SIGTERM on POSIX; `taskkill /T /F` on Windows to also reap child processes pi itself spawned (e.g. bash). */
+    /** Immediate process-tree termination request. `dispose()` is the settlement receipt. */
     kill(): void;
+    waitClosed(): Promise<void>;
+    dispose(): Promise<void>;
+    private processTreeOptions;
     private onData;
     private onLine;
     /**

package/dist/adapters/process-tree.d.ts

@@ -0,0 +1,19 @@
+import { type ChildProcess, type SpawnOptions } from 'node:child_process';
+export interface OwnedProcessTreeOptions {
+    child: ChildProcess;
+    waitClosed: () => Promise<void>;
+    isClosed: () => boolean;
+    label: string;
+    termGraceMs?: number;
+    killGraceMs?: number;
+}
+/**
+ * Every bundled runtime root is an owned process-group leader on POSIX. Pipes
+ * remain referenced, so `detached` changes ownership topology without making
+ * the runtime outlive the daemon. Windows uses taskkill's `/T` tree authority.
+ */
+export declare function withOwnedProcessTree<T extends SpawnOptions>(options: T): T;
+/** Immediate termination request used by interrupt paths; close remains the receipt. */
+export declare function requestOwnedProcessTreeTermination(options: OwnedProcessTreeOptions): void;
+/** Resolve only after the adapter-owned root and descendants are quiescent. */
+export declare function disposeOwnedProcessTree(options: OwnedProcessTreeOptions): Promise<void>;

package/dist/bin/audit-log.d.ts

@@ -118,6 +118,18 @@ export declare const AUDIT_LOG_TRIM_TARGET_LINES = 5000;
  * tail) rather than the file growing without bound.
  */
 export declare const MAX_LIVE_TASK_ANCHORS = 500;
+/**
+ * Git failures are serialized only as this closed, stable category set —
+ * never raw Git errors or command output. Projected from
+ * `daemon/git-workspace.ts`'s `GIT_ERROR_CATEGORIES` (the single source of
+ * truth for the `GitErrorCategory` union) rather than carrying a literal
+ * copy that could drift from it; the runtime half of that guarantee is
+ * `__tests__/git-category-drift.test.ts`.
+ *
+ * @internal Exported for the drift-guard test only (never re-exported from
+ * `index.ts`).
+ */
+export declare const STABLE_GIT_ERROR_CATEGORIES: Set<string>;
 /**
  * Appends one `DaemonEvent` as a single redacted JSON line (finding P1 #3 —
  * see this file's module doc comment) at 0600, and rotates the file if it's