@mudlet/mudlet-web 0.4.5 → 1.0.0

package/dist-lib/ui/windows/panels/ScriptEditorPanel.d.ts

@@ -1,10 +1,20 @@
 import React from 'react';
+import type { TriggerPatternType } from '../../../storage/schema';
 import type { MudSession } from '../../../mud/MudSession';
 import type { ProfileVFS } from '../../../scripting/vfs/ProfileVFS';
 import type { ScriptingEngine } from '../../../scripting/ScriptingEngine';
 import './ScriptEditorPanel.css';
 type Category = 'scripts' | 'aliases' | 'triggers' | 'timers' | 'keys' | 'buttons' | 'packages' | 'errors' | 'variables';
 type EditCategory = Exclude<Category, 'errors' | 'packages' | 'variables'>;
+/** The `text` a pattern row should carry after its type changes.
+ *
+ *  `colorTrigger` stores `"fg,bg"` and `lineSpacer` stores a line count, so
+ *  neither can inherit a regex left over from the previous type — and a regex
+ *  must not inherit `"-1,-1"` or `"2"` either. Mudlet gets this for free by
+ *  giving each type its own widget (`dlgTriggerEditor.cpp:7196-7239`); here one
+ *  `text` field is shared, so it is reset explicitly whenever the type crosses
+ *  into or out of one of the two structured kinds. */
+export declare function retypePatternText(text: string, from: TriggerPatternType, to: TriggerPatternType): string;
 interface ScriptEditorPanelProps {
     connectionId: string;
     session: MudSession;
@@ -19,6 +29,10 @@ export interface ScriptEditorPanelHandle {
     /** Switch to the item's category, expand its ancestors, select it, and —
      *  when a line is given — move the editor cursor there. */
     navigateToItem: (category: EditCategory, id: string, line?: number) => void;
+    /** Show the Variables tab with its filter set to the named top-level global.
+     *  Desktop selects the row in its variables tree; filtering is the same job
+     *  in a view that has no persistent selection. */
+    navigateToVariable: (name: string) => void;
 }
 export declare const ScriptEditorPanel: React.ForwardRefExoticComponent<ScriptEditorPanelProps & React.RefAttributes<ScriptEditorPanelHandle>>;
 export {};

package/dist-lib/ui/windows/panels/ScriptSearch.d.ts

@@ -1,12 +1,17 @@
+import React from 'react';
+import type { ScriptingEngine } from '../../../scripting/ScriptingEngine';
 import './ScriptSearch.css';
 export type EditCategory = 'scripts' | 'aliases' | 'triggers' | 'timers' | 'keys' | 'buttons';
 interface ScriptSearchProps {
     connectionId: string;
+    scriptingEngineRef?: React.RefObject<ScriptingEngine | null>;
     /** Navigate the editor to a matched item (and optionally a code line). */
     onNavigate: (category: EditCategory, id: string, line?: number) => void;
+    /** Show the Variables tab filtered to the named top-level global. */
+    onNavigateVariable?: (name: string) => void;
 }
 /** Global search for the Scripts editor — lives in the modal title bar and
  *  drops a VS Code-style results overlay (rendered through a portal so it
  *  escapes the modal's `overflow: hidden`). */
-export declare function ScriptSearch({ connectionId, onNavigate }: ScriptSearchProps): import("react/jsx-runtime").JSX.Element;
+export declare function ScriptSearch({ connectionId, scriptingEngineRef, onNavigate, onNavigateVariable }: ScriptSearchProps): import("react/jsx-runtime").JSX.Element;
 export {};

package/dist-lib/ui/windows/panels/TextPanel.d.ts

@@ -2,6 +2,7 @@ import type { WindowManager } from '../WindowManager';
 import type { LabelManager } from '../../labels/LabelManager';
 import type { CommandLineManager } from '../../cmdline/CommandLineManager';
 import type { ScrollBoxManager } from '../../scrollbox/ScrollBoxManager';
+import { type MouseEventRegistry } from '../../MouseEventRegistry';
 interface TextPanelProps {
     id: string;
     /** Human-readable window title (defaults to the id), used as the accessible
@@ -11,6 +12,8 @@ interface TextPanelProps {
     labels?: LabelManager;
     cmdLines?: CommandLineManager;
     scrollBoxes?: ScrollBoxManager;
+    /** addMouseEvent entries, which desktop puts in every console's menu. */
+    mouseEvents?: MouseEventRegistry;
     fontSize?: number;
     fontFamily?: string;
     /** Rendered row height in px (MXP frames). See WindowManager.setLineHeight. */
@@ -33,5 +36,5 @@ interface TextPanelProps {
     cmdLineValue?: string;
     cmdLineValueSeq?: number;
 }
-export declare function TextPanel({ id, title, manager, labels, cmdLines, scrollBoxes, fontSize, fontFamily, lineHeight, wrapAt, wrapIndent, wrapHangingIndent, backgroundColor, backgroundImage, cmdLineEnabled, cmdLineStyleSheet, cmdLineValue, cmdLineValueSeq }: TextPanelProps): import("react/jsx-runtime").JSX.Element;
+export declare function TextPanel({ id, title, manager, labels, cmdLines, scrollBoxes, mouseEvents, fontSize, fontFamily, lineHeight, wrapAt, wrapIndent, wrapHangingIndent, backgroundColor, backgroundImage, cmdLineEnabled, cmdLineStyleSheet, cmdLineValue, cmdLineValueSeq }: TextPanelProps): import("react/jsx-runtime").JSX.Element;
 export {};

package/dist-lib/ui/windows/panels/VariablesView.d.ts

@@ -2,20 +2,50 @@ import type { ScriptingEngine } from '../../../scripting/ScriptingEngine';
 interface VariablesViewProps {
     connectionId: string;
     scriptingEngineRef?: React.RefObject<ScriptingEngine | null>;
+    /** A search result asking for this top-level global to be brought into view.
+     *  `revision` makes a repeat jump to the same name re-apply the filter. */
+    focus?: {
+        name: string;
+        revision: number;
+    } | null;
+    /** Called once `focus` has been applied. The request lives in the parent,
+     *  which outlives this view — without clearing it, leaving the tab and
+     *  coming back would silently re-type the old name into the filter. */
+    onFocusConsumed?: () => void;
 }
+/**
+ * Re-point every hidden path that lived at `from` (or underneath it) at `to`,
+ * for a rename. Returns null when nothing referred to the old path, so the
+ * caller can skip a no-op store write.
+ *
+ * A descendant is spelled `from` followed by `.` or `[`, which are the only two
+ * separators {@link pathKey} emits — so `myTable` never captures `myTableTwo`.
+ */
+export declare function renameHiddenPaths(hidden: readonly string[], from: string, to: string): string[] | null;
+/** Drop every hidden path at `at` or underneath it, for a delete. Returns null
+ *  when none matched, so the caller can skip a no-op store write. */
+export declare function dropHiddenPaths(hidden: readonly string[], at: string): string[] | null;
 /**
  * Mudlet's Variables view: the live `_G` tree with a checkbox per top-level
  * entry that toggles whether it persists across sessions (the profile's
- * save-list / Mudlet `<VariablePackage>`). Built-in globals — the default Lua +
- * Mudlet API namespace present at runtime boot — are hidden by default (toggle
- * to show), so only your own variables appear. Tables expand to browse their
- * contents (fetched eagerly, so expansion is instant). Functions/userdata are
- * shown but not flaggable. Save flagging is top-level granularity (checking a
- * table persists all of it); per-key flagging is a follow-up.
+ * save-list / Mudlet `<VariablePackage>`), and the create/rename/retype/edit/
+ * hide/delete controls desktop puts in `vars_main_area.ui` — name
+ * (`lineEdit_var_name:73`), key type (`comboBox_variable_key_type:105`), hidden
+ * (`checkBox_variable_hidden:142`), value type
+ * (`comboBox_variable_value_type:165`), plus `dlgTriggerEditor::addVar`
+ * (:5211). Edits go straight into the running `_G`, so a script sees them
+ * immediately.
+ *
+ * Built-in globals — the default Lua + Mudlet API namespace present at runtime
+ * boot — are hidden by default (toggle to show), so only your own variables
+ * appear. Tables expand to browse their contents (fetched eagerly, so expansion
+ * is instant). Functions/userdata are shown but neither flaggable nor editable.
+ * Save flagging is top-level granularity (checking a table persists all of it);
+ * per-key flagging is a follow-up.
  *
  * Enumerating `_G` runs synchronously on the Lua/main thread, so we defer it a
  * tick behind a loader: the spinner paints first, then the walk runs, keeping
  * opening the tab responsive even for a large namespace.
  */
-export declare function VariablesView({ connectionId, scriptingEngineRef }: VariablesViewProps): import("react/jsx-runtime").JSX.Element;
+export declare function VariablesView({ connectionId, scriptingEngineRef, focus, onFocusConsumed }: VariablesViewProps): import("react/jsx-runtime").JSX.Element;
 export {};

package/dist-lib/ui/windows/panels/WindowCmdLine.d.ts

@@ -16,8 +16,10 @@ interface WindowCmdLineProps {
  * with WindowManager so getCmdLine([name]) can read the live text.
  *
  * Enter dispatches to the bound Lua callback (setCmdLineAction). When no
- * callback is bound, Enter is a no-op — userwindow command lines don't
- * automatically send to the MUD the way the main command bar does.
+ * callback is bound, the text is sent to the game as typed input, the way
+ * Mudlet's TCommandLine::enterCommand falls back to Host::send. History, Tab
+ * completion, Shift+Enter, Escape and what Enter leaves behind follow desktop's
+ * TCommandLine (see useSubCommandLineKeys).
  */
 export declare function WindowCmdLine({ id, manager, styleSheet, seedValue, seedSeq }: WindowCmdLineProps): import("react/jsx-runtime").JSX.Element;
 export {};

package/dist-lib/ui/windows/panels/aliasLoop.d.ts

@@ -0,0 +1,24 @@
+/**
+ * Edit-time detection of the alias that feeds itself: a pattern that matches
+ * its own substitution, so sending the command re-triggers the alias.
+ *
+ * Desktop refuses the save outright — `if (aliasSubstitutionLoops(regex,
+ * substitution)) { showAliasLoopWarning(...); return; }`
+ * (dlgTriggerEditor.cpp:6174-6178, :15054, :15090), implemented at :6269 as an
+ * unanchored match of the pattern against the substitution.
+ *
+ * Here it only warns. Mudlet Web already stops the damage at runtime — send()
+ * refuses past `MAX_SEND_DEPTH` with a message naming the alias — and that
+ * guard catches indirect loops (A → B → A) this one cannot see. Refusing the
+ * save on top of it would block the direct case while still letting the
+ * indirect one through, so the warning is what the runtime guard is missing:
+ * feedback before the 25 junk lines rather than after them.
+ *
+ * The match runs through JS `RegExp`, not PCRE — near enough for a warning, and
+ * a pattern that does not compile here produces none, mirroring desktop's
+ * `if (!rx.isValid()) return false`.
+ */
+export declare function aliasSubstitutionLoops(pattern: string, substitution: string): boolean;
+/** The warning shown beside a looping alias, worded as desktop words it
+ *  (`showAliasLoopWarning`, dlgTriggerEditor.cpp:6364-6369) minus the refusal. */
+export declare function aliasLoopWarning(name: string): string;

package/dist-lib/ui/windows/panels/editorClipboard.d.ts

@@ -0,0 +1,45 @@
+/**
+ * Copy / paste / duplicate for editor items.
+ *
+ * Mudlet round-trips the item and its subtree through XML — `slot_copyXml`
+ * (dlgTriggerEditor.cpp:11777) exports it to `mpHost->mpEditorDialog`'s
+ * clipboard buffer and `slot_pasteXml` (:11913) imports it back, which is why
+ * the paste mints fresh ids there too. Mudlet Web's nodes are plain objects, so the
+ * same job is a structured clone with remapped ids; the clipboard is an
+ * in-memory snapshot rather than XML text, which keeps it exact (no lossy
+ * element set) at the cost of not surviving a page reload — Mudlet's doesn't
+ * outlive its editor either.
+ */
+import type { EditorItemCategory, EditorItemNode } from './editorUndo';
+export interface EditorClipboard {
+    category: EditorItemCategory;
+    /** The copied item followed by its descendants, in tree order. */
+    nodes: EditorItemNode[];
+    /** What the context menu says it will paste, e.g. `trigger "qa-sub"`. */
+    label: string;
+}
+/**
+ * The item plus every descendant, root first and the rest in `items` order.
+ *
+ * Root-first matters because {@link cloneSubtree} and the paste placement both
+ * treat the first element as the item the user picked. Every producer happens
+ * to keep parents ahead of children today, but the walk below explicitly does
+ * not rely on that — so neither does this.
+ */
+export declare function collectSubtree<T extends {
+    id: string;
+    parentId: string | null;
+}>(items: readonly T[], rootId: string): T[];
+/**
+ * Copy `nodes` (a subtree, root first) under `newParentId` with fresh ids.
+ *
+ * `packageName` is dropped: uninstalling a package removes every item carrying
+ * its name, so a copy that kept the tag would be deleted along with the
+ * original the next time that package went away — and the package's own
+ * manifest never listed the copy in the first place.
+ *
+ * `existingNames` are the names already in use among the new siblings; a
+ * collision gets a " (copy)" suffix so the paste is visible in the tree rather
+ * than looking like nothing happened.
+ */
+export declare function cloneSubtree<T extends EditorItemNode>(nodes: readonly T[], newParentId: string | null, existingNames: ReadonlySet<string>, newId?: () => string): T[];

package/dist-lib/ui/windows/panels/editorUndo.d.ts

@@ -0,0 +1,79 @@
+/**
+ * The script editor's item-level undo stack.
+ *
+ * Mudlet's editor deletes immediately and never asks; what makes that safe is
+ * that every delete path builds an `EditorDeleteItemCommand` and pushes it onto
+ * the editor's own `EditorUndoStack` (dlgTriggerEditor.cpp:3714 for triggers,
+ * and the same at :3089 aliases, :3237 buttons, :3441 scripts, :3575 keys,
+ * :3848 timers), reachable from Ctrl+Z. This is that stack, minus the parts
+ * Mudlet only needs because of how it stores items:
+ *
+ *  * Mudlet snapshots each deleted item to XML and re-imports it on undo, which
+ *    mints fresh ids — hence the id remapping, the `remapItemID` plumbing and
+ *    the child-id fix-up loops all over `EditorDeleteItemCommand::undo()`.
+ *    Mudlet Web's nodes are plain objects with stable string ids, so the very same
+ *    objects go back and none of that is needed.
+ *  * Mudlet restores parents before children (a topological sort) because a
+ *    child needs a live parent pointer. Here the tree is a flat array plus
+ *    `parentId`, so restoring the whole subtree at its recorded indices
+ *    reproduces it in one step, in any order.
+ */
+import type { AliasNode, ButtonNode, KeyNode, ScriptNode, TimerNode, TriggerNode } from '../../../storage/schema';
+import type { RestoredNode } from '../../../storage/appStore';
+/** The six editor views that hold deletable items. Mirrors Mudlet's
+ *  EditorViewType minus the varUnit view, which has no delete command. */
+export type EditorItemCategory = 'scripts' | 'aliases' | 'triggers' | 'timers' | 'keys' | 'buttons';
+export type EditorItemNode = ScriptNode | AliasNode | TriggerNode | TimerNode | KeyNode | ButtonNode;
+/** Mudlet caps the editor stack at 50 commands (`setUndoLimit(50)`,
+ *  dlgTriggerEditor.cpp:457). */
+export declare const EDITOR_UNDO_LIMIT = 50;
+/**
+ * One reversible edit to the item tree.
+ *
+ * `delete` and `insert` are the same record read in opposite directions: both
+ * hold every node involved plus the index it occupied, so undoing one is
+ * redoing the other. Mudlet only ever pushes deletions here, but a paste that
+ * cannot be undone makes Ctrl+Z do something unrelated to what the user just
+ * did — so pastes and duplicates go on the same stack.
+ */
+export interface EditorItemCommand {
+    kind: 'delete' | 'insert';
+    category: EditorItemCategory;
+    /** Every node the command covers — the item and its whole subtree — each
+     *  with the index it occupied in the category's flat list. */
+    entries: ReadonlyArray<RestoredNode<EditorItemNode>>;
+    /** Undo-menu wording, e.g. `delete trigger "qa-sub"`. Mirrors
+     *  `EditorDeleteItemCommand::generateText`. */
+    label: string;
+}
+/**
+ * The item plus every descendant, paired with the index each occupies in
+ * `items` — exactly the set the store's `removeX` actions drop (they take the
+ * same `id` + `getDescendantIds` closure), so the capture and the removal can
+ * never disagree.
+ *
+ * Mudlet's `captureTriggerAndChildren` lambda (dlgTriggerEditor.cpp:3616) does
+ * the same walk, recording `positionInParent` because its tree is real
+ * parent/child widgets. Here sibling order lives in the flat array, so the flat
+ * index is the position worth keeping.
+ */
+export declare function captureDeletion<T extends {
+    id: string;
+    parentId: string | null;
+}>(items: readonly T[], id: string): RestoredNode<T>[];
+/** `delete trigger "qa-sub"` / `delete 4 triggers`, following
+ *  `EditorDeleteItemCommand::generateText` — including its choice to count the
+ *  captured descendants, not just the item the user picked. */
+export declare function describeDeletion(category: EditorItemCategory, entries: ReadonlyArray<{
+    node: {
+        name: string;
+    };
+}>): string;
+/** The same wording for the other direction — `paste trigger "qa-sub"`. */
+export declare function describeInsertion(category: EditorItemCategory, entries: ReadonlyArray<{
+    node: {
+        name: string;
+    };
+}>): string;
+/** Push onto a stack held at Mudlet's 50-command limit, dropping the oldest. */
+export declare function pushBounded<T>(stack: readonly T[], command: T): T[];

package/dist-lib/ui/windows/panels/mapAreaChange.d.ts

@@ -0,0 +1,10 @@
+/**
+ * The `sysMapAreaChanged(newAreaID, prevAreaID)` a centerview raises, or null
+ * when it raises none.
+ *
+ * Moving into another area raises it, as does the first centerview since the
+ * map widget opened (or its map was replaced) even when the room lies in the
+ * area already on show: that area is only the view restored from last time,
+ * and desktop reports the first centerview with -2 as the previous area.
+ */
+export declare function centerviewAreaChange(first: boolean, prevArea: number | null, areaId: number): [number, number] | null;

package/dist-lib/utils/appShellCache.d.ts

@@ -0,0 +1,25 @@
+/**
+ * Whether this build wants its shell cached at all.
+ *
+ * Only a built app does. A dev server has no content-hashed assets to cache
+ * anyway, and the caching it *could* do — the icons, the manifest, the WASM the
+ * plugin serves at the root — is pure cost there: a second copy written on every
+ * boot, and a hot-reload hazard for the one file that isn't content-addressed.
+ * It is measurable cost, too. The busted corpus boots the whole app 41 times in
+ * parallel contexts, and on a four-core CI runner the extra work per boot was
+ * enough to push readiness past its 90s timeout.
+ *
+ * Read at the two edges rather than inside the functions below, so the worker's
+ * registration URL and the page's decision to speak to it can't disagree.
+ */
+export declare const appShellCacheEnabled: boolean;
+/**
+ * Hand the active worker this build's resource list, once the page has settled.
+ * Safe to call when there is no worker, no support, or nothing loaded — it is a
+ * best-effort optimisation of a cache the worker also fills on its own.
+ */
+export declare function primeAppShellCache(): Promise<void>;
+/** How long after load to let stragglers arrive before taking the snapshot.
+ *  A flat wait rather than an idle callback: the browser counts as idle while a
+ *  WASM download is still in flight, which is exactly the case this is for. */
+export declare const SETTLE_MS = 5000;

package/dist-lib/utils/fontFamilyName.d.ts

@@ -0,0 +1,13 @@
+/**
+ * The family name a font file declares, or null when the bytes are not a font
+ * this can read.
+ *
+ * Null is a normal answer, not an error: a package may ship a font in a format
+ * with no sfnt wrapper, and the caller's job is then to say so rather than to
+ * register the file under a name nothing would ask for.
+ */
+export declare function fontFamilyName(bytes: Uint8Array): string | null;
+/** File extensions desktop's `Host::installPackageFonts` picks up
+ *  (Host.cpp:3513). */
+export declare const FONT_EXTENSIONS: readonly [".otf", ".ttf", ".ttc", ".otc"];
+export declare function isFontPath(path: string): boolean;

package/dist-lib/utils/fontLoader.d.ts

@@ -1,5 +1,9 @@
 import type { ProfileVFS } from '../scripting/vfs/ProfileVFS';
 import type { OutputFontSource } from '../storage';
+/** Cache-key component for anything that memoises a font measurement. */
+export declare function getFontGeneration(): number;
+/** Note that a family became usable — see `getFontGeneration`. */
+export declare function bumpFontGeneration(): void;
 /** Synchronous detection. May false-negative on a system font whose face the
  *  browser hasn't materialized yet — use {@link ensureFontAvailable} when an
  *  await is acceptable. */
@@ -53,5 +57,32 @@ export declare function primeLocalFontsCache(): Promise<void>;
  *  forms ("Family Name") are unwrapped to plain names. */
 export declare function getRegisteredFontFamilies(): string[];
 export declare function loadFontFromUrl(family: string, url: string): Promise<void>;
+/**
+ * Register a font file from the profile VFS under `family`.
+ *
+ * The face goes into `document.fonts` before this returns — synchronously —
+ * and the returned promise settles once the browser has parsed it. That order
+ * is what lets a package use its own font in the events its install raises
+ * straight after (#438): `getAvailableFonts()` reads `document.fonts`, and
+ * desktop's font database has the family the moment `loadFont` returns, so a
+ * `setFont` in sysInstallPackage or sysLoadEvent must find it. Text already
+ * asking for the family re-renders in it once the face has loaded, as with any
+ * web font. A file that will not load is taken out again and the promise
+ * rejects.
+ */
 export declare function loadFontFromVfs(family: string, path: string, vfs: ProfileVFS): Promise<void>;
+/**
+ * Make a font source drawable, without saying where it is to be drawn.
+ *
+ * A `system` source is whatever the machine already has, so there is nothing to
+ * do; the other two have to be fetched or read out of the profile before the
+ * family name means anything. Both underlying loaders are idempotent, so calling
+ * this again for a font already registered costs nothing — which is what lets it
+ * sit in an effect keyed on the setting.
+ *
+ * Separate from {@link applyOutputFont} because the map's room-symbol font needs
+ * the registration half and not the CSS-variable half: it is handed to a canvas
+ * by the renderer, not inherited through the document.
+ */
+export declare function registerFontSource(font: OutputFontSource | undefined, vfs: ProfileVFS | null): Promise<void>;
 export declare function applyOutputFont(font: OutputFontSource | undefined, vfs: ProfileVFS | null): Promise<void>;

package/dist-lib/utils/formatBytes.d.ts

@@ -0,0 +1,4 @@
+/** Byte count for a person: "912 B", "48 KB", "3.4 MB". Rounded hard on
+ *  purpose — these appear next to a control, where the order of magnitude is
+ *  the whole message and a second decimal place is noise. */
+export declare function formatBytes(n: number): string;

package/dist-lib/utils/mustBeOneOf.d.ts

@@ -0,0 +1,9 @@
+/**
+ * The refusal Mudlet gives a value outside a fixed set of words, in the one
+ * wording its API settled on: `<what> must be "a", "b" or "c", got "x"` — no
+ * function-name prefix, double quotes, no comma before the "or".
+ *
+ * The Lua twin is `__mudlet_must_be_one_of` in `src/scripting/lua/Bridge.lua`;
+ * keep the two in step.
+ */
+export declare function mustBeOneOf(what: string, values: readonly string[], got: unknown): string;

package/dist-lib/utils/profileLock.d.ts

@@ -1,5 +1,5 @@
 /** Shared prefix for every per-profile Web Lock name. */
-export declare const PROFILE_LOCK_PREFIX = "mudix:profile:";
+export declare const PROFILE_LOCK_PREFIX = "mudlet:profile:";
 /** Web Lock name for a profile. */
 export declare const profileLockName: (connectionId: string) => string;
 /** Inverse of {@link profileLockName}: the connectionId encoded in a lock name,

package/dist-lib/utils/storedCredentials.d.ts

@@ -0,0 +1,31 @@
+/**
+ * Where auto-login credentials come from, in priority order — one place so the
+ * GMCP `Char.Login` path and the text-login state machine can never disagree
+ * about which password they are about to send.
+ *
+ * 1. **In-memory** (`sessionCredentials`) — a branded build's login form. Those
+ *    builds never persist anything, so this is the only source they have.
+ * 2. **The credential vault**, when one is installed and unlocked.
+ * 3. **`charLoginPassword` on the connection record** — the pre-vault plaintext
+ *    field. Never written any more (see issue #25) and no longer offered in the
+ *    UI, but still read so that an existing saved login keeps working until the
+ *    user sets a vault up, at which point it is migrated and deleted
+ *    (`useVaultSaver`).
+ *
+ * The account name is not a secret and stays on the connection record either
+ * way: prefilling it is also what lets a browser password manager pick the one
+ * matching password instead of offering every profile's.
+ */
+export interface StoredLogin {
+    account: string;
+    password: string;
+}
+export declare function readStoredLogin(connectionId: string): StoredLogin;
+/**
+ * Drop vault entries for profiles that no longer exist.
+ *
+ * Deleting a profile can't rewrite the vault when it is locked — there is no
+ * key to re-encrypt the remaining secrets with — so `forgetConnection` leaves
+ * the entry behind and the sweep happens here instead, on the next unlock.
+ */
+export declare function pruneVaultEntries(): void;

package/dist-lib/utils/systemTheme.d.ts

@@ -0,0 +1,24 @@
+import type { Theme } from '../storage/schema';
+/** The stored value meaning "whatever the OS is set to". Never reaches
+ *  `data-theme`; {@link resolveTheme} turns it into a real palette first. */
+export declare const SYSTEM_THEME = "system";
+/** Whether the OS is asking for a dark UI right now. Defaults to dark when
+ *  nothing can be asked, which is this app's own default. */
+export declare function prefersDark(): boolean;
+/**
+ * The concrete palette to render: `theme` itself, unless it is the system
+ * sentinel. Safe to call with any stored value, including one from a brand.
+ */
+export declare function resolveTheme(theme: Theme | undefined): Theme;
+/** `isLightTheme` through {@link resolveTheme}, for callers holding a stored
+ *  value rather than a resolved one (the editor's syntax palette). */
+export declare function isLightResolvedTheme(theme: Theme | undefined): boolean;
+/**
+ * Call `onChange` whenever the OS preference flips, so a theme left on "System
+ * setting" repaints without a reload. Returns an unsubscribe.
+ *
+ * Subscribed unconditionally rather than only while `system` is selected: the
+ * listener is one boolean check, and gating it on the current value would mean
+ * re-subscribing every time the theme changes for no saving worth having.
+ */
+export declare function onSystemThemeChange(onChange: () => void): () => void;

package/dist-lib/utils/timeZone.d.ts

@@ -0,0 +1,10 @@
+/** Short zone name in effect at `date` ("UTC", "EST", "CET") — what glibc's
+ *  `%Z` and Qt's `t` format token print. A zone tzdata gives no letters gets
+ *  its numeric abbreviation ("+03", "+0545"); a time before the zone adopted
+ *  standard time is its local mean time, "LMT". `timeZone` is an IANA id; the
+ *  local zone when omitted. */
+export declare function timeZoneAbbreviation(date: Date, timeZone?: string): string;
+export declare function timeZoneLongName(date: Date): string;
+/** The local zone's offset from UTC at `date` as "+hhmm", or "+hh:mm" with
+ *  `colon` — Qt's `tt` and `ttt`. */
+export declare function timeZoneOffset(date: Date, colon?: boolean): string;