dsh-zen-remote 2.3.11 → 2.4.0

package/lib/types/cli/bootstrap.d.ts

@@ -0,0 +1,170 @@
+/**
+ * CLI-2 bootstrap: everything a CLI session needs BEFORE any subcommand
+ * logic runs — interactive prompting, candidate-profile scanning with the
+ * multi-select plugin install, and bringing a DSH instance up.
+ *
+ * Three injectable seams keep this testable without a real terminal or a
+ * real daemon (SPEC's test seam three): a `CliPrompter` the tests replace
+ * with fakes, a `spawnCommand` the tests record instead of running
+ * `dsh plugin add`, and an `execProbe` the tests substitute for systemctl /
+ * launchctl / open. The real implementations sit next to them in this file
+ * and exercise the very same code paths.
+ *
+ * The non-interactive iron rule lives here: with `!isTTY` or `--yes`, a
+ * question with no command-line answer throws `MissingRequiredOptionError`
+ * IMMEDIATELY — a headless run must fail fast and legibly, never hang on a
+ * stdin read nothing will ever answer.
+ */
+import type { Readable, Writable } from 'node:stream';
+import { discoverCliSockets } from './ipc-client.js';
+import type { CliIpcClient, CliPingResponse } from './ipc-client.js';
+import type { CliTranslator } from './i18n.js';
+export interface CliMultiSelection {
+    /** Indices into the `choices` array, in the order the user entered them. */
+    indices: number[];
+    /** Names typed via the manual-input entry (`a`). */
+    customNames: string[];
+}
+export interface CliPrompter {
+    selectOne(question: string, choices: readonly string[], defaultIndex: number): Promise<number>;
+    selectMulti(question: string, choices: readonly string[], defaultIndices: readonly number[], allowCustomInput?: boolean): Promise<CliMultiSelection>;
+    inputText(question: string, defaultValue?: string, validate?: (value: string) => string | undefined): Promise<string>;
+    confirm(question: string, defaultYes?: boolean): Promise<boolean>;
+    close(): void;
+}
+/** Raised when a required value is missing in a run that must not prompt
+ * (`!isTTY` or `--yes`). Carries the option name so the top level can render
+ * one precise bilingual line instead of a stack trace. */
+export declare class MissingRequiredOptionError extends Error {
+    readonly optionName: string;
+    constructor(optionName: string);
+}
+/** The interactivity verdict every prompt flows through: a TTY and no
+ * `--yes`. One function so the rule has exactly one home. */
+export declare function isInteractiveSession(args: {
+    options: {
+        yes: boolean;
+    };
+}, isTty: boolean): boolean;
+/**
+ * One ask-everything funnel: a command-line-provided (or caller-default)
+ * value answers directly; otherwise interactive runs prompt, and
+ * non-interactive runs throw {@link MissingRequiredOptionError} naming the
+ * option — before any await that could hang.
+ */
+export declare function promptOrFail<T>(params: {
+    optionName: string;
+    interactive: boolean;
+    provided: T | undefined;
+    ask: () => Promise<T>;
+}): Promise<T>;
+/**
+ * The default `CliPrompter` over `node:readline/promises`. Scaffold strings
+ * (the "pick a number" hints) go through the translator like everything
+ * else; questions and choices arrive pre-translated from the callers.
+ */
+export declare function createReadlinePrompter(input?: Readable, output?: Writable, t?: CliTranslator): CliPrompter;
+export interface CandidateProfile {
+    name: string;
+    installed: boolean;
+}
+/**
+ * The installable profiles under `<dshHome>/profiles/`: real directories,
+ * excluding `desktop` (the DSH app manages it and `dsh plugin` must not
+ * touch it), `node_modules`, and dot-hidden entries. `web` is ALWAYS at
+ * index 0 — synthesized when the directory does not exist yet — so both the
+ * prompt's default check and the preferred-profile rule can rely on it.
+ */
+export declare function scanCandidateProfiles(dshHome: string): CandidateProfile[];
+export interface EnsurePluginInstalledOptions {
+    dshHome: string;
+    /** Explicit `--profile p1,p2` targets; skips the scan-and-ask flow and
+     * installs even over already-installed profiles (idempotent add). */
+    profileFlag?: readonly string[];
+    /** TTY && !`--yes`, decided by the caller (see isInteractiveSession). */
+    interactive?: boolean;
+    prompter?: CliPrompter;
+    /** Injectable runner for `dsh plugin … add` — tests record instead of run. */
+    spawnCommand?: (command: string, args: readonly string[]) => Promise<number>;
+    stdout?: {
+        write(text: string): void;
+    };
+    t?: CliTranslator;
+}
+export interface EnsurePluginInstalledResult {
+    ok: boolean;
+    code: 'ok' | 'desktop-refused' | 'install-failed' | 'no-profiles';
+    /** Every profile this step decided is (or should now be) installed. */
+    targets: string[];
+    /** `web` when the targets include it, else the first target. */
+    preferredProfile: string | undefined;
+    /** Profiles the install actually ran for, in order. */
+    installedNow: string[];
+    selectedBy: 'flag' | 'prompt' | 'default' | 'already-installed';
+    failedProfile?: string;
+    manualCommand?: string;
+}
+/**
+ * Make sure `dsh-zen-remote` is installed into at least one usable profile:
+ * explicit `--profile` wins; otherwise an already-installed profile ends the
+ * flow; otherwise an interactive TTY multi-selects from the candidate scan
+ * (default-checked `web`, manual names welcome) and a non-interactive run
+ * defaults to `web`. Each selected profile gets
+ * `dsh plugin --profile <name> add dsh-zen-remote`; a failure prints the
+ * verbatim manual command and reports `install-failed`. `desktop` is
+ * refused everywhere — the DeepSeek Harness app owns that profile.
+ */
+export declare function ensurePluginInstalled(options: EnsurePluginInstalledOptions): Promise<EnsurePluginInstalledResult>;
+export interface ExecProbeResult {
+    code: number;
+    stdout: string;
+}
+export type ExecProbe = (command: string, args: readonly string[]) => Promise<ExecProbeResult>;
+export interface EnsureDshRunningOptions {
+    dshHome: string;
+    /** Among several live instances prefer the one serving this role. */
+    targetRole?: 'host' | 'client';
+    /** Feeds the manual-start guidance and (nothing spawns daemons per-profile
+     * today) future per-profile daemons. */
+    preferredProfile?: string;
+    /** Poll budget after a daemon trigger; default 20s. */
+    waitSeconds?: number;
+    /** Probe only this socket instead of the candidate walk. */
+    explicitSocket?: string;
+    /** Platform override (tests pin every branch on one machine). */
+    platform?: NodeJS.Platform;
+    /** uid for the launchd `gui/<uid>/…` target; default process.getuid(). */
+    uid?: number;
+    /** Injectable command runner for the daemon probes/triggers. */
+    execProbe?: ExecProbe;
+    /** Injectable discovery (tests can stage socket states per call). */
+    discover?: typeof discoverCliSockets;
+    /** macOS app bundle path; tests relocate it off the real /Applications. */
+    macosAppPath?: string;
+    /** System systemd unit dir; tests relocate it off the real /etc. */
+    systemUnitDir?: string;
+    stdout?: {
+        write(text: string): void;
+    };
+    t?: CliTranslator;
+}
+export type EnsureDshRunningResult = {
+    started: true;
+    client: CliIpcClient;
+    socketPath: string;
+    ping: CliPingResponse;
+} | {
+    started: false;
+    outcome: 'permission-denied' | 'no-daemon' | 'timeout';
+    message: string;
+};
+/**
+ * Find (or launch) a DSH this CLI can drive: discovery first — a live
+ * version-matching socket answers immediately (preferring the target role
+ * among multiple instances); EACCES / EPERM reports the cross-user hint and
+ * stops; otherwise the platform's daemon triggers fire and discovery polls
+ * until a socket appears or `waitSeconds` run out. Windows and daemon-less
+ * machines get the manual-start guidance and a structured `no-daemon` result.
+ */
+export declare function ensureDshRunning(options: EnsureDshRunningOptions): Promise<EnsureDshRunningResult>;
+//# sourceMappingURL=bootstrap.d.ts.map

package/lib/types/cli/bootstrap.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"bootstrap.d.ts","sourceRoot":"","sources":["../../../src/cli/bootstrap.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;GAgBG;AAOH,OAAO,KAAK,EAAE,QAAQ,EAAE,QAAQ,EAAE,MAAM,aAAa,CAAA;AACrD,OAAO,EAAsB,kBAAkB,EAAE,MAAM,iBAAiB,CAAA;AACxE,OAAO,KAAK,EAAE,YAAY,EAAE,eAAe,EAAqC,MAAM,iBAAiB,CAAA;AAEvG,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,WAAW,CAAA;AAM9C,MAAM,WAAW,iBAAiB;IAChC,4EAA4E;IAC5E,OAAO,EAAE,MAAM,EAAE,CAAA;IACjB,oDAAoD;IACpD,WAAW,EAAE,MAAM,EAAE,CAAA;CACtB;AAED,MAAM,WAAW,WAAW;IAC1B,SAAS,CAAC,QAAQ,EAAE,MAAM,EAAE,OAAO,EAAE,SAAS,MAAM,EAAE,EAAE,YAAY,EAAE,MAAM,GAAG,OAAO,CAAC,MAAM,CAAC,CAAA;IAC9F,WAAW,CAAC,QAAQ,EAAE,MAAM,EAAE,OAAO,EAAE,SAAS,MAAM,EAAE,EAAE,cAAc,EAAE,SAAS,MAAM,EAAE,EAAE,gBAAgB,CAAC,EAAE,OAAO,GAAG,OAAO,CAAC,iBAAiB,CAAC,CAAA;IACpJ,SAAS,CAAC,QAAQ,EAAE,MAAM,EAAE,YAAY,CAAC,EAAE,MAAM,EAAE,QAAQ,CAAC,EAAE,CAAC,KAAK,EAAE,MAAM,KAAK,MAAM,GAAG,SAAS,GAAG,OAAO,CAAC,MAAM,CAAC,CAAA;IACrH,OAAO,CAAC,QAAQ,EAAE,MAAM,EAAE,UAAU,CAAC,EAAE,OAAO,GAAG,OAAO,CAAC,OAAO,CAAC,CAAA;IACjE,KAAK,IAAI,IAAI,CAAA;CACd;AAED;;0DAE0D;AAC1D,qBAAa,0BAA2B,SAAQ,KAAK;IACnD,QAAQ,CAAC,UAAU,EAAE,MAAM,CAAA;gBAEf,UAAU,EAAE,MAAM;CAK/B;AAED;6DAC6D;AAC7D,wBAAgB,oBAAoB,CAAC,IAAI,EAAE;IAAE,OAAO,EAAE;QAAE,GAAG,EAAE,OAAO,CAAA;KAAE,CAAA;CAAE,EAAE,KAAK,EAAE,OAAO,GAAG,OAAO,CAEjG;AAED;;;;;GAKG;AACH,wBAAsB,YAAY,CAAC,CAAC,EAAE,MAAM,EAAE;IAC5C,UAAU,EAAE,MAAM,CAAA;IAClB,WAAW,EAAE,OAAO,CAAA;IACpB,QAAQ,EAAE,CAAC,GAAG,SAAS,CAAA;IACvB,GAAG,EAAE,MAAM,OAAO,CAAC,CAAC,CAAC,CAAA;CACtB,GAAG,OAAO,CAAC,CAAC,CAAC,CAIb;AAED;;;;GAIG;AACH,wBAAgB,sBAAsB,CAAC,KAAK,CAAC,EAAE,QAAQ,EAAE,MAAM,CAAC,EAAE,QAAQ,EAAE,CAAC,CAAC,EAAE,aAAa,GAAG,WAAW,CA8F1G;AAMD,MAAM,WAAW,gBAAgB;IAC/B,IAAI,EAAE,MAAM,CAAA;IACZ,SAAS,EAAE,OAAO,CAAA;CACnB;AAqBD;;;;;;GAMG;AACH,wBAAgB,qBAAqB,CAAC,OAAO,EAAE,MAAM,GAAG,gBAAgB,EAAE,CAmBzE;AAqBD,MAAM,WAAW,4BAA4B;IAC3C,OAAO,EAAE,MAAM,CAAA;IACf;yEACqE;IACrE,WAAW,CAAC,EAAE,SAAS,MAAM,EAAE,CAAA;IAC/B,yEAAyE;IACzE,WAAW,CAAC,EAAE,OAAO,CAAA;IACrB,QAAQ,CAAC,EAAE,WAAW,CAAA;IACtB,8EAA8E;IAC9E,YAAY,CAAC,EAAE,CAAC,OAAO,EAAE,MAAM,EAAE,IAAI,EAAE,SAAS,MAAM,EAAE,KAAK,OAAO,CAAC,MAAM,CAAC,CAAA;IAC5E,MAAM,CAAC,EAAE;QAAE,KAAK,CAAC,IAAI,EAAE,MAAM,GAAG,IAAI,CAAA;KAAE,CAAA;IACtC,CAAC,CAAC,EAAE,aAAa,CAAA;CAClB;AAED,MAAM,WAAW,2BAA2B;IAC1C,EAAE,EAAE,OAAO,CAAA;IACX,IAAI,EAAE,IAAI,GAAG,iBAAiB,GAAG,gBAAgB,GAAG,aAAa,CAAA;IACjE,uEAAuE;IACvE,OAAO,EAAE,MAAM,EAAE,CAAA;IACjB,gEAAgE;IAChE,gBAAgB,EAAE,MAAM,GAAG,SAAS,CAAA;IACpC,uDAAuD;IACvD,YAAY,EAAE,MAAM,EAAE,CAAA;IACtB,UAAU,EAAE,MAAM,GAAG,QAAQ,GAAG,SAAS,GAAG,mBAAmB,CAAA;IAC/D,aAAa,CAAC,EAAE,MAAM,CAAA;IACtB,aAAa,CAAC,EAAE,MAAM,CAAA;CACvB;AAED;;;;;;;;;GASG;AACH,wBAAsB,qBAAqB,CAAC,OAAO,EAAE,4BAA4B,GAAG,OAAO,CAAC,2BAA2B,CAAC,CAoEvH;AAMD,MAAM,WAAW,eAAe;IAC9B,IAAI,EAAE,MAAM,CAAA;IACZ,MAAM,EAAE,MAAM,CAAA;CACf;AAED,MAAM,MAAM,SAAS,GAAG,CAAC,OAAO,EAAE,MAAM,EAAE,IAAI,EAAE,SAAS,MAAM,EAAE,KAAK,OAAO,CAAC,eAAe,CAAC,CAAA;AAE9F,MAAM,WAAW,uBAAuB;IACtC,OAAO,EAAE,MAAM,CAAA;IACf,qEAAqE;IACrE,UAAU,CAAC,EAAE,MAAM,GAAG,QAAQ,CAAA;IAC9B;4CACwC;IACxC,gBAAgB,CAAC,EAAE,MAAM,CAAA;IACzB,uDAAuD;IACvD,WAAW,CAAC,EAAE,MAAM,CAAA;IACpB,4DAA4D;IAC5D,cAAc,CAAC,EAAE,MAAM,CAAA;IACvB,iEAAiE;IACjE,QAAQ,CAAC,EAAE,MAAM,CAAC,QAAQ,CAAA;IAC1B,0EAA0E;IAC1E,GAAG,CAAC,EAAE,MAAM,CAAA;IACZ,gEAAgE;IAChE,SAAS,CAAC,EAAE,SAAS,CAAA;IACrB,qEAAqE;IACrE,QAAQ,CAAC,EAAE,OAAO,kBAAkB,CAAA;IACpC,2EAA2E;IAC3E,YAAY,CAAC,EAAE,MAAM,CAAA;IACrB,oEAAoE;IACpE,aAAa,CAAC,EAAE,MAAM,CAAA;IACtB,MAAM,CAAC,EAAE;QAAE,KAAK,CAAC,IAAI,EAAE,MAAM,GAAG,IAAI,CAAA;KAAE,CAAA;IACtC,CAAC,CAAC,EAAE,aAAa,CAAA;CAClB;AAED,MAAM,MAAM,sBAAsB,GAC9B;IAAE,OAAO,EAAE,IAAI,CAAC;IAAC,MAAM,EAAE,YAAY,CAAC;IAAC,UAAU,EAAE,MAAM,CAAC;IAAC,IAAI,EAAE,eAAe,CAAA;CAAE,GAClF;IAAE,OAAO,EAAE,KAAK,CAAC;IAAC,OAAO,EAAE,mBAAmB,GAAG,WAAW,GAAG,SAAS,CAAC;IAAC,OAAO,EAAE,MAAM,CAAA;CAAE,CAAA;AAwF/F;;;;;;;GAOG;AACH,wBAAsB,gBAAgB,CAAC,OAAO,EAAE,uBAAuB,GAAG,OAAO,CAAC,sBAAsB,CAAC,CAgExG"}

package/lib/types/cli/command-setup.d.ts

@@ -0,0 +1,72 @@
+/**
+ * CLI-5: the `setup` end-to-end wizard — the web three-step wizard
+ * (`GatewayWizard.tsx`) rendered onto a terminal, in one interactive /
+ * parametric state machine: command-line-provided answers are taken as-is,
+ * missing ones are asked in a TTY run and raise MissingRequiredOptionError
+ * in a `--yes` / headless run.
+ *
+ * Preflight (SPEC §4) runs FIRST and always: discover the plugin's IPC
+ * socket — when nothing live answers (or `--profile` was given explicitly)
+ * the multi-select profile install runs, then `ensureDshRunning` brings a
+ * DSH up (daemon trigger + bounded poll). Everything after that goes through
+ * THAT live IPC client.
+ *
+ * Step 1 is the role. Switching mirrors GatewayWizard.tsx's discipline
+ * exactly: host → client stops the managed Caddy / Cloudflare tunnel through
+ * their IPC stop routes BEFORE writing `role: 'client'`, then polls ping
+ * until `connects`; client → host writes `role: 'host'` and polls until
+ * `serves` (the row reloads under the CLI — the hot-swap socket never
+ * drops).
+ *
+ * Steps 2 & 3 are NOT reimplementations: the host branch drives
+ * `runHostIngressStartCommand` / `runHostIngressVerifyCommand` (mode
+ * switch cleanup, snippets, three lights, QR) and the client branch drives
+ * `runClientPairCommand` / `runClientUnpairCommand` (claim, handshake lights,
+ * removal) — the same code `host *` / `client *` use, over a synthesized
+ * argv. `setup`'s own additions are only the flow around them: the
+ * keep-current-config choice, the two-question recommendation funnel, the
+ * retry menu after a failed verification, the desktop-client pairing
+ * follow-up, and the paired-host management menu.
+ */
+import type { ParsedCliArgs } from './args.js';
+import type { CliPrompter, ExecProbe } from './bootstrap.js';
+import { discoverCliSockets } from './ipc-client.js';
+import type { CliTranslator } from './i18n.js';
+/** Everything `runSetupCommand` needs beyond a plain command context: the
+ * preflight owns discovery and launch, so it takes the same injectable
+ * seams `main.ts` collected (SPEC's test seam three). */
+export interface SetupCommandContext {
+    args: ParsedCliArgs;
+    dshHome: string;
+    /** TTY && !`--yes`, decided once by the entry point. */
+    interactive: boolean;
+    t: CliTranslator;
+    stdout: {
+        write(text: string): void;
+    };
+    /** Present whenever the run may prompt. */
+    prompter?: CliPrompter;
+    /** Poll-interval seam (role-switch wait, shared with the driven commands). */
+    pollIntervalMs?: number;
+    /** Ctrl-C seam — forwarded into the verify wait. */
+    abortSignal?: AbortSignal;
+    now?: () => Date;
+    cwd?: string;
+    /** Discover seam (tests stage socket states per call). */
+    discover?: typeof discoverCliSockets;
+    /** `dsh plugin add` runner seam. */
+    spawnCommand?: (command: string, args: readonly string[]) => Promise<number>;
+    /** Daemon probe/trigger seam. */
+    execProbe?: ExecProbe;
+    platform?: NodeJS.Platform;
+    uid?: number;
+    macosAppPath?: string;
+    systemUnitDir?: string;
+}
+/**
+ * `dsh-zen-remote setup` — preflight, step 1 (role + switch sync), then the
+ * role's steps 2 & 3. Missing required answers in a headless run throw
+ * MissingRequiredOptionError for the entry point to render.
+ */
+export declare function runSetupCommand(ctx: SetupCommandContext): Promise<number>;
+//# sourceMappingURL=command-setup.d.ts.map

package/lib/types/cli/command-setup.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"command-setup.d.ts","sourceRoot":"","sources":["../../../src/cli/command-setup.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA6BG;AAGH,OAAO,KAAK,EAAc,aAAa,EAAE,MAAM,WAAW,CAAA;AAE1D,OAAO,KAAK,EAAE,WAAW,EAAE,SAAS,EAAE,MAAM,gBAAgB,CAAA;AAC5D,OAAO,EAAE,kBAAkB,EAAE,MAAM,iBAAiB,CAAA;AAIpD,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,WAAW,CAAA;AAa9C;;yDAEyD;AACzD,MAAM,WAAW,mBAAmB;IAClC,IAAI,EAAE,aAAa,CAAA;IACnB,OAAO,EAAE,MAAM,CAAA;IACf,wDAAwD;IACxD,WAAW,EAAE,OAAO,CAAA;IACpB,CAAC,EAAE,aAAa,CAAA;IAChB,MAAM,EAAE;QAAE,KAAK,CAAC,IAAI,EAAE,MAAM,GAAG,IAAI,CAAA;KAAE,CAAA;IACrC,2CAA2C;IAC3C,QAAQ,CAAC,EAAE,WAAW,CAAA;IACtB,8EAA8E;IAC9E,cAAc,CAAC,EAAE,MAAM,CAAA;IACvB,oDAAoD;IACpD,WAAW,CAAC,EAAE,WAAW,CAAA;IACzB,GAAG,CAAC,EAAE,MAAM,IAAI,CAAA;IAChB,GAAG,CAAC,EAAE,MAAM,CAAA;IACZ,0DAA0D;IAC1D,QAAQ,CAAC,EAAE,OAAO,kBAAkB,CAAA;IACpC,oCAAoC;IACpC,YAAY,CAAC,EAAE,CAAC,OAAO,EAAE,MAAM,EAAE,IAAI,EAAE,SAAS,MAAM,EAAE,KAAK,OAAO,CAAC,MAAM,CAAC,CAAA;IAC5E,iCAAiC;IACjC,SAAS,CAAC,EAAE,SAAS,CAAA;IACrB,QAAQ,CAAC,EAAE,MAAM,CAAC,QAAQ,CAAA;IAC1B,GAAG,CAAC,EAAE,MAAM,CAAA;IACZ,YAAY,CAAC,EAAE,MAAM,CAAA;IACrB,aAAa,CAAC,EAAE,MAAM,CAAA;CACvB;AA2YD;;;;GAIG;AACH,wBAAsB,eAAe,CAAC,GAAG,EAAE,mBAAmB,GAAG,OAAO,CAAC,MAAM,CAAC,CA2D/E"}

package/lib/types/cli/commands-client.d.ts

@@ -0,0 +1,36 @@
+/**
+ * CLI-3: the `client` subcommand family — `pair`, `unpair`, `list`. Every
+ * entry point passes the connectsRole gate FIRST (the task discipline: a
+ * host never dials a remote host; the message names the `setup --role
+ * client` switch), then drives the plugin's own pairing routes over IPC —
+ * the CLI never touches the relay pool or the state file directly, the
+ * plugin process stays the single owner.
+ *
+ * Interactivity follows the bootstrap iron rule: a missing value prompts in
+ * a TTY run, and a non-interactive run throws MissingRequiredOptionError
+ * immediately — except the one retry the SPEC pins: a WRONG pairing code in
+ * an interactive run falls back to re-asking ONLY the code, the already
+ * entered address stays put.
+ */
+import type { CliExecutionContext } from './context.js';
+/**
+ * `client list [--json]` — the paired-host table. `--json` echoes the pool
+ * status's own servers array verbatim (the machine-readable truth), the
+ * terminal mode prints the header count and one line per host.
+ */
+export declare function runClientListCommand(ctx: CliExecutionContext): Promise<number>;
+/**
+ * `client pair [hostUrl] [--code <8位码>] [--name <本机名>] [--json]` — the
+ * full pairing flow: local address validation, name sync through the
+ * anti-shadowing config writer, the claim round-trip (with the SPEC's
+ * code-only retry in interactive runs), and the bounded wait for `online`.
+ */
+export declare function runClientPairCommand(ctx: CliExecutionContext): Promise<number>;
+/**
+ * `client unpair [<hostUrl|entryId>|--all] [--yes] [--json]` — a target is
+ * matched against the pool's own status rows (entry id first, then the
+ * normalized address); `--all` needs `--yes` outside a TTY confirm; no
+ * target at all in an interactive run picks from the current list.
+ */
+export declare function runClientUnpairCommand(ctx: CliExecutionContext): Promise<number>;
+//# sourceMappingURL=commands-client.d.ts.map

package/lib/types/cli/commands-client.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"commands-client.d.ts","sourceRoot":"","sources":["../../../src/cli/commands-client.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;GAaG;AAKH,OAAO,KAAK,EAAE,mBAAmB,EAAE,MAAM,cAAc,CAAA;AA+DvD;;;;GAIG;AACH,wBAAsB,oBAAoB,CAAC,GAAG,EAAE,mBAAmB,GAAG,OAAO,CAAC,MAAM,CAAC,CA0BpF;AAqFD;;;;;GAKG;AACH,wBAAsB,oBAAoB,CAAC,GAAG,EAAE,mBAAmB,GAAG,OAAO,CAAC,MAAM,CAAC,CAkDpF;AA6CD;;;;;GAKG;AACH,wBAAsB,sBAAsB,CAAC,GAAG,EAAE,mBAAmB,GAAG,OAAO,CAAC,MAAM,CAAC,CAgEtF"}

package/lib/types/cli/commands-host.d.ts

@@ -0,0 +1,82 @@
+/**
+ * CLI-4: the `host` subcommand family — `device pair|list|revoke` and
+ * `ingress start|stop|verify|snippet`. Every entry point passes the
+ * servesRole gate FIRST (the task discipline: a client never drives the
+ * server-owner surfaces; the message names the `setup` switch), then drives
+ * the plugin's own admin/wizard routes over IPC.
+ *
+ * The iron rule for ingress: the CLI NEVER spawns `caddy` or `cloudflared`
+ * itself — download, start, stop, status and the three-light verification
+ * all happen inside the plugin process through the
+ * `/_dsh/zen-remote/admin/wizard/*` routes (SPEC §1). Mode switches mirror
+ * `GatewayWizard.tsx`'s discipline: any managed ingress process that does
+ * not belong to the new mode is stopped through its stop route before the
+ * new mode's flow runs, managed caddy/cloudflared reset `host` back to
+ * `127.0.0.1`, and lan rebinds it to `0.0.0.0`.
+ *
+ * Interactivity follows the bootstrap iron rule: a missing value prompts in
+ * a TTY run and throws MissingRequiredOptionError otherwise — except the
+ * values with a SAVED fallback (domain, public URL), which the saved wizard
+ * status answers before any prompt.
+ */
+import type { CliExecutionContext } from './context.js';
+/** The anti-shadowing config write, reporting `env-shadowed` and generic
+ * failures through the translator. Shared with `command-setup.ts`'s role
+ * switch, which writes the same way. */
+export declare function writeConfigOrReport(ctx: CliExecutionContext, set: Record<string, unknown>): Promise<boolean>;
+/**
+ * `host device pair [--device-role web|desktop-client] [--json]` — mint one
+ * pairing code through the admin pair route and print it with everything
+ * the receiving side needs: the reachable URL (public URL, or the LAN
+ * address assembled with the gateway's actual port), a terminal QR for web
+ * devices, the copy-paste `client pair` command for desktop clients, and
+ * the code with its validity window (the gateway mints 10-minute codes).
+ */
+export declare function runHostDevicePairCommand(ctx: CliExecutionContext): Promise<number>;
+/**
+ * `host device list [--json]` — the gateway's device table. `--json` echoes
+ * the gateway's own devices array verbatim (the machine-readable truth);
+ * the terminal mode prints one line per device with its id, name, role,
+ * kind and the created / last-seen stamps.
+ */
+export declare function runHostDeviceListCommand(ctx: CliExecutionContext): Promise<number>;
+/**
+ * `host device revoke [<id>|--all] [--yes] [--json]` — one revoke POST per
+ * invocation. `--all` needs `--yes` outside a TTY confirm (the missing
+ * confirmation IS the missing required option); a missing target in an
+ * interactive run picks from the current list.
+ */
+export declare function runHostDeviceRevokeCommand(ctx: CliExecutionContext): Promise<number>;
+/**
+ * `host ingress snippet [--proxy nginx|caddy|lucky]` — the copy-paste
+ * reverse-proxy material for the external ingress mode. The upstream port
+ * is the gateway's ACTUAL port (a gateway that retried past its configured
+ * port must not hand out snippets pointing at the wrong place); the domain
+ * falls back to the example placeholder.
+ */
+export declare function runHostIngressSnippetCommand(ctx: CliExecutionContext): Promise<number>;
+/**
+ * `host ingress start [--mode …] …` — the four ingress modes, all driven
+ * through the plugin's wizard routes. The mode comes from the flags, then
+ * the saved config, then the interactive question; before the new mode's
+ * flow runs, every managed process that does not belong to it is stopped
+ * through its own stop route (GatewayWizard.tsx's discipline).
+ */
+export declare function runHostIngressStartCommand(ctx: CliExecutionContext): Promise<number>;
+/**
+ * `host ingress stop [--yes] [--json]` — stop both managed ingress
+ * processes through their stop routes (the CLI owns no process handles to
+ * reach for). `--yes` outside a TTY confirm, same discipline as revoke.
+ */
+export declare function runHostIngressStopCommand(ctx: CliExecutionContext): Promise<number>;
+/**
+ * `host ingress verify [--public-url <origin>] [--no-wait] [--json]` — the
+ * three-light check, driven entirely by the plugin's verify orchestration:
+ * POST mints the code and walks the public URL (lights 1 + 2), GET polls
+ * for the real phone pairing (light 3). `--no-wait` / `--json` stop after
+ * the first two lights; an aborted signal (the entry point's Ctrl-C seam)
+ * skips the wait gracefully with exit code 0 — the first two lights'
+ * verdict is already on the record.
+ */
+export declare function runHostIngressVerifyCommand(ctx: CliExecutionContext): Promise<number>;
+//# sourceMappingURL=commands-host.d.ts.map

package/lib/types/cli/commands-host.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"commands-host.d.ts","sourceRoot":"","sources":["../../../src/cli/commands-host.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;GAoBG;AAqBH,OAAO,KAAK,EAAE,mBAAmB,EAAE,MAAM,cAAc,CAAA;AAgDvD;;wCAEwC;AACxC,wBAAsB,mBAAmB,CAAC,GAAG,EAAE,mBAAmB,EAAE,GAAG,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,GAAG,OAAO,CAAC,OAAO,CAAC,CAclH;AAsED;;;;;;;GAOG;AACH,wBAAsB,wBAAwB,CAAC,GAAG,EAAE,mBAAmB,GAAG,OAAO,CAAC,MAAM,CAAC,CA2FxF;AAMD;;;;;GAKG;AACH,wBAAsB,wBAAwB,CAAC,GAAG,EAAE,mBAAmB,GAAG,OAAO,CAAC,MAAM,CAAC,CA4BxF;AAMD;;;;;GAKG;AACH,wBAAsB,0BAA0B,CAAC,GAAG,EAAE,mBAAmB,GAAG,OAAO,CAAC,MAAM,CAAC,CAkE1F;AAmED;;;;;;GAMG;AACH,wBAAsB,4BAA4B,CAAC,GAAG,EAAE,mBAAmB,GAAG,OAAO,CAAC,MAAM,CAAC,CAe5F;AAkWD;;;;;;GAMG;AACH,wBAAsB,0BAA0B,CAAC,GAAG,EAAE,mBAAmB,GAAG,OAAO,CAAC,MAAM,CAAC,CAkD1F;AAMD;;;;GAIG;AACH,wBAAsB,yBAAyB,CAAC,GAAG,EAAE,mBAAmB,GAAG,OAAO,CAAC,MAAM,CAAC,CA6BzF;AAwCD;;;;;;;;GAQG;AACH,wBAAsB,2BAA2B,CAAC,GAAG,EAAE,mBAAmB,GAAG,OAAO,CAAC,MAAM,CAAC,CAgJ3F"}

package/lib/types/cli/commands-status.d.ts

@@ -0,0 +1,46 @@
+/**
+ * CLI-3: the `status` command — one identity read (ping) plus whatever the
+ * role actually answers, rendered either as pretty JSON (`--json`) or as
+ * bilingual terminal lines. `--debug` is its own branch: fetch the plugin
+ * process's redacted diagnostic report over IPC and write it to a file
+ * (explicit path or a `zen-remote-debug-<role>-<yyyymmdd-hhmm>.json` in the
+ * working directory).
+ *
+ * Per SPEC the IPC channel only carries structured data — every terminal
+ * string is rendered here through the translator. The per-server line
+ * renderer is shared with `commands-client.ts` (`client list` prints the
+ * same rows), so the two surfaces cannot drift.
+ */
+import type { CliIpcRequestResult } from './ipc-client.js';
+import type { CliTranslator } from './i18n.js';
+import type { CliExecutionContext } from './context.js';
+/** One pool `servers` row (client/status), defensively typed — the command
+ * layer renders whatever shape arrived, it never trusts it. */
+export type ServerRow = Record<string, unknown>;
+/**
+ * Fetch one JSON object over IPC; every failure mode (transport error,
+ * error status, non-object body) is `null` — a broken surface means "no
+ * information" for a status view, never a failed command.
+ */
+export declare function fetchBody(run: () => Promise<CliIpcRequestResult>): Promise<ServerRow | null>;
+/** One plain JSON object, or null. */
+export declare function plainOf(value: unknown): ServerRow | null;
+/** The connection-state label: the three common states translated, the rest
+ * (revoked / incompatible / unpaired) each with their own word. */
+export declare function stateLabelOf(t: CliTranslator, value: unknown): string;
+/** The fingerprint-compat half of the compat/bridge column. */
+export declare function compatLabelOf(t: CliTranslator, value: unknown): string;
+/** The bridged-plugin half: how many of the row's plugins are bridged. */
+export declare function bridgeLabelOf(t: CliTranslator, value: unknown): string;
+/** One paired-host row, the exact shape both surfaces print:
+ * `[entryId] displayName  serverUrl  state  compat/bridge`. */
+export declare function serverLineText(t: CliTranslator, row: ServerRow): string;
+/**
+ * `dsh-zen-remote status [--json] [--debug [outPath]]`. Identity from one
+ * ping; the host surfaces (admin status, wizard status, share list) and the
+ * client pool status each fetched only when the role answers them. Exit
+ * codes: 0 on any answered status, 1 when the ping itself or the debug
+ * round-trip failed.
+ */
+export declare function runStatusCommand(ctx: CliExecutionContext): Promise<number>;
+//# sourceMappingURL=commands-status.d.ts.map

package/lib/types/cli/commands-status.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"commands-status.d.ts","sourceRoot":"","sources":["../../../src/cli/commands-status.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;GAYG;AAOH,OAAO,KAAK,EAAE,mBAAmB,EAAE,MAAM,iBAAiB,CAAA;AAE1D,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,WAAW,CAAA;AAC9C,OAAO,KAAK,EAAE,mBAAmB,EAAE,MAAM,cAAc,CAAA;AAEvD;+DAC+D;AAC/D,MAAM,MAAM,SAAS,GAAG,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAA;AAE/C;;;;GAIG;AACH,wBAAsB,SAAS,CAAC,GAAG,EAAE,MAAM,OAAO,CAAC,mBAAmB,CAAC,GAAG,OAAO,CAAC,SAAS,GAAG,IAAI,CAAC,CAQlG;AAED,sCAAsC;AACtC,wBAAgB,OAAO,CAAC,KAAK,EAAE,OAAO,GAAG,SAAS,GAAG,IAAI,CAIxD;AAcD;mEACmE;AACnE,wBAAgB,YAAY,CAAC,CAAC,EAAE,aAAa,EAAE,KAAK,EAAE,OAAO,GAAG,MAAM,CAUrE;AAED,+DAA+D;AAC/D,wBAAgB,aAAa,CAAC,CAAC,EAAE,aAAa,EAAE,KAAK,EAAE,OAAO,GAAG,MAAM,CAOtE;AAED,0EAA0E;AAC1E,wBAAgB,aAAa,CAAC,CAAC,EAAE,aAAa,EAAE,KAAK,EAAE,OAAO,GAAG,MAAM,CAItE;AAED;+DAC+D;AAC/D,wBAAgB,cAAc,CAAC,CAAC,EAAE,aAAa,EAAE,GAAG,EAAE,SAAS,GAAG,MAAM,CAGvE;AAuJD;;;;;;GAMG;AACH,wBAAsB,gBAAgB,CAAC,GAAG,EAAE,mBAAmB,GAAG,OAAO,CAAC,MAAM,CAAC,CAuChF"}

package/lib/types/cli/config-writer.d.ts

@@ -0,0 +1,92 @@
+/**
+ * The CLI's anti-shadowing config writer (CLI-1).
+ *
+ * `resolveConfig` reads four layers in the order env > row > file > default
+ * (src/config.ts). A CLI write lands in the FILE layer
+ * (`<dshHome>/lan-gate.config.json`), so two layers can silently swallow it:
+ * an environment variable set at the top, and a value the loader put on the
+ * plugin row (persisted in the current profile's `cordis.patch.yml`). The
+ * writer refuses the first case with the exact variable name, and REMOVES the
+ * shadowing keys in the other two — the in-memory row object `apply()` still
+ * holds, and the `dsh-zen-remote` `config:` block of every profile patch file
+ * it can find — so the just-written file value is what the next
+ * `resolveConfig` answers. `onAfterWrite` then lets the caller (the IPC
+ * delegate in src/index.ts) trigger the restart watcher immediately, so a
+ * restart-required field reloads the row without waiting out the 2s poll.
+ *
+ * The file is read from `dshHome` DIRECTLY, not through `readFileConfig(env)`:
+ * the latter resolves `<env.DSH_HOME ?? ~/.dsh>` and would silently read the
+ * developer's real file when a test passes an explicit dshHome with an empty
+ * env — resolution and the write must never disagree about which file is the
+ * truth.
+ *
+ * The `cordis.patch.yml` edit is line-based on purpose: the files are
+ * user-owned YAML full of comments and hand-tuned formatting that a
+ * parse-serialize round trip would destroy, and the edit itself (delete a
+ * key line and its indented children from one plugin's config block) is a
+ * purely textual operation.
+ */
+import type { ZenRemoteConfig } from '../config.js';
+/**
+ * The env variable each config field answers to, for fields that HAVE one.
+ * Fields without an entry (role, serverName, idleHours, the wizard's ingress
+ * fields, pluginBridgeConsent — src/config.ts explains each absence) can
+ * never be env-shadowed, so they are deliberately missing: `writeCliConfig`
+ * falls back to the field name itself when asked for one.
+ */
+export declare const ENV_VAR_BY_FIELD: Readonly<Partial<Record<keyof ZenRemoteConfig, string>>>;
+export interface WriteCliConfigOptions {
+    /** The DSH home the config files live under (`lan-gate.config.json`,
+     * `profiles/<name>/cordis.patch.yml`). Authoritative — env.DSH_HOME is
+     * not consulted. */
+    dshHome: string;
+    /** The profile whose `cordis.patch.yml` is scanned FIRST; the fallback
+     * scan over every `<dshHome>/profiles/<name>/cordis.patch.yml` runs
+     * besides it, so an un-named profile carrying a stale key is un-shadowed
+     * too. */
+    profileName?: string | undefined;
+    /** The plugin row as `apply()` received it (volatile `{ get() }` wrappers
+     * included). Shadowing keys on it are DELETED so the file layer shows
+     * through; omit on a composition without a row. */
+    row?: Record<string, unknown> | undefined;
+    /** The environment carrying `LAN_GATE_*` / `DSH_PUSH_*`; defaults to
+     * `process.env`. */
+    env?: NodeJS.ProcessEnv | undefined;
+    /** Keys to merge into `lan-gate.config.json` (and un-shadow everywhere). */
+    set?: Record<string, unknown> | undefined;
+    /** Keys to delete from `lan-gate.config.json` (and un-shadow everywhere). */
+    unset?: readonly string[] | undefined;
+    /** Called AFTER every successful write (never on a refusal and never for
+     * an empty write) — the IPC delegate passes the restart watcher's
+     * `checkNow`, which reloads the row at once when a restart-required field
+     * moved. */
+    onAfterWrite?: (() => void) | undefined;
+}
+export type WriteCliConfigResult = {
+    ok: true;
+    values: ZenRemoteConfig;
+} | {
+    ok: false;
+    code: 'env-shadowed';
+    field: string;
+    envVar: string;
+};
+export declare function applyUnshadowedRowKeys(dshHome: string, row: Record<string, unknown> | undefined): void;
+export declare function clearUnshadowedRowKeys(dshHome: string, keys: readonly string[]): void;
+/**
+ * Remove `keys` from EVERY `- id: dsh-zen-remote` (or bare `id:`) entry's
+ * `config:` block, purely textually: a key line and its deeper-indented
+ * children disappear, every other line — comments, other plugins' blocks,
+ * formatting — survives byte for byte. A block emptied by the removal keeps
+ * a `config: {}` line (an entry with no config key at all changes loader
+ * semantics). No match, no change: the same string comes back.
+ */
+export declare function unshadowPatchYml(text: string, keys: readonly string[]): string;
+/**
+ * Write CLI config changes through the anti-shadowing pipeline. Returns the
+ * refused `env-shadowed` verdict (with the exact field and its variable
+ * name) WITHOUT touching any file, or the freshly resolved effective values
+ * after the write, the row-key deletions and the patch-file un-shadowing.
+ */
+export declare function writeCliConfig(options: WriteCliConfigOptions): WriteCliConfigResult;
+//# sourceMappingURL=config-writer.d.ts.map

package/lib/types/cli/config-writer.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"config-writer.d.ts","sourceRoot":"","sources":["../../../src/cli/config-writer.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;GA2BG;AAKH,OAAO,KAAK,EAAgB,eAAe,EAAE,MAAM,cAAc,CAAA;AAEjE;;;;;;GAMG;AACH,eAAO,MAAM,gBAAgB,EAAE,QAAQ,CAAC,OAAO,CAAC,MAAM,CAAC,MAAM,eAAe,EAAE,MAAM,CAAC,CAAC,CAerF,CAAA;AAED,MAAM,WAAW,qBAAqB;IACpC;;wBAEoB;IACpB,OAAO,EAAE,MAAM,CAAA;IACf;;;cAGU;IACV,WAAW,CAAC,EAAE,MAAM,GAAG,SAAS,CAAA;IAChC;;uDAEmD;IACnD,GAAG,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,GAAG,SAAS,CAAA;IACzC;wBACoB;IACpB,GAAG,CAAC,EAAE,MAAM,CAAC,UAAU,GAAG,SAAS,CAAA;IACnC,4EAA4E;IAC5E,GAAG,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,GAAG,SAAS,CAAA;IACzC,6EAA6E;IAC7E,KAAK,CAAC,EAAE,SAAS,MAAM,EAAE,GAAG,SAAS,CAAA;IACrC;;;gBAGY;IACZ,YAAY,CAAC,EAAE,CAAC,MAAM,IAAI,CAAC,GAAG,SAAS,CAAA;CACxC;AAED,MAAM,MAAM,oBAAoB,GAC5B;IAAE,EAAE,EAAE,IAAI,CAAC;IAAC,MAAM,EAAE,eAAe,CAAA;CAAE,GACrC;IAAE,EAAE,EAAE,KAAK,CAAC;IAAC,IAAI,EAAE,cAAc,CAAC;IAAC,KAAK,EAAE,MAAM,CAAC;IAAC,MAAM,EAAE,MAAM,CAAA;CAAE,CAAA;AAetE,wBAAgB,sBAAsB,CAAC,OAAO,EAAE,MAAM,EAAE,GAAG,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,GAAG,SAAS,GAAG,IAAI,CAUtG;AAED,wBAAgB,sBAAsB,CAAC,OAAO,EAAE,MAAM,EAAE,IAAI,EAAE,SAAS,MAAM,EAAE,GAAG,IAAI,CAIrF;AAoED;;;;;;;GAOG;AACH,wBAAgB,gBAAgB,CAAC,IAAI,EAAE,MAAM,EAAE,IAAI,EAAE,SAAS,MAAM,EAAE,GAAG,MAAM,CAsF9E;AAED;;;;;GAKG;AACH,wBAAgB,cAAc,CAAC,OAAO,EAAE,qBAAqB,GAAG,oBAAoB,CAgEnF"}

package/lib/types/cli/context.d.ts

@@ -0,0 +1,39 @@
+/**
+ * CLI-3: the execution context every command function receives. One bag with
+ * everything a command needs but never constructs itself — the parsed
+ * grammar, the live IPC client, the translator, and the interactivity
+ * verdict — plus the seams tests inject (a clock, a poll interval, an
+ * alternate working directory). Pure types: the real builder is CLI-5's
+ * main.ts; the tests assemble the object literal directly.
+ */
+import type { ParsedCliArgs } from './args.js';
+import type { CliIpcClient } from './ipc-client.js';
+import type { CliTranslator } from './i18n.js';
+import type { CliPrompter } from './bootstrap.js';
+export interface CliExecutionContext {
+    /** The command and options this run parsed. */
+    args: ParsedCliArgs;
+    /** A client bound to the discovered live IPC socket. */
+    ipc: CliIpcClient;
+    /** The translator for this run's language. */
+    t: CliTranslator;
+    /** TTY && !`--yes`, decided once by the entry point (isInteractiveSession). */
+    interactive: boolean;
+    /** The ask-everything funnel; present whenever the run may prompt. */
+    prompter?: CliPrompter;
+    stdout: {
+        write(text: string): void;
+    };
+    /** Clock for the `status --debug` default filename; default `new Date()`. */
+    now?: () => Date;
+    /** Working directory for that default path; default `process.cwd()`. */
+    cwd?: string;
+    /** `client pair`'s online-wait poll interval (default 250ms; tests shrink
+     * it — the 10s budget itself stays fixed). */
+    pollIntervalMs?: number;
+    /** `host ingress verify`'s Ctrl-C seam: the entry point (CLI-5's main)
+     * aborts it on SIGINT so the phone-pairing wait can be skipped gracefully;
+     * tests abort it directly. */
+    abortSignal?: AbortSignal;
+}
+//# sourceMappingURL=context.d.ts.map

package/lib/types/cli/context.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"context.d.ts","sourceRoot":"","sources":["../../../src/cli/context.ts"],"names":[],"mappings":"AAAA;;;;;;;GAOG;AAEH,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,WAAW,CAAA;AAC9C,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,iBAAiB,CAAA;AACnD,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,WAAW,CAAA;AAC9C,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,gBAAgB,CAAA;AAEjD,MAAM,WAAW,mBAAmB;IAClC,+CAA+C;IAC/C,IAAI,EAAE,aAAa,CAAA;IACnB,wDAAwD;IACxD,GAAG,EAAE,YAAY,CAAA;IACjB,8CAA8C;IAC9C,CAAC,EAAE,aAAa,CAAA;IAChB,+EAA+E;IAC/E,WAAW,EAAE,OAAO,CAAA;IACpB,sEAAsE;IACtE,QAAQ,CAAC,EAAE,WAAW,CAAA;IACtB,MAAM,EAAE;QAAE,KAAK,CAAC,IAAI,EAAE,MAAM,GAAG,IAAI,CAAA;KAAE,CAAA;IACrC,6EAA6E;IAC7E,GAAG,CAAC,EAAE,MAAM,IAAI,CAAA;IAChB,wEAAwE;IACxE,GAAG,CAAC,EAAE,MAAM,CAAA;IACZ;kDAC8C;IAC9C,cAAc,CAAC,EAAE,MAAM,CAAA;IACvB;;kCAE8B;IAC9B,WAAW,CAAC,EAAE,WAAW,CAAA;CAC1B"}

package/lib/types/cli/i18n.d.ts

@@ -0,0 +1,32 @@
+/**
+ * CLI-2 bilingual dictionary and language resolution. Per SPEC the IPC
+ * channel only ever carries machine-readable codes and structured data —
+ * every terminal string the user sees is rendered HERE, on the CLI side, in
+ * the selected language. Placeholder syntax is `{name}`, filled from the
+ * `params` argument.
+ *
+ * Vocabulary discipline (SPEC): the copy speaks ONLY of `host` / `client` /
+ * `peer` — `server` / `both` and similar aliases must not leak into any
+ * string, in either language. The test file scans both tables for the banned
+ * English words to keep it that way.
+ */
+export type CliLang = 'zh' | 'en';
+export type CliTranslator = ((key: string, params?: Record<string, string | number>) => string) & {
+    /** The language's raw table, for tests and for key inventory checks. */
+    readonly keys: Readonly<Record<string, string>>;
+};
+/**
+ * Resolve the CLI language: `--lang` wins (`zh` / `en`; `auto` and unknown
+ * values fall through), then `ZEN_REMOTE_LANG`, then the locale variables in
+ * the standard `LC_ALL` > `LC_MESSAGES` > `LANG` order — anything matching
+ * `/^zh/i` is Chinese, everything else (including `C`, `POSIX`, empty) is
+ * English.
+ */
+export declare function resolveCliLang(flagLang: string | undefined, env?: NodeJS.ProcessEnv): CliLang;
+/**
+ * Build a translator for `lang`. Missing keys fall back to the English table
+ * and then to the key itself — a forgotten key must be VISIBLE in the output,
+ * never silently empty.
+ */
+export declare function createTranslator(lang: CliLang): CliTranslator;
+//# sourceMappingURL=i18n.d.ts.map

package/lib/types/cli/i18n.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"i18n.d.ts","sourceRoot":"","sources":["../../../src/cli/i18n.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;GAWG;AAEH,MAAM,MAAM,OAAO,GAAG,IAAI,GAAG,IAAI,CAAA;AAEjC,MAAM,MAAM,aAAa,GAAG,CAAC,CAAC,GAAG,EAAE,MAAM,EAAE,MAAM,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,GAAG,MAAM,CAAC,KAAK,MAAM,CAAC,GAAG;IAChG,wEAAwE;IACxE,QAAQ,CAAC,IAAI,EAAE,QAAQ,CAAC,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC,CAAA;CAChD,CAAA;AA8kBD;;;;;;GAMG;AACH,wBAAgB,cAAc,CAAC,QAAQ,EAAE,MAAM,GAAG,SAAS,EAAE,GAAG,CAAC,EAAE,MAAM,CAAC,UAAU,GAAG,OAAO,CAU7F;AAED;;;;GAIG;AACH,wBAAgB,gBAAgB,CAAC,IAAI,EAAE,OAAO,GAAG,aAAa,CAY7D"}