mulmoterminal 4.6.1 → 4.7.1

package/README.md

@@ -567,12 +567,12 @@ CLAUDE_CWD=/Users/you/my-project
 
 ### UI settings (`~/.mulmoterminal/config.json`)
 
-The Settings modal (⚙) persists per-user UI choices to `~/.mulmoterminal/config.json`
+The Settings modal (the gear button) persists per-user UI choices to `~/.mulmoterminal/config.json`
 (read/written via `GET`/`POST /api/config`):
 
 ![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**, **font** 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, register your own **MCP servers**, and turn on the switches for what this app writes on your behalf — **issue work comments**, the **PR clone footer**, the **closing summary**, the **decision digest**, the **dev worklog** — no need to hand-edit the config file. Four settings stay with their skill because a form would be the wrong tool for them (`keymap`, `themes`, `providers`, `buttons`/`chips`); Settings shows what each is doing now and launches that skill. 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.*
+*Open it from the gear button in the toolbar. Under the title, a **Version** row shows what is running: the version from the shipped `package.json`, plus a `commit <sha>` chip on a git checkout — there the version is only whatever was last released, so the commit is what identifies the build. When something newer exists, the row is followed by the header badge's update notice, command included. Pick a **theme**, set the **terminal font size**, **font** 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, register your own **MCP servers**, and turn on the switches for what this app writes on your behalf — **issue work comments**, the **PR clone footer**, the **closing summary**, the **decision digest**, the **dev worklog** — no need to hand-edit the config file. Four settings stay with their skill because a form would be the wrong tool for them (`keymap`, `themes`, `providers`, `buttons`/`chips`); Settings shows what each is doing now and launches that skill. 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 |
 | ------------ | ------- |
@@ -879,7 +879,7 @@ alongside the Claude sessions. Scripts are **per-directory**: the cell reads the
 different projects' scripts.
 
 The same launcher also has an **or launch** row for your configured **launch commands**
-— any interactive command — set in Settings (⚙) → **Launch commands** as
+— any interactive command — set in Settings (the gear button) → **Launch commands** as
 `{ label, command }` (e.g. `htop` → `htop`, `Codex` → `codex`). A plain shell needs no
 entry here: the Agent Picker's **Shell** option already opens `$SHELL`. Unlike
 a one-shot script, a launcher runs as a **persistent terminal in the cell's directory**:
@@ -1170,7 +1170,7 @@ with no schema on disk, so the fields are identified by measurement (see
 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.
 
-The **Settings** modal (⚙) shows an **estimated $ cost** — Session / Today / Month — from
+The **Settings** modal (the gear button) shows an **estimated $ cost** — Session / Today / Month — from
 `GET /api/cost`, using a built-in public per-model price table (cache reads billed at
 0.1×, cache writes at 1.25× input). It's an estimate: real billing differs, **flat-plan
 (Max) usage isn't reflected**, and turns on unpriced models are flagged and excluded.
@@ -1205,7 +1205,7 @@ it came from — `mcp__<id>__presentChart` in Claude Code, `mcp-<id>-presentChar
 also rewrites `-` in the id to `_`). So the id you register under is repeated on every tool, in
 every listing, for the life of the session.
 
-MulmoTerminal delivers the GUI MCP by **two different routes**, and they do not share an id:
+MulmoTerminal delivers the GUI MCP by **three different routes**, and they do not share an id:
 
 | | Workspace cell / single view | Project-directory grid cell |
 |---|---|---|
@@ -1214,14 +1214,39 @@ MulmoTerminal delivers the GUI MCP by **two different routes**, and they do not
 | Tools carried | all of them, on one URL | only the groups that directory registered |
 | Tool name looks like | `mcp__mt__presentChart` | `mcp__mulmoterminal-render__presentChart` |
 
+The third is **Muse**, which reads neither a flag nor a file in the directory: its MCP servers are
+declared by an installed **plugin**, and `muse plugins install` records one per MACHINE. So
+MulmoTerminal registers a single `mulmoterminal` plugin holding all four group servers, and each
+session is narrowed back to what its own directory switched on — the bridge asks the server which
+session it belongs to (by its process tree) and is told which groups that session may reach. The
+servers are named by group alone, because Muse composes the tool name out of both ids:
+
+| | Muse cell (anywhere) |
+|---|---|
+| How it arrives | a `mulmoterminal` plugin installed for the machine, re-registered whenever the bridge path or port changes |
+| Server id | **`render`**, `data`, `media`, `external` — inside the `mulmoterminal` plugin |
+| Tools carried | only the groups that directory registered; the rest serve an empty toolset |
+| Tool name looks like | `mcp__plugin_mulmoterminal_render__presentChart` |
+
+Muse's plugin support is behind its own experimental flag (`MUSE_EXPERIMENTAL_PLUGINS`), which
+MulmoTerminal sets on the sessions it starts. A Muse build without it simply has no GUI tools —
+the registration fails with one warning and the session starts anyway.
+
+**A Muse session picks its plugins up when its own process starts, and MulmoTerminal's sessions
+outlive the server.** So a Muse cell that was already running when you switched a group on — or
+when you first upgraded to a version that has this — keeps no tools until that CELL is started
+again. Restarting the server is not enough: the session is still there in tmux and gets reattached,
+exactly as it was. Close the cell and open a new one (or `Stop` it in Settings → Surviving sessions),
+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**
 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 and
 codex ask the same predicate, so two terminals in the workspace reach the same tools no matter which
-of the two started them. **Antigravity and Grok cannot, and that is the exception you will meet
-first:**
+of the two started them. **Antigravity, Grok and Muse cannot, and that is the exception you will
+meet first:**
 
 | Started as | In the workspace | In a project directory |
 |---|---|---|
@@ -1229,11 +1254,13 @@ first:**
 | codex cell | `mt`, every tool | the directory's registered groups |
 | antigravity cell | **the directory's registered groups** — nothing registered means **no GUI tools at all** | the directory's registered groups |
 | grok cell | **the directory's registered groups** — nothing registered means **no GUI tools at all** | the directory's registered groups |
+| muse cell | **the directory's registered groups** — nothing registered means **no GUI tools at all** | the directory's registered groups |
 | any launcher chip | untouched | untouched |
 
-Neither takes an MCP flag: `agy` reads `.agents/mcp_config.json` and `grok` reads `.grok/config.toml`
-in the working directory, and a file shared by every session in a directory cannot be handed to one
-session and not another — so there is nothing for "this cwd is the workspace" to change. The
+None of the three takes an MCP flag: `agy` reads `.agents/mcp_config.json`, `grok` reads
+`.grok/config.toml` in the working directory, and `muse` reads a plugin installed for the whole
+machine — and neither a file shared by every session in a directory nor a machine-wide plugin can be
+handed to one session and not another — so there is nothing for "this cwd is the workspace" to change. The
 membership is `FULL_GUI_MCP_AGENTS` in `common/guiMcpAgents.ts`, in `common/` precisely so the
 launcher form and the spawn cannot disagree about it
 ([#1423](https://github.com/receptron/mulmoterminal/issues/1423)).
@@ -1584,6 +1611,7 @@ From a shell: `mulmoterminal room read <room>` · `room post <room> <text…> [-
 | `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/update-status` | What is running and whether anything newer exists: `install` (`npm` / `git`), `version`, `commit` (a checkout's short HEAD sha), `latest` (npm, only when newer) and the one-line `notice`. Backs the header's **Update** badge and the Settings version line. Computed once at startup and served from memory — `ready` is false until that check lands. |
 | `GET /api/notifications`(`/history`) · `POST /api/notifications/:id/clear` | Notification feed. |
 | `POST /api/transcribe`(`/model`…) | Voice-input transcription (Whisper, macOS). |
 | `POST /api/translation` | Runtime UI-string translation. |
@@ -1931,7 +1959,7 @@ src/
     PrsOverlay.vue                           cross-repo PRs & Issues
     Wiki*View.vue, Collections*.vue, AccountingOverlay.vue   workspace views
     TimelineOverlay.vue, ToolsPane.vue, NotificationBell.vue, RemoteHostControl.vue
-    SettingsModal.vue                        ⚙ settings — the dialog shell + section order
+    SettingsModal.vue                        settings — the dialog shell + section order
     settings/                                one file per settings section (theme, sounds,
                                              web push, google, PR repos, launchers, quick
                                              commands, MCP, cost, shortcuts, …), plus the

package/bin/update-check.d.ts

@@ -6,6 +6,16 @@ export interface UpdateNoticeDeps {
   fetchLatest?: () => Promise<string | null>;
 }
 export declare function computeUpdateNotice(pkgDir: string, currentVersion: string, deps?: UpdateNoticeDeps): Promise<string | null>;
+export declare function readInstallInfo(
+  pkgDir: string,
+  currentVersion: string,
+  deps?: UpdateNoticeDeps,
+): Promise<Pick<import("../common/updateStatus.js").UpdateStatus, "install" | "version" | "commit">>;
+export declare function computeUpdateInfo(
+  pkgDir: string,
+  currentVersion: string,
+  deps?: UpdateNoticeDeps,
+): Promise<Omit<import("../common/updateStatus.js").UpdateStatus, "ready">>;
 export declare function isUpdateCheckDisabled(env: Record<string, string | undefined>): boolean;
 export declare function hasNodeModulesSegment(pkgDir: string): boolean;
 export declare function classifyInstall(pkgDir: string, isGitWorkTree: boolean): "npm" | "git";

package/bin/update-check.js

@@ -168,15 +168,12 @@ export function gitUpdateNotice({ localSha, localShort, remoteSha, defaultBranch
 const LS_REMOTE_TIMEOUT_MS = 6000;
 
 // The git branch of the check: local HEAD vs the remote's, read with ls-remote so no fetch is
-// forced. Silent on a dirty tree (can't fast-forward) or any unreadable probe.
-async function gitUpdateNotice_(git) {
+// forced. Silent on a dirty tree (can't fast-forward) or any unreadable probe. `localShort` is
+// passed in because the caller has already read it for the version display.
+async function gitUpdateNotice_(git, localShort) {
   const status = await git(["status", "--porcelain"]);
   if (status === null || isTreeDirtyForUpdate(status)) return null;
-  const [localSha, localShort, lsRemote] = await Promise.all([
-    git(["rev-parse", "HEAD"]),
-    git(["rev-parse", "--short", "HEAD"]),
-    git(["ls-remote", "--symref", "origin", "HEAD"], LS_REMOTE_TIMEOUT_MS),
-  ]);
+  const [localSha, lsRemote] = await Promise.all([git(["rev-parse", "HEAD"]), git(["ls-remote", "--symref", "origin", "HEAD"], LS_REMOTE_TIMEOUT_MS)]);
   return gitUpdateNotice({
     localSha,
     localShort,
@@ -186,14 +183,32 @@ async function gitUpdateNotice_(git) {
   });
 }
 
-// The whole check, front to back: which install this is, then its notice (or null when
-// current). `pkgDir` is where the tool lives — a node_modules dir (→ npm) or a bare checkout
-// (→ git). `deps` lets tests drive it without spawning git or hitting the network; production
-// callers pass nothing and get the real git/registry probes bound to pkgDir.
-export async function computeUpdateNotice(pkgDir, currentVersion, deps = {}) {
+// What is running, without asking the network: the install kind and — for a checkout, where the
+// package.json version is only the last release — the commit that identifies the build. Local
+// probes only, so this is also what the UI gets when the update check is opted out.
+export async function readInstallInfo(pkgDir, currentVersion, deps = {}) {
   const git = deps.runGit ?? ((args, timeout_ms) => runGit(pkgDir, args, timeout_ms));
-  const fetchLatest = deps.fetchLatest ?? fetchLatestVersion;
   const inWorkTree = hasNodeModulesSegment(pkgDir) ? false : (await git(["rev-parse", "--is-inside-work-tree"])) === "true";
-  if (classifyInstall(pkgDir, inWorkTree) === "git") return gitUpdateNotice_(git);
-  return npmUpdateNotice(currentVersion, await fetchLatest());
+  const install = classifyInstall(pkgDir, inWorkTree);
+  return { install, version: currentVersion, commit: install === "git" ? await git(["rev-parse", "--short", "HEAD"]) : null };
+}
+
+// The whole check, front to back: what is running, what is newer, and the one line that says so
+// (null when current). `pkgDir` is where the tool lives — a node_modules dir (→ npm) or a bare
+// checkout (→ git). `deps` lets tests drive it without spawning git or hitting the network;
+// production callers pass nothing and get the real git/registry probes bound to pkgDir.
+export async function computeUpdateInfo(pkgDir, currentVersion, deps = {}) {
+  const git = deps.runGit ?? ((args, timeout_ms) => runGit(pkgDir, args, timeout_ms));
+  const fetchLatest = deps.fetchLatest ?? fetchLatestVersion;
+  const info = await readInstallInfo(pkgDir, currentVersion, { runGit: git });
+  if (info.install === "git") return { ...info, latest: null, notice: await gitUpdateNotice_(git, info.commit) };
+  const latest = await fetchLatest();
+  // `latest` is what the UI OFFERS, so it carries only a version worth moving to — the registry
+  // answering with the version already installed is not news.
+  return { ...info, latest: latest && isNewerVersion(latest, currentVersion) ? latest : null, notice: npmUpdateNotice(currentVersion, latest) };
+}
+
+// The notice alone, for the launcher's console line.
+export async function computeUpdateNotice(pkgDir, currentVersion, deps = {}) {
+  return (await computeUpdateInfo(pkgDir, currentVersion, deps)).notice;
 }

package/common/agentSessionList.ts

@@ -18,6 +18,7 @@ export const AGENT_SESSION_LIST_PATHS: Record<TerminalAgent, string> = {
   codex: "/api/codex/sessions",
   antigravity: "/api/antigravity/sessions",
   grok: "/api/grok/sessions",
+  muse: "/api/muse/sessions",
 };
 
 /** The listing URL for one agent's conversations in one directory. */

package/common/guiMcpAgents.ts

@@ -19,6 +19,16 @@
 // `~/.grok/config.toml` or `./.grok/config.toml` (server/agents/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
+// 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
+// belongs to (by its process tree) and is told the groups with the answer. Do not add a bridge
+// environment variable; it is dropped on the way and the failure is silent. The launcher form offers muse the same four per-group
+// toggles as grok and agy, which is the truthful answer for the same reason it is theirs.
 import { type SessionAgent } from "./sessionAgent.js";
 import { isLaunchAgent } from "./launchAgent.js";
 import { customAgentFor, type AgentPick, type CustomAgent } from "./customAgents.js";

package/common/launchAgent.ts

@@ -4,7 +4,7 @@
 // Deliberately NOT the configured `launchers` list: those are arbitrary user commands, and
 // the phone picks from a fixed set the host can name. "shell" is the OS default shell, the
 // same thing the header's new-terminal button opens.
-export const LAUNCH_AGENTS = ["shell", "claude", "codex", "antigravity", "grok"] as const;
+export const LAUNCH_AGENTS = ["shell", "claude", "codex", "antigravity", "grok", "muse"] as const;
 
 export type LaunchAgent = (typeof LAUNCH_AGENTS)[number];
 

package/common/modelPresets.ts

@@ -260,6 +260,16 @@ export const MODEL_PRESETS: readonly ModelPreset[] = [
     trials: measured(3, 3, 38),
   },
 
+  // ── Muse (Meta) ────────────────────────────────────────────────────────────────
+  {
+    provider: "meta",
+    id: "muse-spark-1.2-contributor",
+    label: "Muse Spark 1.2",
+    contextLength: 1_000_000,
+    pricePerMTok: { input: 1, output: 3 },
+    trials: { status: "unmeasured" },
+  },
+
   // ── Reached fine, never drove the tool loop ──────────────────────────────────
   // Kept so the list answers "what about X?" with a measurement instead of silence.
   {

package/common/sessionAgent.ts

@@ -1,7 +1,7 @@
 // What a remote-host session is running. The server decides it (from the PtyEntry, or from
 // what tmux says is in the pane) and the settings UI offers it as the scope for a quick
 // command, so the list of kinds is a value both sides read.
-export const SESSION_AGENTS = ["claude", "codex", "antigravity", "grok", "shell"] as const;
+export const SESSION_AGENTS = ["claude", "codex", "antigravity", "grok", "muse", "shell"] as const;
 
 // Null anywhere this appears means the host cannot tell — a session that outlived a restart
 // exists only in tmux, and nothing recorded what launched it. That is distinct from "shell".
@@ -9,7 +9,7 @@ export type SessionAgent = (typeof SESSION_AGENTS)[number];
 
 // The agents a terminal can be LAUNCHED as, which is the session kinds minus "shell" (a shell is
 // a launcher, not an agent). Claude is first because it is the default everywhere below.
-export const TERMINAL_AGENTS = ["claude", "codex", "antigravity", "grok"] as const;
+export const TERMINAL_AGENTS = ["claude", "codex", "antigravity", "grok", "muse"] as const;
 
 export type TerminalAgent = (typeof TERMINAL_AGENTS)[number];
 
@@ -47,6 +47,7 @@ const AGENT_BADGES: Partial<Record<TerminalAgent, AgentBadge>> = {
   codex: { full: "codex", short: "cx" },
   antigravity: { full: "agy", short: "agy" },
   grok: { full: "grok", short: "gk" },
+  muse: { full: "muse", short: "mu" },
 };
 
 /** How a session row announces which agent it is running, or null when it wears no badge. The one

package/common/updateStatus.ts

@@ -0,0 +1,42 @@
+// What GET /api/update-status answers: which install is running, what it is, and what is newer.
+// Shared because both sides decide from it — the server builds it from the startup probe, the
+// header badge and the Settings version line read it.
+
+import { isRecord } from "./isRecord.js";
+
+/** How the tool was installed, which decides what "the running version" even means. */
+export type InstallKind = "npm" | "git";
+
+export interface UpdateStatus {
+  /** False until the startup check has landed; `commit` / `latest` / `notice` are not final yet. */
+  ready: boolean;
+  install: InstallKind;
+  /** The shipped package.json version. For a git checkout this is the last release, not the build. */
+  version: string;
+  /** git installs: short HEAD sha — the only thing that identifies which build is running. */
+  commit: string | null;
+  /** npm installs: the registry's version, present only when it is newer than `version`. */
+  latest: string | null;
+  /** The one-line "update available" rendering both the launcher and the header badge show. */
+  notice: string | null;
+}
+
+const isInstallKind = (value: unknown): value is InstallKind => value === "npm" || value === "git";
+
+const stringOrNull = (value: unknown): string | null => (typeof value === "string" ? value : null);
+
+/**
+ * The response as a status, or null when it is not one. Null rather than a filled-in default: a
+ * body we could not read must leave the version line hidden, not print a version nobody is on.
+ */
+export function parseUpdateStatus(body: unknown): UpdateStatus | null {
+  if (!isRecord(body) || !isInstallKind(body.install) || typeof body.version !== "string") return null;
+  return {
+    ready: body.ready === true,
+    install: body.install,
+    version: body.version,
+    commit: stringOrNull(body.commit),
+    latest: stringOrNull(body.latest),
+    notice: stringOrNull(body.notice),
+  };
+}

package/dist/assets/{abnfDiagram-VRR7QNED-WSmThe6b-CBO7sBGR.js → abnfDiagram-VRR7QNED-WSmThe6b-dBgFOZJ6.js}

@@ -1 +1 @@
-import{n as e}from"./chunk-Y2CYZVJY-Bdt8pFDJ-DsF7k-Jl.js";import{f as t}from"./src-CvsWqFln-Tc7ZSrRz.js";import{_ as n,g as r}from"./mermaid-parser.core-C1baW7NG-B11a01NO.js";import"./chunk-WYO6CB5R-nS6zX9ct-Dttxo6Qs.js";import"./chunk-VAUOI2AC-BKx35BBi-Bi2sMyOB.js";import{n as i,r as a,t as o}from"./chunk-MOJQB5TN-CorQ_Pl1-C9s38qkp.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-CvsWqFln-Tc7ZSrRz.js";import{_ as n,g as r}from"./mermaid-parser.core-C1baW7NG-DMZf-3IA.js";import"./chunk-WYO6CB5R-nS6zX9ct-KrP8SxMs.js";import"./chunk-VAUOI2AC-BKx35BBi-E0yAewsj.js";import{n as i,r as a,t as o}from"./chunk-MOJQB5TN-CorQ_Pl1-mXFOYgnO.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-Cqhmai3f-sj7JkliI.js

@@ -0,0 +1 @@
+import{f as e}from"./mermaid-parser.core-C1baW7NG-DMZf-3IA.js";export{e as createArchitectureServices};