@h-rig/cli 0.0.6-alpha.89 → 0.0.6-alpha.90

package/dist/src/commands/_pi-frontend.d.ts

@@ -20,35 +20,8 @@ export declare function buildOperatorPiEnv(input: {
     readonly serverProjectRoot?: string | null;
     readonly sessionDir: string;
 }): Record<string, string>;
-export declare function shouldRequireOperatorTranscript(status: unknown): boolean;
-export declare function missingOperatorTranscriptMessage(runId: string, status: unknown): string;
-/** Run Pi's `main()` in-process but RETURN to the caller when Pi quits, instead
- * of letting it terminate the process. Pi's interactive quit calls
- * `process.exit(...)` (interactive-mode.js); when the OpenTUI shell hands Pi the
- * terminal IN-PROCESS (the eject), that would kill the whole rig process. We
- * temporarily intercept `process.exit` for the duration of the Pi session,
- * convert the exit into a thrown sentinel that unwinds back here, then restore
- * the real `process.exit`. The OpenTUI store + React tree are still alive (the
- * renderer was only suspended), so the caller resumes the shell at the same
- * state/screen. Returns Pi's intended exit code. */
-/** Run `body` in-process while RETURNING (instead of terminating) when it calls
- * `process.exit`. Used to run Pi's `main()` from the OpenTUI shell so Pi's
- * interactive quit (which calls `process.exit`, interactive-mode.js) returns
- * control to the shell rather than killing the whole rig process.
- *
- * We replace `process.exit` with a guard that resolves a `quit` promise — raced
- * against `body` — instead of terminating, then restore the real `process.exit`.
- * We deliberately do NOT throw from the guard: Pi's `process.exit` calls are
- * terminal (the last statement of their quit path, after Pi has already stopped
- * its render loop and disposed), and Pi often calls exit from a detached input
- * callback where a throw would escape to the event loop (the bug that first
- * shipped — the shell hung). Resolving `quit` synchronously returns control
- * whichever path the exit takes. Returns the intended exit code. Exported for
- * unit testing both exit paths. */
-export declare function runWithProcessExitGuard(body: () => Promise<unknown>): Promise<number>;
 export declare function attachRunBundledPiFrontend(context: Pick<RunnerContext, "projectRoot" | "outputMode">, input: {
     readonly runId: string;
     readonly steered?: boolean;
-    readonly returnOnQuit?: boolean;
 }): Promise<AttachResult>;
 export {};