mulmoterminal 9.4.0 → 9.6.0

package/README.md

@@ -1526,7 +1526,7 @@ one click: read the issue, cut an `issue/<number>-<slug>` worktree in your clone
 open Claude there as a grid cell with the issue **typed into its input box but not sent**. The
 **Start issues in** menu above the list picks another agent instead (and, for Claude or Codex, an
 account); every agent but Claude runs the issue text at once, which the view warns about. The
-prompt is seeded server-side as a *draft* (`server/session/draft-injection.ts`), which waits for
+prompt is seeded server-side as a *draft* (`server/session/spawn/draft-injection.ts`), which waits for
 claude's input box to be ready — text pushed in before that lands in the scrollback instead. A repo
 with several clones asks which one the first time and remembers the answer; a repo with no clone
 here disables the button and says why. Backed by `POST /api/issues/start`.
@@ -1587,7 +1587,7 @@ has been prompted once — a few seconds, not the rest of the session.
 Antigravity's numbers are the one case read from a store with **no published format**: agy keeps
 its per-generation accounting as protobuf in `~/.gemini/antigravity-cli/conversations/<id>.db`,
 with no schema on disk, so the fields are identified by measurement (see
-`server/agents/antigravity-usage.ts`). Every layer of that reader is built to answer *nothing*
+`server/agents/antigravity/antigravity-usage.ts`). Every layer of that reader is built to answer *nothing*
 rather than a number it is unsure of, so if a future agy release moves those fields, an
 Antigravity cell falls back to showing its model alone — it will not show a wrong percentage.
 
@@ -1633,7 +1633,7 @@ Copilot** can. **Antigravity, Grok and Cursor** cannot — they read a file in t
 **Muse** reads neither, which is the third route below.
 
 **Cursor is half of each**, and the half nobody would guess is the second: it reads a file in the
-directory as agy does (`.cursor/mcp.json`, written by `server/agents/cursor-mcp.ts`), but it starts
+directory as agy does (`.cursor/mcp.json`, written by `server/agents/cursor/cursor-mcp.ts`), but it starts
 that MCP server on a CURATED ENVIRONMENT rather than its own — so the group and the port travel as
 ARGV, as muse's do, and the SESSION is resolved through `/api/mcp-resolve`. An agy-shaped entry (group
 in `env`, port inherited) was tried first and reached the bridge with no port at all. Cursor also refuses to
@@ -1674,7 +1674,7 @@ exactly as it was. Close the cell and open a new one (or `Stop` it in Settings
 and it comes back with the tools its directory registered.
 
 Which route a session takes is decided by `carriesFullGuiMcp()` in
-`server/session/mcp-config.ts` — the single view, a cell-less chat, or anything whose cwd **is**
+`server/session/spawn/setup/mcp-config.ts` — the single view, a cell-less chat, or anything whose cwd **is**
 the workspace take the first; anything in a project directory takes the second.
 
 **The workspace is agent-agnostic for the agents that can RECEIVE a per-spawn config** — claude,
@@ -2016,7 +2016,7 @@ Empty output returns a `{ summary }` note rather than calling the CLI. Errors:
 (see [Claude hook injection](#claude-hook-injection)); **Copilot's and Cursor's arrive from a
 machine-global hook file** and name their agent in an `x-mt-agent: copilot|cursor` header, with the
 event in `x-mt-hook` — the body is translated into the Claude shape below before anything reads it
-(`server/agents/{copilot,cursor}-hook.ts`), so everything downstream is written against one
+(`server/agents/{copilot/copilot,cursor/cursor}-hook.ts`), so everything downstream is written against one
 vocabulary. A request with no `x-mt-agent` is a Claude payload and is untouched.
 You normally don't call this yourself.
 

package/bin/agent-bins.js

@@ -5,7 +5,7 @@
 // with no tsx. The server imports from `bin/` already (bin/instances.js), so this direction is the
 // established one.
 //
-// The table is duplicated knowledge by construction — `server/config/agent-bins.ts` builds the same
+// The table is duplicated knowledge by construction — `server/config/agent/agent-bins.ts` builds the same
 // mapping out of the adapters — so a spec pins the two together rather than a comment asking the
 // next person to keep them in sync.
 //

package/bin/cli-args.js

@@ -14,7 +14,7 @@ import { join } from "node:path";
 import { NODE_DOWNLOAD_URL } from "./node-install.js";
 
 // The v4 loopback every local client of this server dials by literal — `guiMcpUrlTemplate` in
-// server/infra/gui-mcp-registration.ts builds `http://127.0.0.1:<port>/api/mcp/...`. Duplicated
+// server/infra/process/gui-mcp-registration.ts builds `http://127.0.0.1:<port>/api/mcp/...`. Duplicated
 // here because bin/ is plain JS and cannot import the server's TypeScript, and pinned by a spec
 // the same way PORT_IN_USE_EXIT_CODE is.
 const V4_LOOPBACK_CLIENTS_DIAL = "127.0.0.1";
@@ -120,7 +120,7 @@ export function probeFailureIsPortInUse(err) {
  * `localhost`, `127.1` — and a host string has no last case. The kernel has none of that problem:
  * measured, `listen(0,"0:0:0:0:0:0:0:0")` reports `::` and `listen(0,"localhost")` reports `::1`.
  * The comparisons below are exact because the kernel's OUTPUT vocabulary is finite even though
- * its input vocabulary is not. server/infra/loopback.ts made the same argument for its own
+ * its input vocabulary is not. server/infra/http/loopback.ts made the same argument for its own
  * question: "asking after the fact answers all of them".
  *
  * The probe/bind race the launcher already lives with is unchanged: this narrows the window, it
@@ -149,7 +149,7 @@ export function companionHostsFor(boundAddress) {
  *
  * The authority for a name is the kernel, not this function, and the launcher asks it the only
  * way that is exact — the child reports what `server.address()` says it bound. See
- * server/infra/loopback.ts, which had already written the argument down for its own question.
+ * server/infra/http/loopback.ts, which had already written the argument down for its own question.
  */
 export function launcherReachHost(bindHost) {
   if (bindHost === "0.0.0.0") return "127.0.0.1";
@@ -206,7 +206,7 @@ export function launcherUrl(reachHost, port) {
  * feature nothing in `bin/` mentions. Changing the URL means adding the new loopback address to
  * that authorized-domain list first.
  *
- * Reachability is not the reason it is safe; #1834 is. `server/infra/loopback-listener.ts` makes
+ * Reachability is not the reason it is safe; #1834 is. `server/infra/http/loopback-listener.ts` makes
  * this server serve `127.0.0.1` in EVERY configuration — as the primary bind, or as a second
  * listener when the operator widens it — because eight local callers write that address as a
  * literal. So `localhost` arrives here whatever `MULMOTERMINAL_HOST` says, falling back to v4
@@ -467,7 +467,7 @@ export function unsupportedNodeMessage(version, execPath, upgrade) {
  * hands its own environment to every PTY it spawns, so a port set there reaches every terminal
  * in every cell — which is how a raw `PORT` made a dev server started in a cell try to take
  * MulmoTerminal's own port (#1857). Renaming it would only move that: `MULMOTERMINAL_PORT` is
- * deliberately given to PTYs (server/session/mcp-config.ts) for the MCP URLs, so a server
+ * deliberately given to PTYs (server/session/spawn/setup/mcp-config.ts) for the MCP URLs, so a server
  * reading it as its bind port would clash with itself the moment `yarn dev` ran inside a cell.
  *
  * `--agent` rides the same channel for the same reason (#2082): it is a preference, and a

package/bin/has-command.js

@@ -14,7 +14,7 @@
 //
 // A file lookup has neither problem: nothing is interpreted, it is just candidate names on disk.
 // WHICH candidates is the whole remaining question, and it is not this file's to invent — it is
-// `server/infra/has-binary.ts`'s, because "can we launch it" and "what would we launch" must not
+// `server/infra/process/has-binary.ts`'s, because "can we launch it" and "what would we launch" must not
 // answer differently. `test/bin/gate-agrees-with-spawn.spec.ts` compares the two over generated
 // machines rather than trusting these comments.
 //
@@ -64,7 +64,7 @@ export const extensionsFor = (platform) => (platform === "win32" ? WINDOWS_LAUNC
 
 // A Windows PATH entry may be QUOTED — `"C:\Program Files\tools"` — which the shells strip and a
 // plain join would not, leaving a path that matches nothing. Same rule as the server's
-// `windowsSearchDirectories` (server/infra/resolve-bin.ts); `C:\Program Files` is the canonical
+// `windowsSearchDirectories` (server/infra/process/resolve-bin.ts); `C:\Program Files` is the canonical
 // path that needs the quotes, so this is the common case rather than an exotic one.
 // The current directory is on neither platform's list. cmd.exe searches it and POSIX shells do
 // not, but what launches an agent is node-pty on both — and the directory THIS process sits in is
@@ -81,7 +81,7 @@ export const searchDirectories = (platform, env) => {
 };
 
 // Can this process enumerate everything execvp would search? Two cases where it cannot, both taken
-// from server/infra/has-binary.ts, which reasoned them out first:
+// from server/infra/process/has-binary.ts, which reasoned them out first:
 //
 //   - an UNSET PATH is not an empty one. execvp falls back to its own built-in default
 //     (confstr _CS_PATH), which is not readable from here.

package/bin/mulmoterminal.js

@@ -127,7 +127,7 @@ function readRemoteServer() {
 //
 // The override is the point rather than a detail: the gate used to look for the literal word
 // `claude` on PATH while the server ran `process.env.CLAUDE_BIN || "claude"`
-// (server/agents/claude.ts). A user who set CLAUDE_BIN to a real install was refused start-up by a
+// (server/agents/claude/claude.ts). A user who set CLAUDE_BIN to a real install was refused start-up by a
 // check asking a different question than the thing it was gating (#2082).
 function agentInstalled(agent) {
   const bin = agentBin(agent);
@@ -546,7 +546,7 @@ function runServer({ port, probedAddress, localhostIsUnambiguous, noOpen, launch
     // The address to check is the one the CHILD REPORTS, not one derived from BIND_HOST — three
     // rounds of review found three different spellings BIND_HOST can take that a guess gets
     // wrong (`::` vs `::1`, `localhost` resolving per-platform, a printed `localhost` that a
-    // browser re-resolves). server/infra/loopback.ts already argued this for its own question:
+    // browser re-resolves). server/infra/http/loopback.ts already argued this for its own question:
     // "classifying the requested string cannot be made right … asking after the fact answers all
     // of them, because the kernel has already resolved whatever was typed" (#1876).
     //

package/bin/room.js

@@ -49,7 +49,7 @@ function splitAtTerminator(args) {
 
 /** The port to talk to: `--port`, else MULMOTERMINAL_PORT, else PORT, else the default.
  *
- *  MULMOTERMINAL_PORT is what a terminal INSIDE MulmoTerminal is given (server/session/pty-spawn.ts),
+ *  MULMOTERMINAL_PORT is what a terminal INSIDE MulmoTerminal is given (server/session/pty/pty-spawn.ts),
  *  and it has to be preferred: `PORT` used to carry the same answer only because the launcher
  *  exported it to every PTY, which is the leak #1857 is about. Without this, `room` run in a cell
  *  of a server on 34601 would talk to whatever holds 34567 — or to another instance entirely.

package/bin/server-supervision.js

@@ -16,7 +16,7 @@
 // otherwise. Nothing here reads a clock, a socket or a process.
 
 /** The exit code `server/index.ts` leaves with when the port was already taken at bind time.
- *  Kept in sync with `PORT_IN_USE_EXIT_CODE` in server/infra/server-exit.ts, which a spec pins. */
+ *  Kept in sync with `PORT_IN_USE_EXIT_CODE` in server/infra/process/server-exit.ts, which a spec pins. */
 export const PORT_IN_USE_EXIT_CODE = 75;
 
 /** How long the launcher waits before the first restart, and the ceiling the doubling stops at.
@@ -87,7 +87,7 @@ export function planAfterServerExit({ code, signal, everServed, consecutiveFailu
   // A port that is taken will still be taken next time; the caller names who has it and stops.
   if (code === PORT_IN_USE_EXIT_CODE) return { action: "port-in-use", delayMs: 0, reason: null };
   // `mulmoterminal stop` and the browser's Stop button both SIGTERM the server, whose handler
-  // exits 0 (server/infra/shutdown.ts). Restarting that is the product's stop button not stopping.
+  // exits 0 (server/infra/process/shutdown.ts). Restarting that is the product's stop button not stopping.
   if (code === 0) return { action: "stop", delayMs: 0, reason: null };
   // Nothing below can be decided on a platform where a stop and a crash arrive identically, so it
   // is not guessed at: the launcher leaves with its server, exactly as it did before (see above).

package/common/agentAccounts.ts

@@ -62,5 +62,5 @@ export const accountsForAgent = (accounts: readonly AgentAccount[], agent: unkno
   isAccountAgent(agent) ? accounts.filter((account) => account.agent === agent) : [];
 
 /** What a cell or a list row calls an account: its label, or the bare id once the entry has left the
- *  config (the session still runs on it — see server/session/account-log.ts). */
+ *  config (the session still runs on it — see server/session/accounts/account-log.ts). */
 export const accountLabel = (accounts: readonly AgentAccount[], id: string): string => accounts.find((account) => account.id === id)?.label ?? id;

package/common/collectionNotifyTarget.ts

@@ -1,6 +1,6 @@
 // The navigate target a collection-completion bell carries, and the one narrowing
 // that reads it back. Shared because BOTH sides decide from it: the server writes
-// the target when it publishes a bell (server/backends/collectionNotifierAdapter.ts)
+// the target when it publishes a bell (server/backends/collections/collectionNotifierAdapter.ts)
 // and the UI reads it to accent the record's card (src/utils/collectionNotified.ts).
 // A second copy of the literal in the reader is exactly how a writer/reader pair
 // drifts silently — the bell keeps arriving, only the accent stops appearing.

package/common/collectionPortability.ts

@@ -1,5 +1,5 @@
 // "Would this collection survive a clone?" — the wire shape, shared because BOTH sides decide
-// from it: the server produces the report (server/backends/collectionSelfContainment.ts) and the
+// from it: the server produces the report (server/backends/collections/collectionSelfContainment.ts) and the
 // Collections pane renders it, colouring by severity and blocking on `portable`.
 //
 // In `common/` rather than mirrored, for the reason the layout rule gives: a second copy of a

package/common/customAgents.ts

@@ -29,7 +29,7 @@ import { isRecord } from "./isRecord.js";
 // appended, so it must say.
 //
 // Claude Code is the only one today. Codex and Antigravity take a different argument set
-// (server/agents/codex-args.ts), so adding one here means teaching the spawn to build ITS argv —
+// (server/agents/codex/codex-args.ts), so adding one here means teaching the spawn to build ITS argv —
 // which is why this is a list rather than a boolean.
 export const CUSTOM_AGENT_KINDS = ["claude"] as const;
 

package/common/dirConfigSource.ts

@@ -6,7 +6,7 @@
 // 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
+// concerned, however sensible it looks — `test/server/config/dir/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",

package/common/guiMcpAgents.ts

@@ -16,13 +16,13 @@
 //
 // Grok is out for exactly the same reason, and it is written down here rather than left to be
 // rediscovered: `grok` has no `--mcp-config` and no `-c key=value`, only `grok mcp add` writing
-// `~/.grok/config.toml` or `./.grok/config.toml` (server/agents/grok-mcp.ts). So a grok session in
+// `~/.grok/config.toml` or `./.grok/config.toml` (server/agents/grok/grok-mcp.ts). So a grok session in
 // the workspace gets the groups its DIRECTORY registered, and the launcher form offers it the four
 // per-group toggles — which is the truthful answer, and the one #1423 failed to give.
 //
 // Muse is out for the same reason and reaches its tools a third way. It has no `--mcp-config` and
 // no per-directory config file either: MCP servers are declared by an installed PLUGIN, which
-// `muse plugins install` records per MACHINE (server/agents/muse-mcp.ts). So MulmoTerminal
+// `muse plugins install` records per MACHINE (server/agents/muse/muse-mcp.ts). So MulmoTerminal
 // registers one plugin holding all four group servers, and each SESSION is narrowed back to what
 // its directory switched on — by a lookup, not by the environment: a plugin's MCP server is started
 // with a curated environment that carries nothing of ours, so the bridge resolves which session it

package/common/machineLoad.ts

@@ -32,7 +32,7 @@ const usableLoad = (avg1: number, avg5: number, avg15: number, cores: number): M
 };
 
 /** The reading, or null where there is nothing to report. Pure — `node:os` is touched by the one
- *  caller in `server/infra/machine-load.ts`, so every rule here stays testable without waiting for
+ *  caller in `server/infra/process/machine-load.ts`, so every rule here stays testable without waiting for
  *  a machine that happens to be busy. */
 export function machineLoadFrom(averages: readonly number[], cores: number, platform: string): MachineLoad | null {
   if (!keepsLoadAverage(platform)) return null;

package/common/mobileFiles.ts

@@ -3,7 +3,7 @@
 // Declared, never discovered: a project lists the directories and extensions in its
 // `.mulmoterminal.json` under `mobileFiles`, and nothing is visible without that. These rules are
 // pure so the containment-adjacent decisions (which extension, which name) are testable without a
-// filesystem; the filesystem half lives in server/config/dir-file.ts and the remote-host backend.
+// filesystem; the filesystem half lives in server/config/dir/dir-file.ts and the remote-host backend.
 
 export const MOBILE_FILE_KINDS = ["markdown", "html", "pdf", "image"] as const;
 export type MobileFileKind = (typeof MOBILE_FILE_KINDS)[number];

package/common/playfulEffects.ts

@@ -3,7 +3,7 @@
 // the picture and draws the level.
 import { isRecord } from "./isRecord.js";
 
-export const HEAT_PATTERNS = ["bomb", "volcano", "kettle", "rocket", "dynamite", "balloon", "skull", "sumo"] as const;
+export const HEAT_PATTERNS = ["bomb", "volcano", "kettle", "rocket", "dynamite", "balloon", "skull", "sumo", "ufo"] as const;
 export type HeatPattern = (typeof HEAT_PATTERNS)[number];
 export const isHeatPattern = (value: unknown): value is HeatPattern => HEAT_PATTERNS.some((pattern) => pattern === value);
 

package/common/promptHistory.ts

@@ -1,7 +1,7 @@
 // The wire shape of GET /api/transcript/prompts — the prompts the user sent one session (#1748).
 //
 // In `common/` because both sides decide from it: the server builds the window (which log it reads
-// and how it caps is its own business, in server/session/prompt-history.ts), and the pane renders
+// and how it caps is its own business, in server/session/transcript/prompt-history.ts), and the pane renders
 // each field. A shape kept twice is the one that drifts.
 
 import { isRecord } from "./isRecord";

package/common/rawContentType.ts

@@ -1,7 +1,7 @@
 // What a browser is handed for a file, decided from its name alone.
 //
 // BOTH sides read this. The server sets it as the raw route's `Content-Type`
-// (server/backends/rawServingPlan.ts); the terminal's file links ask the same question to decide
+// (server/backends/files/rawServingPlan.ts); the terminal's file links ask the same question to decide
 // where a click goes, because a type the browser cannot display is a type that turns a new tab
 // into a silent download (#2038). Two copies of this table would send a click to a tab the server
 // then made a download — which is the bug, arrived at from the other side.

package/common/sessionProcesses.ts

@@ -1,7 +1,7 @@
 // What the Processes page shows: each tmux session and the process tree under its panes (#2219).
 //
 // In `common/` because both sides decide from it: the server builds it from `ps` and tmux
-// (server/session/session-processes.ts), and the page reads it back and highlights from it.
+// (server/session/list/session-processes.ts), and the page reads it back and highlights from it.
 import { isRecord } from "./isRecord.js";
 import { isUnknownArray } from "./isUnknownArray.js";
 

package/common/sourceExtensions.ts

@@ -4,7 +4,7 @@
 // Both sides of the file-path link decide something from this set, and the two decisions
 // are different, so this is the shared CORE rather than either side's whole answer:
 //   - the server serves these as text/plain so they VIEW instead of downloading
-//     (backends/rawServingPlan.ts, which also covers docs, markup and dotfiles), and
+//     (backends/files/rawServingPlan.ts, which also covers docs, markup and dotfiles), and
 //   - the client opens these in the app's own Files view instead of a new tab
 //     (composables/terminalFilePathLinkProvider.ts, which also covers .txt).
 // Each side adds its own extras next to its import; anything that belongs to only one of

package/common/survivingSessions.ts

@@ -6,7 +6,7 @@
 // visible nowhere. This is the row that makes them visible, and endable.
 //
 // In `common/` because both sides decide from it: the server fills it from tmux plus its own
-// registry (session/surviving-sessions.ts), and the section renders and acts on it
+// registry (session/reaping/surviving-sessions.ts), and the section renders and acts on it
 // (components/settings/SurvivingSessionsSection.vue).
 import type { TerminalAgent } from "./sessionAgent.js";
 

package/common/toolGroups.ts

@@ -115,6 +115,10 @@ const GROUP_BY_TOOL = new Map<string, ToolGroup>([
 
   ["generateImage", "media"],
   ["presentMulmoScript", "media"],
+  // manageJingleScript writes and renders short jingles and plays them in the Canvas: audio,
+  // so media. It renders locally (ffmpeg at most) and calls nothing external; whether it joins
+  // AUTO_ALLOWED_TOOLS is left to the maintainers, so for now it keeps the permission prompt.
+  ["manageJingleScript", "media"],
 
   // useSharedApp is the participant's half of the shared-app pair, and it is NOT beside
   // manageSharedApp in `data`. That group is the workspace's own structured data; this tool moves
@@ -166,7 +170,7 @@ export const toolGroupServerId = (group: ToolGroup): string => `mulmoterminal-${
 // `--mcp-config` (claude) or `-c mcp_servers.<id>.url=` (codex), so it is ours to name.
 //
 // Which of the two ids a session gets is decided by `carriesFullGuiMcp` in
-// server/session/spawn-claude.ts: the single view, a cell-less chat, and a cell whose cwd IS the
+// server/session/spawn/agents/spawn-claude.ts: the single view, a cell-less chat, and a cell whose cwd IS the
 // workspace carry this one; a cell in a project directory is handed no --mcp-config at all and
 // reaches the group ids through the user's own per-folder config. Both are live, on purpose.
 //
@@ -260,7 +264,7 @@ export const AUTO_ALLOWED_TOOLS: readonly string[] = [
  *  then deploy" arriving in that text is a tool call rather than a question.
  *
  *  IT SAYS CLAUDE, AND THAT IS THE WHOLE OF ITS REACH. codex approves per SERVER — `guiMcpServers`
- *  in `server/session/mcp-config.ts` marks every attached group `autoApprove: true`, by the owner's
+ *  in `server/session/spawn/setup/mcp-config.ts` marks every attached group `autoApprove: true`, by the owner's
  *  decision of 2026-07-28 — so a codex cell holding a group waves through every tool in it, this
  *  list included. That is already true of `manageSharedApp` in `data` and is now equally true of
  *  `useSharedApp` in `external`; adding the tool did not create it. It cannot be narrowed per tool

package/common/transcriptView.ts

@@ -1,7 +1,7 @@
 // What a hosted agent's conversation looks like ON THE WIRE.
 //
 // In `common/` because both ends decide from it: the host folds an agent's JSONL (or copilot's
-// table) into these shapes in `server/session/transcript-view.ts`, and two clients render them —
+// table) into these shapes in `server/session/transcript/transcript-view.ts`, and two clients render them —
 // the phone's terminal detail page over the remoteHost socket, and the browser's transcript pane
 // over `/api/transcript/view`. Mirroring the shape into `src/` would let one side gain a status the
 // other silently renders as nothing.

package/common/worktreeEnv.ts

@@ -3,7 +3,7 @@
 // isolated by a worktree; these are not, so two trees running `yarn dev` race for one 3000.
 //
 // The pure half — what a slot is worth, what a slug looks like, and the shape the browser
-// receives. Reserving lives in server/config/worktree-env.ts, which needs the disk.
+// receives. Reserving lives in server/config/worktree/worktree-env.ts, which needs the disk.
 
 /** How far apart two consecutive slots sit.
  *

package/dist/assets/{abnfDiagram-YUKMZFIV-DWmlUOJW.js → abnfDiagram-YUKMZFIV-hhgBEMEq.js}

@@ -1 +1 @@
-import{m as e,t}from"./mermaid-parser.core--3w-WUbe.js";import{n}from"./chunk-Y2CYZVJY-DsF7k-Jl.js";import{m as r}from"./src-CllyRBe0.js";import"./chunk-VPRB5NB3-BsayPsyI.js";import{n as i,r as a,t as o}from"./chunk-AW2ZBBNX-CmX9OUG5.js";import{t as s}from"./chunk-JWPE2WC7-DVXcaiue.js";import"./mermaid.core-Dd_Uhv_d.js";var c=e().RailroadAbnf.parser.LangiumParser,l=n(e=>{let t=e.alternatives.map(u);return t.length===1?t[0]:{type:`choice`,alternatives:t}},`transformAlternation`),u=n(e=>{let t=e.elements.map(f);return t.length===1?t[0]:{type:`sequence`,elements:t}},`transformConcatenation`),d=n(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=n(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=n(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=n(e=>({name:e.name,definition:l(e.definition)}),`transformRule`),h=n(e=>{s(e,o),e.title&&o.setTitle(e.title),e.rules.map(e=>o.addRule(m(e)))},`populateDb`),g={parser:{parse:n(e=>{o.clear(),r.debug(`[ABNF Parser] Starting Langium parse`);let n=c.parse(e);if(n.lexerErrors.length>0||n.parserErrors.length>0)throw new t(n);let i=n.value;r.debug(`[ABNF Parser] Parsed rules:`,i.rules.length),h(i),r.debug(`[ABNF Parser] Parse complete`)},`parse`),parser:{yy:o}},db:o,renderer:a,styles:i};export{g as diagram};
+import{m as e,t}from"./mermaid-parser.core-D9bG0VLG.js";import{n}from"./chunk-Y2CYZVJY-DsF7k-Jl.js";import{m as r}from"./src-CllyRBe0.js";import"./chunk-VPRB5NB3-zipI-qki.js";import{n as i,r as a,t as o}from"./chunk-AW2ZBBNX-CzNEI48Y.js";import{t as s}from"./chunk-JWPE2WC7-DVXcaiue.js";import"./mermaid.core-xdDqFngm.js";var c=e().RailroadAbnf.parser.LangiumParser,l=n(e=>{let t=e.alternatives.map(u);return t.length===1?t[0]:{type:`choice`,alternatives:t}},`transformAlternation`),u=n(e=>{let t=e.elements.map(f);return t.length===1?t[0]:{type:`sequence`,elements:t}},`transformConcatenation`),d=n(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=n(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=n(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=n(e=>({name:e.name,definition:l(e.definition)}),`transformRule`),h=n(e=>{s(e,o),e.title&&o.setTitle(e.title),e.rules.map(e=>o.addRule(m(e)))},`populateDb`),g={parser:{parse:n(e=>{o.clear(),r.debug(`[ABNF Parser] Starting Langium parse`);let n=c.parse(e);if(n.lexerErrors.length>0||n.parserErrors.length>0)throw new t(n);let i=n.value;r.debug(`[ABNF Parser] Parsed rules:`,i.rules.length),h(i),r.debug(`[ABNF Parser] Parse complete`)},`parse`),parser:{yy:o}},db:o,renderer:a,styles:i};export{g as diagram};

package/dist/assets/architecture-WOLXFQ4H-C2eqTYis.js

@@ -0,0 +1 @@
+import"./chunk-NGNAAXSQ-DqoPQk1a.js";import{M as e}from"./mermaid-parser.core-D9bG0VLG.js";export{e as createArchitectureServices};