@webmcp-auto-ui/agent 2.5.27 → 2.5.28

package/src/notebook-widgets/recipes/workspace.md

@@ -1,94 +0,0 @@
----
-widget: notebook-workspace
-description: Dense analyst workspace with a header bar (title, draft/published tag, run all, publish) and a left sidebar listing data sources and cells for navigation. Cells display their name, execution time, and row counts. Targets data-team workflows with a publishable deliverable.
-schema:
-  type: object
-  properties:
-    id:
-      type: string
-    title:
-      type: string
-    mode:
-      type: string
-      enum: [edit, view]
-    cells:
-      type: array
-      items:
-        type: object
-        required: [type, content]
-        properties:
-          type:
-            type: string
-            enum: [md, sql, js]
-          content:
-            type: string
-          name:
-            type: string
-            description: Cell name shown in sidebar navigation (e.g. "intro", "sql_sales", "plot")
-          hideSource:
-            type: boolean
-          hideResult:
-            type: boolean
----
-
-## When to use
-
-Use `notebook-workspace` for analyst-oriented work that needs:
-- Multi-cell analyses with named, navigable cells (sidebar)
-- A clear separation between the editing context and a publishable "app" view
-- A data source reference permanently visible (even as placeholder: "no source connected")
-- Team workflows where "run all" and "publish" are distinct actions
-
-This layout is more enterprise-flavoured than `notebook-compact`. Prefer it when the user is building something to hand off, not just exploring.
-
-## How to use
-
-1. **Create with named cells** so the sidebar navigation is meaningful:
-   ```
-   widget_display({name: "notebook-workspace", params: {
-     title: "My analysis",
-     cells: [
-       {type: "md", name: "intro", content: "What we are investigating."},
-       {type: "sql", name: "fetch_rows", content: "select * from source limit 100"},
-       {type: "js", name: "visualize", content: "// chart the rows"}
-     ]
-   }})
-   ```
-
-2. **The sidebar shows** data sources (when connected) and the numbered list of cells. Clicking a cell item in the sidebar focuses that cell.
-
-3. **The header has** run all / share / publish buttons. Publish is the primary (accent-coloured) CTA — it represents the transition from draft to read-only app view.
-
-## Notes
-
-- Cells are added via buttons in the sidebar (not in the header).
-- Run controls (green/red pill) sit at the left of each cell's header, right after the drag handle.
-- Each cell head can be renamed inline in the sidebar (click the "N · name" item).
-- The sidebar under "sources" shows a placeholder when no MCP source is connected — a gentle nudge toward the connect flow.
-
-## Integration with connected data servers
-
-If a MCP **data** server is currently connected (the user has linked one, e.g. `tricoteuses`, `metmuseum`), BEFORE seeding cells the agent MUST:
-
-1. Call `{server}_list_recipes()` or `{server}_search_recipes(query)` to discover data recipes relevant to the user's intent.
-2. Call `{server}_list_tools()` to see available tables and endpoints.
-3. For each high-signal recipe or table, seed ONE named cell that demonstrates it — typical shapes:
-   - an SQL `SELECT ... LIMIT 10` with a meaningful cell name (e.g. `fetch_amendments`)
-   - a `run_script` invocation for recipes requiring code
-   - a short markdown cell describing the recipe and its parameters
-4. Pass the server metadata via the `servers:` param so the sidebar "sources" section and server menu modal render correctly:
-
-   ```ts
-   widget_display({
-     name: 'notebook-workspace',
-     params: {
-       title: '...',
-       cells: [...],
-       servers: [{ name: 'tricoteuses', url: 'https://...', kind: 'data' }]
-     }
-   })
-   ```
-
-If NO data server is connected, seed generic markdown-only cells that describe the intended analysis and invite the user to connect an MCP server — this matches the "no source connected" sidebar placeholder.
-
-**Filter rule**: only MCP *data* servers (`kind: 'data'`) belong in `servers:`. Do NOT include WebMCP UI servers such as `autoui` — they expose no queryable data and would clutter the sources sidebar.