dsh-ssh-tui 0.6.2 → 0.6.3

package/lib/types/preset-label.d.ts

@@ -0,0 +1,38 @@
+/**
+ * Agent-preset display names, and the profile row the terminal `/mode` needs.
+ *
+ * A shipped preset's name resolves through the id-keyed dictionary this module
+ * owns — the same rule `@deepseek-ai/dsh-agent-presets/display` applies on the
+ * browser surface — so `/language` reaches the picker, the banner, and
+ * `/status`. A user-authored preset keeps the name its own `preset.yml`
+ * published: that metadata is never translated.
+ *
+ * A terminal profile built on `dsh-base` composes no preset roster, and this
+ * plugin's own bundle patch may not mount one (DSH STORE accepts additive
+ * plugin-owned rows only), so the profile's user layer owns the row. When it is
+ * absent `/mode` reports the exact repair instead of a dead end.
+ * @module dsh-ssh-tui/preset-label
+ */
+/** Whether this id belongs to the shipped, translatable roster. */
+export declare function isShippedPreset(id: string): boolean;
+/**
+ * Resolve the name a picker, banner, or report renders for one preset.
+ *
+ * A published name equal to the id is the roster's own "no metadata" answer,
+ * not a name, so it falls through to the dictionary or back to the id.
+ * @param id - the preset id, also the last-resort label.
+ * @param name - display name the preset published, when it published one.
+ * @param trust - `user` keeps published metadata; anything else (including an
+ *   unknown trust) resolves a shipped id through the dictionary.
+ * @returns the localized or published name, never empty.
+ */
+export declare function presetLabel(id: string, name?: string, trust?: string): string;
+/**
+ * The profile this process booted, from `--profile <name>` / `--profile=<name>`.
+ *
+ * The launcher passes the same arguments to the front end and to the Host it
+ * spawns (only `--resume`/`--new` are rewritten), so both report one profile.
+ * @param argv - the argument list to read.
+ * @returns the profile name, or the TUI's own default when none was named.
+ */
+export declare function profileFromArgv(argv?: readonly string[]): string;

package/lib/types/preset-rows.d.ts

@@ -0,0 +1,47 @@
+/**
+ * The profile patch that mounts the agent-preset roster `/mode` needs.
+ *
+ * A terminal profile built on `dsh-base` composes no preset roster (only the
+ * Web bundle does), and this plugin's own bundle patch may not mount one: DSH
+ * STORE accepts additive rows with plugin-owned ids and no `@deepseek-ai/*`
+ * module names. The profile's user layer is the supported home for the row, so
+ * both the install script and the running TUI write the same block here — the
+ * TUI needs it because `dsh plugin add dsh-ssh-tui@latest` (the in-app update
+ * path) never runs `scripts/`, which npm installs do not ship.
+ *
+ * The roster is not cosmetic: without it `/mode` cannot switch, and the tools
+ * the shipped presets own (`ask_user_question`, `present`, PTC's presentation)
+ * are absent from the agent's catalog.
+ * @module dsh-ssh-tui/preset-rows
+ */
+/**
+ * The exact profile patch block that mounts the roster and the two host
+ * services the shipped presets need. `scripts/ensure-profile-rows.sh` carries
+ * the same text; a test compares the two so they cannot drift.
+ */
+export declare const ROSTER_PATCH_BLOCK = "# dsh-ssh-tui /mode: the agent-preset roster (standard / minimal / PTC /\n# cordis, plus every preset under $DSH_HOME/.agent-presets) and the two host\n# services the shipped presets need. dsh-base composes no roster in a terminal\n# profile, and a third-party bundle patch may not mount an @deepseek-ai row, so\n# the profile's user layer owns them.\n- insert:\n    - id: agent-presets\n      name: '@deepseek-ai/dsh-agent-presets'\n      config:\n        default: standard\n\n    - id: code-runtime\n      name: '@deepseek-ai/dsh-code-runtime-worker-thread'\n\n    - id: subagent-model-selection-settings\n      name: '@deepseek-ai/dsh-tool-subagent/model-selection-settings'\n";
+/** The profile patch file the roster block belongs in. */
+export declare function rosterPatchPath(home: string, profile: string): string;
+/**
+ * The patch text with the roster block appended, or `undefined` when the file
+ * already names the roster row.
+ *
+ * A file that is exactly `[]` (the profile template) is replaced, so the result
+ * stays a valid top-level patch list; anything else keeps its content and the
+ * block is appended after a blank line.
+ * @param existing - the patch file's current text.
+ * @returns the new text, or `undefined` when nothing has to change.
+ */
+export declare function rosterPatchText(existing: string): string | undefined;
+/**
+ * Mount the roster in one profile, unless it is already composed.
+ *
+ * Idempotent: a profile whose patch already names the roster row (one bundling
+ * `@deepseek-ai/dsh-web-app`, for example) is left untouched. The write is a
+ * plain whole-file replace because the file is small and read once at boot; a
+ * half-written patch would only be seen by the next launch.
+ * @param home - the harness home carrying `profiles/`.
+ * @param profile - the profile to patch.
+ * @returns `present` when the row already exists, else `written`.
+ */
+export declare function ensureRosterRows(home: string, profile: string): Promise<'present' | 'written'>;

package/lib/types/reasoning.d.ts

@@ -2,11 +2,16 @@
  * Shared reasoning-effort defaults for the SSH TUI.
  *
  * OpenCode / third-party (llm-pi-ai) routes carry no adapter-level reasoning
- * default (unlike `llm-deepseek`, whose row declares `reasoningEffort: max`).
- * Without an explicit effort the model streams its thinking as plain `text`
- * chunks instead of `reasoning` blocks, so the TUI never receives the data
- * needed to render the collapsible `思考中` block. This helper picks a
+ * default. Without an explicit effort the model streams its thinking as plain
+ * `text` chunks instead of `reasoning` blocks, so the TUI never receives the
+ * data needed to render the collapsible `思考中` block. This helper picks a
  * supported default so the fold has data to show.
+ *
+ * `llm-deepseek` is not covered here: its adapter always reports a
+ * `defaultEffort`, which the LLM runtime materializes into the request on its
+ * own. Since the 0.5.1 STORE compliance trim dropped the bundle patch's
+ * `reasoningEffort: max` row override, that adapter default is `high` unless a
+ * deployment sets it (or `/effort` picks one, remembered per route).
  */
 import { type LlmRuntime, type ReasoningEffortId } from '@deepseek-ai/dsh-llm';
 /**

package/lib/types/tui.d.ts

@@ -63,6 +63,12 @@ export interface TuiConfig {
     presetId?: string;
     /** Display name of the active preset. */
     presetName?: string;
+    /**
+     * Trust of the root the active preset came from (`system`/`user`). A `user`
+     * preset keeps its own published name; a shipped one resolves through the
+     * locale dictionary.
+     */
+    presetTrust?: string;
     /** Notify the launcher of an explicit in-process selection change. */
     onSelectionChanged?: (selection: ModelSelection) => void;
     /**
@@ -568,6 +574,14 @@ export declare class SshTui {
     private runDisconnectCommand;
     /** /mode: pick an agent preset (standard / minimal / ptc / cordis / routing-suite / ...). */
     private runModeCommand;
+    /**
+     * `/mode fix`: write the roster row into this profile's user patch layer.
+     *
+     * The write only takes effect on the next launch — the loader composes the
+     * patch tree once at boot — so the report says so instead of pretending the
+     * running session gained a roster.
+     */
+    private repairRoster;
     /** Current provider route selected for the running agent. */
     private currentProvider;
     /** Resolve one credential reference without exposing its value. */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-ssh-tui",
-  "version": "0.6.2",
+  "version": "0.6.3",
   "description": "SSH-friendly interactive terminal TUI plugin for DeepSeek Harness",
   "keywords": [
     "deepseek-harness",