@webmcp-auto-ui/agent 2.5.27 → 2.5.29

package/src/providers/wasm.ts

@@ -313,11 +313,13 @@ export class WasmProvider implements LLMProvider {
       }
     }
 
-    // Strip hallucinated framework tokens the model should never emit on its own:
-    // - <|tool_response>...<tool_response|>  (injected by the framework, never generated)
-    // - <|channel>thought...<channel|>      (ghost thought channels if Gemma emits one
-    //   without <|think|> activation — stray artefacts from pretraining)
-    // - <|think|>                            (stray thinking-mode markers)
+    // Strip hallucinated framework tokens the model should never emit on its own.
+    // Thinking mode is disabled for Gemma (since commit 164a24d) but the model
+    // may still leak these tokens as pretraining artefacts — keep the defensive
+    // strip regardless of activation.
+    // - <|tool_response>...<tool_response|>  (framework-injected, never generated)
+    // - <|channel>thought...<channel|>       (ghost thought channels)
+    // - <|think|>                             (stray pretraining artefacts)
     fullText = fullText
       .replace(/<\|tool_response>[\s\S]*?<tool_response\|>/g, '')
       .replace(/<\|channel>thought[\s\S]*?<channel\|>/g, '')

package/src/recipes/_generated.ts

@@ -932,7 +932,7 @@ component("gallery", {
   'hackathon-assemblee-nationale': `---
 id: hackathon-assemblee-nationale-mcp-webmcp
 name: Hackathon Assemblée Nationale · MCP & WebMCP starter
-components_used: [notebook-document, notebook-compact]
+components_used: [notebook]
 when: the user mentions the Assemblée Nationale hackathon, wants to experiment with parliamentary data (Tricoteuses, Legifrance), or asks for a starter notebook to explore deputies, votes, amendments, or legislative texts in a hackathon context. Keywords include "hackathon Assemblée Nationale", "MCP WebMCP hackathon", "tricoteuses playbook", "parlement playground", "hackathon parlementaire".
 servers: [autoui, tricoteuses]
 layout:
@@ -951,14 +951,9 @@ This recipe is a **specialization** of the generic \`notebook-playbook\` recipe
 
 ## How to use
 
-### Step 1 — Pick the document layout
+### Step 1 — Use the \`notebook\` widget
 
-Default to \`notebook-document\` for the hackathon. Reasons:
-- Participants expect to collaborate and leave traces for each other (avatars, comments)
-- The document layout reads naturally as "hackathon brief + starter code" rather than "dev tool"
-- Margin comments can be seeded to hint at directions to explore
-
-If the participant asks for a minimal dev-focused playground instead, fall back to \`notebook-compact\`.
+The single \`notebook\` widget fits the hackathon brief: prose, SQL and JS share one drag-and-droppable flow, suited both to a "brief + starter code" read and to free exploration.
 
 ### Step 2 — Seed the cells
 
@@ -974,7 +969,7 @@ The notebook should contain 5–7 cells covering:
 Example template (to be refined with actual hackathon organizers' briefs):
 
 \`\`\`
-widget_display({name: "notebook-document", params: {
+widget_display({name: "notebook", params: {
   title: "Hackathon Assemblée Nationale · starter",
   cells: [
     {
@@ -1039,7 +1034,6 @@ These recipes produce more specialized layouts than a generic notebook, and are
 - **Forgetting the hackathon framing**: without the "bienvenue" and "à vous" markdown cells, participants land on a bare notebook and lose the playbook feeling.
 - **SQL without LIMIT**: Tricoteuses queries without \`LIMIT\` can return thousands of rows and slow down the first impression.
 - **Inventing data**: do not seed with fake French parliamentary content (fake deputies, fake votes). If the actual data is not known at seed time, use generic queries (\`SELECT * FROM scrutins LIMIT 5\`) and let the user discover from there.
-- **Picking the wrong layout**: if the user is solo and wants to code fast, \`notebook-compact\` is better than \`notebook-document\`. Default to document for hackathon context because of the collaborative framing, not as a hard rule.
 `,
   'hummingbird-data': `---
 id: hummingbird-data
@@ -1133,8 +1127,8 @@ Do NOT render any widget.
   'notebook-playbook': `---
 id: create-interactive-notebook-playbook
 name: Create an interactive notebook playbook
-components_used: [notebook-compact, notebook-workspace, notebook-document, notebook-editorial]
-when: the user wants to experiment with data, prototype a small analysis, share a reusable scenario, let others fork and try a dataset, or prepare a hackathon-ready playground. Keywords include "playground", "playbook", "experiment", "try", "prototype", "hackathon", "share a notebook", "template", "starter".
+components_used: [notebook]
+when: the user wants to experiment with data, prototype a small analysis, share a reusable scenario, or prepare a hackathon-ready playground. Keywords include "playground", "playbook", "experiment", "try", "prototype", "hackathon", "share a notebook", "template", "starter", "publish", "memo", "report".
 servers: [autoui]
 layout:
   type: single
@@ -1148,37 +1142,29 @@ The user asks for a **notebook-like interactive playground** that combines text,
 - "I want to prototype a small analysis"
 - "Set up a hackathon starter"
 - "Make a reusable template for exploring CSVs / this API / these tables"
+- "Publish this analysis as a short memo"
 
 This recipe applies across domains (parliamentary data, biodiversity, news, business datasets, etc.) — it only prescribes the **shape** of the answer, not its content.
 
 ## How to use
 
-### Step 1 — Pick the right notebook layout
-
-Choose one of the four \`notebook-*\` widgets based on the user's implicit intent:
-
-| Layout | Use when |
-|---|---|
-| \`notebook-compact\` | Quick data exploration, reactive dataflow with named outputs, minimal chrome. **Default for most "playground" and "hackathon" requests.** |
-| \`notebook-workspace\` | The user expects a multi-cell analyst workspace with sources, cell navigation, and a "publish" step. Use when they mention "dashboard", "app", "workspace". |
-| \`notebook-document\` | The user plans to share and discuss with a team. Use when "collaborate", "review", "comment" appear. |
-| \`notebook-editorial\` | The user wants a polished, article-like final deliverable mixing prose and code. Use for "memo", "report", "writeup", "blog-style". |
+### Step 1 — Use the \`notebook\` widget
 
-When in doubt, pick \`notebook-compact\`.
+There is a single notebook widget. Prose paragraphs (\`md\`), SQL queries (\`sql\`) and JS code (\`js\`) share one ordered flow, all drag-and-droppable together. Publication-ready serif prose, suitable for playgrounds, memos, collaborative reviews and analyst workspaces alike.
 
 ### Step 2 — Pre-fill the cells with context-aware seeds
 
 Never create an empty notebook. Always seed with 3–5 cells that give the user an immediate starting point:
 
 1. **First cell: markdown** — title + one-sentence context of what the notebook is for
-2. **Second cell: markdown or code** — if an MCP data source is connected, a starter query that returns something visible (e.g. \`SELECT * FROM {table} LIMIT 10\`). Otherwise a markdown cell describing the next step
-3. **Third cell: code** — a transformation or a visualization that uses the output of step 2. Use \`varname\` on the SQL cell (\`varname: "rows"\`) and reference it in the JS cell
-4. **Last cell: markdown** — a short "to you to play" note inviting the user to add cells, edit, or fork
+2. **Second cell: sql or md** — if an MCP data source is connected, a starter query that returns something visible (e.g. \`SELECT * FROM {table} LIMIT 10\`). Otherwise a markdown cell describing the next step
+3. **Third cell: code** — a transformation or a visualization that uses the output of step 2. Use \`varname\` on the SQL cell (\`varname: "rows"\`) and reference it in the JS cell to activate the reactive dataflow
+4. **Last cell: markdown** — a short "to you to play" note inviting the user to add cells or edit
 
 Example seed for a generic data playground:
 
 \`\`\`
-widget_display({name: "notebook-compact", params: {
+widget_display({name: "notebook", params: {
   title: "Exploration playground",
   cells: [
     {type: "md", content: "### Exploration playground\\n\\nStart by running the first SQL cell, then iterate."},
@@ -1198,47 +1184,71 @@ If a specific MCP server is connected, replace the generic \`source\` and \`sele
 
 Always keep queries **short** and **limited** so the first run returns quickly and visually.
 
-### Step 4 — Share and fork
+SQL cells are dispatched automatically to the server's \`*_query_sql\` tool (first match). JS cells run in a Web Worker with upstream named outputs injected as scope.
 
-After creating the notebook, mention to the user that they can:
-- Click \`share\` in the toolbar to open the export modal (hyperskill link for in-session sharing, markdown/png/json for external export)
-- Switch to \`view\` mode (read-only, no controls visible) when presenting to someone
-- Access the \`⟲ history\` panel to see the trace of edits, and restore deleted cells
+### Step 4 — Exporting & publishing
+
+The toolbar \`share\` button offers **four export formats**:
+
+| Format | What it does |
+|---|---|
+| **Hyperskill link** | Copies both the canonical Hyperskill URL and a short domain-scoped URL (\`?n=<token>\`). The short URL opens the read-only public viewer at \`nb.hyperskills.net\`. |
+| **Markdown** | Downloads a \`.md\` file containing the notebook content. |
+| **PNG** | Snapshots the rendered notebook to an image. |
+| **JSON** | Exports the full widget state — re-importable for programmatic reuse. |
+
+### Step 5 — Working with connected data servers
+
+When one or more MCP data servers are connected, the notebook exposes a **collapsible left pane** (bookmark-bar styling, collapsed by default) that lists:
+- **Recipes** published by each server (\`{server}_list_recipes()\`)
+- **Tools / tables** exposed by each server (\`{server}_list_tools()\`)
+
+Clicking any recipe opens a viewer modal. Each fenced code block inside the recipe has a \`↳ inject\` button that drops the snippet into the notebook as a new cell.
 
-For hackathon contexts, prefer seeding a **document** layout (comments + avatars) so participants feel they are joining a shared space.
+Two toolbar buttons flank the left pane:
+- **\`+ md\`** — 3-tab modal (New / File / URL) to create a markdown cell from scratch, from a local \`.md\` file, or from a URL
+- **\`+ recipe\`** — 3-tab modal (Browser / File / URL) to import a recipe from a connected server, a local \`.recipe.md\` file, or a URL
+
+Pass the server metadata via the \`servers:\` param:
+
+\`\`\`ts
+widget_display({
+  name: 'notebook',
+  params: {
+    title: '...',
+    cells: [...],
+    servers: [{ name: 'tricoteuses', url: 'https://...', kind: 'data' }]
+  }
+})
+\`\`\`
+
+**Filter rule**: only MCP *data* servers (\`kind: 'data'\`) belong in \`servers:\`. Do NOT include WebMCP UI servers such as \`autoui\`.
+
+### Step 6 — Hand-off guidance
+
+After creating the notebook, mention to the user that they can:
+- **Share in four formats** via the toolbar \`share\` button (Hyperskill / Markdown / PNG / JSON)
+- **Switch to \`view\` mode** (read-only) when presenting
+- Access the \`⟲ history\` panel to see the edit trace and restore deleted cells
+- **Import recipes** from connected MCP servers via the left pane or the \`+ recipe\` modal
 
 ## Examples
 
 ### Generic CSV / table playground
 \`\`\`
-// user: "I need a playground to play with this CSV"
-widget_display({name: "notebook-compact", params: {
+widget_display({name: "notebook", params: {
   title: "CSV playground",
   cells: [
     {type: "md", content: "### CSV playground\\n\\nRun the SQL cell to see the first rows, then iterate."},
     {type: "sql", content: "select * from source limit 20", varname: "rows"},
-    {type: "js", content: "// summarize, chart, or filter rows here"}
-  ]
-}})
-\`\`\`
-
-### Collaborative analysis
-\`\`\`
-// user: "Set up a notebook my team can edit together"
-widget_display({name: "notebook-document", params: {
-  title: "Team analysis",
-  cells: [
-    {type: "md", content: "Kick-off: describe the question here."},
-    {type: "sql", content: "select * from source limit 10"},
-    {type: "md", content: "Your findings: add thoughts, highlights (<mark>key sentence</mark>), and comments on the code cells above."}
+    {type: "js", content: "// summarize, chart, or filter rows here\\nconsole.table(rows)"}
   ]
 }})
 \`\`\`
 
 ### Final memo
 \`\`\`
-// user: "Prepare a short memo of my findings"
-widget_display({name: "notebook-editorial", params: {
+widget_display({name: "notebook", params: {
   title: "Findings memo",
   kicker: "memo",
   cells: [
@@ -1255,10 +1265,10 @@ widget_display({name: "notebook-editorial", params: {
 ## Common mistakes
 
 - **Empty notebook**: never call \`widget_display\` without at least 3 seed cells. The user expects something they can immediately run.
-- **Wrong layout for the intent**: do not use \`notebook-editorial\` for quick exploration — it signals "finished article" and intimidates. Use \`notebook-compact\` unless the user explicitly asks for a publication feel.
 - **Heavy initial queries**: always \`LIMIT 10\` or \`LIMIT 20\` in seed SQL cells. Users will expand later if needed.
-- **Missing \`varname\` on SQL cells** (in compact layout): the named output is what the compact layout showcases. Without it, the notebook loses half its reactive story.
-- **Inventing UUIDs or fork IDs**: leave \`id\` and \`forkId\` unset — the widget generates sensible defaults. Only pass \`id\` when restoring an existing notebook.
+- **Missing \`varname\` on SQL cells**: the named output drives the reactive dataflow (downstream JS cells go stale when their upstream re-runs). Without it, the notebook loses half its story.
+- **Inventing UUIDs**: leave \`id\` unset — the widget generates a sensible default. Only pass \`id\` when restoring an existing notebook.
+- **Including \`autoui\` in \`servers:\`**: only MCP *data* servers (\`kind: 'data'\`) belong there.
 `,
   'parlementaire-profile': `---
 id: display-parliamentary-profile-with-hemicycle-and-votes

package/src/recipes/hackathon-assemblee-nationale.md

@@ -1,7 +1,7 @@
 ---
 id: hackathon-assemblee-nationale-mcp-webmcp
 name: Hackathon Assemblée Nationale · MCP & WebMCP starter
-components_used: [notebook-document, notebook-compact]
+components_used: [notebook]
 when: the user mentions the Assemblée Nationale hackathon, wants to experiment with parliamentary data (Tricoteuses, Legifrance), or asks for a starter notebook to explore deputies, votes, amendments, or legislative texts in a hackathon context. Keywords include "hackathon Assemblée Nationale", "MCP WebMCP hackathon", "tricoteuses playbook", "parlement playground", "hackathon parlementaire".
 servers: [autoui, tricoteuses]
 layout:
@@ -20,14 +20,9 @@ This recipe is a **specialization** of the generic `notebook-playbook` recipe
 
 ## How to use
 
-### Step 1 — Pick the document layout
+### Step 1 — Use the `notebook` widget
 
-Default to `notebook-document` for the hackathon. Reasons:
-- Participants expect to collaborate and leave traces for each other (avatars, comments)
-- The document layout reads naturally as "hackathon brief + starter code" rather than "dev tool"
-- Margin comments can be seeded to hint at directions to explore
-
-If the participant asks for a minimal dev-focused playground instead, fall back to `notebook-compact`.
+The single `notebook` widget fits the hackathon brief: prose, SQL and JS share one drag-and-droppable flow, suited both to a "brief + starter code" read and to free exploration.
 
 ### Step 2 — Seed the cells
 
@@ -43,7 +38,7 @@ The notebook should contain 5–7 cells covering:
 Example template (to be refined with actual hackathon organizers' briefs):
 
 ```
-widget_display({name: "notebook-document", params: {
+widget_display({name: "notebook", params: {
   title: "Hackathon Assemblée Nationale · starter",
   cells: [
     {
@@ -108,4 +103,3 @@ These recipes produce more specialized layouts than a generic notebook, and are
 - **Forgetting the hackathon framing**: without the "bienvenue" and "à vous" markdown cells, participants land on a bare notebook and lose the playbook feeling.
 - **SQL without LIMIT**: Tricoteuses queries without `LIMIT` can return thousands of rows and slow down the first impression.
 - **Inventing data**: do not seed with fake French parliamentary content (fake deputies, fake votes). If the actual data is not known at seed time, use generic queries (`SELECT * FROM scrutins LIMIT 5`) and let the user discover from there.
-- **Picking the wrong layout**: if the user is solo and wants to code fast, `notebook-compact` is better than `notebook-document`. Default to document for hackathon context because of the collaborative framing, not as a hard rule.

package/src/recipes/notebook-playbook.md

@@ -1,8 +1,8 @@
 ---
 id: create-interactive-notebook-playbook
 name: Create an interactive notebook playbook
-components_used: [notebook-compact, notebook-workspace, notebook-document, notebook-editorial]
-when: the user wants to experiment with data, prototype a small analysis, share a reusable scenario, let others fork and try a dataset, or prepare a hackathon-ready playground. Keywords include "playground", "playbook", "experiment", "try", "prototype", "hackathon", "share a notebook", "template", "starter".
+components_used: [notebook]
+when: the user wants to experiment with data, prototype a small analysis, share a reusable scenario, or prepare a hackathon-ready playground. Keywords include "playground", "playbook", "experiment", "try", "prototype", "hackathon", "share a notebook", "template", "starter", "publish", "memo", "report".
 servers: [autoui]
 layout:
   type: single
@@ -16,37 +16,29 @@ The user asks for a **notebook-like interactive playground** that combines text,
 - "I want to prototype a small analysis"
 - "Set up a hackathon starter"
 - "Make a reusable template for exploring CSVs / this API / these tables"
+- "Publish this analysis as a short memo"
 
 This recipe applies across domains (parliamentary data, biodiversity, news, business datasets, etc.) — it only prescribes the **shape** of the answer, not its content.
 
 ## How to use
 
-### Step 1 — Pick the right notebook layout
+### Step 1 — Use the `notebook` widget
 
-Choose one of the four `notebook-*` widgets based on the user's implicit intent:
-
-| Layout | Use when |
-|---|---|
-| `notebook-compact` | Quick data exploration, reactive dataflow with named outputs, minimal chrome. **Default for most "playground" and "hackathon" requests.** |
-| `notebook-workspace` | The user expects a multi-cell analyst workspace with sources, cell navigation, and a "publish" step. Use when they mention "dashboard", "app", "workspace". |
-| `notebook-document` | The user plans to share and discuss with a team. Use when "collaborate", "review", "comment" appear. |
-| `notebook-editorial` | The user wants a polished, article-like final deliverable mixing prose and code. Use for "memo", "report", "writeup", "blog-style". |
-
-When in doubt, pick `notebook-compact`.
+There is a single notebook widget. Prose paragraphs (`md`), SQL queries (`sql`) and JS code (`js`) share one ordered flow, all drag-and-droppable together. Publication-ready serif prose, suitable for playgrounds, memos, collaborative reviews and analyst workspaces alike.
 
 ### Step 2 — Pre-fill the cells with context-aware seeds
 
 Never create an empty notebook. Always seed with 3–5 cells that give the user an immediate starting point:
 
 1. **First cell: markdown** — title + one-sentence context of what the notebook is for
-2. **Second cell: markdown or code** — if an MCP data source is connected, a starter query that returns something visible (e.g. `SELECT * FROM {table} LIMIT 10`). Otherwise a markdown cell describing the next step
-3. **Third cell: code** — a transformation or a visualization that uses the output of step 2. Use `varname` on the SQL cell (`varname: "rows"`) and reference it in the JS cell
-4. **Last cell: markdown** — a short "to you to play" note inviting the user to add cells, edit, or fork
+2. **Second cell: sql or md** — if an MCP data source is connected, a starter query that returns something visible (e.g. `SELECT * FROM {table} LIMIT 10`). Otherwise a markdown cell describing the next step
+3. **Third cell: code** — a transformation or a visualization that uses the output of step 2. Use `varname` on the SQL cell (`varname: "rows"`) and reference it in the JS cell to activate the reactive dataflow
+4. **Last cell: markdown** — a short "to you to play" note inviting the user to add cells or edit
 
 Example seed for a generic data playground:
 
 ```
-widget_display({name: "notebook-compact", params: {
+widget_display({name: "notebook", params: {
   title: "Exploration playground",
   cells: [
     {type: "md", content: "### Exploration playground\n\nStart by running the first SQL cell, then iterate."},
@@ -66,47 +58,71 @@ If a specific MCP server is connected, replace the generic `source` and `select
 
 Always keep queries **short** and **limited** so the first run returns quickly and visually.
 
-### Step 4 — Share and fork
+SQL cells are dispatched automatically to the server's `*_query_sql` tool (first match). JS cells run in a Web Worker with upstream named outputs injected as scope.
 
-After creating the notebook, mention to the user that they can:
-- Click `share` in the toolbar to open the export modal (hyperskill link for in-session sharing, markdown/png/json for external export)
-- Switch to `view` mode (read-only, no controls visible) when presenting to someone
-- Access the `⟲ history` panel to see the trace of edits, and restore deleted cells
+### Step 4 — Exporting & publishing
+
+The toolbar `share` button offers **four export formats**:
+
+| Format | What it does |
+|---|---|
+| **Hyperskill link** | Copies both the canonical Hyperskill URL and a short domain-scoped URL (`?n=<token>`). The short URL opens the read-only public viewer at `nb.hyperskills.net`. |
+| **Markdown** | Downloads a `.md` file containing the notebook content. |
+| **PNG** | Snapshots the rendered notebook to an image. |
+| **JSON** | Exports the full widget state — re-importable for programmatic reuse. |
+
+### Step 5 — Working with connected data servers
+
+When one or more MCP data servers are connected, the notebook exposes a **collapsible left pane** (bookmark-bar styling, collapsed by default) that lists:
+- **Recipes** published by each server (`{server}_list_recipes()`)
+- **Tools / tables** exposed by each server (`{server}_list_tools()`)
+
+Clicking any recipe opens a viewer modal. Each fenced code block inside the recipe has a `↳ inject` button that drops the snippet into the notebook as a new cell.
+
+Two toolbar buttons flank the left pane:
+- **`+ md`** — 3-tab modal (New / File / URL) to create a markdown cell from scratch, from a local `.md` file, or from a URL
+- **`+ recipe`** — 3-tab modal (Browser / File / URL) to import a recipe from a connected server, a local `.recipe.md` file, or a URL
+
+Pass the server metadata via the `servers:` param:
+
+```ts
+widget_display({
+  name: 'notebook',
+  params: {
+    title: '...',
+    cells: [...],
+    servers: [{ name: 'tricoteuses', url: 'https://...', kind: 'data' }]
+  }
+})
+```
+
+**Filter rule**: only MCP *data* servers (`kind: 'data'`) belong in `servers:`. Do NOT include WebMCP UI servers such as `autoui`.
 
-For hackathon contexts, prefer seeding a **document** layout (comments + avatars) so participants feel they are joining a shared space.
+### Step 6 — Hand-off guidance
+
+After creating the notebook, mention to the user that they can:
+- **Share in four formats** via the toolbar `share` button (Hyperskill / Markdown / PNG / JSON)
+- **Switch to `view` mode** (read-only) when presenting
+- Access the `⟲ history` panel to see the edit trace and restore deleted cells
+- **Import recipes** from connected MCP servers via the left pane or the `+ recipe` modal
 
 ## Examples
 
 ### Generic CSV / table playground
 ```
-// user: "I need a playground to play with this CSV"
-widget_display({name: "notebook-compact", params: {
+widget_display({name: "notebook", params: {
   title: "CSV playground",
   cells: [
     {type: "md", content: "### CSV playground\n\nRun the SQL cell to see the first rows, then iterate."},
     {type: "sql", content: "select * from source limit 20", varname: "rows"},
-    {type: "js", content: "// summarize, chart, or filter rows here"}
-  ]
-}})
-```
-
-### Collaborative analysis
-```
-// user: "Set up a notebook my team can edit together"
-widget_display({name: "notebook-document", params: {
-  title: "Team analysis",
-  cells: [
-    {type: "md", content: "Kick-off: describe the question here."},
-    {type: "sql", content: "select * from source limit 10"},
-    {type: "md", content: "Your findings: add thoughts, highlights (<mark>key sentence</mark>), and comments on the code cells above."}
+    {type: "js", content: "// summarize, chart, or filter rows here\nconsole.table(rows)"}
   ]
 }})
 ```
 
 ### Final memo
 ```
-// user: "Prepare a short memo of my findings"
-widget_display({name: "notebook-editorial", params: {
+widget_display({name: "notebook", params: {
   title: "Findings memo",
   kicker: "memo",
   cells: [
@@ -123,7 +139,7 @@ widget_display({name: "notebook-editorial", params: {
 ## Common mistakes
 
 - **Empty notebook**: never call `widget_display` without at least 3 seed cells. The user expects something they can immediately run.
-- **Wrong layout for the intent**: do not use `notebook-editorial` for quick exploration — it signals "finished article" and intimidates. Use `notebook-compact` unless the user explicitly asks for a publication feel.
 - **Heavy initial queries**: always `LIMIT 10` or `LIMIT 20` in seed SQL cells. Users will expand later if needed.
-- **Missing `varname` on SQL cells** (in compact layout): the named output is what the compact layout showcases. Without it, the notebook loses half its reactive story.
-- **Inventing UUIDs or fork IDs**: leave `id` and `forkId` unset — the widget generates sensible defaults. Only pass `id` when restoring an existing notebook.
+- **Missing `varname` on SQL cells**: the named output drives the reactive dataflow (downstream JS cells go stale when their upstream re-runs). Without it, the notebook loses half its story.
+- **Inventing UUIDs**: leave `id` unset — the widget generates a sensible default. Only pass `id` when restoring an existing notebook.
+- **Including `autoui` in `servers:`**: only MCP *data* servers (`kind: 'data'`) belong there.

package/src/server/hawkProxy.ts

@@ -0,0 +1,54 @@
+/**
+ * Shared Hawk proxy handler — used by apps' /api/hawk/+server.ts
+ * Hawk = OpenAI-compatible endpoint at https://hawk.hyperskills.net/v1
+ * Bearer token lives server-side in HAWK_API_KEY env var.
+ */
+function sanitizeId(id: string | undefined): string {
+  if (!id) return 'x';
+  const clean = id.replace(/[^a-zA-Z0-9]/g, '');
+  return clean || 'x';
+}
+
+/**
+ * Some llama-cpp chat templates (Qwen, Mistral family) enforce alphanumeric
+ * tool_call IDs via Jinja raise_exception. Gemma's template drops tool_use_id
+ * entirely (cf. gemma4-prompt-builder.ts:194) — safe passthrough.
+ * Mirrors the convention of sanitizeServerName (tool-layers.ts:24).
+ */
+function needsIdSanitize(model: string | null | undefined): boolean {
+  if (!model) return false;
+  return /^(qwen|mistral|ministral|devstral|codestral|bielik)/.test(model);
+}
+
+export async function hawkProxy(
+  body: Record<string, unknown>,
+  apiKey: string,
+  model?: string | null,
+): Promise<Response> {
+  if (!apiKey) {
+    return new Response('HAWK_API_KEY missing', { status: 500 });
+  }
+  const m = model ?? 'qwen35-4b';
+  const cloned = JSON.parse(JSON.stringify(body)) as Record<string, unknown>;
+  if (needsIdSanitize(m) && Array.isArray(cloned.messages)) {
+    for (const msg of cloned.messages as Array<Record<string, unknown>>) {
+      if (msg.role === 'assistant' && Array.isArray(msg.tool_calls)) {
+        for (const tc of msg.tool_calls as Array<Record<string, unknown>>) {
+          tc.id = sanitizeId(tc.id as string | undefined);
+        }
+      } else if (msg.role === 'tool' && typeof msg.tool_call_id === 'string') {
+        msg.tool_call_id = sanitizeId(msg.tool_call_id);
+      }
+    }
+  }
+  const res = await fetch('https://hawk.hyperskills.net/v1/chat/completions', {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/json',
+      'Authorization': `Bearer ${apiKey}`,
+    },
+    body: JSON.stringify({ ...cloned, model: m }),
+  });
+  if (!res.ok) return new Response(await res.text(), { status: res.status });
+  return Response.json(await res.json());
+}

package/src/server/index.ts

@@ -0,0 +1,2 @@
+export { llmProxy } from './llmProxy.js';
+export { hawkProxy } from './hawkProxy.js';

package/src/tool-layers.ts

@@ -456,19 +456,31 @@ export function buildDiscoveryTools(layers: ToolLayer[]): ProviderTool[] {
   return tools;
 }
 
+/** Result of activateServerTools — extended tool set + per-call path maps for newly activated tools */
+export interface ActivateServerToolsResult {
+  tools: ProviderTool[];
+  /** Path maps for flattened schemas of newly added tools (empty if flatten is off). */
+  pathMaps: Map<string, Record<string, string[]>>;
+}
+
 /**
  * Add all tools from a specific server layer to the active tool set.
  * Called when a server is "touched" for the first time.
+ *
+ * Returns `{ tools, pathMaps }` — `pathMaps` is non-empty when `schemaOptions.flatten`
+ * is on, and must be merged into the loop-local pathMaps so `unflattenParams` works
+ * for lazily-activated tools. Backward-compat: if you only need `tools`, read `.tools`.
  */
 export function activateServerTools(
   currentTools: ProviderTool[],
   layer: ToolLayer,
   schemaOptions?: SchemaTransformOptions,
   trace?: PipelineTrace,
-): ProviderTool[] {
+): ActivateServerToolsResult {
   const prefix = `${sanitizeServerName(layer.serverName)}_${protocolToken(layer.protocol)}_`;
   const existing = new Set(currentTools.map(t => t.name));
   const newTools = [...currentTools];
+  const pathMaps = new Map<string, Record<string, string[]>>();
 
   const layerTools = layer.protocol === 'mcp'
     ? toProviderTools(layer.tools, schemaOptions, trace)
@@ -476,12 +488,22 @@ export function activateServerTools(
 
   for (const tool of layerTools) {
     const prefixed = `${prefix}${tool.name}`;
-    if (!existing.has(prefixed)) {
-      newTools.push({ ...tool, name: prefixed });
+    if (existing.has(prefixed)) continue;
+
+    let finalTool = { ...tool, name: prefixed };
+
+    if (schemaOptions?.flatten) {
+      const { schema: flatSchema, pathMap } = flattenSchema(finalTool.input_schema as import('@webmcp-auto-ui/core').JsonSchema);
+      if (Object.keys(pathMap).length > 0) {
+        finalTool.input_schema = flatSchema as Record<string, unknown>;
+        pathMaps.set(prefixed, pathMap);
+      }
     }
+
+    newTools.push(finalTool);
   }
 
-  return newTools;
+  return { tools: newTools, pathMaps };
 }
 
 /**

package/src/trace-observer.ts

@@ -374,9 +374,7 @@ export function createTraceObserver(ctx: TraceObserverContext): TraceObserver {
 
   function flush(): void {
     if (ids === null) return;
-    ctx.updateWidget(ids.dagId, buildCytoscapeData());
     ctx.updateWidget(ids.treeId, buildTreeData());
-    ctx.updateWidget(ids.sankeyId, buildSankeyData());
   }
 
   const callbacks: Partial<AgentCallbacks> = {
@@ -602,11 +600,11 @@ export function createTraceObserver(ctx: TraceObserverContext): TraceObserver {
     callbacks,
     mount(): { dagId: string; treeId: string; sankeyId: string } | null {
       if (ids !== null) return ids;
-      const dag = ctx.addWidget('animated-flow', buildCytoscapeData(), 'cytoscape');
       const tree = ctx.addWidget('tree', buildTreeData(), 'd3');
-      const sankey = ctx.addWidget('sankey', buildSankeyData(), 'autoui');
-      if (!dag || !tree || !sankey) return null;
-      ids = { dagId: dag.id, treeId: tree.id, sankeyId: sankey.id };
+      if (!tree) return null;
+      // dagId/sankeyId kept as empty strings for shape compatibility — the
+      // cytoscape + sankey sub-widgets were removed in favor of the tree only.
+      ids = { dagId: '', treeId: tree.id, sankeyId: '' };
       // Synchronous immediate flush — guarantees widgets reflect full buffer
       // when trace is toggled mid-run (retroactive within current session).
       flush();
@@ -633,19 +631,10 @@ export function createTraceObserver(ctx: TraceObserverContext): TraceObserver {
         flushTimer = null;
       }
       if (ids !== null) {
-        ctx.updateWidget(ids.dagId, {
-          elements: [],
-          style: CYTOSCAPE_STYLE,
-          layout: { name: 'cose', animate: true },
-        });
         ctx.updateWidget(ids.treeId, {
           root: { name: 'conv', children: [] },
           orientation: 'horizontal',
         });
-        ctx.updateWidget(ids.sankeyId, {
-          nodes: [],
-          links: [],
-        });
       }
     },
     detach(): void {