dsh-over-ssh 0.1.0 → 0.2.0

package/lib/types/src/client/roots/connection-test.d.ts

@@ -1,69 +0,0 @@
-/**
- * The 「测试」 button's state: one connection at a time, answer or failure, and nothing else.
- *
- * Kept out of the component (which is a pure template) and out of the roots editor (which owns the *file*):
- * this is transient UI state whose only job is to hold "what did the last probe say" long enough to render it.
- *
- * The probe itself runs on the host (a real connect plus one command); this module only carries the request and
- * narrows the answer, so the four fields it reads are the four the host whitelists  - an answer that grew a
- * field cannot reach the panel.
- *
- * @module dsh-over-ssh/client/connection-test
- */
-import type { MessageKey } from '../core/message.ts';
-import type { FetchLike } from './roots-panel.ts';
-/** Where one connection's probe stands. */
-/**
- * Where one connection's probe stands.
- *
- * `idle` is the state a row is in **before** anyone clicked  - the button must already be there (it is what the
- * user clicks), so "no answer yet" is a status, not a missing field.
- */
-export type ConnectionTestStatus = 'idle' | 'running' | 'ok' | 'failed';
-/** The last answer for one connection. */
-export interface ConnectionTestState {
-    readonly status: ConnectionTestStatus;
-    /** Transport the host actually used (`alias` / `ssh2` / `agent`), once it answered. */
-    readonly transport?: string;
-    /** Whether that transport was a degraded substitute. */
-    readonly degraded?: boolean;
-    /** Machine-readable failure code (`AUTH_FAILED`, `TIMEOUT`, …). */
-    readonly code?: string;
-    /** The host's own sentence about the failure (or the carrier's, e.g. `Failed to fetch`). */
-    readonly message?: string;
-    /**
-     * Our own sentence, when the failure was ours.
-     *
-     * A key rather than text: this module has no dictionary, and the three sentences it used to spell were Chinese
-     * in both locales (`roots-panel-view` renders them through `resolveMessage` with the active dictionary).
-     */
-    readonly messageKey?: MessageKey;
-    /** Round trip in milliseconds, either way. */
-    readonly ms?: number;
-}
-/** The tester the panel drives. */
-export interface ConnectionTester {
-    /** Current answers by connection id; a new map after every change (safe for a snapshot comparison). */
-    readonly getState: () => ReadonlyMap<string, ConnectionTestState>;
-    /** Probe one connection; resolves when the answer (or the failure) has been recorded. */
-    readonly test: (id: string) => Promise<void>;
-    /** Watch for changes; returns the disposer. */
-    readonly subscribe: (listener: () => void) => () => void;
-    /** Drop listeners; an in-flight answer is discarded rather than delivered. */
-    readonly dispose: () => void;
-}
-/**
- * How long a probe may stay 「测试中…」 before the client gives up on it.
- *
- * A real connect plus one command can take seconds, but it can also hang forever: the host's own connect has no
- * deadline the client can see, and a `fetch` with no signal keeps its promise (and the row's button) in limbo.
- * Without this the 「测试」 button stayed disabled and read 「测试中…」 **forever**, with no cancel and no way to try
- * again short of reloading the page (audit 2026-11-01b ui P2-11).
- */
-export declare const CONNECTION_TEST_TIMEOUT_MS = 15000;
-export declare function createConnectionTester(options: {
-    readonly fetchImpl: FetchLike;
-    readonly path?: string;
-    /** Override for {@link CONNECTION_TEST_TIMEOUT_MS}; a test drives the timeout instead of waiting 15 s. */
-    readonly timeoutMs?: number;
-}): ConnectionTester;

package/lib/types/src/client/roots/roots-panel-state.d.ts

@@ -1,307 +0,0 @@
-/**
- * 根面板的**状态层**：草稿、状态机、reducer、选择器与文案解析。
- *
- * 从 `roots-panel-view.ts` 抽出（审计 0076）：这一层是纯函数，不碰 React，
- * 也是测试最密集的部分；拆开后 view 只负责渲染与接线。
- *
- * @module dsh-over-ssh/client/roots-panel-state
- */
-import type { OverSshKey } from '../core/locale.ts';
-import { type MessageKey, type RootsSnapshot, type RootsView, type SshConfigListing } from './roots-panel.ts';
-export type RootsPanelCopy = Record<OverSshKey, string>;
-/** The three forms' contents. Kept flat so a patch is one spread and a test can name a single field. */
-export interface RootsPanelDrafts {
-    /** Local root path (form 1). */
-    readonly localPath: string;
-    /** Remote root path (form 2). */
-    readonly remotePath: string;
-    /** Connection chosen for the remote root (form 2). */
-    readonly remoteConnectionId: string;
-    /** Optional label for the remote root (form 2). */
-    readonly remoteLabel: string;
-    /** New connection: id. */
-    readonly newId: string;
-    /** New connection: host. */
-    readonly newHost: string;
-    /** New connection: user. */
-    readonly newUser: string;
-    /** New connection: authentication mode. */
-    readonly newAuthKind: 'agent' | 'key' | 'password';
-    /** New connection: key path, only meaningful for `newAuthKind === 'key'`. */
-    readonly newKeyPath: string;
-    /**
-     * New connection: password, only meaningful for `newAuthKind === 'password'`.
-     *
-     * Held only between typing and the POST that follows it — the drafts are reset once the request settles, and
-     * no answer ever carries it back (the host stores it in `ctx.credentials`).
-     */
-    readonly newPassword: string;
-    /** New connection: port as typed; parsed by the controller so a bad value can be refused, not coerced. */
-    readonly newPort: string;
-}
-/** A change to the drafts; every field is optional so one handler can serve every input. */
-export type RootsPanelDraftPatch = Partial<RootsPanelDrafts>;
-/**
- * The **edit dialog's** own fields, kept apart from {@link RootsPanelDrafts}.
- *
- * The two forms used to share one flat draft set, and that is exactly what went wrong (audit 2026-11-01b ui
- * P1-4 — three symptoms, one cause):
- *
- *  - `edit-started` overwrote the add form's drafts with the row being edited, so opening 「编辑」 to look at a
- *    record threw away whatever the operator had already typed into 「新增连接」;
- *  - `edit-ended` reset **all** drafts, so even cancelling the dialog wiped the add form;
- *  - both forms read the same fields, so submitting the add form (reachable while the dialog is up, in a
- *    composition where the card has no backdrop) posted the edit dialog's values as a *new* connection.
- *
- * The password box belongs here, not in {@link RootsPanelDrafts}: it is always empty on render, and empty means
- * 「keep the stored password」 — a rule about the edit path only (「新增连接」 has its own required-password rule).
- */
-export interface RootsPanelEditDrafts {
-    /** The connection's id. Editable: a change is a rename that re-keys its remote roots. */
-    readonly id: string;
-    readonly host: string;
-    readonly user: string;
-    readonly authKind: 'agent' | 'key' | 'password';
-    readonly keyPath: string;
-    /** Always empty on render; empty means 「keep the stored password」. */
-    readonly password: string;
-    /** Port as typed; parsed by the controller so a bad value can be refused, not coerced. */
-    readonly port: string;
-}
-/** A change to the edit dialog's fields. */
-export type RootsPanelEditDraftPatch = Partial<RootsPanelEditDrafts>;
-/** @returns the edit dialog's fields in their fresh state. */
-export declare function emptyRootsPanelEditDrafts(): RootsPanelEditDrafts;
-/** Where an inline form message belongs. */
-export type RootsPanelFormScope = 'roots' | 'connection' | 'edit';
-/** A refusal or a failed submit, shown next to the form it belongs to. */
-export interface RootsPanelFormNotice {
-    readonly scope: RootsPanelFormScope;
-    readonly message: MessageKey;
-}
-/** Everything the section renders from. */
-export interface RootsPanelState {
-    /** True once an initial `load()` has been asked for, so a remount does not re-fetch. */
-    readonly started: boolean;
-    /** True while a request is in flight; the edit gate is `buildRootsView`'s `canEdit`. */
-    readonly pending: boolean;
-    /** True once a `load()` answered (ok or not). */
-    readonly loaded: boolean;
-    /** The last host answer, if any. */
-    readonly snapshot?: RootsSnapshot;
-    /** The last transport-level failure, if any. */
-    readonly error?: string;
-    /** The forms' contents. */
-    readonly drafts: RootsPanelDrafts;
-    /**
-     * The **edit dialog's** fields (see {@link RootsPanelEditDrafts}).
-     *
-     * Always present, empty while no dialog is open: an optional field would make "the dialog is closed" and "the
-     * value was dropped" the same state, which is how the two forms ended up sharing one draft set.
-     */
-    readonly editDrafts: RootsPanelEditDrafts;
-    /**
-     * The connection currently open in the edit form, if any.
-     *
-     * Only the **id** is remembered: every other value lives in the drafts, so the form cannot show a stale copy
-     * of a record the host has since changed. `undefined` means the add form is the one on screen.
-     */
-    readonly editingId?: string;
-    /**
-     * The connection whose removal is awaiting confirmation.
-     *
-     * Deleting a connection also deletes its roots (the host does that), which is not obvious from a row that
-     * shows only `id · host`  -  hence the confirmation, the same shape the session panel uses for its
-     * irreversible actions.
-     */
-    readonly confirmingRemove?: string;
-    /** The last validation refusal or submit failure, with the form it belongs to. */
-    readonly formNotice?: RootsPanelFormNotice;
-    /**
-     * The last **successful** submit, with the form it belongs to.
-     *
-     * Adding a root, adding a connection or saving an edit used to end silently: the form emptied itself and the
-     * only evidence was the list changing somewhere else on the page. The success line reuses the same
-     * per-form slot mechanism as {@link RootsPanelState.formNotice}, with the opposite tone
-     * (audit 2026-11-01b ui P3-5).
-     */
-    readonly formSuccess?: RootsPanelFormNotice;
-    /**
-     * True while the `~/.ssh/config` import dialog is open (FR-2.1.4).
-     *
-     * The dialog is state in this controller rather than local `useState` in the view for the same reason the
-     * forms are: the controller owns every request, and an import is a request. Keeping the listing here also
-     * means reopening the dialog does not re-read the file unless the user asks.
-     */
-    readonly importOpen?: boolean;
-    /** The aliases the host offered, once `list-ssh-config` answered. */
-    readonly importListing?: SshConfigListing;
-    /** Aliases ticked in the dialog, in the order they were ticked. */
-    readonly importSelected?: readonly string[];
-    /** True while `list-ssh-config` or `import-ssh-config` is in flight. */
-    readonly importBusy?: boolean;
-    /** The last import's report, shown inside the dialog (ids imported, aliases refused). */
-    readonly importReport?: {
-        readonly imported: readonly string[];
-        readonly refused: readonly {
-            readonly alias: string;
-            readonly reason: string;
-        }[];
-    };
-    /** Why the last import attempt failed, shown inside the dialog. */
-    readonly importError?: string;
-}
-/** What the reducer accepts. */
-export type RootsPanelAction = 
-/** A request is being sent; also marks the panel as started. */
-{
-    readonly type: 'load';
-} | {
-    readonly type: 'loaded';
-    readonly snapshot: RootsSnapshot;
-}
-/**
- * A request failed. With a `scope` it is a submit failure and is shown next to that form; without one it
- * is the initial load failing, which the view's own `notice` already reports  - showing both would say the
- * same thing twice.
- */
- | {
-    readonly type: 'failed';
-    readonly error: string;
-    readonly scope?: RootsPanelFormScope;
-}
-/** One form field changed: clears the inline message, because the user is fixing it. */
- | {
-    readonly type: 'draft-changed';
-    readonly patch: RootsPanelDraftPatch;
-}
-/** One field of the **edit** dialog changed; the add form's drafts are untouched. */
- | {
-    readonly type: 'edit-draft-changed';
-    readonly patch: RootsPanelEditDraftPatch;
-}
-/** A submit is in flight. */
- | {
-    readonly type: 'submitted';
-}
-/** A draft was refused before any request; nothing was sent. */
- | {
-    readonly type: 'refused';
-    readonly scope: RootsPanelFormScope;
-    readonly message: MessageKey;
-}
-/**
- * A request succeeded. `resetDrafts` clears the forms (an add did); a removal keeps them.
- *
- * `scope` decides which form gets the "saved" line — a removal passes none, because its evidence is the row
- * leaving the list, not a sentence.
- */
- | {
-    readonly type: 'succeeded';
-    readonly resetDrafts?: boolean;
-    readonly scope?: RootsPanelFormScope;
-}
-/** A removal is in flight; the reducer itself refuses a row that is not removable. */
- | {
-    readonly type: 'remove';
-    readonly key: string;
-}
-/** Open the edit form for one connection, prefilled from the last answer. */
- | {
-    readonly type: 'edit-started';
-    readonly id: string;
-}
-/** Close the edit form (cancelled, or the edit settled). */
- | {
-    readonly type: 'edit-ended';
-}
-/** Ask for confirmation before removing a connection (it takes its roots with it). */
- | {
-    readonly type: 'remove-connection-asked';
-    readonly id: string;
-}
-/** Dismiss the confirmation without removing anything. */
- | {
-    readonly type: 'remove-connection-dismissed';
-}
-/** Open the ssh-config import dialog (FR-2.1.4). */
- | {
-    readonly type: 'import-opened';
-}
-/** Close it, keeping nothing but the panel's own state. */
- | {
-    readonly type: 'import-closed';
-}
-/** A read or an import is in flight. */
- | {
-    readonly type: 'import-busy';
-}
-/** The host's candidate list arrived. */
- | {
-    readonly type: 'import-loaded';
-    readonly listing: SshConfigListing;
-}
-/** One alias was ticked or unticked. */
- | {
-    readonly type: 'import-toggled';
-    readonly alias: string;
-}
-/** Tick every candidate. */
- | {
-    readonly type: 'import-all';
-}
-/** Untick everything. */
- | {
-    readonly type: 'import-none';
-}
-/** The import settled: what went in, and what was refused with its reason. */
- | {
-    readonly type: 'import-settled';
-    readonly imported: readonly string[];
-    readonly refused: readonly {
-        readonly alias: string;
-        readonly reason: string;
-    }[];
-}
-/** The read or the import failed. */
- | {
-    readonly type: 'import-failed';
-    readonly error: string;
-} | {
-    readonly type: 'import-failed';
-    readonly error: string;
-};
-/** The starting state: nothing loaded, no drafts, no queue. */
-export declare function emptyRootsPanelDrafts(): RootsPanelDrafts;
-/** @returns the state a freshly created controller holds. */
-export declare function initialRootsPanelState(): RootsPanelState;
-/**
- * The panel's state machine. Pure: same state + same action => same result, and an action that changes
- * nothing returns the **same object**, so a subscriber is never woken for a no-op.
- *
- * @param state - the current state.
- * @param action - what happened.
- * @returns the next state.
- */
-export declare function rootsPanelReducer(state: RootsPanelState, action: RootsPanelAction): RootsPanelState;
-/**
- * The view model for a state.
- *
- * @param state - the panel state.
- * @returns exactly what `buildRootsView` says: rows with `removable`, connections, notice and the edit gate.
- */
-export declare function selectRootsView(state: RootsPanelState): RootsView;
-/** True when the panel may accept input right now: an answer arrived and no request is in flight. */
-export declare function canEdit(state: RootsPanelState): boolean;
-/**
- * Turn one `MessageKey` into text, with its parameters substituted.
- *
- * The implementation is `core/message.ts`'s (the session panel and the transfer panel need the same two lines and
- * must not import this React-bearing module); what stays here is the roots panel's own convenience: no message
- * renders as `''`, because every caller in this file is a template slot that simply renders nothing.
- *
- * @param copy - the dictionary of the active locale.
- * @param message - the key plus optional `{name}` parameters.
- * @returns the rendered text, or `''` when there is no message.
- */
-export declare function resolveMessage(copy: RootsPanelCopy, message: MessageKey | undefined): string;

package/lib/types/src/client/roots/roots-panel-view.d.ts

@@ -1,280 +0,0 @@
-/**
- * The **editable** remote-workspaces section of the settings panel.
- *
- * Three layers, deliberately separated so the interesting parts can be tested without a browser:
- *
- *  1. {@link rootsPanelReducer}  - a pure state machine over the panel's drafts, the last host answer and
- *     whether a request is in flight. No DOM, no I/O, no React: `tests/client-roots-view.test.ts` drives it
- *     directly.
- *  2. {@link createRootsPanelController}  - the same state plus the two calls from
- *     `./roots-panel.ts` (`load` / `send`). Everything that is *not* pure lives here: validation gate,
- *     double-submit gate, the refresh after a success, and dropping answers that a newer request superseded.
- *  3. {@link RootsPanelSection}  - a pure template (`createElement`, never JSX: Node's native type stripping
- *     cannot transform JSX) and {@link RootsPanelContainer}, the thin React shell that subscribes to the
- *     controller.
- *
- * Rules this file is responsible for, and where they are enforced:
- *
- *  - **A `config` root never gets a delete button.** The button is rendered from
- *    {@link RootRowView.removable} and from nothing else; the controller refuses such a key before a POST.
- *  - **Nothing is submitted before validation.** `validateRootDraft` / `validateConnectionDraft` are the only
- *    way a draft becomes a request body, and their `MessageKey` refusal is rendered as text through the
- *    locale dictionaries.
- *  - **No double submit.** `canEdit === false` (no answer yet, or a request in flight) disables every control
- *    and stops every handler.
- *  - **No credentials.** This file can only send the fields its drafts hold; the password field does not
- *    exist, and `validateConnectionDraft` refuses `authKind: 'password'` outright.
- *
- * @module dsh-over-ssh/client/roots-panel-view
- */
-import { type ReactNode } from 'react';
-import { type CardPortal } from '../core/portal.ts';
-import { type RootLocation, type RootsApi } from './roots-panel.ts';
-import type { RootsPanelCopy, RootsPanelDraftPatch, RootsPanelEditDraftPatch, RootsPanelState } from './roots-panel-state.ts';
-export * from './roots-panel-state.ts';
-export * from './transfer-panel-view.ts';
-/**
- * Placement of the connection **edit dialog**'s portal.
- *
- * `CLASS.portal` is the fixed body-level container; `CLASS.portalTop` is the wider placement the other two
- * dialogs share, which this form needs because it carries five fields plus the rename note.
- */
-export declare const ROOTS_EDIT_PORTAL_CLASS: string;
-/**
- * The click sink for that card: the settings modal's own layers are 900/1001, so the sink sits at 1001 and the
- * card above it (audit 2026-11-01b ui P2-1). The edit dialog is the case where a click *through* the gap used to
- * be worst: the 「新增连接」 form behind it shares the screen, and its 保存 was reachable.
- */
-export declare const ROOTS_EDIT_BACKDROP_CLASS: string;
-/** The calls the section makes. `roots-panel.ts` owns how they are implemented. */
-export interface RootsPanelController {
-    /** The current state; a stable reference until something changes (safe for `useSyncExternalStore`). */
-    readonly getState: () => RootsPanelState;
-    /** Watch for changes; returns the disposer. */
-    readonly subscribe: (listener: () => void) => () => void;
-    /** Ask for the first answer once; a remount does not re-fetch. */
-    readonly start: () => void;
-    /** Reload unconditionally (used after a successful change). */
-    readonly reload: () => Promise<void>;
-    /** Change one field of the **add connection** form. */
-    readonly changeDraft: (patch: RootsPanelDraftPatch) => void;
-    /**
-     * Change one field of the **edit dialog**.
-     *
-     * A separate writer because the two forms have separate drafts (`RootsPanelEditDrafts`): one set made opening
-     * the dialog overwrite the add form and cancelling it wipe it (audit 2026-11-01b ui P1-4).
-     */
-    readonly changeEditDraft: (patch: RootsPanelEditDraftPatch) => void;
-    /** Validate and add a root of the given location. */
-    readonly submitRoot: (location: RootLocation) => Promise<void>;
-    /** Validate and add a connection. */
-    readonly submitConnection: () => Promise<void>;
-    /** Open the edit form for one connection, prefilled from the last host answer. */
-    readonly startEdit: (id: string) => void;
-    /** Close the edit form without saving. */
-    readonly cancelEdit: () => void;
-    /** Validate and save the edit form (a rename included). */
-    readonly submitEdit: () => Promise<void>;
-    /** Ask for confirmation before removing a connection (it takes its remote roots with it). */
-    readonly askRemoveConnection: (id: string) => void;
-    /** Dismiss the confirmation. */
-    readonly cancelRemoveConnection: () => void;
-    /** Remove a connection, once the confirmation was accepted. */
-    readonly confirmRemoveConnection: (id: string) => Promise<void>;
-    /** Remove one row, if the view allows it. */
-    readonly remove: (key: string) => Promise<void>;
-    /** Open the ssh-config import dialog and read the file (FR-2.1.4). */
-    readonly openImport: () => Promise<void>;
-    /** Re-read `~/.ssh/config`, replacing the candidate list. */
-    readonly reloadImport: () => Promise<void>;
-    /** Close the dialog. */
-    readonly closeImport: () => void;
-    /** Tick or untick one alias. */
-    readonly toggleImport: (alias: string) => void;
-    /** Tick every candidate. */
-    readonly selectAllImports: () => void;
-    /** Untick everything. */
-    readonly clearImports: () => void;
-    /** Import the ticked aliases. */
-    readonly submitImport: () => Promise<void>;
-    /**
-     * Tell the controller the settings surface is on screen again.
-     *
-     * Cancels a pending {@link RootsPanelController.surfaceDetached} — see there for why unmounting is not by
-     * itself "the page was closed".
-     */
-    readonly surfaceAttached: () => void;
-    /**
-     * Tell the controller the settings surface went away.
-     *
-     * **Not** "close the editor": the platform re-registers this section whenever its inject face changes, and
-     * opening the editor is such a change, so the component unmounts and remounts as a normal part of opening
-     * it. Closing the settings page looks the same except that **nothing remounts**. The two are told apart in
-     * time: the clear is deferred by one task, and a remount cancels it (audit 0091).
-     */
-    readonly surfaceDetached: () => void;
-    /** Stop accepting results and drop listeners. */
-    readonly dispose: () => void;
-}
-/** What a controller needs: the one call, plus the one scheduling choice. */
-export interface RootsPanelControllerOptions {
-    readonly api: RootsApi;
-    /**
-     * Defer one task and return its canceller.
-     *
-     * Injectable so {@link RootsPanelController.surfaceDetached} is testable without timers: the policy it
-     * encodes ("did anything remount before this ran?") is the whole point, and a test that has to wait on a
-     * real `setTimeout` would be both slow and flaky.
-     */
-    readonly defer?: (run: () => void) => () => void;
-}
-/**
- * Build the stateful half of the panel.
- *
- * The refresh-after-success is the reason this exists at all: `POST` answers with the *persisted* state,
- * whose `roots` are the user's roots  - the same field name `GET` uses for the *config* roots. Rendering that
- * answer directly would show a config root as a user root (or the reverse), so a success always ends with a
- * fresh `GET` and the POST body is used only as a signal.
- *
- * @param options - the injected API.
- * @returns the controller the container subscribes to.
- */
-export declare function createRootsPanelController(options: RootsPanelControllerOptions): RootsPanelController;
-/**
- * The section's callbacks, derived from the controller.
- *
- * A factory rather than an inline object literal so the shell can `useMemo(() => rootsPanelSectionActions(controller),
- * [controller])` — stable props are the precondition for ever putting `memo` on the two child components — **and**
- * so "each callback really drives the controller" is a decision a test can hold on to (audit 2026-11-01b ui P3-7).
- *
- * @param controller - the panel's controller.
- * @returns the callbacks the pure template calls.
- */
-export declare function rootsPanelSectionActions(controller: RootsPanelController): RootsPanelSectionActions;
-/** What the section's controls call. All of them are no-ops when the gate is closed. */
-export interface RootsPanelSectionActions {
-    readonly onDraftChange: (patch: RootsPanelDraftPatch) => void;
-    /** One field of the edit dialog changed (its own draft set). */
-    readonly onEditDraftChange: (patch: RootsPanelEditDraftPatch) => void;
-    readonly onSubmitRoot: (location: RootLocation) => void;
-    readonly onSubmitConnection: () => void;
-    readonly onRemove: (key: string) => void;
-    readonly onSubmitEdit: () => void;
-    readonly onCancelEdit: () => void;
-    /** FR-2.1.4: the ssh-config import dialog's controls. */
-    readonly onImportOpen: () => void;
-    readonly onImportClose: () => void;
-    readonly onImportReload: () => void;
-    readonly onImportToggle: (alias: string) => void;
-    readonly onImportAll: () => void;
-    readonly onImportNone: () => void;
-    readonly onImportSubmit: () => void;
-}
-/**
- * The `~/.ssh/config` import dialog (FR-2.1.4).
- *
- * Three things it deliberately does:
- *
- *  - **It shows the refusals.** Every alias the host would not offer is listed with the reason, because the
- *    user is looking at their own config file and can see the entry that is missing from the list. A silent
- *    subset reads as a broken feature.
- *  - **It shows the id each alias will become.** `deploy@bastion` is a valid alias and not a valid id, so the
- *    dialog says what the id will be instead of letting `add-connection` refuse it later.
- *  - **It never shows an identity path.** The host answers `hasIdentityFile` as a boolean; the path itself is
- *    not on the wire (the route's invariant 1), so nothing here can leak one.
- *
- * @param props - copy, state and callbacks.
- * @returns the dialog, or nothing when it is closed.
- */
-export declare function SshConfigImportDialog({ copy, state, actions, idPrefix }: RootsPanelSectionProps): ReactNode;
-/**
- * The **edit** form for one saved connection.
- *
- * It exists as its own component because it is the one form whose fields are prefilled from a host answer: the
- * panel's top list renders the row buttons that open it, and this renders what those buttons open. Splitting
- * them keeps `RootsPanelSection` about the roots it owns and this about one connection.
- *
- * Two rules it inherits and one it adds:
- *
- *  - **Nothing is submitted before validation** ({@link validateConnectionEdit} is the only way in);
- *  - **no credential is ever rendered**  -  the password box is always empty, because no answer carries a
- *    secret back, and an empty box means "keep the stored password" (see the key's own note);
- *  - **the id is editable, and the rename is explained**: a rename re-keys the connection's remote roots and
- *    is therefore not a cosmetic field, so the form says so rather than leaving it to be discovered.
- *
- * @param props - copy, state and callbacks.
- * @returns the form, or nothing when no connection is open for editing.
- */
-export declare function ConnectionEditForm({ copy, state, actions, idPrefix }: RootsPanelSectionProps): ReactNode;
-/** Props of the pure template: state in, callbacks out, no hooks and no store access. */
-/**
- * The `id` prefix the pure templates use when the shell does not pass one (direct template calls, tests).
- *
- * The shell always passes `useId()`'s value instead, so the ids are **per mount** — see
- * {@link RootsPanelSectionProps.idPrefix}.
- */
-export declare const DEFAULT_ROOTS_ID_PREFIX = "dsh-rw-roots";
-export interface RootsPanelSectionProps {
-    readonly copy: RootsPanelCopy;
-    readonly state: RootsPanelState;
-    readonly actions: RootsPanelSectionActions;
-    /**
-     * `id` prefix for this mount's form controls (`{prefix}-edit-host`, `{prefix}-import-<alias>`, …).
-     *
-     * A module constant was enough while there was exactly one section on one page, and it stopped being enough
-     * the moment the platform started re-registering the section on every inject-face change: for one commit the
-     * old mount and the new one are both in the DOM, so two inputs share an `id` and every `<label for>` in the
-     * overlap points at whichever one the browser found first. `useId()` in the container makes that impossible.
-     *
-     * Optional only so the offline view tests can call these templates directly (audit 2026-10-31 client.md §2.4).
-     */
-    readonly idPrefix?: string;
-    /**
-     * The body-level portal the connection **edit dialog** is rendered into.
-     *
-     * Optional on purpose: the pure template is called directly by the offline view tests (and by any caller
-     * without a DOM), where the card is rendered in place. The shell always passes one, so the real UI gets a
-     * card that floats over the settings page instead of being pushed below the "新增连接" form (audit 0088).
-     */
-    readonly portal?: CardPortal;
-}
-/**
- * Props of the whole settings section.
- *
- * It is {@link RootsPanelSectionProps} plus the one element that needs the container: the transfer progress
- * panel. The remote file **tree** is not here at all: it was deleted (audit 0085) because remote paths are
- * reached through the conversation, and because this function is called **directly** by the view tests,
- * outside any React render, where a hook throws `Invalid hook call` (the constraint documented in
- * `controls.ts`).
- */
-export interface RootsPanelSectionViewProps extends RootsPanelSectionProps {
-    /** The transfer progress panel element, or `undefined` in a template-only render. */
-    readonly transfers?: ReactNode;
-}
-/**
- * Render the editable section. Pure: calling it twice with the same props yields the same tree.
- *
- * @param props - copy, state and callbacks.
- * @returns the section element.
- */
-export declare function RootsPanelSection({ copy, state, actions, transfers, portal, idPrefix, }: RootsPanelSectionViewProps): ReactNode;
-/** Props of the React shell: the controller owns the state, the shell only subscribes. */
-export interface RootsPanelContainerProps {
-    readonly copy: RootsPanelCopy;
-    readonly controller: RootsPanelController;
-}
-/**
- * Subscribe to a controller and render {@link RootsPanelSection}.
- *
- * `useSyncExternalStore` is the whole reason this is a component and not a function call: the slot's inject
- * face is a synchronous snapshot, so the section has to be re-rendered by the store it reads.
- *
- * The right-pane entry point is the one piece of state this shell owns itself: whether the composition
- * publishes the right sidebar is not a fact the controller's store carries (it is answered live by the entry
- * point), and an open that failed after the button was enabled must say so somewhere. Both are re-read on
- * every render, which is exactly when a `ctx.get` seam can have changed.
- *
- * @param props - the dictionary and the controller.
- * @returns the section element.
- */
-export declare function RootsPanelContainer({ copy, controller }: RootsPanelContainerProps): ReactNode;