@noodleseed/agent-kit 0.68.0 → 0.70.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@noodleseed/agent-kit",
-  "version": "0.68.0",
+  "version": "0.70.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.68.0 hash:13ddce01769caae4 -->
+<!-- noodle-skill version:0.70.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.68.0 hash:11523cb33b9473c0 -->
+<!-- noodle-skill version:0.70.0 hash:11523cb33b9473c0 -->
 
 # 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.68.0 hash:9fd67d4d24328e15 -->
+<!-- noodle-skill version:0.70.0 hash:9fd67d4d24328e15 -->
 
 # 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.68.0 hash:21bbd3ec441ffd30 -->
+<!-- noodle-skill version:0.70.0 hash:21bbd3ec441ffd30 -->
 
 # 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.68.0 hash:0fa48a82fe836cf0 -->
+<!-- noodle-skill version:0.70.0 hash:0fa48a82fe836cf0 -->
 
 # 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.68.0 hash:aa715bae12041d7c -->
+<!-- noodle-skill version:0.70.0 hash:aa715bae12041d7c -->
 
 # 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.68.0 hash:93e735b7ffb45df1 -->
+<!-- noodle-skill version:0.70.0 hash:93e735b7ffb45df1 -->
 
 # 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.68.0 hash:78a6f181b61f92f1 -->
+<!-- noodle-skill version:0.70.0 hash:78a6f181b61f92f1 -->
 
 # 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.68.0 hash:cc54a67f21c0ecdb -->
+<!-- noodle-skill version:0.70.0 hash:cc54a67f21c0ecdb -->
 
 # embedding-mcp-assistants
 

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

@@ -28,7 +28,7 @@ There is no second tool set and no second app — one `server.ts`, projected ont
 and closed by default: a tool added to this server later is unreachable from the website until someone
 lists it. A tool that needed a signed-in user could not be listed here at all (the compiler rejects it);
 serve those from `authenticatedWebsite({ origins })` instead, where Acme's own backend proves who the
-visitor is. Mid-conversation sign-in on a public surface is not available yet.
+visitor is, or add `signIn: true` so visitors sign in mid-conversation through Acme own login.
 
 ## Design spec (write this before the code)
 

package/skills/claude-code/examples/acme-discovery/src/knowledge/faq.txt

@@ -0,0 +1,10 @@
+ACME GETAWAYS FAQ
+
+Q: Does the assistant book and take payment?
+A: No. The assistant shapes the trip and hands off to Acmes own checkout with a signed link.
+
+Q: How current are prices?
+A: Starting prices come from Acmes live site; the assistant cites the page it used.
+
+Q: Can I compare destinations?
+A: Yes, ask for a shortlist by vibe, month, or budget.

package/skills/claude-code/examples/acme-discovery/src/knowledge/product.md

@@ -0,0 +1,7 @@
+# Acme Getaways product guide
+
+Acme Getaways curates four destination types: beach, mountains, culture, and city escapes. Every listing shows a real starting price and the best months to travel. Bookings, payments, and date selection happen on Acmes own site through a signed handoff link; the assistant never takes payment details.
+
+## Cancellation and support
+
+All trips can be cancelled free within 48 hours of the handoff. Support runs seven days a week through the chat on book.acme.example.

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

@@ -1,10 +1,13 @@
 import {
   annotations,
   embeddedAssistant,
+  file,
+  knowledge,
   openAICompatible,
   publicWebsite,
   secret,
   server,
+  site,
   tool,
   variable,
   z,
@@ -196,6 +199,27 @@ const shortlistGetaway = tool('shortlist_getaway', {
   }),
 });
 
+// Grounding beyond the catalog: two controlled files answer policy/pricing/support questions with
+// citations, and Acme's live public site stays current through its search provider — no sync job,
+// no handwritten search tool. One declaration, one generated `search_destinations` capability.
+const destinations = knowledge('destinations', {
+  title: 'Acme Getaways destinations',
+  description: 'Public destination, pricing, cancellation, and support information.',
+  documents: [
+    file('./knowledge/product.md', {
+      title: 'Product guide',
+      sourceUrl: 'https://getaways.acme.example/product',
+    }),
+    file('./knowledge/faq.txt', { title: 'FAQ' }),
+  ],
+  sites: [
+    site({
+      origin: 'https://getaways.acme.example',
+      include: ['/destinations/**', '/pricing', '/support'],
+    }),
+  ],
+});
+
 export default server(
   'acme_discovery',
   {
@@ -217,7 +241,8 @@ export default server(
     // The same three tools also serve Acme's own marketing site, with no second tool set and no
     // session backend: a visitor with no account gets the discovery carousel and the booking
     // handoff. `capabilities` is the whole externally reachable surface — short enough to review in
-    // one glance, and closed by default when a tool is added to the server later.
+    // one glance, and closed by default when a tool is added to the server later. The knowledge
+    // component projects its generated search capability the same way a tool does.
     assistant: embeddedAssistant({
       model: openAICompatible({
         baseUrl: variable('ASSISTANT_MODEL_BASE_URL'),
@@ -226,11 +251,12 @@ export default server(
       }),
       access: publicWebsite({
         origins: ['https://getaways.acme.example'],
-        capabilities: [discoverGetaways, createHandoff, shortlistGetaway],
+        capabilities: [destinations, discoverGetaways, createHandoff, shortlistGetaway],
       }),
       layout: { mode: 'floating', position: 'bottom-right' },
       labels: { welcomeHeading: 'Where would you like to go?' },
     }),
+    knowledge: [destinations],
   },
   [discoverGetaways, createHandoff, shortlistGetaway],
 );

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

@@ -21,4 +21,14 @@ describe('acme-discovery example', () => {
     expect(text).toContain('create_handoff');
     expect(text).toContain('shortlist_getaway');
   });
+
+  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
+    // generated `search_destinations` capability with citations.
+    expect(manifest.server.knowledge).toHaveLength(1);
+    const text = JSON.stringify(manifest);
+    expect(text).toContain('knowledge/product.md');
+    expect(text).toContain('https://getaways.acme.example');
+  });
 });

package/skills/claude-code/examples/food-ordering/README.md

@@ -3,7 +3,7 @@
 **Owns:** The flagship consumer ordering MCP App example: React view authoring, app-only helper tools,
 caller-scoped cart state handles, invocation context, model-visible widget state/lifecycle, packaged image
 assets, portable structured elicitation, checkout handoff policy, host actions, CSP/permissions metadata,
-and widget preview coverage.
+product-agent guidance, host-neutral distribution metadata, and widget preview coverage.
 
 Food Ordering is a generic, synthetic version of a live marketplace ordering app. It lets a user search
 stores, browse menus, customize an item, build a multi-line cart, review the order, and hand off checkout to
@@ -15,6 +15,7 @@ private customer data.
 | Capability | Example |
 | :--- | :--- |
 | Public entry tool | `open_ordering` returns structured fallback content and renders the React widget |
+| Product and distribution projections | `agentGuide` supplies grounded cross-capability guidance; `distribution` supplies listing, publisher, legal, image, and review facts separately from the runtime manifest |
 | App-only helper tools | `search_stores`, `load_menu`, `load_item`, `read_cart`, `sync_cart`, `prepare_checkout`; mutating widget-owned helpers use `confirm: false` (equivalent to omission) and execute directly because action hints alone never gate |
 | Durable cart state | `server(..., { state: { handles: { cart } }, use: { state } })` with caller scope and revision checks |
 | React app runtime kit | `@noodleseed/one/react` supplies app flow, shell/nav/view, async state, form, quantity, choice, and handoff primitives |
@@ -47,6 +48,11 @@ noodle test
 noodle dev
 ```
 
+The same `server.ts` declares `distribution` metadata for host adapters. It references real packaged images
+and keeps listing copy, support/legal URLs, and positive/negative review scenarios outside the canonical App
+Package and Runtime Artifact. Explicit OpenAI and Claude adapters project those facts with the generated
+product skill; installable plugin archives and directory-submission dossiers remain separate outputs.
+
 In another terminal:
 
 ```sh
@@ -71,6 +77,65 @@ For Apps metadata conformance, start `noodle dev`, copy the loopback MCP endpoin
 npx @mcpjam/cli@latest apps conformance --url http://127.0.0.1:<port>/o/demo/food-ordering/mcp --quiet --format json
 ```
 
+## Export an OpenAI plugin
+
+This flagship includes the guided workflows, listing metadata, review cases, and image assets needed to test
+OpenAI export. See the public [product-agent guide](https://docs.noodleseed.dev/docs/guides/product-agent-guides#export-an-openai-package)
+for the current package workflow and boundaries.
+
+Against its deployed MCP URL, generate the Food Ordering submission candidate with:
+
+```sh
+noodle export plugin openai \
+  --state submission \
+  --mcp-url https://food-ordering.noodleseed.app/mcp \
+  --category "Food & Drink" \
+  --output food-ordering-openai.zip
+```
+
+Extract `food-ordering-openai.zip` before using the portal. Upload
+`submission/chatgpt-app-submission.json` to the Codex-assisted import field and
+`submission/food-ordering-skill.zip` to **With MCP → Skills**. The outer ZIP is the complete review kit and
+is not itself a valid skill upload; `submission/README.md` repeats the portal steps.
+
+After registering that same URL in ChatGPT developer mode, substitute its real technical ID to generate the
+Food Ordering local test package:
+
+```sh
+noodle export plugin openai \
+  --state local \
+  --mcp-url https://food-ordering.noodleseed.app/mcp \
+  --category "Food & Drink" \
+  --registered-app-id plugin_asdk_app_0123456789abcdef0123456789abcdef \
+  --output food-ordering-openai-local.zip
+```
+
+## Export for Claude
+
+Claude Code plugin packaging and Anthropic Connector Directory review are separate outputs. Generate the
+installable plugin repository with:
+
+```sh
+noodle export plugin claude \
+  --mcp-url https://food-ordering.noodleseed.app/mcp \
+  --output food-ordering-claude.zip
+```
+
+Generate the credential-free operator dossier for the remote Connector Directory with:
+
+```sh
+noodle export connector claude \
+  --mcp-url https://food-ordering.noodleseed.app/mcp \
+  --auth none \
+  --category "Food & Drink" \
+  --output food-ordering-anthropic-connector.zip
+```
+
+The dossier is deliberately marked `portalUploadable: false`: it gathers the listing, tool annotations,
+use cases, allowed-link candidates, test-account guidance, and MCP App screenshot evidence, but a human must
+verify ownership/compliance and enter the final answers in Anthropic's portal. The plugin ZIP does not
+contain this dossier.
+
 ## Client Setup
 
 Use the CLI to print the exact setup flow for your MCP client:
@@ -95,17 +160,21 @@ connector secrets and does not include tokens, caller-key mechanisms, or `.env.n
 
 ## Demo Assets
 
-The packaged demo images live under `assets/` and are public web assets when deployed. The current app uses
-`assets/noodle-bowl.jpg` as the server branding image.
+The packaged demo images live under `assets/`. The current app uses `assets/noodle-bowl.jpg` as the server
+branding image. Its three distribution screenshots are real, response-only MCP App captures from Noodle
+Devtools at 2× device scale; each is 1640×970 PNG and has the producing user prompt next to its `asset(...)`
+reference in `server.ts`.
 
 Image sources:
 
 - `assets/noodle-bowl.jpg` — Unsplash photo
   [`IRv8V9Hb8gI`](https://unsplash.com/photos/IRv8V9Hb8gI), downloaded from Unsplash.
-- `assets/lentil-soup.jpg` — Unsplash image
-  [`photo-1510431198580-7727c9fa1e3a`](https://images.unsplash.com/photo-1510431198580-7727c9fa1e3a), downloaded from Unsplash.
-- `assets/mint-lemonade.jpg` — Unsplash photo
-  [`X7Nx327NtuA`](https://unsplash.com/photos/X7Nx327NtuA) by Imad 786.
-
-Unsplash photos are free to use under the [Unsplash License](https://unsplash.com/license); attribution is
-not required, but source notes are kept here for provenance.
+- `assets/food-ordering-stores.png` — store-discovery state produced by “Help me build a noodle order for
+  pickup.”
+- `assets/food-ordering-menu.png` — Harbor Noodles menu state produced by “Show me the Harbor Noodles
+  menu.”
+- `assets/food-ordering-handoff.png` — checkout-handoff state produced by “Review my spicy miso bowl order
+  before checkout.”
+
+The Unsplash branding photo is free to use under the [Unsplash License](https://unsplash.com/license);
+attribution is not required, but the source note is kept here for provenance.

package/skills/claude-code/examples/food-ordering/src/agent-guide.ts

@@ -0,0 +1,48 @@
+import type { AgentGuideSource } from '@noodleseed/one';
+
+/** Product guidance for the model-visible ordering and planning workflows. */
+export const FOOD_ORDERING_AGENT_GUIDE = {
+  description:
+    'Use Food Ordering to browse synthetic local options, build a reviewable cart, and hand checkout to the user.',
+  useWhen: [
+    'The user wants to browse nearby food or assemble an order.',
+    'The user wants a structured pickup or delivery plan before ordering.',
+  ],
+  workflows: [
+    {
+      id: 'build_order',
+      title: 'Browse and build an order',
+      steps: [
+        {
+          capability: { kind: 'tool', name: 'open_ordering' },
+          guidance:
+            'Open the ordering app so the user can choose a store, review the cart, and control checkout handoff.',
+        },
+      ],
+    },
+    {
+      id: 'summarize_options',
+      title: 'Summarize available options',
+      steps: [{ capability: { kind: 'tool', name: 'summarize_ordering_options' } }],
+    },
+    {
+      id: 'plan_fulfilment',
+      title: 'Plan pickup or delivery',
+      steps: [
+        {
+          capability: { kind: 'tool', name: 'plan_order' },
+          guidance: 'Collect the user’s fulfilment preference without claiming to place an order.',
+        },
+      ],
+    },
+  ],
+  boundaries: [
+    'Treat every store, menu item, price, and service area in this example as synthetic.',
+    'Never claim checkout or payment completed; the final order happens only after the external handoff.',
+  ],
+  examples: [
+    { prompt: 'Help me put together a noodle order.', workflow: 'build_order' },
+    { prompt: 'What food options are available?', workflow: 'summarize_options' },
+    { prompt: 'Plan a delivery for Friday.', workflow: 'plan_fulfilment' },
+  ],
+} as const satisfies AgentGuideSource;

package/skills/claude-code/examples/food-ordering/src/server.ts

@@ -1,6 +1,10 @@
 import { annotations, asset, connector, resource, server, tool, z } from '@noodleseed/one';
+import { FOOD_ORDERING_AGENT_GUIDE } from './agent-guide.js';
 
 const heroImage = asset('assets/noodle-bowl.jpg');
+const storesScreenshot = asset('assets/food-ordering-stores.png');
+const menuScreenshot = asset('assets/food-ordering-menu.png');
+const handoffScreenshot = asset('assets/food-ordering-handoff.png');
 
 const state = connector('noodle_state')
   .version('1.0.0')
@@ -202,6 +206,108 @@ export default server(
   {
     title: 'Food Ordering',
     version: '1.0.0',
+    agentGuide: FOOD_ORDERING_AGENT_GUIDE,
+    distribution: {
+      listing: {
+        summary: 'Build a pickup noodle order.',
+        description:
+          'Food Ordering is a synthetic MCP App that demonstrates store discovery, menu browsing, a caller-scoped cart, fulfilment planning, and explicit checkout handoff.',
+        keywords: ['food', 'ordering', 'delivery'],
+      },
+      publisher: {
+        name: 'Noodle Seed Examples',
+        websiteUrl: 'https://noodleseed.com',
+      },
+      support: {
+        documentationUrl: 'https://docs.noodleseed.com/examples/food-ordering',
+        supportUrl: 'https://noodleseed.com/support',
+      },
+      legal: {
+        privacyPolicyUrl: 'https://noodleseed.com/privacy',
+        termsOfServiceUrl: 'https://noodleseed.com/terms',
+      },
+      assets: {
+        icon: { source: heroImage, alt: 'Food Ordering noodle bowl' },
+        screenshots: [
+          {
+            source: storesScreenshot,
+            alt: 'Food Ordering MCP App showing nearby stores',
+            prompt: 'Help me build a noodle order for pickup.',
+          },
+          {
+            source: menuScreenshot,
+            alt: 'Food Ordering MCP App showing the Harbor Noodles menu',
+            prompt: 'Show me the Harbor Noodles menu.',
+          },
+          {
+            source: handoffScreenshot,
+            alt: 'Food Ordering MCP App reviewing a checkout handoff',
+            prompt: 'Review my spicy miso bowl order before checkout.',
+          },
+        ],
+      },
+      review: {
+        instructions:
+          'Use the synthetic menu and guest cart. No account or reviewer credential is required.',
+        scenarios: [
+          {
+            id: 'build_order',
+            prompt: 'Help me build a noodle order for pickup.',
+            expected:
+              'The ordering app opens with stores and menu items; checkout remains a handoff.',
+            shouldInvoke: true,
+            tools: ['open_ordering'],
+          },
+          {
+            id: 'browse_menu',
+            prompt: 'Show me vegetarian menu options nearby.',
+            expected: 'The app shows matching stores and bounded menu choices.',
+            shouldInvoke: true,
+            tools: ['search_stores', 'load_menu'],
+          },
+          {
+            id: 'compare_options',
+            prompt: 'Compare the quickest open food options for me.',
+            expected: 'The app grounds its comparison in the synthetic store data.',
+            shouldInvoke: true,
+            tools: ['search_stores', 'summarize_ordering_options'],
+          },
+          {
+            id: 'plan_pickup',
+            prompt: 'Plan a pickup order for Friday.',
+            expected: 'The app collects the missing fulfilment details before planning the order.',
+            shouldInvoke: true,
+            tools: ['plan_order'],
+          },
+          {
+            id: 'review_checkout',
+            prompt: 'Review my cart before I continue to checkout.',
+            expected: 'The app shows the cart and keeps payment on the explicit external handoff.',
+            shouldInvoke: true,
+            tools: ['read_cart', 'prepare_checkout'],
+          },
+          // Negative scenarios are non-invocation cases, so they never declare expected tools.
+          {
+            id: 'unrelated_weather',
+            prompt: 'Will it rain tomorrow?',
+            expected: 'Food Ordering is not invoked.',
+            shouldInvoke: false,
+          },
+          {
+            id: 'unrelated_email',
+            prompt: 'Draft an email to my manager.',
+            expected: 'Food Ordering is not invoked.',
+            shouldInvoke: false,
+          },
+          {
+            id: 'unrelated_travel',
+            prompt: 'Book me a flight to Lisbon.',
+            expected: 'Food Ordering is not invoked.',
+            shouldInvoke: false,
+          },
+        ],
+      },
+    },
     use: { state },
     context: {
       defaults: { locale: 'en-US', timeZone: 'America/New_York' },
@@ -287,6 +393,7 @@ export default server(
       permissions: { clipboardWrite: {} },
     }),
     tool('search_stores', {
+      title: 'Search stores',
       visibility: ['app'],
       description: 'Filter synthetic restaurants for the ordering widget.',
       annotations: readOnly,
@@ -298,6 +405,7 @@ export default server(
       fulfil: () => ({ stores }),
     }),
     tool('load_menu', {
+      title: 'Load store menu',
       visibility: ['app'],
       description: 'Load synthetic menu categories and items for one store.',
       annotations: readOnly,
@@ -310,6 +418,7 @@ export default server(
       fulfil: ({ input }) => ({ storeId: input.storeId, stores, items: menu }),
     }),
     tool('load_item', {
+      title: 'Load menu item',
       visibility: ['app'],
       description: 'Load item details and modifier options for the ordering widget.',
       annotations: readOnly,
@@ -318,6 +427,7 @@ export default server(
       fulfil: ({ input }) => ({ itemId: input.itemId, items: menu }),
     }),
     tool('read_cart', {
+      title: 'Read ordering cart',
       visibility: ['app'],
       description: 'Read the caller-scoped ordering cart state.',
       annotations: readOnly,
@@ -333,6 +443,7 @@ export default server(
       },
     }),
     tool('sync_cart', {
+      title: 'Update ordering cart',
       visibility: ['app'],
       description: 'Patch the caller-scoped ordering cart with the widget cart mirror.',
       annotations: action,
@@ -353,6 +464,7 @@ export default server(
       },
     }),
     tool('prepare_checkout', {
+      title: 'Prepare checkout handoff',
       visibility: ['app'],
       description: 'Prepare the caller-scoped cart for checkout handoff.',
       annotations: action,

package/skills/claude-code/examples/food-ordering/test/server.test.ts

@@ -10,6 +10,7 @@ describe('food-ordering example', () => {
     const manifest = (await app.toManifest()) as {
       server: {
         name: string;
+        agentGuide?: unknown;
         context?: {
           defaults?: { locale?: string; timeZone?: string };
           ambient?: {
@@ -23,6 +24,7 @@ describe('food-ordering example', () => {
       connectors?: Record<string, { id: string; version: string }>;
       tools: Array<{
         name: string;
+        title?: string;
         visibility?: string[];
         annotations?: Record<string, unknown>;
         output?: unknown;
@@ -36,6 +38,8 @@ describe('food-ordering example', () => {
     };
 
     expect(manifest.server.name).toBe('food_ordering');
+    expect(manifest.server.agentGuide).toBeDefined();
+    expect(manifest.server).not.toHaveProperty('distribution');
     expect(manifest.server.context).toMatchObject({
       defaults: { locale: 'en-US', timeZone: 'America/New_York' },
       ambient: {
@@ -100,5 +104,49 @@ describe('food-ordering example', () => {
       },
     });
     expect(manifest.widgets?.map((widget) => widget.name)).toContain('capabilities_card');
+    expect(manifest.tools.every((tool) => typeof tool.title === 'string')).toBe(true);
+  });
+
+  it('projects host distribution metadata separately from the runtime manifest', () => {
+    const distribution = app.toDistributionMetadata();
+    expect(distribution).toMatchObject({
+      schemaVersion: 1,
+      listing: { summary: expect.stringContaining('Browse local food') },
+      assets: {
+        icon: { alt: 'Food Ordering noodle bowl' },
+        screenshots: [
+          expect.objectContaining({
+            alt: 'Food Ordering MCP App showing nearby stores',
+            prompt: 'Help me build a noodle order for pickup.',
+          }),
+          expect.objectContaining({
+            alt: 'Food Ordering MCP App showing the Harbor Noodles menu',
+            prompt: 'Show me the Harbor Noodles menu.',
+          }),
+          expect.objectContaining({
+            alt: 'Food Ordering MCP App reviewing a checkout handoff',
+            prompt: 'Review my spicy miso bowl order before checkout.',
+          }),
+        ],
+      },
+    });
+    const scenarios = distribution?.review.scenarios ?? [];
+    expect(scenarios.filter(({ shouldInvoke }) => shouldInvoke).map(({ id }) => id)).toEqual([
+      'build_order',
+      'browse_menu',
+      'compare_options',
+      'plan_pickup',
+      'review_checkout',
+    ]);
+    expect(scenarios.filter(({ shouldInvoke }) => !shouldInvoke).map(({ id }) => id)).toEqual([
+      'unrelated_weather',
+      'unrelated_email',
+      'unrelated_travel',
+    ]);
+    expect(
+      scenarios
+        .filter(({ shouldInvoke }) => !shouldInvoke)
+        .every((scenario) => !('tools' in scenario)),
+    ).toBe(true);
   });
 });

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.68.0 hash:6a9f132ddb79352e -->
+<!-- noodle-skill version:0.70.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.68.0 hash:efffbf82007f935d -->
+<!-- noodle-skill version:0.70.0 hash:efffbf82007f935d -->
 
 # publishing-mcp-integrations