mulmoterminal 4.13.0 → 4.15.0

package/README.md

@@ -101,7 +101,8 @@ the same two behind **[GraphAI](https://github.com/receptron/graphai)**. [More
   command-output explanations — so a wall of parallel agents stays legible.
 - **Make it yours.** Per-directory **themes, colors, and name badges** (`prod` in red,
   `staging` in amber), a configurable header (buttons + info chips), custom attention sounds,
-  and Run / Skill menus to launch a project's scripts and `.claude/skills` right inside a cell.
+  and Run / Skill / Mulmo menus to launch a project's scripts, `.claude/skills` and decks right
+  inside a cell.
 
 ![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)
 
@@ -369,6 +370,7 @@ The launcher detects it and prints the exact, OS-appropriate removal command; ru
 - [Running](#running)
 - [Scripts (Run menu)](#scripts-run-menu)
 - [Skills (Skill menu)](#skills-skill-menu)
+- [Decks (Mulmo menu)](#decks-mulmo-menu)
 - [Files view (browse & edit)](#files-view-browse--edit)
 - [Git worktrees & pull requests](#git-worktrees--pull-requests)
 - [Cost & token usage](#cost--token-usage)
@@ -680,7 +682,9 @@ and open-on-GitHub (🌐, git repos). Setting `buttons` (at either level) **repl
 set** with your list (it is not merged on top), so listing your own — even a **shorter** one — is how
 you drop, reorder, or swap them.
 A button has an `id`, `label`, and a `run` of `"shell"` (run a command), `"input"` (send text to the
-agent), or `"open"`. An `open` button targets one of `url` / `reveal` (OS file manager) / `files`
+agent), `"open"`, or `"action"` (act on the cell itself — `action: "restart"` ends the agent and
+starts it again in the same cell on the same conversation, which is how an MCP / config / plugin
+change takes effect; it costs a resume and asks nothing first). An `open` button targets one of `url` / `reveal` (OS file manager) / `files`
 (in-app explorer) / `view` (a built-in overlay) / `terminal` (a dir → a new cell running `$SHELL`,
 opened next to the current one) / `pr: true` (open the current branch's PR — the button is hidden when
 there's no open PR) / `pickFile: true` (OS file dialog → insert the path).
@@ -1048,6 +1052,46 @@ button. Skills are discovered read-only; the menu never creates or edits them.
 
 ---
 
+## Decks (Mulmo menu)
+
+Beside **⚡ Skill ▾** is **⊞ Mulmo ▾** — the decks (mulmoScript presentations) this project offers,
+one click from the **Canvas**. It appears **only when there are decks to show** (none, no button),
+like the two menus next to it.
+
+Picking one shows it in the Canvas beside that cell, enlarging the cell first if it was tiled.
+Nothing is typed into the session and the agent is not asked: this is a viewer, so it costs no
+tokens and works while the agent is busy.
+
+**Two sources, both named — the menu never searches your disk:**
+
+1. **`artifacts/stories/` under the workspace** — where the plugin keeps the decks an agent makes.
+   Always offered, nothing to configure.
+2. **Decks you list yourself**, for one kept inside a repository:
+
+```jsonc
+// <dir>/.mulmoterminal.json
+{ "decks": ["decks/launch.json", "docs/talks/retro.json"] }
+```
+
+Paths are relative to that file and must stay **inside its directory** — `../elsewhere.json` and
+absolute paths are dropped, because a config file travels with a clone. Each deck is named by its
+own `title`, or by its file name when it has none.
+
+**Why you list them rather than the menu finding them:** a search does find them — along with
+everything else on disk that happens to parse as a deck. Measured on a real workspace: **250 files
+matched, 33 were the user's own decks and 217 were a checked-out repository's test fixtures and
+samples.** A menu is a short list of things you chose.
+
+**Where the decks have to live:** under the workspace MulmoTerminal was started in, which is the
+directory it serves stories from. A cell opened outside it shows no button, because nothing it
+could list could be opened. Any deck you can see in the file tree is also reachable there — right-click
+a row and choose **Open in the Canvas** — with no configuration at all.
+
+If a deck cannot be opened (it was deleted, or the workspace moved since startup), the cell says
+why rather than doing nothing.
+
+---
+
 ## Files view (browse & edit)
 
 A terminal header can carry a **📁 Files** button — add it as a [header button](#header-buttons)

package/common/dirConfigSource.ts

@@ -30,6 +30,7 @@ export const DIR_CONFIG_KEYS = [
   "buttons",
   "chips",
   "skills",
+  "decks",
   "provider",
   "model",
   "addDirs",
@@ -70,6 +71,7 @@ export interface DirConfigExtras {
   provider: string | null;
   model: string | null;
   skills: string[] | null;
+  decks: string[] | null;
   addDirs: string[] | null;
   // Tri-state on purpose: `false` is a setting this file made, and the preview has to show it as
   // one. Carried here because a boolean cannot be read back off the per-cell config the way a
@@ -91,6 +93,7 @@ export const EMPTY_DIR_CONFIG_EXTRAS: DirConfigExtras = {
   provider: null,
   model: null,
   skills: null,
+  decks: null,
   addDirs: null,
   appendSystemPrompt: null,
   buttonLabels: [],

package/common/keymap.ts

@@ -21,6 +21,7 @@ export const KEYMAP_ACTIONS = [
   "terminal-new-here",
   "terminal-new-adjacent",
   "terminal-close",
+  "terminal-restart",
   "copy",
   "paste",
 ] as const;
@@ -48,7 +49,7 @@ export const TERMINAL_SCOPED_ACTIONS: readonly KeymapAction[] = ["copy", "paste"
 // Here rather than beside gridShortcutFor because BOTH sides decide from it: the grid dispatches on
 // it, and validateKeymap has to know that these decline the key — the handler returns WITHOUT
 // stopping the event, so a `send` on the same keystroke fires instead (codex on #1906).
-export const NEEDS_A_CURRENT_TERMINAL: readonly KeymapAction[] = ["zoom-next", "zoom-prev", "terminal-new-adjacent", "terminal-close"];
+export const NEEDS_A_CURRENT_TERMINAL: readonly KeymapAction[] = ["zoom-next", "zoom-prev", "terminal-new-adjacent", "terminal-close", "terminal-restart"];
 
 // A key that puts BYTES into the focused terminal instead of running an app action (#1005) —
 // Cmd+Right as Ctrl+E for end-of-line, say, or Alt+B for word-back.