dsh-over-ssh 0.1.0 → 0.2.0

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

@@ -1,364 +0,0 @@
-/**
- * The roots panel's whole decision surface: wire parsing, the HTTP calls to the host route, input validation
- * and the view model. **No React, no DOM, no `@deepseek-ai/*`** — the component renders what this module
- * returns and nothing else, which is what makes the panel testable without a browser (红线 2).
- *
- * Two rules this module owns:
- *
- *  1. **No credentials, ever.** {@link parseRootsSnapshot} copies field by field and drops anything else, so a
- *     host answer that leaked `keyPath` / `password` still cannot reach the DOM. The host route filters its
- *     side; this is the client's half of the same rule.
- *  2. **Password authentication is not editable here.** A password must never round-trip through a browser
- *     form and a same-origin POST, so {@link validateConnectionDraft} refuses it outright rather than
- *     growing a field that leaks secrets into web storage.
- *
- * @module dsh-over-ssh/client/roots-panel
- */
-import type { MessageKey } from '../core/message.ts';
-/**
- * Where the host route lives, as the browser must request it.
- *
- * **Relative on purpose, and this is the platform's own convention.** The GUI is served from two different
- * origins depending on the carrier, and only a relative path is correct in both:
- *
- *  - `dsh web` (browser): the page origin *is* the host, so `/api/…` reaches
- *    `ctx.webServer` directly;
- *  - the Desktop shell: the page is `dsh-app://app/` and `/api/…` resolves to
- *    `dsh-app://app/api/…`, which Electron's `protocol.handle('dsh-app')` forwards to the owned host with
- *    the browser-session cookie the shell keeps out of the page
- *    (`resources/app.asar/lib/main.js`, `forwardWebRequest`: non-asset paths are proxied with
- *    `headers.set('cookie', cookie)`; `serveWebDocument` never sees `/api/…`).
- *
- * The absolute host origin (`globalThis.__DSH_TRANSPORT__.streamBaseUrl`) is deliberately **not** used here:
- * the shell strips `set-cookie` from proxied responses and the session cookie is host-only + `HttpOnly`, so
- * a direct fetch to the host origin cannot authenticate — it would turn a working request into a 401. The
- * platform uses that origin for the WebSocket only (`dsh-api-gateway`, `REMOTE_STREAM_MUX_PATH`), and its
- * own HTTP callers resolve against `document.baseURI` (`dsh-client-file-upload`, `new URL(request.path,
- * document.baseURI)`).
- */
-export declare const ROOTS_API_PATH = "/api/over-ssh/roots";
-/** A root either lives on this machine or behind a connection. */
-export type RootLocation = 'local' | 'remote';
-/** One root as the panel shows it. */
-export interface RootRow {
-    /** Stable identity: `<location>:<connectionId or '-'>:<path>`. */
-    readonly key: string;
-    readonly location: RootLocation;
-    readonly path: string;
-    readonly connectionId?: string;
-    readonly label?: string;
-    readonly writable: boolean;
-    /** `config` rows come from the profile patch; `user` rows were added in this panel. */
-    readonly source: 'config' | 'user';
-    /** Whether this root also appears in the panel's own file — only those may be deleted. */
-    readonly inUserFile: boolean;
-    /**
-     * The workspaces that list this root; absent means **no session lists it yet**.
-     *
-     * The composer's card shows exactly the roots whose list names its own workspace (one session must not
-     * inherit another's directories). The settings panel ignores it, because that panel manages the whole list
-     * and registers roots with **no** scope of its own — its form has no `workspaces` member (`RootsPanelDrafts`),
-     * so a root added there is not listed by any session until one adds it (audit 0056).
-     */
-    readonly workspaces?: readonly string[];
-    /**
-     * The **sessions** that added this root (ADR-0013); absent on entries written before it.
-     *
-     * The composer's card prefers this over `workspaces`: two conversations opened on the same directory share
-     * the workspace path and differ only here.
-     */
-    readonly sessions?: readonly string[];
-}
-/** A connection, narrowed to what the panel may display. **No credential fields exist on this type.** */
-export interface ConnectionSummary {
-    readonly id: string;
-    readonly host: string;
-    readonly user?: string;
-    readonly port?: number;
-    readonly authKind: 'agent' | 'key' | 'password';
-    /**
-     * The transport in force, **when the host reports it**.
-     *
-     * `publicRoot`/`publicUserState` do not carry it today (the transport is a live fact of the platform's remote
-     * namespace, not of the profile), so production answers leave this `undefined` and the panel says 「未知」
-     * rather than claiming `unknown` — but a host that starts publishing it is honoured without another round
-     * (audit 2026-11-01b ui P2-6).
-     */
-    readonly transport?: ConnectionTransport;
-    /** True when that transport is a degraded substitute, when the host reports it. */
-    readonly degraded?: boolean;
-}
-/** The transports a connection row may name; `unknown` means "the host did not say". */
-/**
- * Re-exported from `core/panel-model.ts`, which **owns** it: `core` must not depend on `roots`, so the
- * definition lives in the lower layer and this file points up at it. `export type {…} from` alone does not put
- * the name in this module's scope, hence the separate `import type` as well.
- */
-export type { ConnectionTransport } from '../core/panel-model.ts';
-import type { ConnectionTransport } from '../core/panel-model.ts';
-/** Everything one GET answers. */
-export interface RootsSnapshot {
-    readonly roots: readonly RootRow[];
-    readonly connections: readonly ConnectionSummary[];
-    readonly warnings: readonly string[];
-    /**
-     * The plugin's anchor root (`<home>/.dsh/over-ssh/roots`), when the host publishes one.
-     *
-     * Not a row: it is what lets a client recognise that a session's cwd *is* a remote workspace (see
-     * `client/session-remote-mark.ts`). Absent means "the host did not say", and every caller must treat that
-     * as unknown rather than as "no remote sessions".
-     */
-    readonly anchorRoot?: string | undefined;
-}
-/** The outcome of one call: the panel never throws on a host failure, it shows it. */
-export type ApiResult<T> = {
-    readonly ok: true;
-    readonly value: T;
-} | {
-    readonly ok: false;
-    readonly error: string;
-};
-/** What this module needs from `fetch`; injected so tests run without a server (红线 3). */
-export type FetchLike = (input: string, init?: {
-    readonly method?: string;
-    readonly headers?: Record<string, string>;
-    readonly body?: string;
-    readonly signal?: AbortSignal;
-}) => Promise<{
-    readonly ok: boolean;
-    readonly status: number;
-    json: () => Promise<unknown>;
-}>;
-/**
- * A message is a key plus its parameters; the component resolves it against the locale dictionaries.
- *
- * The shape (and the resolver, `resolveMessage`) live in `../core/message.ts` because the session panel and the
- * transfer panel produce messages too, and both are pure models that must not import React. Re-exported here so
- * every existing `import { MessageKey } from './roots-panel.ts'` keeps working.
- */
-export type { MessageKey };
-/** A validated draft, or the reason it was refused. */
-export type Validation<T> = {
-    readonly ok: true;
-    readonly value: T;
-} | {
-    readonly ok: false;
-    readonly message: MessageKey;
-};
-/** The payload the panel sends to add a root. */
-export interface RootDraft {
-    readonly location: RootLocation;
-    readonly path: string;
-    readonly connectionId?: string;
-    readonly label?: string;
-    readonly writable?: boolean;
-}
-/**
- * The transport a connection record asks for.
- *
- * It stays in the wire payload type because the host still accepts and persists it, but the **panel no
- * longer offers a choice**: every save asks for `agent`, and the host's selector/preflight degrades to the
- * zero-install transports automatically when the Tier 2 ladder cannot serve the connection. Keeping the type
- * here documents what the payload can contain without re-opening the UI decision.
- */
-export type ConnectionTransportChoice = 'alias' | 'ssh2' | 'agent';
-/**
- * The payload the panel sends to add a connection.
- *
- * `password` is the **only** secret this client ever holds, and only long enough to post it: the host writes
- * it into `ctx.credentials` and answers with a projection that never contains it (FR-2.1.2).
- */
-export interface ConnectionDraft {
-    readonly id: string;
-    readonly host: string;
-    readonly user: string;
-    readonly authKind: 'agent' | 'key' | 'password';
-    /**
-     * The transport the payload asks for.
-     *
-     * Always `agent` now: the panel offers no choice, and the host degrades automatically. Kept in the payload
-     * (rather than omitted) so an older record's `alias`/`ssh2` is rewritten to the preferred path on the first
-     * save, and so the host keeps the "always explicit" contract it already validates.
-     */
-    readonly transport?: ConnectionTransportChoice;
-    readonly keyPath?: string;
-    readonly password?: string;
-    readonly port?: number;
-}
-/** The identity the host also uses, so removals address the same row the list shows. */
-export declare function rootKey(location: RootLocation, path: string, connectionId?: string): string;
-/**
- * Narrow one GET answer to the panel's model, field by field.
- *
- * Unknown fields are dropped rather than copied: an answer carrying `keyPath` reaches the DOM only as a
- * missing field, never as a value. A malformed answer becomes an empty snapshot with a warning instead of a
- * throw — a broken channel must degrade the panel, not break the whole settings page.
- *
- * @param value - the parsed JSON the route answered with.
- * @returns a snapshot that is safe to render.
- */
-export declare function parseRootsSnapshot(value: unknown): RootsSnapshot;
-/** True when a string is an absolute path this machine can open (drive letter, POSIX root, or UNC). */
-export declare function isAbsoluteLocalPath(path: string): boolean;
-/**
- * Refuse a draft before it becomes a request.
- *
- * @param draft - what the form holds.
- * @param existing - roots already shown, to reject a duplicate.
- * @returns the wire payload, or the message key to show next to the field.
- */
-export declare function validateRootDraft(draft: RootDraft, existing?: readonly RootRow[]): Validation<RootDraft>;
-/**
- * Refuse a connection draft before it becomes a request.
- *
- * The id rule is the **host's** rule (a user-chosen name, Chinese included), so the panel refuses exactly
- * what `path-grammar.ts` would refuse instead of sending a request that comes back 400.
- *
- * Password auth is supported: the draft carries the password once, the host stores it in `ctx.credentials`,
- * and nothing in any answer ever carries it back (FR-2.1.2).
- *
- * The payload always carries `transport: 'agent'`: the panel no longer offers a choice, and the host downgrades
- * automatically when the Tier 2 ladder cannot serve this connection.
- *
- * @param draft - what the form holds.
- * @param existing - connections already shown, to reject a duplicate id.
- * @returns the wire payload, or the message key to show next to the field.
- */
-export declare function validateConnectionDraft(draft: ConnectionDraft, existing?: readonly ConnectionSummary[]): Validation<ConnectionDraft>;
-/**
- * Refuse an **edit** draft before it becomes a request.
- *
- * The same rules as {@link validateConnectionDraft} for every field, with the three differences an edit
- * needs, and each one exists for a reason:
- *
- *  1. **A rename is allowed but must not collide with a *different* connection.** Uniqueness is checked
- *     against the rows except the one being edited  -  `validateConnectionDraft` cannot express that, and using
- *     it here would refuse every save that kept the id.
- *  2. **An empty password means "do not touch the stored secret", not "refuse".** No answer ever carries a
- *     secret back, so the form's password box is always empty on render; requiring it would make it
- *     impossible to change a host without retyping the password, and treating empty as "clear" would delete
- *     the password on every unrelated edit. The field is therefore **omitted** from the payload unless the
- *     user typed one, which is exactly how the host reads it.
- *  3. **`keyPath` follows the same rule as the password: blank means "keep the stored one".** The panel
- *     cannot prefill it, because the host's answer deliberately never carries a `keyPath` (it names a real
- *     file). Refusing a blank one would therefore make it impossible to edit a key connection's host without
- *     retyping its private-key path, and *filling* it with a guess would silently repoint the connection.
- *     So it is omitted unless the user typed one  -  the host's merge keeps what is stored.
- *
- * @param draft - what the form holds.
- * @param originalId - the id of the connection being edited (the lookup key the host needs).
- * @param existing - connections already shown, to reject a colliding rename.
- * @returns the wire payload, or the message key to show next to the field.
- */
-export declare function validateConnectionEdit(draft: ConnectionDraft, originalId: string, existing?: readonly ConnectionSummary[]): Validation<Record<string, unknown>>;
-/** One row as the component renders it. */
-export interface RootRowView {
-    readonly key: string;
-    readonly location: RootLocation;
-    readonly title: string;
-    readonly subtitle: string;
-    readonly badgeKey: string;
-    readonly removable: boolean;
-}
-/** The panel's complete render input. */
-export interface RootsView {
-    readonly rows: readonly RootRowView[];
-    readonly connections: readonly ConnectionSummary[];
-    /** Set when the host did not answer, so the panel can say why instead of looking empty. */
-    readonly notice?: MessageKey;
-    /** False while a request is in flight, so the form cannot double-submit. */
-    readonly canEdit: boolean;
-}
-/**
- * Turn a snapshot (or the failure to get one) into render input.
- *
- * @param input - the last answer, or the last error, plus whether a request is running.
- * @returns rows, connections, notice and the edit gate.
- */
-export declare function buildRootsView(input: {
-    readonly snapshot?: RootsSnapshot;
-    readonly error?: string;
-    readonly pending?: boolean;
-}): RootsView;
-/** The calls the panel makes. */
-export interface RootsApi {
-    load(signal?: AbortSignal): Promise<ApiResult<RootsSnapshot>>;
-    send(body: Record<string, unknown>): Promise<ApiResult<RootsSnapshot>>;
-    /**
-     * A POST whose answer is **not** a snapshot.
-     *
-     * The import actions answer a candidate list and an import report, neither of which is a roots snapshot. It
-     * is a separate method rather than a looser return type on {@link RootsApi.send} so that every existing call
-     * keeps the snapshot it already depends on: widening `send` would make `state` optional for all of them.
-     */
-    sendRaw(body: Record<string, unknown>): Promise<ApiResult<Record<string, unknown>>>;
-}
-/** One importable `~/.ssh/config` alias, as the import dialog renders it. */
-export interface SshConfigCandidate {
-    /** The literal alias; also the `ssh` target. Shown verbatim so the user recognises their own config. */
-    readonly alias: string;
-    /** Resolved host name. */
-    readonly host: string;
-    readonly user?: string;
-    readonly port?: number;
-    /** Whether the block named an identity file. The path itself never reaches the client. */
-    readonly hasIdentityFile: boolean;
-    readonly hasProxyJump: boolean;
-    /** The id the import would create. Editable in spirit: the user sees it before committing. */
-    readonly suggestedId: string;
-}
-/** One alias the host refused, with the machine-readable reason. */
-export interface SshConfigSkipped {
-    readonly pattern: string;
-    readonly reason: string;
-    readonly line: number;
-}
-/** What `list-ssh-config` answers. */
-export interface SshConfigListing {
-    readonly candidates: readonly SshConfigCandidate[];
-    readonly skipped: readonly SshConfigSkipped[];
-}
-/**
- * Narrow the host's `list-ssh-config` answer.
- *
- * Defensive in the same way {@link parseRootsSnapshot} is: the client never trusts the wire's shape, and a row
- * without a usable alias or id is **dropped** rather than rendered as a checkbox that would import nothing.
- *
- * @param value - the parsed JSON body.
- * @returns the listing, with unusable rows removed.
- */
-export declare function parseSshConfigListing(value: unknown): SshConfigListing;
-/**
- * The human-readable reason one alias was refused.
- *
- * The mapping lives here rather than in the view so the reasons are testable without rendering, and an unknown
- * reason from a newer host still produces a sentence instead of an empty cell.
- *
- * @param reason - the machine-readable reason.
- * @returns a message key.
- */
-export declare function sshConfigSkipKey(reason: string): string;
-/** A candidate's one-line summary: `user@host:port`, with the flags that matter for the import. */
-export declare function sshConfigCandidateSummary(candidate: SshConfigCandidate): string;
-/**
- * The reason a failed response reports, when the host did not name one.
- *
- * The path is part of the text on purpose: `http-404` alone cannot distinguish "this route is not
- * registered" (the host half never claimed it — that was a real defect) from "the request never reached the
- * host" (the shell's proxy or the composition is at fault). Both are shown verbatim in the panel's notice.
- *
- * @param status - the HTTP status.
- * @param path - the exact URL that was requested.
- * @returns the machine-readable reason.
- */
-export declare function transportFailureReason(status: number, path: string): string;
-/**
- * Bind the route to the panel's two operations.
- *
- * @param fetchImpl - `window.fetch` in the app, a stub in tests.
- * @param path - override for tests; defaults to {@link ROOTS_API_PATH}.
- * @returns the calls the component uses.
- */
-export declare function createRootsApi(fetchImpl: FetchLike, path?: string): RootsApi;
-/** The field names the panel must never send, asserted by tests rather than trusted to reviewers. */
-export declare function isForbiddenField(name: string): boolean;

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

@@ -1,35 +0,0 @@
-/**
- * 传输面板：进度列表、**长轮询驱动**与文案。
- *
- * 从 `roots-panel-view.ts` 抽出（审计 0076）；task-19 把定时轮询换成「回答一到就再问一次」的
- * 长轮询循环，循环本身在 `transfer-progress.ts`（可注入时钟，因此可在离线测试里驱动）。
- *
- * 容器只做三件事：建 io、把 controller 挂到 React 生命周期、把状态与回调交给纯模板。
- *
- * @module dsh-over-ssh/client/transfer-panel-view
- */
-import { type ReactNode } from 'react';
-import type { RootsPanelCopy, RootsPanelState } from './roots-panel-state.ts';
-/**
- * The panel, driven by {@link createTransferProgress}.
- *
- * `state` is accepted but not read: the panel's own snapshot is what it renders, and the roots state it used to
- * receive was never read either (the prop is kept so the section's call site does not have to change).
- *
- * @param props - the dictionary (the section's `state` is unused).
- * @returns the transfer section.
- */
-export declare function TransferProgressSection({ copy }: {
-    readonly copy: RootsPanelCopy;
-    readonly state?: RootsPanelState;
-}): ReactNode;
-/**
- * The tree's strings, read out of the panel's dictionary.
- *
- * Kept as an explicit projection rather than passing the dictionary itself: the tree's copy type is its own
- * contract, so a key it needs and the dictionary does not have is a compile error here, not a blank label at
- * runtime.
- *
- * @param copy - the panel's dictionary.
- * @returns the tree's strings.
- */

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

@@ -1,241 +0,0 @@
-/**
- * The transfer progress panel (FR-2.6.4): rate, bytes done, time left, and the failure list.
- *
- * The client **polls** rather than subscribes: this plugin's client half talks to the host over one HTTP route,
- * so "what is transferring" is a question it asks. Polling only while the panel is mounted is what keeps that
- * from being a permanent request loop.
- *
- * Two rules it inherits from the rest of this half:
- *
- *  - the answer is narrowed field by field (the wire is not trusted), and
- *  - **nothing is inferred**: an unknown status is `running`, an unknown direction is `upload`, and a missing
- *    `remainingMs` renders as "unknown" rather than as a guess.
- *
- * @module dsh-over-ssh/client/transfer-panel
- */
-import { type ReactNode } from 'react';
-import { type MessageKey } from '../core/message.ts';
-import { type ApiResult, type FetchLike } from './roots-panel.ts';
-/** One tracked transfer, as the panel renders it. */
-export interface TransferRow {
-    readonly id: string;
-    readonly direction: 'upload' | 'download';
-    readonly connectionId: string;
-    readonly remotePath: string;
-    readonly localPath: string;
-    readonly status: 'running' | 'done' | 'failed' | 'cancelled';
-    readonly transferredBytes: number;
-    readonly totalBytes: number;
-    readonly percent: number;
-    readonly bytesPerSecond: number;
-    readonly elapsedMs: number;
-    readonly remainingMs: number | null;
-    readonly error?: string;
-    readonly errorCode?: string;
-}
-/** How one snapshot may be asked for. */
-export interface TransferListOptions {
-    /**
-     * Host-side long-poll budget: the host parks the request until the table changes or this many milliseconds pass.
-     *
-     * Omitted/0 answers immediately (the pre-task-19 behaviour) — which is what a **user refresh** wants, because the
-     * user is waiting for an answer now, not for a change.
-     */
-    readonly waitMs?: number;
-    /** Abort the request (panel unmount, or a user refresh superseding a parked one). */
-    readonly signal?: AbortSignal;
-}
-/** The calls the panel makes. Injected, so the model is testable with no server. */
-export interface TransferPanelIo {
-    list(options?: TransferListOptions): Promise<ApiResult<readonly TransferRow[]>>;
-    clear(): Promise<ApiResult<number>>;
-}
-/**
- * Narrow one `list-transfers` answer.
- *
- * @param value - the parsed body.
- * @returns the rows, with unusable entries dropped.
- */
-export declare function parseTransferRows(value: unknown): readonly TransferRow[];
-/**
- * The rows still worth showing: everything running, plus the most recent finished ones.
- *
- * A cap on finished rows because the requirement's "failure list" is a list of *recent* problems; the host keeps
- * the full history, and the panel's job is to be readable.
- *
- * @param rows - every row the host reported.
- * @param finishedLimit - how many finished rows to keep.
- * @returns the rows to render, running first.
- */
-export declare function visibleTransfers(rows: readonly TransferRow[], finishedLimit?: number): readonly TransferRow[];
-/**
- * One row's one-line summary.
- *
- * @param row - the transfer.
- * @param format - the byte/duration formatters plus the localized direction label (injected so this stays free of
- *   the domain layer).
- * @param copy - the sentence templates; see {@link TransferPanelCopy.summaryRunning}.
- * @returns e.g. `上传 40.0%（4.0 KiB/10.0 KiB，2.0 KiB/s，剩余约 3.0s）` in Chinese, and the English template in `en`.
- */
-export declare function transferSummary(row: TransferRow, format: {
-    readonly bytes: (value: number) => string;
-    readonly duration: (value: number) => string;
-    readonly label: string;
-}, copy: Pick<TransferPanelCopy, 'summaryRunning' | 'summaryDone' | 'remaining' | 'remainingUnknown'>): string;
-/**
- * The accessible name of one transfer's progress bar.
- *
- * Separate from {@link transferSummary} on purpose. The summary is the row's *visible* line, and it
- * deliberately leaves the path out because the path is rendered next to it; a `<progress>` element has no
- * other text of its own, so a screen reader user needs the path **inside** the bar's name. Every bar used to
- * carry `copy.title` ("传输进度"), which meant N bars with N identical names and no way to tell which transfer
- * was which.
- *
- * The target falls back to the local path when the remote one is empty, so a row can never end up with a name
- * that is only a percentage.
- *
- * @param row - the transfer.
- * @param format - the label plus the byte/duration formatters.
- * @returns e.g. `上传 40.0%（400B/1000B，200B/s，剩余约 3000ms） — /srv/a.bin`.
- */
-export declare function transferProgressLabel(row: TransferRow, format: {
-    readonly bytes: (value: number) => string;
-    readonly duration: (value: number) => string;
-    readonly label: string;
-}, copy: Pick<TransferPanelCopy, 'summaryRunning' | 'summaryDone' | 'remaining' | 'remainingUnknown'>): string;
-/** Everything the panel renders from. */
-export interface TransferPanelState {
-    readonly rows: readonly TransferRow[];
-    /**
-     * Why the last list read failed, **as a key the view resolves**.
-     *
-     * It used to be the raw transport string, so the failure notice printed `http-500 @ /api/over-ssh/roots`
-     * or `TypeError` — machine text, in both locales, naming an internal URL (audit 2026-11-01b ui P2-5).
-     */
-    readonly error?: MessageKey;
-    readonly loading: boolean;
-    /** True while the user's 「清除」 request is in flight, so the two buttons can be disabled. */
-    readonly clearing: boolean;
-    /** Why the last 「清除」 failed, as a key. Kept apart from {@link TransferPanelState.error}: one is a read, the
-     * other a command, and they need different sentences. */
-    readonly clearError?: MessageKey;
-}
-/**
- * Turn one transport-level failure string into a sentence key.
- *
- * The three cases are the three things the panel can honestly say (audit 2026-11-01b ui P2-5):
- *
- *  - a status the route answered → 「…（HTTP {status}）」, the number is the useful part;
- *  - a transport spelling (`network`, `TypeError`, `AbortError`, `http-500 @ /api/…`) → carrying no information at
- *    all, so the panel says the host did not answer instead of printing the spelling;
- *  - anything else is the **host's own** explanation (this route answers prose for a refused capability), and that
- *    is the one case worth quoting.
- *
- * @param reason - the failure string the io produced.
- * @returns the dictionary key plus its parameters.
- */
-export declare function transferFailureKey(reason: string): MessageKey;
-/** @returns the starting state. */
-export declare function initialTransferPanelState(): TransferPanelState;
-/** A poll started. */
-export declare function transferPanelLoading(state: TransferPanelState): TransferPanelState;
-/** A poll answered. */
-export declare function transferPanelLoaded(state: TransferPanelState, rows: readonly TransferRow[]): TransferPanelState;
-/** A poll failed; the **last known rows stay** (a blip must not blank the panel). */
-export declare function transferPanelFailed(state: TransferPanelState, error: string): TransferPanelState;
-/** The user pressed 「清除」: the request is in flight and the previous clear failure is superseded. */
-export declare function transferPanelClearing(state: TransferPanelState): TransferPanelState;
-/** 「清除」 succeeded: the next poll shows the empty table. */
-export declare function transferPanelCleared(state: TransferPanelState): TransferPanelState;
-/**
- * 「清除」 failed.
- *
- * It used to be dropped on the floor (`void io.clear().then(...)` had no failure branch), so the button did
- * nothing at all on a refusal and the user could click it again and again (audit 2026-11-01b ui P2-5).
- */
-export declare function transferPanelClearFailed(state: TransferPanelState, error: string): TransferPanelState;
-/**
- * The state a poll starts from.
- *
- * `showLoading` separates the user's own action from the timer, and that distinction is the whole point: the
- * view renders a **visible** "reading…" notice for `loading` (`TransferPanelSection`), so a background poll
- * that raised it made the panel alternate between "reading…" and "nothing is transferring" once a second while
- * nothing was happening (audit 0057). Only opening the panel or pressing refresh asks to be seen doing it.
- *
- * A named function rather than an `if` inside the component because this repository's tests render no hooks: a
- * branch buried in a `useEffect` cannot be executed by a test, so the decision lives out here where it can be
- * (removing that branch used to leave every test green).
- *
- * @param state - the current panel state.
- * @param showLoading - `true` when the user asked for this poll.
- * @returns the state to render while the request is in flight.
- */
-export declare function transferPanelPollStarted(state: TransferPanelState, showLoading: boolean): TransferPanelState;
-/**
- * Bind the panel to the route.
- *
- * @param fetchImpl - `window.fetch` in the app, a stub in tests.
- * @param path - override for tests.
- * @returns the two calls the panel makes.
- */
-export declare function createTransferPanelIo(fetchImpl: FetchLike, path?: string): TransferPanelIo;
-/** The strings the panel renders. */
-export interface TransferPanelCopy {
-    readonly title: string;
-    /** The panel's description line (it existed as a locale key and was never rendered). */
-    readonly description: string;
-    readonly empty: string;
-    readonly loading: string;
-    readonly refresh: string;
-    readonly clear: string;
-    readonly failedTitle: string;
-    readonly cancelled: string;
-    readonly done: string;
-    readonly uploadLabel: string;
-    readonly downloadLabel: string;
-    /**
-     * The one-line summary templates, with `{label} {percent} {done} {total} {rate} {elapsed} {remaining}`.
-     *
-     * Templates rather than a sentence spelled here: this module is a pure model, and the sentence it used to
-     * build carried Chinese full-width punctuation (`%（…，…）`) into the English UI. The dictionaries own the
-     * sentence now; the numbers stay here.
-     */
-    readonly summaryRunning: string;
-    readonly summaryDone: string;
-    /** `剩余约 {duration}` */
-    readonly remaining: string;
-    /** `剩余时间未知` */
-    readonly remainingUnknown: string;
-    /** What a duration formatter prints when it was handed a value it cannot render. */
-    readonly durationUnknown: string;
-    /** Resolve one deferred failure message against the active dictionary. */
-    readonly resolve: (message: MessageKey) => string;
-    /** One failed transfer's line: `{path}{sep}{reason}` — the punctuation belongs to the locale. */
-    readonly failureLine: string;
-    /** The badge text when the host gave no `errorCode` (it used to be the English literal `error`). */
-    readonly errorCodeUnknown: string;
-}
-/** What the panel's controls call. */
-export interface TransferPanelActions {
-    readonly onRefresh: () => void;
-    readonly onClear: () => void;
-}
-/**
- * The panel's markup.
- *
- * A `<progress>` element for the bar rather than a styled `div`: it is the platform's own primitive, it is
- * announced correctly by a screen reader, and it needs no CSS to be a progress bar at all (which matters here,
- * because this plugin's stylesheet is injected and can be missing in a composition that never loaded it).
- *
- * @param props - state, copy, formatters and callbacks.
- * @returns the panel section.
- */
-export declare function TransferPanelSection(props: {
-    readonly copy: TransferPanelCopy;
-    readonly state: TransferPanelState;
-    readonly actions: TransferPanelActions;
-    readonly format: {
-        readonly bytes: (value: number) => string;
-        readonly duration: (value: number) => string;
-    };
-}): ReactNode;