mulmoterminal 2.3.0 → 2.5.0

package/README.md

@@ -21,6 +21,13 @@ ping to your phone when a task finishes. One `npx` command, no Electron, no conf
 npx mulmoterminal        # starts on http://localhost:34567 and opens your browser
 ```
 
+> **Something looks wrong?** Type `/mulmoterminal-bug-report` in any MulmoTerminal session. The
+> bundled skill hears the symptom out, checks your **real** config, schema and version to see
+> whether the behaviour is configuration or by design, searches the existing issues — and only
+> helps you file one if none of that explains it, with the environment collected and secrets
+> masked. Getting you unstuck is the goal; an issue is what is left when the first three steps
+> fail.
+
 ![MulmoTerminal's grid view — four live Claude sessions running side by side, each in its own color-coded project](https://raw.githubusercontent.com/receptron/mulmoterminal/main/docs/guide/images/grid-2x2-live.png)
 
 *The grid is a **cockpit for parallel agents** — here, four live Claude sessions, each in its own color-coded project. Every cell's header carries what you need to triage at a glance: **model · context %**, **token counts** (`⇡in ⇣out`), the **git branch / changes** chip, and an AI summary of what the agent is doing. A cell's **border color signals state** — working / done (blue), needs-you (amber — e.g. waiting on a permission), idle — with an attention chime so a stuck cell off-screen still pulls you back. Supervise many; only step in where you're called.*
@@ -93,6 +100,13 @@ than as bytes (files within the session's working directory only):
 | source, config, logs, and `.txt` — 46 extensions | the app's own **Files** view (`/files?path=`), where CodeMirror highlights it, the tree is right there, and it can be edited |
 | everything else — images, PDF, SVG, HTML, video | raw bytes in a new tab, which the browser renders better than an editor would |
 
+**While a grid cell is enlarged, the [Files pane](#files-view-browse--edit) takes the click first** — every
+row above except the last one, since the pane is the same editor plus a Markdown preview. The
+file opens *beside* the terminal that printed it, and the pane opens itself if it was closed.
+It declines, leaving the routing above untouched, when nothing is enlarged, when the path is
+not under that cell's own directory (the pane cannot walk above its root), or for the raw-bytes
+row, where it would only show an empty editor.
+
 Highlighting in the Files view covers the JS/TS family, JSON and Markdown (the modes
 `cmEditor.ts` bundles); other languages open as plain text.
 
@@ -448,7 +462,7 @@ The Settings modal (⚙) persists per-user UI choices to `~/.mulmoterminal/confi
 
 ![The Settings modal — theme, notification sound, PR repos, launch commands, and MCP servers](https://raw.githubusercontent.com/receptron/mulmoterminal/main/docs/guide/images/settings.png)
 
-*Open it from the ⚙ button in the toolbar. Pick a **theme**, set the **terminal font size**, set a custom **attention sound**, list the repos the cross-repo **PRs & Issues** view should aggregate, add **launch commands** for grid cells, and register your own **MCP servers** — no need to hand-edit the config file. Note that **theme and font size are stored per browser** (they're display preferences, so a phone and a desktop keep their own); the rest live in `~/.mulmoterminal/config.json` and are shared by every client.*
+*Open it from the ⚙ button in the toolbar. Pick a **theme**, set the **terminal font size** and **scroll speed**, set a custom **attention sound**, list the repos the cross-repo **PRs & Issues** view should aggregate, add **launch commands** for grid cells, and register your own **MCP servers** — no need to hand-edit the config file. Note that **theme, font size and scroll speed are stored per browser** (they're display preferences, so a phone and a desktop keep their own); the rest live in `~/.mulmoterminal/config.json` and are shared by every client.*
 
 | Field        | Meaning |
 | ------------ | ------- |
@@ -461,16 +475,23 @@ The Settings modal (⚙) persists per-user UI choices to `~/.mulmoterminal/confi
 | `quickCommands` | `{ label, text, agents? }` phrases the **phone** offers as chips on a session's terminal view. Tapping one puts `text` in the input box; it is not sent until you press send. `agents` (`"claude"` / `"codex"` / `"shell"`) scopes a chip to session kinds — omit it to offer the chip everywhere. Empty by default. |
 | `userMcpServers` | `{ id, url }` HTTP MCP servers merged into the **single-view** Claude session's `--mcp-config` (a `localhost` URL is reached over `host.docker.internal` in the Docker sandbox). Takes effect on the next session. |
 | `buttons`    | Header action buttons — see [Header buttons](#header-buttons). Omit to keep the defaults; set to replace them. |
-| `chips`      | Header info chips. Omit to keep the default set; `[]` hides all built-ins. |
+| `chips`      | Header info chips (`dir` / `git` / `work` / `diff` / `ctx` / `usage` / `status` / `tools`, or custom text). Omit to keep the default set; `[]` hides all built-ins. `work` shows which PR / issue the cell is on (`#977 → #966`) and clears itself when the PR merges — see the [Configuration guide](https://receptron.github.io/mulmoterminal/guide/en/config.html#work-chip). |
 | `pushEnabled` | `true` to send a **Web Push** to your registered devices. Off by default; only sends while the **RemoteHost** channel is connected (see below). The master switch — `pushKinds` picks which moments. |
 | `pushKinds` | Which moments push: `"finished"` (a turn ended, ✅) and/or `"waiting"` (the agent stopped to ask — a permission prompt or a question, ❓, **once per prompt**). Omit to keep both; `[]` for none. A kind added in a later version stays off until you tick it. |
 | `worklogEnabled` | `true` to run the built-in **dev worklog** batch (see below). Off by default (each run spawns an LLM session, so it costs tokens). |
 | `worklogIntervalHours` | Worklog cadence in hours (default `6`, clamped to `1`–`168`). |
 | `terminalSubmit` | Which bytes Claude reads as **submit** vs **newline**: `"cr"` (default — Enter submits, Shift+Enter makes a newline) or `"esc-cr"` (for a Claude Code rebound the other way). Applies to the keyboard **and** the phone remote-view submit, for **Claude sessions only** (shell/codex keep plain Enter). See the [Configuration guide](https://receptron.github.io/mulmoterminal/guide/en/config.html#terminal-submit). |
 | `copyOnSelect` | `true` puts a **mouse selection on the clipboard the moment it settles**, with no key pressed (the PuTTY / iTerm2 behaviour). **Off by default** — it changes the clipboard when you may only have meant to highlight something. No Settings UI: edit the file and reload the tab. Composes with the `copy` keymap action rather than replacing it. Over plain `http://` the browser gives a page no clipboard access, so a fallback asks xterm to copy instead; see the [Configuration guide](https://receptron.github.io/mulmoterminal/guide/en/config.html#copy-on-select). |
-| `prWorkdirFooter` | Ends the body of a PR **⧉ Open PR** creates with `work in <clone>` — the directory name of the clone the work happened in, so a PR says which of several side-by-side checkouts produced it. **On by default**; set `false` to opt out — read from the file per PR, so no restart is needed (there is no Settings control for it). Only applied to PRs this app creates (pressing the button again on an existing PR never re-appends). |
+| `prWorkdirFooter` | Ends a PR body with `work in <clone>` — the directory name of the clone the work happened in, so a PR says which of several side-by-side checkouts produced it. Applies to **both** paths that open PRs here: **⧉ Open PR** appends it to the PR it creates, and every Claude session is told to end the bodies it writes with the same line (the name is resolved by the server, so a session inside a managed worktree still names the main checkout). **On by default**; set `false` to opt out — read per PR and per session spawn, so no restart is needed (there is no Settings control for it). Appending is idempotent: an existing PR never gets a second copy. |
 | `fontFamily` | The **terminal font** every session renders in — a CSS font-family stack, e.g. `"'Cica', 'MS Gothic', monospace"`. No Settings UI: edit the file, then **restart** (this config is read once at startup). Unset uses the built-in stack (JetBrains Mono / Fira Code / Menlo / Consolas, then CJK faces for Japanese, Korean and Chinese). Unlike the per-browser font **size**, this is one value for the whole host — it names fonts, and which fonts exist is a property of the machine. A directory can override it. See the [Configuration guide](https://receptron.github.io/mulmoterminal/guide/en/config.html#font-family). |
 
+Every MulmoTerminal on the machine shares this one file, so an older build could save over a key a
+newer one wrote. It doesn't: a **top-level key this version doesn't recognise is written back
+untouched**, which is what makes running two versions side by side — or downgrading for a while —
+safe. A mistyped key survives on the same rule, which is deliberate: a line you can still see is
+easier to debug than one that silently vanished. See the
+[Configuration guide](https://receptron.github.io/mulmoterminal/guide/en/config.html#unknown-keys).
+
 #### Header buttons
 
 Each terminal header shows configurable **action buttons**. Omitting `buttons` (globally or per-dir)
@@ -620,6 +641,12 @@ as the reload signal, so colors, palette, font size and grid order update withou
 anything. There is no filesystem watcher, so an edit made **outside** a session (your own
 editor) is picked up when the terminal is next opened.
 
+**Checking what took effect.** Settings → **Directory settings** lists your recent directories
+and expands each one to the values in force, with a swatch per color and the path of the file
+they came from. It also names the keys it **dropped** (a color that isn't `#rrggbb`, a size out
+of range) and the keys it doesn't read at all (`badgeColour`, a global-only setting) — which is
+what tells "I never set that" apart from "I set it and it didn't take".
+
 ---
 
 ## Running
@@ -771,6 +798,10 @@ shrinks the pane rather than reflowing xterm into garbage. It works in both zoom
 (cockpit roster and thumbnail filmstrip), the pane re-roots as you walk the zoom between
 terminals, and whether it's open plus how wide it is are remembered per browser.
 
+The toggle is not the only way in: while a cell is enlarged, **clicking a file path the agent
+printed** opens it here too, rather than in a new tab or full-screen — see
+[Clicking a file path](#clicking-a-file-path).
+
 All reads and writes go through `GET/PUT /api/files/browse/*?cwd=&path=`, and every
 `path` is **contained within the project root** (server-side) — `..`/absolute escapes
 are rejected for reads and writes alike, so editing can't reach outside the directory
@@ -941,6 +972,10 @@ Favorited collections get their own toolbar buttons.
   **Option** is treated as Meta so Claude's Alt-key bindings work. If your Claude Code is
   rebound so Enter and Shift+Enter behave backwards, flip them with
   [`terminalSubmit`](https://receptron.github.io/mulmoterminal/guide/en/config.html#terminal-submit).
+- **Scroll speed** — one wheel notch or trackpad swipe moves the terminal the same distance
+  whether you're reading a shell's scrollback or a full-screen app like Claude Code. If a
+  two-finger scroll on a Mac trackpad flies past what you were reading, turn **terminal scroll
+  speed** down in Settings (0.25×–3×, per browser — it's a property of the pointing device).
 - **No accidental page zoom** — `Ctrl`+wheel and a trackpad pinch would rescale the whole
   page and drag the layout and the terminal's fit along with it, so both are ignored.
   Keyboard zoom (`Cmd`/`Ctrl` `+` / `-`) still works when you mean it, and a phone's finger
@@ -1137,6 +1172,7 @@ same-origin-guarded.
 | -------- | ------- |
 | `GET\|POST /api/config` | User UI config (`cwdPresets`, `soundFile`, `soundKinds`, `sounds`, `prRepos`, `launchers`, `quickCommands`, `userMcpServers`, `providers`). |
 | `GET /api/sound?kind=` · `/api/dir-sound?cwd=&kind=` · `/api/sound-preset/:id` · `/api/dir-config?cwd=` | Custom / per-directory / preset attention sound + per-dir config. `kind` selects a config entry, never a path. |
+| `GET /api/dir-config-detail?cwd=` | The same per-dir config, **plus** the settings a running terminal doesn't need (`provider`, `model`, `skills`, `addDirs`, header button/chip **labels**), **plus** which keys the file set and how each fared (applied / dropped in validation / not a setting at all). Read-only; backs the Settings modal's **Directory settings** preview. Unlike the other `?cwd=` routes this one does **not** fall back to the default workspace — it reports on the directory it was asked about, so a path that no longer exists comes back as `exists:false`. Sound paths and button commands stay server-side. |
 | `GET /api/launch-options` | The Anthropic-compatible backends this server can reach, each with its models and — when it can't — the reason. Reports the **name** of the env var a key is read from, never the key. |
 | `GET /api/notifications`(`/history`) · `POST /api/notifications/:id/clear` | Notification feed. |
 | `POST /api/transcribe`(`/model`…) | Voice-input transcription (Whisper, macOS). |

package/bin/cli-args.d.ts

@@ -10,3 +10,4 @@ export declare const SECOND_INSTANCE_NOTE: string;
 export declare const MIN_NODE_LABEL: string;
 export declare function nodeMeetsMinimum(version: string): boolean;
 export declare function serverNodeArgs(serverEntry: string, launchDir: string): string[];
+export declare function serverSpawnEnv(env: Record<string, string | undefined>, port: number, cwd: string): Record<string, string | undefined>;

package/bin/cli-args.js

@@ -150,3 +150,19 @@ export function nodeMeetsMinimum(version) {
 export function serverNodeArgs(serverEntry, launchDir) {
   return ["--import", "tsx", `--env-file-if-exists=${join(launchDir, ".env")}`, serverEntry];
 }
+
+/**
+ * The environment the launcher spawns the server with.
+ *
+ * Only the two values the server cannot work out for itself. In particular NOT `NODE_ENV`:
+ * the server hands its own environment to every PTY it spawns, so a `NODE_ENV=production`
+ * set here reaches every terminal in every cell — where yarn v1 reads it and installs
+ * WITHOUT devDependencies while still reporting success (#955). Express is pinned to
+ * production separately, in the server, so nothing here needs to say it.
+ *
+ * A `NODE_ENV` the user exported themselves passes through untouched: this decides what the
+ * launcher adds, not what it removes.
+ */
+export function serverSpawnEnv(env, port, cwd) {
+  return { ...env, PORT: String(port), CLAUDE_CWD: cwd };
+}

package/bin/mulmoterminal.js

@@ -26,6 +26,7 @@ import {
   nodeMeetsMinimum,
   MIN_NODE_LABEL,
   serverNodeArgs,
+  serverSpawnEnv,
 } from "./cli-args.js";
 
 const __dirname = dirname(fileURLToPath(import.meta.url));
@@ -272,7 +273,7 @@ function runServer(port, noOpen, cwd, onChild) {
     // package directory, so serverNodeArgs makes that path absolute (#795).
     const server = spawn(process.execPath, serverNodeArgs(SERVER_ENTRY, process.cwd()), {
       cwd: PKG_DIR,
-      env: { ...process.env, NODE_ENV: "production", PORT: String(port), CLAUDE_CWD: cwd },
+      env: serverSpawnEnv(process.env, port, cwd),
       stdio: ["inherit", "inherit", "pipe"],
     });
     let stderrTail = "";

package/common/dirConfigSource.ts

@@ -0,0 +1,101 @@
+// Where a directory's settings actually came from, for the settings modal's preview.
+//
+// The rest of the app only ever needs the RESOLVED config — the values a terminal adopts.
+// That is exactly what makes a mistyped or rejected setting invisible: the file is on disk,
+// the app reads it, and the value silently isn't there. This says which keys the file set,
+// which of them survived validation, and which the app doesn't read at all.
+
+// Every key `loadDirConfig` reads. A key outside this list is a typo as far as the app is
+// concerned, however sensible it looks — `server/config/dir-config.spec.ts` pins the two
+// together so a field added to the loader can't quietly go missing here.
+export const DIR_CONFIG_KEYS = [
+  "name",
+  "badgeColor",
+  "headerColor",
+  "headerTextColor",
+  "cellColor",
+  "cellBorderColor",
+  "dotColor",
+  "buttonColor",
+  "fontSize",
+  "fontFamily",
+  "orderPriority",
+  "theme",
+  "colors",
+  "sound",
+  "sounds",
+  "buttons",
+  "chips",
+  "skills",
+  "provider",
+  "model",
+  "addDirs",
+] as const;
+
+export interface DirConfigSource {
+  // Keys the file set that the app is using.
+  applied: string[];
+  // Keys the file set that the app read and then dropped — an out-of-range number, a colour
+  // that isn't #rrggbb, a sound outside the directory. The value is gone; the key is the clue.
+  ignored: string[];
+  // Keys the app doesn't read at all: a misspelling (`badgeColour`), or a setting that belongs
+  // in the global config instead of a directory's file.
+  unknown: string[];
+}
+
+export const EMPTY_DIR_CONFIG_SOURCE: DirConfigSource = { applied: [], ignored: [], unknown: [] };
+
+// The settings a directory can make that the per-cell config deliberately doesn't carry — the
+// browser has no use for them while running a terminal, but the preview has to SHOW them or a
+// key like `provider` can only be named as applied, never read back.
+//
+// Labels only for buttons and chips: their `cmd` / `text` is what the button would type into
+// the session, which is not what "did my config take effect" needs, and is the sort of thing a
+// screenshot of the settings screen shouldn't carry. Sound paths stay out for the same reason
+// they stay out of the per-cell config — that path is the confinement boundary.
+export interface DirConfigExtras {
+  provider: string | null;
+  model: string | null;
+  skills: string[] | null;
+  addDirs: string[] | null;
+  buttonLabels: string[];
+  chipLabels: string[];
+}
+
+export const EMPTY_DIR_CONFIG_EXTRAS: DirConfigExtras = {
+  provider: null,
+  model: null,
+  skills: null,
+  addDirs: null,
+  buttonLabels: [],
+  chipLabels: [],
+};
+
+// "The loader kept nothing for this key" — null/undefined, but also the empty collections the
+// loader returns when every entry in a map or list was rejected.
+function isEmptyValue(value: unknown): boolean {
+  if (value === null || value === undefined) return true;
+  if (Array.isArray(value)) return value.length === 0;
+  if (typeof value === "object") return Object.keys(value as Record<string, unknown>).length === 0;
+  return false;
+}
+
+// The keys a resolved config actually holds a value for. Taken as a SET by describeDirConfig
+// rather than the config object itself: the loader's type is an interface with named fields,
+// which no amount of `Record<string, unknown>` will accept without a cast.
+export function keysWithValue(resolved: object): Set<string> {
+  const entries: [string, unknown][] = Object.entries(resolved);
+  return new Set(entries.filter(([, value]) => !isEmptyValue(value)).map(([key]) => key));
+}
+
+// `raw` is the file as parsed; `kept` is which keys survived the loader (see keysWithValue).
+export function describeDirConfig(raw: Record<string, unknown>, kept: ReadonlySet<string>): DirConfigSource {
+  const known = new Set<string>(DIR_CONFIG_KEYS);
+  const source: DirConfigSource = { applied: [], ignored: [], unknown: [] };
+  for (const key of Object.keys(raw)) {
+    if (!known.has(key)) source.unknown.push(key);
+    else if (kept.has(key)) source.applied.push(key);
+    else source.ignored.push(key);
+  }
+  return source;
+}

package/common/prPhase.ts

@@ -0,0 +1,65 @@
+// What a cell is working on, as it travels between the two sides: the branch's PR, its phase in
+// the review loop, and the issue that PR closes. Shared because BOTH sides decide from it — the
+// server derives it from `gh`, the client decides what the header chip shows — and it used to be
+// two declarations with a "keep them in sync" comment on one of them (src/components/rosterPhase.ts).
+
+// Ordered roughly along the lifecycle so the client can pick a colour/label per phase.
+// `none` = no PR for this branch yet (still local work); `ready` = open, CI green, no
+// changes requested — i.e. waiting to merge.
+export type PrPhase = "none" | "draft" | "ci-failing" | "changes-requested" | "ci-running" | "ready" | "merged" | "closed";
+
+export const PR_PHASES: readonly PrPhase[] = ["none", "draft", "ci-failing", "changes-requested", "ci-running", "ready", "merged", "closed"];
+
+export const isPrPhase = (v: unknown): v is PrPhase => typeof v === "string" && (PR_PHASES as readonly string[]).includes(v);
+
+// The /api/pr-phase response. `phase` and `prUrl` predate the rest and the roster reads them;
+// the numbers are what lets a cell say WHICH work it is on rather than just how far along it is.
+export interface WorkItem {
+  phase: PrPhase;
+  pr: number | null;
+  prUrl: string | null;
+  issue: number | null;
+  issueUrl: string | null;
+}
+
+export const EMPTY_WORK_ITEM: Readonly<WorkItem> = { phase: "none", pr: null, prUrl: null, issue: null, issueUrl: null };
+
+// GitHub's closing keywords, as GitHub itself matches them: any of these, then optional
+// whitespace/colon, then #N. Anything else in the body is a mention, not a link — a PR that
+// says "related to #12" is not working on #12.
+// One character class for the separator, not `\s*:?\s+`: two adjacent whitespace quantifiers
+// backtrack super-linearly on a long body, and a PR description is user input.
+//
+// `[1-9]\d*` rather than `\d+`: there is no issue #0, and `#0123` is not issue 123 — both are
+// typos, and a typo that renders as a link to somebody else's issue is worse than no chip.
+const CLOSING_KEYWORD = /\b(?:close[sd]?|fix(?:e[sd])?|resolve[sd]?)[:\s]+#([1-9]\d*)/i;
+
+// Digits from a body or a branch name are unbounded, and `Number("9".repeat(20))` is 1e20 — which
+// would render in the chip as "#1e+20" and link nowhere. Anything past the safe-integer range is
+// not an issue number (found by Codex review).
+function toIssueNumber(digits: string): number | null {
+  const n = Number(digits);
+  return Number.isSafeInteger(n) && n > 0 ? n : null;
+}
+
+// The issue a PR body says it closes, or null. Deliberately blind to the full-URL form
+// (`Fixes https://github.com/o/r/issues/12`): that can name ANOTHER repository, and a number
+// shown next to this cell's PR has to belong to the same repo to be clickable and true.
+export function issueRefFromPrBody(body: string | null | undefined): number | null {
+  const found = typeof body === "string" ? CLOSING_KEYWORD.exec(body) : null;
+  return found ? toIssueNumber(found[1]) : null;
+}
+
+// A branch named after its issue the way this repo names them: `fix/966-preserve-unknown-keys`.
+// Requires a type prefix and a hyphen after the digits, so `chore/dep-updates-20260728` is not
+// read as issue #20260728.
+const BRANCH_ISSUE = /^[a-z][a-z-]*\/([1-9]\d*)-/;
+
+// A CANDIDATE, never an answer: `release/2026-07-28-hotfix` yields 2026 here, and no pattern can
+// tell that apart from a branch for issue #2026 — the year and the number have the same shape.
+// The caller must confirm the issue exists before showing it, or a cell claims to be working on
+// somebody else's issue. Named for the doubt so a call site can't forget it.
+export function issueCandidateFromBranch(branch: string | null | undefined): number | null {
+  const found = typeof branch === "string" ? BRANCH_ISSUE.exec(branch) : null;
+  return found ? toIssueNumber(found[1]) : null;
+}

package/common/rateLimits.ts

@@ -0,0 +1,37 @@
+// The rate-limit wire shape, and the one parser for it (#387).
+//
+// Here rather than on either side because BOTH decide from it: the server reads it back out of its
+// own cache file, and the browser reads it off `/api/rate-limits`. Written twice it was written
+// twice differently — jscpd caught the copies before they had a chance to drift.
+//
+// Everything is optional on purpose. A window can be absent because the agent is not installed,
+// because the plan is API-key billed, because no session has answered yet, or because upstream
+// dropped the field (anthropics/claude-code#40094). None of those are zero, and a gauge reading
+// 0% when the truth is 83% is the worst thing this data can do.
+
+export interface RateLimitWindow {
+  usedPercentage: number; // 0-100, fractional
+  resetsAt_sec: number | null; // Unix epoch seconds
+}
+
+export interface RateLimits {
+  fiveHour: RateLimitWindow | null;
+  sevenDay: RateLimitWindow | null;
+}
+
+const isRecord = (value: unknown): value is Record<string, unknown> => typeof value === "object" && value !== null;
+const finiteNumber = (value: unknown): number | null => (typeof value === "number" && Number.isFinite(value) ? value : null);
+
+export function parseRateLimitWindow(raw: unknown): RateLimitWindow | null {
+  if (!isRecord(raw)) return null;
+  const used = finiteNumber(raw.usedPercentage);
+  return used === null ? null : { usedPercentage: used, resetsAt_sec: finiteNumber(raw.resetsAt_sec) };
+}
+
+/** Null when neither window survives, so a caller can tell "nothing to show" from "0% used". */
+export function parseRateLimits(raw: unknown): RateLimits | null {
+  if (!isRecord(raw)) return null;
+  const fiveHour = parseRateLimitWindow(raw.fiveHour);
+  const sevenDay = parseRateLimitWindow(raw.sevenDay);
+  return fiveHour || sevenDay ? { fiveHour, sevenDay } : null;
+}

package/common/terminalScrollSpeed.ts

@@ -0,0 +1,31 @@
+// How far one wheel/trackpad gesture scrolls the terminal, as a multiplier on the xterm
+// default (1 = xterm's own speed). Shared because both sides decide from the same numbers:
+// the Settings stepper bounds its own buttons, and the client re-validates what it reads back
+// out of localStorage.
+//
+// It drives BOTH scrolling paths, which are different code: xterm's `scrollSensitivity` for
+// the normal buffer's scrollback, and the wheel-report accumulator in ./mouseReports for a
+// full-screen TUI in the alternate buffer (Claude Code). One setting, because to the person
+// scrolling they are the same gesture.
+export const TERMINAL_SCROLL_SPEED_DEFAULT = 1;
+// A macOS trackpad emits a wheel event every few pixels, so the useful range sits below 1 —
+// 0.25 is "a swipe moves a paragraph", still fast enough to cross a long transcript. Above 3
+// a single flick outruns the renderer and lands nowhere readable, which is the complaint this
+// setting exists to answer.
+export const TERMINAL_SCROLL_SPEED_MIN = 0.25;
+export const TERMINAL_SCROLL_SPEED_MAX = 3;
+export const TERMINAL_SCROLL_SPEED_STEP = 0.25;
+
+// Clamp rather than reject an out-of-range number, for the same reason the font size does:
+// honouring the direction the user asked for reads as working, where snapping back to the
+// default reads as ignored. Non-numeric input means "nothing set here" and stays null so the
+// caller can fall back. Values are snapped to the step so the label stays readable (0.75, not
+// 0.7499999) and so the stepper can't drift off its own grid.
+export function normalizeScrollSpeed(input: unknown): number | null {
+  if (typeof input !== "number" || !Number.isFinite(input)) return null;
+  const clamped = Math.min(TERMINAL_SCROLL_SPEED_MAX, Math.max(TERMINAL_SCROLL_SPEED_MIN, input));
+  const snapped = Math.round(clamped / TERMINAL_SCROLL_SPEED_STEP) * TERMINAL_SCROLL_SPEED_STEP;
+  // The multiply above reintroduces binary-float noise (0.30000000000000004); two decimals is
+  // more than the step needs and leaves the value safe to compare and to render.
+  return Math.round(snapped * 100) / 100;
+}

package/dist/assets/{abnfDiagram-VRR7QNED-RjiYivmv-B8nu2pUR.js → abnfDiagram-VRR7QNED-RjiYivmv-ZKZeabOo.js}

@@ -1 +1 @@
-import{n as e}from"./chunk-Y2CYZVJY-Bdt8pFDJ-DsF7k-Jl.js";import{f as t}from"./src-Brzfja-q-ch1VcTiG.js";import{_ as n,g as r}from"./mermaid-parser.core-DxEa8E3F-BILJo_fK.js";import"./chunk-WYO6CB5R-BlzOfotS-04XZ1Jfd.js";import"./chunk-VAUOI2AC-CS9QJ4yz-Dd_VpRsu.js";import{n as i,r as a,t as o}from"./chunk-MOJQB5TN-CMZRaeqt-Dy6S_sS_.js";import{t as s}from"./chunk-JWPE2WC7-BQ3zXr2k-DSd3Ct95.js";var c=r().RailroadAbnf.parser.LangiumParser,l=e(e=>{let t=e.alternatives.map(u);return t.length===1?t[0]:{type:`choice`,alternatives:t}},`transformAlternation`),u=e(e=>{let t=e.elements.map(f);return t.length===1?t[0]:{type:`sequence`,elements:t}},`transformConcatenation`),d=e(e=>{if(e.includes(`*`)){let[t,n]=e.split(`*`);return{min:t?parseInt(t,10):0,max:n?parseInt(n,10):1/0}}let t=parseInt(e,10);return{min:t,max:t}},`parseRepeat`),f=e(e=>{let t=p(e.primary);if(!e.repeat)return t;let{min:n,max:r}=d(e.repeat);return n===0&&r===1?{type:`optional`,element:t}:{type:`repetition`,element:t,min:n,max:r}},`transformElement`),p=e(e=>{switch(e.$type){case`AbnfStringLiteral`:return{type:`terminal`,value:e.value};case`AbnfNumVal`:return{type:`terminal`,value:e.value};case`AbnfRuleName`:return{type:`nonterminal`,name:e.name};case`AbnfGroup`:return l(e.element);case`AbnfOptionalGroup`:return{type:`optional`,element:l(e.element)};default:throw Error(`Unsupported ABNF primary node: ${e.$type}`)}},`transformPrimary`),m=e(e=>({name:e.name,definition:l(e.definition)}),`transformRule`),h=e(e=>{s(e,a),e.title&&a.setTitle(e.title),e.rules.map(e=>a.addRule(m(e)))},`populateDb`),g={parser:{parse:e(e=>{a.clear(),t.debug(`[ABNF Parser] Starting Langium parse`);let r=c.parse(e);if(r.lexerErrors.length>0||r.parserErrors.length>0)throw new n(r);let i=r.value;t.debug(`[ABNF Parser] Parsed rules:`,i.rules.length),h(i),t.debug(`[ABNF Parser] Parse complete`)},`parse`),parser:{yy:a}},db:a,renderer:o,styles:i};export{g as diagram};
+import{n as e}from"./chunk-Y2CYZVJY-Bdt8pFDJ-DsF7k-Jl.js";import{f as t}from"./src-Brzfja-q-ch1VcTiG.js";import{_ as n,g as r}from"./mermaid-parser.core-DxEa8E3F-BAMiAMZz.js";import"./chunk-WYO6CB5R-BlzOfotS-CoeWhGPT.js";import"./chunk-VAUOI2AC-CS9QJ4yz-DYmUgyge.js";import{n as i,r as a,t as o}from"./chunk-MOJQB5TN-CMZRaeqt-B6_lajzj.js";import{t as s}from"./chunk-JWPE2WC7-BQ3zXr2k-DSd3Ct95.js";var c=r().RailroadAbnf.parser.LangiumParser,l=e(e=>{let t=e.alternatives.map(u);return t.length===1?t[0]:{type:`choice`,alternatives:t}},`transformAlternation`),u=e(e=>{let t=e.elements.map(f);return t.length===1?t[0]:{type:`sequence`,elements:t}},`transformConcatenation`),d=e(e=>{if(e.includes(`*`)){let[t,n]=e.split(`*`);return{min:t?parseInt(t,10):0,max:n?parseInt(n,10):1/0}}let t=parseInt(e,10);return{min:t,max:t}},`parseRepeat`),f=e(e=>{let t=p(e.primary);if(!e.repeat)return t;let{min:n,max:r}=d(e.repeat);return n===0&&r===1?{type:`optional`,element:t}:{type:`repetition`,element:t,min:n,max:r}},`transformElement`),p=e(e=>{switch(e.$type){case`AbnfStringLiteral`:return{type:`terminal`,value:e.value};case`AbnfNumVal`:return{type:`terminal`,value:e.value};case`AbnfRuleName`:return{type:`nonterminal`,name:e.name};case`AbnfGroup`:return l(e.element);case`AbnfOptionalGroup`:return{type:`optional`,element:l(e.element)};default:throw Error(`Unsupported ABNF primary node: ${e.$type}`)}},`transformPrimary`),m=e(e=>({name:e.name,definition:l(e.definition)}),`transformRule`),h=e(e=>{s(e,a),e.title&&a.setTitle(e.title),e.rules.map(e=>a.addRule(m(e)))},`populateDb`),g={parser:{parse:e(e=>{a.clear(),t.debug(`[ABNF Parser] Starting Langium parse`);let r=c.parse(e);if(r.lexerErrors.length>0||r.parserErrors.length>0)throw new n(r);let i=r.value;t.debug(`[ABNF Parser] Parsed rules:`,i.rules.length),h(i),t.debug(`[ABNF Parser] Parse complete`)},`parse`),parser:{yy:a}},db:a,renderer:o,styles:i};export{g as diagram};

package/dist/assets/architecture-TIHT7OUA-0NsD2xW1-BlV5di_4.js

@@ -0,0 +1 @@
+import{f as e}from"./mermaid-parser.core-DxEa8E3F-BAMiAMZz.js";export{e as createArchitectureServices};