sim 2.1.18-dev.133.1 → 2.1.18

package/dist/embed.d.ts

@@ -1,40 +0,0 @@
-import { type EmbedContext, type EmbeddedCliIdentity } from './embed-context';
-import { SimClient } from './http/client';
-/**
- * In-process execution of one CLI invocation, for a server that already knows
- * who is calling: the caller supplies endpoint + credential + workspace
- * directly and the profile machinery (config files, env vars, login state) is
- * bypassed entirely. Everything else — command tree, flag parsing, request
- * building, output rendering — is the exact code the installed CLI runs, so
- * the two surfaces cannot drift.
- *
- * Concurrency-safe by construction: the identity and the output capture both
- * live in an AsyncLocalStorage context, so parallel embedded invocations (and
- * any ordinary console logging around them) never interleave.
- */
-export type { EmbeddedCliIdentity, EmbeddedFileSnapshot } from './embed-context';
-export type { ExportWorkflowResponse, ListFilesResponse, ListWorkflowsResponse, ReadFileTextResponse, } from './generated/v2-api';
-export { SimApiError, SimClient } from './http/client';
-export interface EmbeddedCliResult {
-    exitCode: number;
-    stdout: string;
-    stderr: string;
-}
-/**
- * A typed v2 client bound to an embedded identity — for server-side augmentation
- * commands that reuse the v2 surface directly instead of re-parsing rendered
- * CLI output. Same endpoint/credential semantics as {@link runEmbeddedCli}.
- */
-export declare function createEmbeddedClient(identity: EmbeddedCliIdentity): SimClient;
-/**
- * Runs one CLI invocation in-process. `argv` is the token list exactly as the
- * terminal would receive it (no leading node/binary tokens). Errors the
- * installed CLI would print-and-exit-1 on come back the same way: rendered to
- * stderr, exitCode 1 — never thrown.
- */
-export declare function runEmbeddedCli(argv: string[], identity: EmbeddedCliIdentity, options?: {
-    workingDirectory?: string;
-    readFile?: EmbedContext['readFile'];
-    openFile?: EmbedContext['openFile'];
-    writeFile?: EmbedContext['writeFile'];
-}): Promise<EmbeddedCliResult>;

package/dist/environment.d.ts

@@ -1,22 +0,0 @@
-/**
- * Facts about the process environment that more than one feature reads.
- *
- * The update notice and usage telemetry both suppress themselves in CI and
- * both read `SIM_*` switches; one definition keeps the two from disagreeing
- * about what "on" or "in CI" means.
- */
-/** Anything but unset, empty, `0` or `false` turns a switch on. */
-export declare function isEnabled(value: string | undefined): boolean;
-/** Whether any of the {@link CI_VARIABLES} says this is a CI job. */
-export declare function isCi(env?: NodeJS.ProcessEnv): boolean;
-/**
- * The Node proxy flags this process was started with, for a child that must
- * reach the network the same way.
- */
-export declare function proxyExecArgv(): string[];
-/**
- * The process environment for a helper child: proxy and TLS settings intact,
- * the named variables removed so a credential never reaches a process that
- * does not need it, and `extra` added on top.
- */
-export declare function childProcessEnv(strip: readonly string[], extra?: Partial<NodeJS.ProcessEnv>): NodeJS.ProcessEnv;