sim 2.1.8-dev.101.1 → 2.1.8-dev.95.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "sim",
-  "version": "2.1.8-dev.101.1",
+  "version": "2.1.8-dev.95.1",
   "description": "Sim CLI - talk to the Sim API from your terminal",
   "type": "module",
   "imports": {

package/dist/embed.d.ts

@@ -1,39 +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 { 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?: {
-    readFile?: EmbedContext['readFile'];
-    openFile?: EmbedContext['openFile'];
-    writeFile?: EmbedContext['writeFile'];
-}): Promise<EmbeddedCliResult>;

package/dist/update/check.d.ts

@@ -1,53 +0,0 @@
-/**
- * The once-a-day "there is a newer sim" notice.
- *
- * It exists because a missing subcommand is indistinguishable from a feature
- * that was never built: someone on 2.1.2 looking for `sim tools execute` — added
- * in 2.1.5 — sees a help listing without it and concludes the CLI cannot do it.
- * The version is the only thing that can tell them otherwise.
- *
- * Everything here fails silently. A courtesy notice that breaks a command, or
- * that writes anything to stdout, is worse than no notice at all.
- */
-export interface UpdateCheckOptions {
-    /** Current working directory. Injected so project-local installation detection is testable. */
-    cwd?: string;
-    currentVersion?: string;
-    env?: NodeJS.ProcessEnv;
-    /** Whether stderr is a terminal. Injected so the suppression rule is testable. */
-    isTty?: boolean;
-    /** Location of the running module, used to recognise npx and local builds. */
-    modulePath?: string;
-    now?: Date;
-    /** Registry transport. Injectable so network behavior can be tested without global state. */
-    registryRequest?: RegistryRequest;
-    write?: (message: string) => void;
-}
-interface RegistryRequestOptions {
-    headers: Record<string, string>;
-    maxResponseBytes: number;
-    timeoutMs: number;
-}
-type RegistryRequest = (url: URL, options: RegistryRequestOptions) => Promise<string | null>;
-/**
- * The command that upgrades *this* installation.
- *
- * The path is asked first because it describes the installation; the
- * environment is a fallback because for a globally installed CLI it usually
- * describes nothing but the shell that happened to invoke it.
- */
-export declare function upgradeCommand(modulePath?: string, env?: NodeJS.ProcessEnv): string;
-/**
- * Uses a daily cache before telling the user their installation is out of date.
- *
- * Wired as a root `preAction` hook rather than a teardown in the entrypoint for
- * two structural reasons: commander answers `--help` and `--version` during
- * parsing, before any action hook runs, so the two most latency-sensitive
- * invocations are excluded by construction rather than by a check; and some
- * commands call `process.exit` directly, which a `finally` would never see.
- *
- * Never throws, writes only plain text to stderr, and stays silent when stderr
- * is redirected. The caller runs this before the user's actual command.
- */
-export declare function announceUpdateIfAvailable(options?: UpdateCheckOptions): Promise<void>;
-export {};