@noodleseed/agent-kit 0.92.0 → 0.94.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@noodleseed/agent-kit",
-  "version": "0.92.0",
+  "version": "0.94.0",
   "private": false,
   "description": "Self-checking, self-updating agent skills for the Noodle Seed CLI. Authored in this repo by @noodle-borg/agent-kit; this is the published, independently-versioned canonical skills artifact the CLI fetches and verifies.",
   "license": "Apache-2.0",

package/skills/claude-code/SKILL.md

@@ -3,7 +3,7 @@ name: noodle-seed
 description: "Use when building, validating, testing, deploying, or operating a local or hosted Noodle Seed MCP server or app authored in TypeScript with the noodle CLI."
 ---
 
-<!-- noodle-skill version:0.92.0 hash:13ddce01769caae4 -->
+<!-- noodle-skill version:0.94.0 hash:13ddce01769caae4 -->
 
 # Noodle Seed
 

package/skills/claude-code/authoring-mcp-servers/SKILL.md

@@ -3,7 +3,7 @@ name: authoring-mcp-servers
 description: "Use when creating or extending a headless Noodle Seed MCP server, tool, resource, prompt, or typed model-facing capability."
 ---
 
-<!-- noodle-skill version:0.92.0 hash:dd57a15df15d10b2 -->
+<!-- noodle-skill version:0.94.0 hash:dd57a15df15d10b2 -->
 
 # authoring-mcp-servers
 

package/skills/claude-code/building-mcp-apps/SKILL.md

@@ -3,7 +3,7 @@ name: building-mcp-apps
 description: "Use when a Noodle Seed MCP App, widget, interactive card, visual interaction, or host-visible UI is the primary requested outcome."
 ---
 
-<!-- noodle-skill version:0.92.0 hash:98c7b07c82a7d7ce -->
+<!-- noodle-skill version:0.94.0 hash:98c7b07c82a7d7ce -->
 
 # building-mcp-apps
 

package/skills/claude-code/connecting-apis-to-mcp/SKILL.md

@@ -3,7 +3,7 @@ name: connecting-apis-to-mcp
 description: "Use when all four API-evidence inputs exist—and only then: API base URL, authentication scheme, representative safe read, and observed response."
 ---
 
-<!-- noodle-skill version:0.92.0 hash:8020811f1769c538 -->
+<!-- noodle-skill version:0.94.0 hash:8020811f1769c538 -->
 
 # connecting-apis-to-mcp
 

package/skills/claude-code/creating-product-agent-guides/SKILL.md

@@ -3,7 +3,7 @@ name: creating-product-agent-guides
 description: "Use when a Noodle Seed MCP server needs a new or revised product agent guide, App Package skill, or explicit product-skill regeneration."
 ---
 
-<!-- noodle-skill version:0.92.0 hash:0e06e11254563b6a -->
+<!-- noodle-skill version:0.94.0 hash:0e06e11254563b6a -->
 
 # creating-product-agent-guides
 

package/skills/claude-code/debugging-mcp-delivery/SKILL.md

@@ -3,7 +3,7 @@ name: debugging-mcp-delivery
 description: "Use when an existing Noodle Seed MCP project has a concrete validation, runtime, connector, App, host, deployment, or production failure."
 ---
 
-<!-- noodle-skill version:0.92.0 hash:8d75ad13f4b3120a -->
+<!-- noodle-skill version:0.94.0 hash:8d75ad13f4b3120a -->
 
 # debugging-mcp-delivery
 

package/skills/claude-code/deploying-mcp-services/SKILL.md

@@ -3,7 +3,7 @@ name: deploying-mcp-services
 description: "Use when the user explicitly requests a Noodle Seed hosted link, configuration write, deployment, access change, rollback, or connection write."
 ---
 
-<!-- noodle-skill version:0.92.0 hash:3a1e14ff9b98ddbd -->
+<!-- noodle-skill version:0.94.0 hash:3a1e14ff9b98ddbd -->
 
 # deploying-mcp-services
 

package/skills/claude-code/designing-mcp-products/SKILL.md

@@ -3,7 +3,7 @@ name: designing-mcp-products
 description: "Use when a Noodle Seed MCP product idea needs conversational fit, user benefit, scope, interaction, or evidence design before implementation."
 ---
 
-<!-- noodle-skill version:0.92.0 hash:a21b2ed9997f9454 -->
+<!-- noodle-skill version:0.94.0 hash:a21b2ed9997f9454 -->
 
 # designing-mcp-products
 

package/skills/claude-code/embedding-mcp-assistants/SKILL.md

@@ -3,7 +3,7 @@ name: embedding-mcp-assistants
 description: "Use when embedding a Noodle assistant into an existing SaaS or web application with browser, identity, session, and credential boundaries."
 ---
 
-<!-- noodle-skill version:0.92.0 hash:d554d661ed7ac7be -->
+<!-- noodle-skill version:0.94.0 hash:d554d661ed7ac7be -->
 
 # embedding-mcp-assistants
 

package/skills/claude-code/embedding-mcp-assistants/references/embedded-assistant.md

@@ -197,6 +197,8 @@ Omitted UI fields retain the complete managed baseline: a bottom-center frosted
 
 Set `webmcp: { enabled: true }` on the assistant to let a browser agent reach this session's tools through the page's WebMCP API, and set it on an individual access surface to override that default in either direction — a marketing surface can opt in while a signed-in one opts out, or the reverse. Off unless set, and inert in browsers without `document.modelContext`. It governs discovery: whether the embed registers the tools this session already projects, narrowed to those that are both app-callable and model-visible. Every call executes over the same apps-bridge path the assistant's own calls take, so a browser agent gets the session's authority and nothing more, and a `confirm: true` tool still stops for a human in the panel rather than being accepted on the agent's behalf. It is not a second authorization boundary — the session is the only one. Bridge calls spend their own per-session and per-day budgets instead of model turns, and the surface's daily kill switch stops them too. Prefer this over hand-registering page-local tools that borrow the visitor's session: those carry no scoped authority, policy, or audit trail.
 
+Set `continuity: { enabled: true }` on a public or mixed access surface to let an anonymous visitor keep the conversation they can see when they navigate to another page of the same site. Off unless set, and refused on an authenticated surface, which reattaches through a backend-verified sign-in instead. It restores the visible text on a fresh session and never the old one: no tool authority, no share of a spent turn budget, and no pending confirmation carried across, so an unanswered confirmation stays unanswered. `windowSeconds` defaults to 300 with a 600 ceiling, `maxRestores` to 3 with a ceiling of 10, and 0 for either disables continuity outright; an operator may lower what you declare and can never raise it. The handle lives in `sessionStorage` so it dies with the tab, is single-use, and is valid only for the embed, origin, and visitor it was issued to. Declare it when a marketing site spreads one conversation across several pages; leave it off when anonymous conversation text should not survive a navigation at all.
+
 Give every business action a portable `tool(..., { title: "Complete task", description: "This will mark the task complete for everyone.", input: z.object({ task: z.string().meta({ title: "Task" }) }) })` title. The standard confirmation uses the tool title/description plus schema field `title`, `description`, and `format`; it shows Confirm and Don't proceed and keeps technical action details secondary. `behavior.showConfirmationDetails` defaults to `true`; set it to `false` to remove only the built-in card's Additional details disclosure and connector mechanics. The business review and decisions remain, `confirm: true` still suspends until acceptance, and headless/BYO `data-confirmation` stays unchanged. Do not put JSON or implementation names in business-facing copy.
 
 ## Configure and deploy

package/skills/claude-code/examples/acme-discovery/README.md

@@ -7,7 +7,8 @@ deep link. It pairs a `tool` discovery carousel with a model-visible `create_han
 server-level `handoff.allowedDomains`.
 
 Capability slots: top-of-funnel funnel discipline, discovery carousel widget, `create_handoff` deep-link
-handoff with attribution, `handoff.allowedDomains`, the **public website assistant surface**, and a worked
+handoff with attribution, `handoff.allowedDomains`, the **public website assistant surface** with its
+**WebMCP browser-agent bridge** on a real demo page (`site/index.html`), and a worked
 **design-first** artifact (the UX spec + wireframe below). It shows the "design the experience, then build
 it" flow the `noodle-seed` skill's `references/experience-design.md` teaches.
 
@@ -64,6 +65,43 @@ on whichever origin the backend designates:
 The ticket spend after account creation is identical to the one after sign-in; the service never
 operates a login of its own.
 
+## Browser agents on Acme's page
+
+`site/index.html` is the marketing page itself: static markup, four listings, and the one line a
+customer pastes.
+
+```html
+<script src="https://cloud.noodleseed.dev/v1/assistant/embed.js" data-embed-id="pub_…"></script>
+```
+
+Because the marketing surface sets `webmcp: { enabled: true }`, that same line does a second job in a
+browser that supports WebMCP: the embed registers the session's projected tools with
+`document.modelContext`, so a browser agent — Gemini-in-Chrome, Claude-in-Chrome — can call
+`discover_getaways` or `create_handoff` without a human typing in the panel.
+
+What it does **not** do is widen anything. A bridged call carries exactly the embed session's
+authority: the surface's six-capability allowlist, the same policy and budgets, the same audit trail,
+and the same confirmation card on `capture_lead` — the visitor still approves the lead in the panel,
+because a browser agent's consent is not the visitor's. The switch governs *discovery*, not
+permission: it decides whether an agent learns the tools are there. The signed-in account surface
+below leaves it off, which is the point of setting it per surface.
+
+Browsers without `document.modelContext` are unaffected; the page and the panel behave exactly as
+they did before.
+
+To run it:
+
+```sh
+noodle dev                 # the server, in one terminal
+npx serve site             # the page, in another (any static server works)
+```
+
+`noodle dev` serves the MCP endpoint, not HTML, so the page needs its own server. For a real
+end-to-end run, `noodle deploy` this example, paste the minted `pub_…` id into `site/index.html`, and
+add the origin you serve the page from to the `publicWebsite` `origins` list — the session exchange
+refuses any origin that is not listed. WebMCP itself ships behind an origin trial in Chrome 149+, so
+a browser without the trial enabled shows the assistant panel and no bridge.
+
 ## The consultative sales gateway
 
 When a visitor's plans firm up but they would rather not sign up, the assistant may — with explicit

package/skills/claude-code/examples/acme-discovery/site/index.html

@@ -0,0 +1,189 @@
+<!doctype html>
+<html lang="en">
+  <head>
+    <meta charset="utf-8" />
+    <meta name="viewport" content="width=device-width, initial-scale=1" />
+    <title>Acme Getaways — small-group trips</title>
+    <style>
+      :root {
+        --ac-teal: #0ea5a4;
+        --ac-ink: #0b1b1b;
+        --ac-slate: #234a48;
+        --ac-line: #e6e8ec;
+      }
+      * {
+        box-sizing: border-box;
+      }
+      body {
+        margin: 0;
+        font-family: 'Inter', -apple-system, BlinkMacSystemFont, 'Segoe UI', sans-serif;
+        background: #f4f5f7;
+        color: #1a1d22;
+        line-height: 1.55;
+      }
+      header {
+        background: var(--ac-ink);
+        color: #fff;
+        border-bottom: 3px solid var(--ac-teal);
+        padding: 34px 24px 30px;
+      }
+      header .wrap,
+      main {
+        max-width: 900px;
+        margin: 0 auto;
+      }
+      header h1 {
+        margin: 0;
+        font-size: 28px;
+        letter-spacing: -0.5px;
+      }
+      header h1 span {
+        color: var(--ac-teal);
+      }
+      header p {
+        margin: 6px 0 0;
+        font-size: 14px;
+        color: #9db3b1;
+      }
+      main {
+        padding: 32px 24px 96px;
+      }
+      .lede {
+        font-size: 16px;
+        color: var(--ac-slate);
+        margin: 0 0 28px;
+        max-width: 60ch;
+      }
+      .listings {
+        display: grid;
+        gap: 16px;
+        grid-template-columns: repeat(auto-fill, minmax(260px, 1fr));
+        list-style: none;
+        margin: 0;
+        padding: 0;
+      }
+      .listing {
+        background: #fff;
+        border: 1px solid var(--ac-line);
+        border-radius: 12px;
+        padding: 18px 20px;
+      }
+      .listing-name {
+        margin: 0;
+        font-size: 18px;
+        color: var(--ac-ink);
+      }
+      .listing-region {
+        margin: 2px 0 12px;
+        font-size: 12px;
+        letter-spacing: 0.6px;
+        text-transform: uppercase;
+        color: var(--ac-teal);
+        font-weight: 700;
+      }
+      .listing p {
+        margin: 0 0 12px;
+        font-size: 14px;
+        color: #4a545c;
+      }
+      .listing dl {
+        display: flex;
+        gap: 20px;
+        margin: 0;
+        font-size: 13px;
+        color: var(--ac-slate);
+      }
+      .listing dt {
+        font-size: 11px;
+        letter-spacing: 0.5px;
+        text-transform: uppercase;
+        color: #8a929c;
+      }
+      .listing dd {
+        margin: 0;
+        font-weight: 600;
+      }
+      footer {
+        border-top: 1px solid var(--ac-line);
+        margin-top: 40px;
+        padding-top: 20px;
+        font-size: 13px;
+        color: #8a929c;
+      }
+    </style>
+  </head>
+  <body>
+    <header>
+      <div class="wrap">
+        <h1><span>Acme</span> Getaways</h1>
+        <p>Small-group trips, planned in a conversation.</p>
+      </div>
+    </header>
+
+    <main>
+      <p class="lede">
+        Four places we know well. Ask the assistant in the corner to narrow them down, or let the
+        browser agent you already run do it for you — it can call the same tools, under the same
+        rules.
+      </p>
+
+      <ul class="listings">
+        <li class="listing">
+          <h3 class="listing-name">Coral Bay</h3>
+          <p class="listing-region">Adriatic coast</p>
+          <p>Calm swimming coves and a walkable old town — easy for a relaxed first trip.</p>
+          <dl>
+            <div><dt>From</dt><dd>$890</dd></div>
+            <div><dt>Best months</dt><dd>May–Sep</dd></div>
+          </dl>
+        </li>
+        <li class="listing">
+          <h3 class="listing-name">Monte Alto</h3>
+          <p class="listing-region">Northern Alps</p>
+          <p>Ski-in village with beginner slopes and long groomed runs.</p>
+          <dl>
+            <div><dt>From</dt><dd>$1,120</dd></div>
+            <div><dt>Best months</dt><dd>Dec–Mar</dd></div>
+          </dl>
+        </li>
+        <li class="listing">
+          <h3 class="listing-name">Old Quarter</h3>
+          <p class="listing-region">Central Europe</p>
+          <p>Dense museum district and food halls, all reachable on foot.</p>
+          <dl>
+            <div><dt>From</dt><dd>$640</dd></div>
+            <div><dt>Best months</dt><dd>Apr–Oct</dd></div>
+          </dl>
+        </li>
+        <li class="listing">
+          <h3 class="listing-name">Harbor City</h3>
+          <p class="listing-region">Pacific rim</p>
+          <p>Waterfront nightlife and day-trip islands a short ferry away.</p>
+          <dl>
+            <div><dt>From</dt><dd>$980</dd></div>
+            <div><dt>Best months</dt><dd>Sep–Nov</dd></div>
+          </dl>
+        </li>
+      </ul>
+
+      <footer>
+        A fictional brand, for demonstration. Every destination, price, and link is invented.
+      </footer>
+    </main>
+
+    <!--
+      The whole integration: one line, the same one a customer pastes.
+
+      The embed mounts <noodle-assistant>, mints a session against the public surface declared in
+      `src/server.ts`, and — because that surface sets `webmcp: { enabled: true }` — registers the
+      session's projected tools with `document.modelContext` where the browser offers it. A browser
+      agent then sees `discover_getaways`, `create_handoff`, `capture_lead` and the rest, and calling
+      one carries exactly this session's authority: the same allowlist, the same confirmation cards,
+      the same budgets and audit trail as the panel. Browsers without the API ignore all of it.
+
+      The id below is fictional. Run `noodle deploy` on this example to mint your own, paste it here,
+      and add this page's origin to the `publicWebsite` origins list.
+    -->
+    <script src="https://cloud.noodleseed.dev/v1/assistant/embed.js" data-embed-id="pub_examplepublicembedid00"></script>
+  </body>
+</html>

package/skills/claude-code/examples/acme-discovery/src/server.ts

@@ -343,6 +343,18 @@ export default server(
       access: [
         publicWebsite({
           origins: ['https://getaways.acme.example'],
+          // A browser agent on Acme's marketing page (Gemini-in-Chrome, Claude-in-Chrome) discovers
+          // exactly the capabilities listed below and reaches them over the same authorization,
+          // confirmation, budget, and audit path the panel's own calls take: `capture_lead` still
+          // stops for its confirmation card. `site/index.html` is the page this runs on.
+          webmcp: { enabled: true },
+          // A visitor who asks about Coral Bay on one page and clicks through to another would
+          // otherwise arrive at an empty panel and have to start over. This carries the text they
+          // have already read onto the next page, on a fresh session — never the old session's
+          // authority, budget, or a half-answered confirmation (ADR 0223). Opt-in because anonymous
+          // conversation text is Acme's content on Acme's page; the defaults below are deliberately
+          // tighter than the platform ceiling.
+          continuity: { enabled: true, windowSeconds: 300, maxRestores: 3 },
           capabilities: [
             destinations,
             discoverGetaways,

package/skills/claude-code/examples/acme-discovery/test/server.test.ts

@@ -69,6 +69,24 @@ describe('acme-discovery example', () => {
     expect(manifest.server.assistant?.labels?.signUpAction).toBe('Create free account');
   });
 
+  it('opens the marketing surface to browser agents and leaves the account surface closed', async () => {
+    const manifest = await app.toManifest();
+    const surfaces = manifest.server.assistant?.surfaces ?? [];
+
+    // Both front doors, asserted by count first: without it the per-surface claims below read a
+    // missing surface as `undefined` and pass, so deleting a surface would silently satisfy them.
+    expect(surfaces).toHaveLength(2);
+    // ADR 0220: the opt-in governs *discovery* — whether the embed registers this session's already
+    // projected tools with `document.modelContext`. A browser agent on Acme's marketing page reaches
+    // exactly the six capabilities above, over the same authorization, confirmation, and budget path
+    // the panel's own calls take. `capture_lead` still stops for its confirmation card.
+    expect(surfaces[0]?.webmcp).toEqual({ enabled: true });
+    // Per-surface opt-in exists so the two front doors can answer differently, and here they do: the
+    // signed-in account surface carries a traveler's identity, so its tools are not advertised to
+    // whatever agent happens to be running in that browser.
+    expect(surfaces[1]?.webmcp).toBeUndefined();
+  });
+
   it('declares the grounded knowledge component and its live site scope', async () => {
     const manifest = (await app.toManifest()) as { server: { knowledge?: unknown[] } };
     // One declaration: controlled files plus the live public site, compiled later into the

package/skills/claude-code/examples/acme-discovery/test/site-page.test.ts

@@ -0,0 +1,50 @@
+import { readFileSync } from 'node:fs';
+import { join } from 'node:path';
+import { describe, expect, it } from 'vitest';
+import app from '../src/server.js';
+
+/**
+ * `site/index.html` is the demo half of the WebMCP story (ADR 0220): the marketing page a browser
+ * agent actually visits. The compiled server says the marketing surface opts in; only a real page
+ * running the real snippet shows what that buys.
+ *
+ * These guard the two properties that make the demo honest rather than the markup, which is meant to
+ * be edited: the page mounts the published one-liner and nothing else, and it never advertises a
+ * getaway the server cannot discuss.
+ */
+
+const page = readFileSync(join(import.meta.dirname, '..', 'site', 'index.html'), 'utf8');
+
+describe('the acme-discovery demo page', () => {
+  it('mounts the assistant with the published one-line snippet', () => {
+    expect(page).toContain('<script src="https://cloud.noodleseed.dev/v1/assistant/embed.js"');
+    expect(page).toMatch(/data-embed-id="pub_[a-z0-9]{20,64}"/u);
+  });
+
+  it('carries bootstrap markup only, so the page never borrows the session itself', () => {
+    // The bridge lives in the embed bundle, where it runs under the session's authority and budgets.
+    // Page-local JavaScript reaching for the same tools would carry none of that, so there is none:
+    // the demo's only script is the snippet above, and it has no body of its own.
+    expect(page.match(/<script\b/gu)).toHaveLength(1);
+    expect(page).toMatch(/data-embed-id="pub_[a-z0-9]{20,64}"><\/script>/u);
+  });
+
+  it('is a placeholder deployment, not a live embed anyone can point at', () => {
+    // Copying this file must not aim a stranger's page at a real deployment, so the id is fictional
+    // and the README says how to mint your own.
+    expect(page).toContain('pub_examplepublicembedid00');
+    expect(page).toContain('noodle deploy');
+  });
+
+  it('offers only getaways the server can actually discuss', async () => {
+    const catalog = JSON.stringify(await app.toManifest());
+    const offered = [...page.matchAll(/<h3 class="listing-name">([^<]+)<\/h3>/gu)].map(
+      (match) => match[1],
+    );
+
+    expect(offered.length).toBeGreaterThan(2);
+    for (const name of offered) {
+      expect(catalog, `${name} is on the page but not in the server's catalog`).toContain(name);
+    }
+  });
+});

package/skills/claude-code/executing-noodle-plans/SKILL.md

@@ -3,7 +3,7 @@ name: executing-noodle-plans
 description: "Use when the user asks to execute an approved, decision-complete implementation plan for a Noodle Seed project task by task with test-first changes, review, recovery, and final verification."
 ---
 
-<!-- noodle-skill version:0.92.0 hash:6a9f132ddb79352e -->
+<!-- noodle-skill version:0.94.0 hash:6a9f132ddb79352e -->
 
 # Execute a Noodle Seed implementation plan
 

package/skills/claude-code/publishing-mcp-integrations/SKILL.md

@@ -3,7 +3,7 @@ name: publishing-mcp-integrations
 description: "Use when preparing, reviewing, or submitting a Noodle Seed MCP integration to a host or app directory."
 ---
 
-<!-- noodle-skill version:0.92.0 hash:0ccafb222038f553 -->
+<!-- noodle-skill version:0.94.0 hash:0ccafb222038f553 -->
 
 # publishing-mcp-integrations
 

package/skills/claude-code/references/embedded-assistant.md

@@ -197,6 +197,8 @@ Omitted UI fields retain the complete managed baseline: a bottom-center frosted
 
 Set `webmcp: { enabled: true }` on the assistant to let a browser agent reach this session's tools through the page's WebMCP API, and set it on an individual access surface to override that default in either direction — a marketing surface can opt in while a signed-in one opts out, or the reverse. Off unless set, and inert in browsers without `document.modelContext`. It governs discovery: whether the embed registers the tools this session already projects, narrowed to those that are both app-callable and model-visible. Every call executes over the same apps-bridge path the assistant's own calls take, so a browser agent gets the session's authority and nothing more, and a `confirm: true` tool still stops for a human in the panel rather than being accepted on the agent's behalf. It is not a second authorization boundary — the session is the only one. Bridge calls spend their own per-session and per-day budgets instead of model turns, and the surface's daily kill switch stops them too. Prefer this over hand-registering page-local tools that borrow the visitor's session: those carry no scoped authority, policy, or audit trail.
 
+Set `continuity: { enabled: true }` on a public or mixed access surface to let an anonymous visitor keep the conversation they can see when they navigate to another page of the same site. Off unless set, and refused on an authenticated surface, which reattaches through a backend-verified sign-in instead. It restores the visible text on a fresh session and never the old one: no tool authority, no share of a spent turn budget, and no pending confirmation carried across, so an unanswered confirmation stays unanswered. `windowSeconds` defaults to 300 with a 600 ceiling, `maxRestores` to 3 with a ceiling of 10, and 0 for either disables continuity outright; an operator may lower what you declare and can never raise it. The handle lives in `sessionStorage` so it dies with the tab, is single-use, and is valid only for the embed, origin, and visitor it was issued to. Declare it when a marketing site spreads one conversation across several pages; leave it off when anonymous conversation text should not survive a navigation at all.
+
 Give every business action a portable `tool(..., { title: "Complete task", description: "This will mark the task complete for everyone.", input: z.object({ task: z.string().meta({ title: "Task" }) }) })` title. The standard confirmation uses the tool title/description plus schema field `title`, `description`, and `format`; it shows Confirm and Don't proceed and keeps technical action details secondary. `behavior.showConfirmationDetails` defaults to `true`; set it to `false` to remove only the built-in card's Additional details disclosure and connector mechanics. The business review and decisions remain, `confirm: true` still suspends until acceptance, and headless/BYO `data-confirmation` stays unchanged. Do not put JSON or implementation names in business-facing copy.
 
 ## Configure and deploy

package/skills/claude-code/reporting-noodle-feedback/SKILL.md

@@ -3,7 +3,7 @@ name: reporting-noodle-feedback
 description: "Use when a Noodle Seed bug, misleading instruction, missing capability, or concrete product improvement should be proposed to the user."
 ---
 
-<!-- noodle-skill version:0.92.0 hash:660cc6ad9469d90f -->
+<!-- noodle-skill version:0.94.0 hash:660cc6ad9469d90f -->
 
 # reporting-noodle-feedback
 

package/skills/claude-code/verifying-mcp-delivery/SKILL.md

@@ -3,7 +3,7 @@ name: verifying-mcp-delivery
 description: "Use when proving a Noodle Seed MCP project works at a named compile, local, connector, App, host, deployment, or production evidence level."
 ---
 
-<!-- noodle-skill version:0.92.0 hash:292253cbaed9a3c5 -->
+<!-- noodle-skill version:0.94.0 hash:292253cbaed9a3c5 -->
 
 # verifying-mcp-delivery
 

package/skills/claude-code/wrapping-existing-applications/SKILL.md

@@ -3,7 +3,7 @@ name: wrapping-existing-applications
 description: "Use when an existing application has no stable usable API and needs a read-only, identity-first Noodle Seed integration plan before implementation."
 ---
 
-<!-- noodle-skill version:0.92.0 hash:379ab9f64878f1fe -->
+<!-- noodle-skill version:0.94.0 hash:379ab9f64878f1fe -->
 
 # wrapping-existing-applications
 

package/skills/codex/SKILL.md

@@ -3,7 +3,7 @@ name: noodle-seed
 description: "Use when building, validating, testing, deploying, or operating a local or hosted Noodle Seed MCP server or app authored in TypeScript with the noodle CLI."
 ---
 
-<!-- noodle-skill version:0.92.0 hash:13ddce01769caae4 -->
+<!-- noodle-skill version:0.94.0 hash:13ddce01769caae4 -->
 
 # Noodle Seed
 

package/skills/codex/authoring-mcp-servers/SKILL.md

@@ -3,7 +3,7 @@ name: authoring-mcp-servers
 description: "Use when creating or extending a headless Noodle Seed MCP server, tool, resource, prompt, or typed model-facing capability."
 ---
 
-<!-- noodle-skill version:0.92.0 hash:dd57a15df15d10b2 -->
+<!-- noodle-skill version:0.94.0 hash:dd57a15df15d10b2 -->
 
 # authoring-mcp-servers
 

package/skills/codex/building-mcp-apps/SKILL.md

@@ -3,7 +3,7 @@ name: building-mcp-apps
 description: "Use when a Noodle Seed MCP App, widget, interactive card, visual interaction, or host-visible UI is the primary requested outcome."
 ---
 
-<!-- noodle-skill version:0.92.0 hash:98c7b07c82a7d7ce -->
+<!-- noodle-skill version:0.94.0 hash:98c7b07c82a7d7ce -->
 
 # building-mcp-apps
 

package/skills/codex/connecting-apis-to-mcp/SKILL.md

@@ -3,7 +3,7 @@ name: connecting-apis-to-mcp
 description: "Use when all four API-evidence inputs exist—and only then: API base URL, authentication scheme, representative safe read, and observed response."
 ---
 
-<!-- noodle-skill version:0.92.0 hash:8020811f1769c538 -->
+<!-- noodle-skill version:0.94.0 hash:8020811f1769c538 -->
 
 # connecting-apis-to-mcp
 

package/skills/codex/creating-product-agent-guides/SKILL.md

@@ -3,7 +3,7 @@ name: creating-product-agent-guides
 description: "Use when a Noodle Seed MCP server needs a new or revised product agent guide, App Package skill, or explicit product-skill regeneration."
 ---
 
-<!-- noodle-skill version:0.92.0 hash:0e06e11254563b6a -->
+<!-- noodle-skill version:0.94.0 hash:0e06e11254563b6a -->
 
 # creating-product-agent-guides
 

package/skills/codex/debugging-mcp-delivery/SKILL.md

@@ -3,7 +3,7 @@ name: debugging-mcp-delivery
 description: "Use when an existing Noodle Seed MCP project has a concrete validation, runtime, connector, App, host, deployment, or production failure."
 ---
 
-<!-- noodle-skill version:0.92.0 hash:8d75ad13f4b3120a -->
+<!-- noodle-skill version:0.94.0 hash:8d75ad13f4b3120a -->
 
 # debugging-mcp-delivery
 

package/skills/codex/deploying-mcp-services/SKILL.md

@@ -3,7 +3,7 @@ name: deploying-mcp-services
 description: "Use when the user explicitly requests a Noodle Seed hosted link, configuration write, deployment, access change, rollback, or connection write."
 ---
 
-<!-- noodle-skill version:0.92.0 hash:3a1e14ff9b98ddbd -->
+<!-- noodle-skill version:0.94.0 hash:3a1e14ff9b98ddbd -->
 
 # deploying-mcp-services
 

package/skills/codex/designing-mcp-products/SKILL.md

@@ -3,7 +3,7 @@ name: designing-mcp-products
 description: "Use when a Noodle Seed MCP product idea needs conversational fit, user benefit, scope, interaction, or evidence design before implementation."
 ---
 
-<!-- noodle-skill version:0.92.0 hash:a21b2ed9997f9454 -->
+<!-- noodle-skill version:0.94.0 hash:a21b2ed9997f9454 -->
 
 # designing-mcp-products
 

package/skills/codex/embedding-mcp-assistants/SKILL.md

@@ -3,7 +3,7 @@ name: embedding-mcp-assistants
 description: "Use when embedding a Noodle assistant into an existing SaaS or web application with browser, identity, session, and credential boundaries."
 ---
 
-<!-- noodle-skill version:0.92.0 hash:d554d661ed7ac7be -->
+<!-- noodle-skill version:0.94.0 hash:d554d661ed7ac7be -->
 
 # embedding-mcp-assistants
 

package/skills/codex/embedding-mcp-assistants/references/embedded-assistant.md

@@ -197,6 +197,8 @@ Omitted UI fields retain the complete managed baseline: a bottom-center frosted
 
 Set `webmcp: { enabled: true }` on the assistant to let a browser agent reach this session's tools through the page's WebMCP API, and set it on an individual access surface to override that default in either direction — a marketing surface can opt in while a signed-in one opts out, or the reverse. Off unless set, and inert in browsers without `document.modelContext`. It governs discovery: whether the embed registers the tools this session already projects, narrowed to those that are both app-callable and model-visible. Every call executes over the same apps-bridge path the assistant's own calls take, so a browser agent gets the session's authority and nothing more, and a `confirm: true` tool still stops for a human in the panel rather than being accepted on the agent's behalf. It is not a second authorization boundary — the session is the only one. Bridge calls spend their own per-session and per-day budgets instead of model turns, and the surface's daily kill switch stops them too. Prefer this over hand-registering page-local tools that borrow the visitor's session: those carry no scoped authority, policy, or audit trail.
 
+Set `continuity: { enabled: true }` on a public or mixed access surface to let an anonymous visitor keep the conversation they can see when they navigate to another page of the same site. Off unless set, and refused on an authenticated surface, which reattaches through a backend-verified sign-in instead. It restores the visible text on a fresh session and never the old one: no tool authority, no share of a spent turn budget, and no pending confirmation carried across, so an unanswered confirmation stays unanswered. `windowSeconds` defaults to 300 with a 600 ceiling, `maxRestores` to 3 with a ceiling of 10, and 0 for either disables continuity outright; an operator may lower what you declare and can never raise it. The handle lives in `sessionStorage` so it dies with the tab, is single-use, and is valid only for the embed, origin, and visitor it was issued to. Declare it when a marketing site spreads one conversation across several pages; leave it off when anonymous conversation text should not survive a navigation at all.
+
 Give every business action a portable `tool(..., { title: "Complete task", description: "This will mark the task complete for everyone.", input: z.object({ task: z.string().meta({ title: "Task" }) }) })` title. The standard confirmation uses the tool title/description plus schema field `title`, `description`, and `format`; it shows Confirm and Don't proceed and keeps technical action details secondary. `behavior.showConfirmationDetails` defaults to `true`; set it to `false` to remove only the built-in card's Additional details disclosure and connector mechanics. The business review and decisions remain, `confirm: true` still suspends until acceptance, and headless/BYO `data-confirmation` stays unchanged. Do not put JSON or implementation names in business-facing copy.
 
 ## Configure and deploy