sim 2.1.8-dev.94.1 → 2.1.8-preview.100.1

package/package.json

@@ -1,17 +1,14 @@
 {
   "name": "sim",
-  "version": "2.1.8-dev.94.1",
+  "version": "2.1.8-preview.100.1",
   "description": "Sim CLI - talk to the Sim API from your terminal",
   "type": "module",
-  "imports": {
-    "#cli/*": "./src/*.ts"
-  },
   "bin": {
     "sim": "dist/index.js"
   },
   "scripts": {
     "prebuild": "bun run clean",
-    "build": "bun build src/index.ts src/runtime.ts --target=node --format=esm --packages=bundle --reject-unresolved --outdir=dist && tsc -p tsconfig.types.json",
+    "build": "bun build src/index.ts --target=node --format=esm --packages=bundle --reject-unresolved --outfile=dist/index.js",
     "clean": "bun -e \"import { rmSync } from 'node:fs'; rmSync('dist', { recursive: true, force: true })\"",
     "type-check": "tsc --noEmit",
     "lint": "biome check --write --unsafe .",
@@ -52,23 +49,16 @@
   "dependencies": {
     "chalk": "5.6.2",
     "commander": "^11.1.0",
-    "js-yaml": "4.3.1"
+    "js-yaml": "4.3.1",
+    "proper-lockfile": "4.1.2"
   },
   "devDependencies": {
     "@sim/tsconfig": "0.0.0",
+    "@sim/utils": "0.1.0",
     "@types/js-yaml": "4.0.9",
     "@types/node": "24.2.1",
+    "@types/proper-lockfile": "4.1.4",
     "typescript": "^7.0.2",
     "vitest": "^4.1.0"
-  },
-  "exports": {
-    "./embed": {
-      "types": "./src/embed.ts",
-      "default": "./src/embed.ts"
-    },
-    "./runtime": {
-      "types": "./dist/runtime.d.ts",
-      "default": "./dist/runtime.js"
-    }
   }
 }

package/dist/auth/device-flow.d.ts

@@ -1,38 +0,0 @@
-export type CliAuthScope = 'copilot' | 'platform';
-export interface AuthRequest {
-    /** Semi-public rendezvous handle; travels in the browser URL. */
-    request: string;
-    /** Never leaves this process until the poll redeems it. */
-    pollSecret: string;
-    /** BASE64URL(SHA256(pollSecret)), registered when the user approves. */
-    challenge: string;
-    /** Printed for the user to compare against the browser. Never sent to the API. */
-    pairing: string;
-}
-export interface MintedKey {
-    id: string;
-    apiKey: string;
-    scope: CliAuthScope;
-    /** The workspace picked in the browser — the profile's default target. */
-    workspaceId: string | null;
-    /** Whether the key can *only* reach that workspace. */
-    workspaceBound: boolean;
-}
-export declare function createAuthRequest(): AuthRequest;
-export declare function buildApprovalUrl(endpoint: string, auth: AuthRequest, scope: CliAuthScope, workspaceId?: string): string;
-/**
- * Polls until the user approves in the browser.
- *
- * Transport failures are swallowed and retried rather than aborting the login:
- * a laptop that slept, a VPN reconnecting, or a deploy rolling the server mid-
- * wait are all recoverable, and the approval sits in Redis with its own TTL. A
- * non-2xx *response*, by contrast, is the server refusing on purpose and is
- * surfaced immediately.
- *
- * Retried is not the same as unreported: once
- * {@link TRANSPORT_FAILURES_BEFORE_WARNING} attempts in a row fail to reach the
- * endpoint at all, the reason is printed once to stderr and the poll carries on.
- * Without it a typo'd endpoint was indistinguishable from a slow approval for
- * the entire 15-minute timeout.
- */
-export declare function pollForKey(endpoint: string, auth: AuthRequest, signal?: AbortSignal): Promise<MintedKey>;

package/dist/commands/auth.d.ts

@@ -1,5 +0,0 @@
-import { Command } from 'commander';
-export declare function loginCommand(): Command;
-export declare function logoutCommand(): Command;
-export declare function whoamiCommand(): Command;
-export declare function profilesCommand(): Command;

package/dist/commands/configure.d.ts

@@ -1,2 +0,0 @@
-import { Command } from 'commander';
-export declare function configureCommand(): Command;

package/dist/commands/credentials.d.ts

@@ -1,3 +0,0 @@
-import { type Command } from 'commander';
-/** Adds the human-facing OAuth connection commands backed by the v2 credentials API. */
-export declare function attachCredentialCommands(program: Command): void;

package/dist/commands/protocol/chat.d.ts

@@ -1,11 +0,0 @@
-import type { Command } from 'commander';
-/**
- * Adds `sim chat`.
- *
- * A protocol command rather than a generated one: the generated pass can only
- * make one JSON request, while a chat turn can run for minutes and is consumed
- * as an NDJSON stream so the reply prints as it generates and heartbeats keep
- * proxies from idling the connection out. The generated `chat` operation is
- * hidden in the CLI contract in favour of this command.
- */
-export declare function attachChat(program: Command): void;

package/dist/commands/protocol/files-get.d.ts

@@ -1,25 +0,0 @@
-import { type WriteStream } from 'node:fs';
-import { type Writable } from 'node:stream';
-import type { Command } from 'commander';
-/** Streams a fetch body to disk while honoring write-stream backpressure. */
-export declare function streamToFile(body: ReadableStream<Uint8Array>, file: Writable & Pick<WriteStream, 'path'>, reportedPath?: WriteStream['path']): Promise<void>;
-/**
- * Removes the staging directory when a signal ends the process.
- *
- * `saveStagedFile` cleans up in normal control flow, which a signal never
- * reaches: the process is torn down mid-`pipeline`, so every Ctrl-C left
- * another `.sim-download-*` holding a partial payload beside the destination.
- * The removal is synchronous because the termination that follows gives an
- * async `rm` no turn to run.
- *
- * Exported for its own test: driving it through a real interrupt would take the
- * test runner down with it.
- */
-export declare function removeStagingOnSignal(stagingDirectory: () => string | null, terminate?: (signal: NodeJS.Signals) => void): () => void;
-/** Publishes a complete staged body atomically, with overwrite requiring explicit force. */
-export declare function saveToFile(body: ReadableStream<Uint8Array>, target: string, force: boolean): Promise<void>;
-/** Streams a fetch body to stdout without closing the process-wide stream. */
-export declare function streamToStdout(body: ReadableStream<Uint8Array>, output?: NodeJS.WriteStream): Promise<void>;
-/** Returns whether content can be written directly to an interactive terminal. */
-export declare function isTerminalSafeContentType(contentType: string | null): boolean;
-export declare function attachFileGet(files: Command): void;

package/dist/commands/protocol/files-upload.d.ts

@@ -1,2 +0,0 @@
-import type { Command } from 'commander';
-export declare function attachFileUpload(files: Command): void;

package/dist/commands/protocol/index.d.ts

@@ -1,3 +0,0 @@
-import { Command } from 'commander';
-/** Attaches commands whose multi-request or binary protocols cannot be generated. */
-export declare function attachProtocolCommands(program: Command): void;

package/dist/commands/protocol/knowledge-document-upload.d.ts

@@ -1,2 +0,0 @@
-import { type Command } from 'commander';
-export declare function attachKnowledgeDocumentUpload(documents: Command): void;

package/dist/commands/protocol/logs-follow.d.ts

@@ -1,39 +0,0 @@
-import { type Command } from 'commander';
-import { type ListLogsResponse } from '../../generated/v2-api';
-/** One run, as `GET /api/v2/logs` returns it. */
-export type LogRow = ListLogsResponse['data'][number];
-/** Widest a table column renders, matching the `logs list` table. */
-export declare const MAX_CELL_WIDTH = 60;
-export interface FollowStatus {
-    /** Replaces the status line, if there is a terminal to draw it on. */
-    note: (message: string) => void;
-    /**
-     * Reports something the reader has to know, on its own line.
-     *
-     * Unlike {@link note} this is not progress and is never erased: it records
-     * that rows are missing, which stays true after the follow moves on. It is
-     * written even when stderr is not a terminal, because a piped log is exactly
-     * where an unexplained hole is hardest to spot.
-     */
-    warn: (message: string) => void;
-    /** Erases the line, if anything was ever written to it. */
-    clear: () => void;
-}
-/**
- * Reports what the follow is doing, on stderr.
- *
- * The rule `pageProgress` follows: stdout is the stream of rows and gets piped,
- * so anything that is not a row goes to stderr, and only to a terminal.
- */
-export declare function followStatus(): FollowStatus;
-/**
- * Adds `sim logs follow`.
- *
- * A sibling command rather than `logs list --follow`, because `logs list` is
- * generated from the CLI contract, which describes the HTTP surface: `--follow`
- * has no wire counterpart, and its paging is the inverse of the contract's —
- * re-reading the newest page forever, rather than walking a cursor to the end
- * once. The filters are the same ones `logs list` exposes, so the two commands
- * take the same arguments and render the same columns.
- */
-export declare function attachLogsFollow(logs: Command): void;

package/dist/commands/protocol/resource-directory.d.ts

@@ -1,24 +0,0 @@
-import { type Command } from 'commander';
-type ResourceDirectoryConfig = {
-    kind: 'file';
-    resources: 'listFiles';
-    folders: 'listFileFolders';
-    createFolder: 'createFileFolder';
-} | {
-    kind: 'knowledge';
-    resources: 'listKnowledgeBases';
-    folders: 'listKnowledgeFolders';
-    createFolder: 'createKnowledgeFolder';
-} | {
-    kind: 'table';
-    resources: 'listTables';
-    folders: 'listTableFolders';
-    createFolder: 'createTableFolder';
-} | {
-    kind: 'workflow';
-    resources: 'listWorkflows';
-    folders: 'listWorkflowFolders';
-    createFolder: 'createWorkflowFolder';
-};
-export declare function attachResourceDirectoryCommands(group: Command, config: ResourceDirectoryConfig): void;
-export {};

package/dist/commands/protocol/result.d.ts

@@ -1,2 +0,0 @@
-import type { OutputFormat } from '../../config/index';
-export declare function printProtocolResult(format: OutputFormat, result: Record<string, unknown>): void;

package/dist/commands/protocol/tables-import.d.ts

@@ -1,2 +0,0 @@
-import { type Command } from 'commander';
-export declare function attachTableImport(tables: Command): void;

package/dist/commands/protocol/workflow-run-follow.d.ts

@@ -1,56 +0,0 @@
-import type { Command } from 'commander';
-/** The sink live commentary is written to; `process.stderr` satisfies it. */
-export interface CommentaryWriter {
-    write(text: string): unknown;
-}
-export interface FollowOptions {
-    includeThinking: boolean;
-    includeToolCalls: boolean;
-    stderr: CommentaryWriter;
-}
-type WorkflowRunSelection = {
-    source: 'manual';
-} | {
-    source: 'manual';
-    entry: {
-        type: 'trigger';
-        blockId?: string;
-        useMockPayload?: boolean;
-    };
-} | {
-    source: 'manual';
-    entry: {
-        type: 'block';
-        blockId: string;
-        sourceRunId: string;
-    };
-};
-/** Projects friendly CLI flags into the API's strict nested run selector. */
-export declare function resolveWorkflowRunSelection(flags: Record<string, unknown>): WorkflowRunSelection | undefined;
-/**
- * Renders one execute stream, returning the `final` envelope.
- *
- * Everything rendered here is commentary and goes to `stderr`: the payload a
- * script captures is the final envelope, which the caller prints to stdout in
- * the profile's output format. Streaming the answer text to stdout as well
- * would put the same content in the redirect twice, once unparseable.
- *
- * Throws on a terminal `error` frame and on a stream that stops before either
- * terminal frame arrives — a truncated stream is a failed run, and reporting it
- * as an empty success is the one outcome a caller cannot detect afterwards.
- */
-export declare function renderRunStream(body: ReadableStream<Uint8Array>, options: FollowOptions): Promise<Record<string, unknown>>;
-/**
- * Teaches the generated `workflows run` leaf to stream.
- *
- * `--follow` rides on `run` rather than standing up a sibling command because
- * it is the same operation with a different response encoding: the input,
- * output-selection, and `--async` flags all still apply, and a second command
- * would have to restate every one of them and then drift.
- *
- * Commander offers no way to read the action it already holds, so the existing
- * handler is captured and delegated to — every non-`--follow` invocation still
- * runs the generated path byte for byte.
- */
-export declare function attachWorkflowRunFollow(workflows: Command): void;
-export {};

package/dist/commands/protocol/workflow-run-get.d.ts

@@ -1,15 +0,0 @@
-import type { Command } from 'commander';
-/**
- * Teaches the generated `workflows runs get` leaf the block names
- * `workflows run --select-output` already takes.
- *
- * The run resource matches recorded block ids only — it never loads the
- * workflow — so `--select-output summarize.result`, the spelling the run was
- * started with, came back `400` and the fix was to go and look up an id. The
- * lookup is done here instead: a selection with any name-headed selector reads
- * the workflow's blocks once, rewrites names onto ids, and reads the run keyed
- * the way it was asked. A selection of ids alone, or no selection, still runs
- * the generated handler byte for byte. Commander offers no way to read the
- * action it holds, so it is captured and delegated to, as `--follow` does.
- */
-export declare function attachWorkflowRunGet(runs: Command): void;

package/dist/commands/protocol/workflow-run-wait.d.ts

@@ -1,3 +0,0 @@
-import { type Command } from 'commander';
-/** Adds `workflows runs wait` — poll one run until it stops moving. */
-export declare function attachWorkflowRunWait(runs: Command): void;

package/dist/commands/secrets.d.ts

@@ -1,3 +0,0 @@
-import { type Command } from 'commander';
-/** Adds interactive secret entry while preserving an explicit value flag for scripts. */
-export declare function attachSecretCommands(program: Command): void;

package/dist/config/index.d.ts

@@ -1,2 +0,0 @@
-export { configDir, configPath, credentialsPath } from './paths';
-export { DEFAULT_ENDPOINT, DEFAULT_PROFILE, deleteProfile, FORBIDDEN_IN_VALUE, listAuthenticationDependents, listProfiles, normalizeEndpoint, normalizeWorkspaceId, OUTPUT_FORMATS, type OutputFormat, PROFILE_NAME_PATTERN, ProfileConfigError, type ProfileOverrides, type ResolvedProfile, readConfigProfile, readCredentialsProfile, resolveAuthenticationProfileName, resolveProfile, type SettingSource, validateProfileName, writeConfigProfile, writeCredentialsProfile, } from './profile';

package/dist/config/ini.d.ts

@@ -1,111 +0,0 @@
-/**
- * A minimal INI reader/writer for the AWS-style `~/.sim/config` and
- * `~/.sim/credentials` files.
- *
- * Parsing keeps every line it did not understand — comments, blank lines,
- * unrecognized keys — and writing re-emits them in place. These are files people
- * hand-edit, so a round trip through `sim login` must not silently delete the
- * comment above someone's staging endpoint.
- *
- * Deliberately not a general INI implementation: no nested sections, no `[a.b]`
- * paths, no quoting rules beyond trimming. The format only has to carry a
- * handful of flat string settings.
- */
-/**
- * An invalid stored setting, or a value the config files cannot represent.
- *
- * Defined here rather than in `profile.ts` because the writer below is the
- * lowest layer that rejects input, and `profile.ts` already imports this module.
- * `profile.ts` re-exports it, so callers keep seeing one error type — the one
- * the entrypoint renders as a message instead of a stack trace.
- */
-export declare class ProfileConfigError extends Error {
-    constructor(message: string);
-}
-type Entry = {
-    kind: 'kv';
-    key: string;
-    value: string;
-} | {
-    kind: 'raw';
-    text: string;
-};
-interface Section {
-    name: string;
-    /**
-     * The header line exactly as it was read, re-emitted verbatim.
-     *
-     * {@link parseIni} trims the bracketed text to get {@link name}, so writing
-     * `[${name}]` back rewrote the header of every section in the file — a
-     * `configure --set-output` on `default` silently reformatted a hand-written
-     * `[profile   padded   ]` it was never asked to touch. Absent only on a
-     * section {@link setSectionValues} created, which has no original line.
-     */
-    header?: string;
-    entries: Entry[];
-}
-export interface IniDocument {
-    /** Lines before the first section header. */
-    preamble: string[];
-    sections: Section[];
-}
-/**
- * Characters a stored value may not contain.
- *
- * The format has no escape syntax (see the module note), so text that can end a
- * line is structure, not data: a value carrying a line break was written
- * verbatim and read back on the next load as a *second* setting in the same
- * section. That is the class of bug this closes — untrusted text reaching the
- * serializer could add settings nobody typed.
- *
- * The set is every C0 and C1 control character plus U+2028 and U+2029, the two
- * Unicode line separators. The separators matter for a second reason: they are
- * not line breaks to the reader below, so {@link KV_PATTERN} (whose `.` never
- * matches them) fails and the line is kept as opaque `raw` text — the key
- * silently vanishes on the next read although the write reported success, and
- * because the dead line no longer matches the key, the write after that appends
- * a duplicate.
- *
- * Exported because callers that refuse untrusted text *before* writing — so they
- * can say which side produced it — have to refuse exactly this set. A second
- * hand-kept copy drifted from this one once already, and the gap let a rejected
- * write land after an accepted one.
- */
-export declare const FORBIDDEN_IN_VALUE: RegExp;
-export declare function parseIni(text: string): IniDocument;
-export declare function serializeIni(doc: IniDocument): string;
-/**
- * Reads a section's keys, merging every block that repeats its name.
- *
- * A hand-edited file can carry two `[default]` blocks; reading only the first
- * silently dropped the second's keys and reported them as unset. The merge is
- * **first wins** per key, matching {@link setSectionValues}, which upserts into
- * the first block — so a value written through this module is the one read back.
- */
-export declare function getSection(doc: IniDocument, name: string): Record<string, string> | null;
-export declare function listSections(doc: IniDocument): string[];
-/**
- * Upserts values into a section, creating it when absent. A `null` value removes
- * the key. Existing keys are updated where they sit so surrounding comments keep
- * describing the line they were written above.
- *
- * A write targets the first block of that name, matching the first-wins read in
- * {@link getSection}. A removal instead has to clear every block and every
- * repeat of the key within one: deleting only the first left a later duplicate
- * to win the merged read, so `--unset` reported success while the value stayed
- * in force. A removal against a section that is not there writes nothing at all.
- *
- * This is the one place untrusted text enters the document, so it is where the
- * write is refused: see {@link FORBIDDEN_IN_VALUE} for what cannot be stored
- * and why the answer is a refusal rather than an escape.
- */
-export declare function setSectionValues(doc: IniDocument, name: string, values: Record<string, string | null>): void;
-/**
- * Drops every block carrying the name, and reports whether one was there.
- *
- * A hand-edited file can repeat a section, and {@link getSection} merges them
- * all — so removing only the first left `sim logout` reporting a profile gone
- * while its later block still answered every read.
- */
-export declare function removeSection(doc: IniDocument, name: string): boolean;
-export {};

package/dist/config/paths.d.ts

@@ -1,10 +0,0 @@
-/**
- * Where the CLI keeps its state. `SIM_CONFIG_DIR` overrides the location
- * wholesale, which is what lets tests and CI point at a scratch directory
- * instead of the invoking user's real credentials.
- */
-export declare function configDir(): string;
-/** Non-secret per-profile settings. Safe to commit to a dotfiles repo. */
-export declare function configPath(): string;
-/** API keys, written 0600. Kept apart from `config` so the two can be handled differently. */
-export declare function credentialsPath(): string;

package/dist/config/profile.d.ts

@@ -1,158 +0,0 @@
-import { ProfileConfigError } from './ini';
-export declare const DEFAULT_PROFILE = "default";
-/**
- * The API host, which is the `www` one and not the apex.
- *
- * `sim.ai` answers `/api/**` with a 301 to `www.sim.ai`, and the CLI refuses to
- * follow a redirect — a 301 rewrites a POST into a bodyless GET, so following
- * one turns a write into a silent no-op and hands the API key to whatever host
- * `Location` names. Defaulting to the apex therefore made every command fail
- * for anyone who never set an endpoint, and before the refusal existed it was
- * worse: reads succeeded while writes quietly did nothing.
- */
-export declare const DEFAULT_ENDPOINT = "https://www.sim.ai";
-/**
- * Output formats, in the order `--help` lists them.
- *
- * `table` is for reading, `json`/`yaml` for piping into a parser, and `text` is
- * the one for shell loops: tab-separated, no header, no colour, so `cut`/`awk`/
- * `while read` work without a JSON tool on the box.
- */
-export declare const OUTPUT_FORMATS: readonly ['table', 'json', 'yaml', 'text'];
-export type OutputFormat = (typeof OUTPUT_FORMATS)[number];
-export { FORBIDDEN_IN_VALUE, ProfileConfigError } from './ini';
-/**
- * Makes a rejected value safe to quote inside an error message.
- *
- * A message is one terminal line, so a value carrying a line break appends
- * lines that read as the CLI's own output. Every message that interpolates text
- * the CLI did not produce — a flag, an environment variable, a hand-edited
- * setting — goes through this, so the rule does not have to be rediscovered at
- * each new message.
- */
-export declare function redact(value: string): string;
-/**
- * A root flag typed with a value the CLI cannot use.
- *
- * Separate from the rest of {@link ProfileConfigError} so a caller that
- * deliberately tolerates an unresolvable profile — `profiles` shows a broken
- * one as a marked row rather than aborting, because that is the command you run
- * *because* a profile is broken — can still refuse the caller's own argument.
- * The class is the discriminator on purpose: matching the message text would
- * stop working the first time the wording changes.
- */
-export declare class ProfileOverrideError extends ProfileConfigError {
-    constructor(message: string);
-}
-/**
- * The shape a newly created profile name has to have.
- *
- * Enforced only when a profile is being created. A name reaches the config file
- * as part of a section header, and the file format has no escape syntax, so a
- * name that carries a bracket or a line break would forge a header for another
- * profile — the writer refuses that outright, and this pattern is the friendlier
- * refusal that names the rule instead of the mechanism.
- */
-export declare const PROFILE_NAME_PATTERN: RegExp;
-/**
- * Refuses a name for a profile that does not exist yet.
- *
- * Creation only, deliberately: a hand-written `[profile my stack]` predates this
- * rule and must keep resolving, so the read path stays governed by
- * {@link requireKnownProfile} alone.
- */
-export declare function validateProfileName(name: string): void;
-/** Everything a command needs to make a call, after the resolution chain runs. */
-export interface ResolvedProfile {
-    name: string;
-    endpoint: string;
-    apiKey: string | null;
-    workspaceId: string | null;
-    output: OutputFormat;
-    /**
-     * Replaces global `fetch` for every request. Only an embedding server sets it, to
-     * answer its own v2 routes in-process; the installed CLI never does.
-     */
-    transport?: typeof fetch;
-    signal?: AbortSignal;
-    /** Where each value came from, for `sim whoami` to explain surprising results. */
-    sources: {
-        endpoint: SettingSource;
-        apiKey: SettingSource;
-        workspaceId: SettingSource;
-        output: SettingSource;
-    };
-}
-export type SettingSource = 'flag' | 'env' | 'config' | 'credentials' | 'default' | 'unset';
-export interface ProfileOverrides {
-    profile?: string;
-    endpoint?: string;
-    apiKey?: string;
-    workspaceId?: string;
-    output?: OutputFormat;
-    /**
-     * Skips the "does this profile exist?" check for the two commands that
-     * legitimately name a profile before it exists — `sim login --profile x` and
-     * `sim configure --profile x --set-…`, both of which create it.
-     */
-    allowUnknownProfile?: boolean;
-}
-export declare function readConfigProfile(profile: string): Record<string, string>;
-export declare function readCredentialsProfile(profile: string): Record<string, string>;
-/**
- * Resolves the one stored identity a profile authenticates through.
- *
- * Existing profiles authenticate through their same-named credentials section.
- * A workspace alias may instead name one direct `auth_profile`; references are
- * deliberately non-recursive so a hand-edited cycle or missing target fails
- * with the setting that needs repair rather than surfacing later as "no key".
- */
-export declare function resolveAuthenticationProfileName(profile: string): string;
-/**
- * Every profile named by either file, deduplicated and sorted.
- *
- * The name is taken verbatim from what follows `profile `, without a second
- * trim. `configSectionName` builds the header back by prefixing `profile `, so
- * trimming here made the two disagree for a hand-written `[profile   padded]`:
- * it listed and passed the "does this profile exist?" check as `padded`, while
- * every read looked for `profile padded` and found nothing — so `-P padded`
- * silently resolved to the built-in defaults, and the spelling that does name
- * the section was refused as unknown. Reporting the padded name keeps the one
- * that selects it the one that is shown, which is also how the credentials
- * file's sections have always been listed.
- */
-export declare function listProfiles(): string[];
-/** Profiles that directly share the named profile's stored authentication. */
-export declare function listAuthenticationDependents(authProfile: string): string[];
-export declare function writeConfigProfile(profile: string, values: Record<string, string | null>): void;
-export declare function writeCredentialsProfile(profile: string, apiKey: string | null): void;
-/** Drops the profile from both files. Returns whether anything was removed. */
-export declare function deleteProfile(profile: string): {
-    config: boolean;
-    credentials: boolean;
-};
-/**
- * Validates an endpoint and strips its trailing slashes.
- *
- * The check has to live here rather than at the call sites because an endpoint
- * reaches the HTTP client from four directions — `--endpoint`, `SIM_ENDPOINT`,
- * `configure --set-endpoint`, and a hand-edited `~/.sim/config` — and an
- * unparseable one escapes as a raw `TypeError: Invalid URL` stack trace from
- * inside Node's URL parser instead of a CLI error.
- *
- * `source` names where the value came from, so the message points at the thing
- * the user has to edit.
- */
-export declare function normalizeEndpoint(endpoint: string, source: string): string;
-/**
- * Validates a workspace id on its way into the config file.
- *
- * The sibling of {@link normalizeEndpoint}, and for the same reason: a stored
- * setting is read back as a real setting, so a value that could carry a line
- * break would come back as an extra setting the user never typed — including an
- * `endpoint`, which decides where the API key is sent. Only structure is
- * checked, not the id's shape: ids are server-minted and the CLI has no business
- * deciding what one may look like.
- */
-export declare function normalizeWorkspaceId(workspaceId: string, source: string): string;
-export declare function resolveProfile(overrides?: ProfileOverrides): ResolvedProfile;

package/dist/context.d.ts

@@ -1,21 +0,0 @@
-import type { Command } from 'commander';
-import { type OutputFormat, type ProfileOverrides, type ResolvedProfile } from './config/index';
-import { SimClient } from './http/client';
-/** Global flags, shared by every subcommand. */
-export interface GlobalOptions {
-    profile?: string;
-    endpoint?: string;
-    workspace?: string;
-    output?: OutputFormat;
-}
-/**
- * Commander stores globals on the root command, not on the leaf that ran, so a
- * subcommand handler has to walk up to find them. `optsWithGlobals()` does that
- * walk; reading `command.opts()` alone silently drops `--profile`.
- */
-export declare function globalsOf(command: Command): GlobalOptions;
-export declare function profileFrom(command: Command, extra?: ProfileOverrides): ResolvedProfile;
-export declare function clientFrom(command: Command): {
-    client: SimClient;
-    profile: ResolvedProfile;
-};

package/dist/contract/commands.d.ts

@@ -1,14 +0,0 @@
-import type { CliContract } from './types';
-/**
- * The CLI contract for the v2 surface.
- *
- * Read this as a diff against what is already derivable — an operation absent
- * from this table still gets a command, built entirely from the generated
- * operation table. Only the entries below needed a human.
- *
- * Derived by default:
- *   listTables            → sim tables list
- *   getKnowledgeDocument  → sim knowledge documents get <knowledgeBaseId> <documentId>
- *   upsertTableRow        → sim tables upsert <tableId>
- */
-export declare const CLI_CONTRACT: CliContract;