@noodleseed/agent-kit 0.63.1 → 0.65.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@noodleseed/agent-kit",
-  "version": "0.63.1",
+  "version": "0.65.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.63.1 hash:88e3ae21d02f2fe7 -->
+<!-- noodle-skill version:0.65.0 hash:7732a64aac011333 -->
 
 # Noodle Seed
 
@@ -56,7 +56,7 @@ Inside the installed plugin, perform mapped steps with `noodle-readiness` tools
 This is a lookup catalog, not a discovery checklist. Return here only when the selected primary route names a missing technical detail:
 
 - `references/agent-contract.md` — the `--json` envelope, exit codes, and the three output modes.
-- `references/product-agent-guides.md` — author one host-neutral guide for a product MCP surface.
+- `references/product-agent-guides.md` — decide whether a product needs one host-neutral guide, then author it when selected.
 - `references/sdk-surface.md` — what to import from `@noodleseed/one` and which builder to use.
 - `references/cli-commands.md` — every `noodle` command, grouped by area.
 - `references/compile-errors.md` — fix `noodle validate` errors by code.

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.63.1 hash:0b2fd8c7e43fc69f -->
+<!-- noodle-skill version:0.65.0 hash:11523cb33b9473c0 -->
 
 # authoring-mcp-servers
 
@@ -33,7 +33,7 @@ Load `references/sdk-surface.md` at `../noodle-seed/references/sdk-surface.md` o
 
 ## Verification evidence
 
-The TypeScript behavior validates and passes local smoke; connector reads also have real-output proof.
+The TypeScript behavior and explicit product-guide decision validate and pass local smoke; connector reads also have real-output proof.
 
 ## Recovery paths
 

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.63.1 hash:f7fa54992c8d7692 -->
+<!-- noodle-skill version:0.65.0 hash:9fd67d4d24328e15 -->
 
 # building-mcp-apps
 
@@ -33,7 +33,7 @@ Load `references/widgets-and-apps.md` at `../noodle-seed/references/widgets-and-
 
 ## Verification evidence
 
-The App passes validation, local smoke, app checks, and the requested preview or host evidence level.
+The App records its product-guide decision and passes validation, local smoke, app checks, and the requested preview or host evidence level.
 
 ## Recovery paths
 

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.63.1 hash:21bbd3ec441ffd30 -->
+<!-- noodle-skill version:0.65.0 hash:21bbd3ec441ffd30 -->
 
 # connecting-apis-to-mcp
 

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.63.1 hash:aa715bae12041d7c -->
+<!-- noodle-skill version:0.65.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.63.1 hash:93e735b7ffb45df1 -->
+<!-- noodle-skill version:0.65.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.63.1 hash:76cce86729cffbee -->
+<!-- noodle-skill version:0.65.0 hash:78a6f181b61f92f1 -->
 
 # designing-mcp-products
 
@@ -32,7 +32,7 @@ Load `references/authoring-workflow.md` at `../noodle-seed/references/authoring-
 
 ## Verification evidence
 
-A bounded product contract states user benefit, model boundary, interaction, fallback, risks, and next implementation skill.
+A bounded product contract states user benefit, model boundary, interaction, fallback, product-guide decision, risks, and next implementation skill.
 
 ## Recovery paths
 

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.63.1 hash:cc54a67f21c0ecdb -->
+<!-- noodle-skill version:0.65.0 hash:cc54a67f21c0ecdb -->
 
 # embedding-mcp-assistants
 

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

@@ -7,9 +7,28 @@ 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`, 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.
+handoff with attribution, `handoff.allowedDomains`, the **public website assistant surface**, 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.
+
+## The same tools on Acme's own website
+
+The funnel does not only start in ChatGPT. The `assistant` block projects these same three tools onto
+Acme's marketing site for a visitor with **no account and no session backend**:
+
+```ts
+access: publicWebsite({
+  origins: ['https://getaways.acme.example'],
+  capabilities: [discoverGetaways, createHandoff, shortlistGetaway],
+}),
+```
+
+There is no second tool set and no second app — one `server.ts`, projected onto another front door.
+`capabilities` is the entire externally reachable surface, so it stays short enough to review at a glance
+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);
+serving those to visitors means `publicWebsite({ ..., signIn: true })`, which lets a visitor sign in
+mid-conversation through Acme's own login.
 
 ## Design spec (write this before the code)
 

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

@@ -1,4 +1,14 @@
-import { annotations, server, tool, z } from '@noodleseed/one';
+import {
+  annotations,
+  embeddedAssistant,
+  openAICompatible,
+  publicWebsite,
+  secret,
+  server,
+  tool,
+  variable,
+  z,
+} from '@noodleseed/one';
 
 // Acme Getaways is a fictional travel brand. This app is deliberately top-of-funnel: discovery and
 // configuration happen inside ChatGPT; the booking/transaction happens off-app on Acme's own site,
@@ -95,6 +105,97 @@ const destinationOutput = z.object({
   why: z.string(),
 });
 
+const discoverGetaways = tool('discover_getaways', {
+  title: 'Discover getaways',
+  description:
+    'Suggest Acme Getaways destinations for a vibe and month and render a discovery carousel.',
+  annotations: readOnly,
+  input: discoverInput,
+  output: z.object({
+    status: z.string(),
+    vibe: z.string(),
+    month: z.string(),
+    travelers: z.number(),
+    // Bounded list: the curated catalog is fixed and small, and the declared ceiling tells the
+    // model and host the payload cannot grow. `noodle check` reports `tool_design_output_bounds`.
+    options: z.array(destinationOutput).max(20),
+  }),
+  // The carousel presents Acme's curated catalog; the model narrates which fit the stated vibe.
+  // (A tool cannot filter on an input value — that is connector/flow work — so all are returned.)
+  fulfil: ({ input }) => ({
+    status: `Acme Getaways for a ${input.vibe} trip in ${input.month}, ${input.travelers} traveler(s).`,
+    vibe: input.vibe,
+    month: input.month,
+    travelers: input.travelers,
+    options: catalog,
+  }),
+  viewTitle: 'Discover getaways',
+  // ChatGPT host status copy (openai/toolInvocation/*) — required for widget-opening tools.
+  invoking: 'Finding getaways…',
+  invoked: 'Getaways ready',
+  domain: 'https://getaways.acme.example',
+  view: {
+    component: 'discovery-carousel',
+    entry: './views/discovery-carousel.tsx',
+  },
+  viewDescription:
+    'A top-of-funnel discovery carousel: pick a destination, then hand off to Acme to book.',
+  csp: {
+    connectDomains: ['https://acme.example'],
+    resourceDomains: ['https://acme.example'],
+    frameDomains: ['https://acme.example'],
+  },
+});
+
+const createHandoff = tool('create_handoff', {
+  title: 'Create booking handoff',
+  description:
+    'Create the Acme booking deep link for a chosen destination, carrying the configured trip. ' +
+    'Pass the destination id (url-safe slug, e.g. "coral_bay") and its display name.',
+  annotations: openLink,
+  input: z.object({
+    destination: destinationId,
+    destinationName: z.string().min(1),
+    month: monthEnum,
+    travelers: z.number().int().min(1).default(2),
+  }),
+  output: z.object({
+    status: z.string(),
+    destination: z.string(),
+    summary: z.string(),
+    handoffUrl: z.string(),
+  }),
+  // Inline the inputs directly so they substitute at runtime; every value is already url-safe
+  // (id slug, month enum, integer), and `src=chatgpt` is the attribution the partner measures
+  // ChatGPT-sourced conversions on.
+  fulfil: ({ input }) => ({
+    status: `Ready to continue on Acme for ${input.destinationName}.`,
+    destination: input.destination,
+    summary: `${input.destinationName} · ${input.month} · ${input.travelers} traveler(s)`,
+    handoffUrl: `https://book.acme.example/plan?dest=${input.destination}&month=${input.month}&pax=${input.travelers}&src=chatgpt`,
+  }),
+});
+
+const shortlistGetaway = tool('shortlist_getaway', {
+  visibility: ['app'],
+  description: 'Record the traveler’s shortlisted destination from the discovery widget.',
+  annotations: localWrite,
+  input: z.object({
+    destination: z.string(),
+    note: z.string().default(''),
+  }),
+  output: z.object({
+    status: z.string(),
+    destination: z.string(),
+    note: z.string(),
+  }),
+  fulfil: ({ input }) => ({
+    status: `Shortlisted ${input.destination}.`,
+    destination: input.destination,
+    note: input.note,
+  }),
+});
+
 export default server(
   'acme_discovery',
   {
@@ -113,95 +214,23 @@ export default server(
     handoff: {
       allowedDomains: ['https://book.acme.example', 'https://acme.example'],
     },
-  },
-  [
-    tool('discover_getaways', {
-      title: 'Discover getaways',
-      description:
-        'Suggest Acme Getaways destinations for a vibe and month and render a discovery carousel.',
-      annotations: readOnly,
-      input: discoverInput,
-      output: z.object({
-        status: z.string(),
-        vibe: z.string(),
-        month: z.string(),
-        travelers: z.number(),
-        // Bounded list: the curated catalog is fixed and small, and the declared ceiling tells the
-        // model and host the payload cannot grow. `noodle check` reports `tool_design_output_bounds`.
-        options: z.array(destinationOutput).max(20),
+    // 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.
+    assistant: embeddedAssistant({
+      model: openAICompatible({
+        baseUrl: variable('ASSISTANT_MODEL_BASE_URL'),
+        model: variable('ASSISTANT_MODEL'),
+        apiKey: secret('ASSISTANT_MODEL_API_KEY'),
       }),
-      // The carousel presents Acme's curated catalog; the model narrates which fit the stated vibe.
-      // (A tool cannot filter on an input value — that is connector/flow work — so all are returned.)
-      fulfil: ({ input }) => ({
-        status: `Acme Getaways for a ${input.vibe} trip in ${input.month}, ${input.travelers} traveler(s).`,
-        vibe: input.vibe,
-        month: input.month,
-        travelers: input.travelers,
-        options: catalog,
+      access: publicWebsite({
+        origins: ['https://getaways.acme.example'],
+        capabilities: [discoverGetaways, createHandoff, shortlistGetaway],
       }),
-      viewTitle: 'Discover getaways',
-      // ChatGPT host status copy (openai/toolInvocation/*) — required for widget-opening tools.
-      invoking: 'Finding getaways…',
-      invoked: 'Getaways ready',
-      domain: 'https://getaways.acme.example',
-      view: {
-        component: 'discovery-carousel',
-        entry: './views/discovery-carousel.tsx',
-      },
-      viewDescription:
-        'A top-of-funnel discovery carousel: pick a destination, then hand off to Acme to book.',
-      csp: {
-        connectDomains: ['https://acme.example'],
-        resourceDomains: ['https://acme.example'],
-        frameDomains: ['https://acme.example'],
-      },
+      layout: { mode: 'floating', position: 'bottom-right' },
+      labels: { welcomeHeading: 'Where would you like to go?' },
     }),
-    tool('create_handoff', {
-      title: 'Create booking handoff',
-      description:
-        'Create the Acme booking deep link for a chosen destination, carrying the configured trip. ' +
-        'Pass the destination id (url-safe slug, e.g. "coral_bay") and its display name.',
-      annotations: openLink,
-      input: z.object({
-        destination: destinationId,
-        destinationName: z.string().min(1),
-        month: monthEnum,
-        travelers: z.number().int().min(1).default(2),
-      }),
-      output: z.object({
-        status: z.string(),
-        destination: z.string(),
-        summary: z.string(),
-        handoffUrl: z.string(),
-      }),
-      // Inline the inputs directly so they substitute at runtime; every value is already url-safe
-      // (id slug, month enum, integer), and `src=chatgpt` is the attribution the partner measures
-      // ChatGPT-sourced conversions on.
-      fulfil: ({ input }) => ({
-        status: `Ready to continue on Acme for ${input.destinationName}.`,
-        destination: input.destination,
-        summary: `${input.destinationName} · ${input.month} · ${input.travelers} traveler(s)`,
-        handoffUrl: `https://book.acme.example/plan?dest=${input.destination}&month=${input.month}&pax=${input.travelers}&src=chatgpt`,
-      }),
-    }),
-    tool('shortlist_getaway', {
-      visibility: ['app'],
-      description: 'Record the traveler’s shortlisted destination from the discovery widget.',
-      annotations: localWrite,
-      input: z.object({
-        destination: z.string(),
-        note: z.string().default(''),
-      }),
-      output: z.object({
-        status: z.string(),
-        destination: z.string(),
-        note: z.string(),
-      }),
-      fulfil: ({ input }) => ({
-        status: `Shortlisted ${input.destination}.`,
-        destination: input.destination,
-        note: input.note,
-      }),
-    }),
-  ],
+  },
+  [discoverGetaways, createHandoff, shortlistGetaway],
 );

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

@@ -82,8 +82,9 @@ noodle open
 
 ## Optional in-product assistant
 
-The same task tools can also sit inside Acme's authenticated web app. Add an `assistant` option to this
-server without creating a second tool set:
+The default SaaS and widget scaffolds are credential-free. When the product deliberately includes an
+assistant, use the existing server tools and add an `assistant` option to the same `server.ts` instead of
+creating a second entrypoint or tool set:
 
 ```ts
 assistant: embeddedAssistant({

package/skills/claude-code/examples/customer-auth/src/server.ts

@@ -1,5 +1,6 @@
 import {
   annotations,
+  authenticatedWebsite,
   connector,
   customerAuth,
   customerEndpoint,
@@ -113,11 +114,13 @@ export default server(
         apiKey: secret('ASSISTANT_MODEL_API_KEY'),
       }),
       // Production origins are exact HTTPS; http://localhost:<port> is allowed for local development.
-      allowedOrigins: [
-        'https://app.noodleseed.com',
-        'https://dev.noodleseed.com',
-        'http://localhost:3000',
-      ],
+      access: authenticatedWebsite({
+        origins: [
+          'https://app.noodleseed.com',
+          'https://dev.noodleseed.com',
+          'http://localhost:3000',
+        ],
+      }),
       layout: { mode: 'floating', position: 'bottom-right', panelWidth: 420 },
       labels: {
         welcomeHeading: 'How can I help with Noodle Seed?',

package/skills/claude-code/examples/weather/README.md

@@ -32,7 +32,8 @@ It exercises, in one TypeScript-authored app:
   to `[]`.
 - **A per-operation transport bound** — `search_list` sets
   `limits: { maxResponseBytes: 256 * 1024 }`, tightening this known-small endpoint below the 1 MiB default.
-  Raise a limit only when representative evidence proves the required raw response is larger.
+  The authoring ceiling is 6 MiB, but grant only the bytes representative evidence proves this operation
+  needs.
 - **Sandboxed compute** (no network/fs/env/clock) turning raw numbers into conditions + advice.
 - **Typed input/output schemas** emitted as JSON Schema 2020-12.
 

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.63.1 hash:6a9f132ddb79352e -->
+<!-- noodle-skill version:0.65.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.63.1 hash:efffbf82007f935d -->
+<!-- noodle-skill version:0.65.0 hash:efffbf82007f935d -->
 
 # publishing-mcp-integrations
 

package/skills/claude-code/references/authoring-workflow.md

@@ -4,6 +4,7 @@
 
 - Input paths
 - Fit check
+- Product-guide decision
 - Repair loop
 - Connectors
 - HTTP connector example (full server)
@@ -28,6 +29,10 @@
 
 Before building, confirm the idea fits a conversational surface: 1–3 focused actions where saying it beats clicking, plus data or actions the model lacks on its own. Poor fits — long-form or static content, dashboards, deep multi-step navigation, or a full app port. When an idea does not fit, narrow the scope to the actions that do.
 
+## Product-guide decision
+
+Before authoring, record whether the product is guided or unguided and why. Do not wait for the user to name `agentGuide`; load `references/product-agent-guides.md` for the canonical decision criteria and TypeScript shape whenever product-level workflow guidance may add value.
+
 ## Repair loop
 
 Author in `server.ts`, then `noodle validate` → fix cited errors (see `compile-errors.md`) → re-validate → `noodle test` → `noodle dev`. Keep the loop tight and error-driven.

package/skills/claude-code/references/build-an-mcp-app.md

@@ -23,14 +23,15 @@ Before implementation, capture a short design spec: target user, conversational
 2. **Agree on the design spec.** Describe the smallest complete experience and its states before writing the component. Avoid recreating a full dashboard or website inside the conversation.
 3. **Define the output boundary.** Keep concise facts and action results model-visible. Put presentation-heavy or interactive widget data in the widget-only channel. The model must not depend on opaque UI state to continue the conversation.
 4. **Preserve fallback.** Every tool that launches a widget must still return useful text without the widget, so unsupported hosts and failed rendering remain usable.
-5. **Author and wire the App contract.** Follow `references/widgets-and-apps.md` for the canonical component guidance, view registration, hooks, state, CSP, tool visibility, and output shaping. Keep tool effects and confirmation semantics correct independently of the UI.
-6. **Validate the local artifact.** Run `noodle validate --json`, `noodle test --json`, and `noodle check --json`. Repair failures at the layer that produced them.
-7. **Inspect the experience.** Run `noodle devtools` and verify loading, empty, error, success, responsive layout, focus/keyboard behavior, and the text fallback.
-8. **Escalate evidence only on request.** Run a host test only when the user requested host verification. Run host-specific compliance only when preparing that host submission; select the exact host-testing or compliance entry from the router lookup catalog only after that evidence level is explicitly requested.
+5. **Decide product-guide coverage.** Record the required product-guide decision and its reason, then use `references/product-agent-guides.md` as the canonical selection and authoring guidance.
+6. **Author and wire the App contract.** Follow `references/widgets-and-apps.md` for the canonical component guidance, view registration, hooks, state, CSP, tool visibility, and output shaping. Keep tool effects and confirmation semantics correct independently of the UI.
+7. **Validate the local artifact.** Run `noodle validate --json`, `noodle test --json`, and `noodle check --json`. Repair failures at the layer that produced them.
+8. **Inspect the experience.** Run `noodle devtools` and verify loading, empty, error, success, responsive layout, focus/keyboard behavior, and the text fallback.
+9. **Escalate evidence only on request.** Run a host test only when the user requested host verification. Run host-specific compliance only when preparing that host submission; select the exact host-testing or compliance entry from the router lookup catalog only after that evidence level is explicitly requested.
 
 ## Verification evidence
 
-- **Product:** the design spec states the user benefit and the UI fit decision.
+- **Product:** the design spec states the user benefit, UI fit decision, and product-guide decision with its reason.
 - **Server:** `noodle validate --json` and `noodle test --json` succeeded.
 - **App contract:** `noodle check --json` succeeded.
 - **Local UX:** `noodle devtools` exercised the relevant states and the useful text fallback without the widget.

package/skills/claude-code/references/build-an-mcp-server.md

@@ -21,19 +21,20 @@ Establish only the inputs needed for the requested stopping point. Follow `refer
 
 1. **Confirm conversational fit.** Name one to three focused jobs where saying the request is easier than navigating the underlying system, and identify the data or action the model cannot provide by itself.
 2. **Define the product contract.** For each job, write the user phrase, the intent-shaped tool or resource, its minimal typed input, the useful output, read/write effect, and backing operation. Design for user intent, not a 1:1 API endpoint wrapper.
-3. **Choose the smallest implementation.** Use native tools, resources, or prompts for local/static behavior; add a connector only when external data or actions are required. Keep response output small and model-readable.
-4. **Author in TypeScript.** Follow `references/authoring-workflow.md` for connector and flow patterns, `references/tool-design.md` for the model-facing tool surface, and `references/sdk-surface.md` for exact builders. These are this route’s complete canonical support set; use the router lookup catalog only when observed evidence names a different concern.
+3. **Decide product-guide coverage.** Record the required product-guide decision and its reason, then use `references/product-agent-guides.md` as the canonical selection and authoring guidance.
+4. **Choose the smallest implementation.** Use native tools, resources, or prompts for local/static behavior; add a connector only when external data or actions are required. Keep response output small and model-readable.
+5. **Author in TypeScript.** Follow `references/authoring-workflow.md` for connector and flow patterns, `references/tool-design.md` for the model-facing tool surface, and `references/sdk-surface.md` for exact builders. These are this route’s complete canonical support set; use the router lookup catalog only when observed evidence names a different concern.
    MCP protocol versions are platform-owned and negotiated automatically at the serving endpoint. Do not add protocol-version settings to server options, `noodle.json`, app manifests, or deployment configuration.
-5. **Validate and repair.** Run `noodle validate --json`. Parse `error.errors[]`, repair the cited `path`, and rerun validation. Consult the lookup catalog only for the specific reported error code; do not open another reference speculatively.
-6. **Run the local smoke.** After validation succeeds, run `noodle test --json` and repair any failure at that evidence layer.
-7. **Prove external behavior.** For connector-backed reads, set credentials through the effective local target and run a safe representative `noodle tools call`. Confirm populated mapped fields from real output, not merely successful registration.
-8. **Stop at the requested boundary.** Do not add an App, host test, hosted environment, publication work, or deployment unless the user requested that outcome. Deploy only when the selected route or the user explicitly requires it.
+6. **Validate and repair.** Run `noodle validate --json`. Parse `error.errors[]`, repair the cited `path`, and rerun validation. Consult the lookup catalog only for the specific reported error code; do not open another reference speculatively.
+7. **Run the local smoke.** After validation succeeds, run `noodle test --json` and repair any failure at that evidence layer.
+8. **Prove external behavior.** For connector-backed reads, set credentials through the effective local target and run a safe representative `noodle tools call`. Confirm populated mapped fields from real output, not merely successful registration.
+9. **Stop at the requested boundary.** Do not add an App, host test, hosted environment, publication work, or deployment unless the user requested that outcome. Deploy only when the selected route or the user explicitly requires it.
 
 ## Verification evidence
 
 Report evidence as a ladder and claim only levels actually exercised:
 
-- **Authoring:** the requested TypeScript behavior exists with typed inputs and outputs.
+- **Authoring:** the requested TypeScript behavior exists with typed inputs and outputs, and the product-guide decision and reason are recorded.
 - **Compilation:** `noodle validate --json` returned success.
 - **Local smoke:** `noodle test --json` returned success.
 - **Connector reality:** a representative safe read via `noodle tools call` returned populated mapped fields. This is required for connector-backed work.

package/skills/claude-code/references/compile-errors.md

@@ -67,6 +67,9 @@ Run `noodle validate` (add `--json` for the machine-readable envelope, `--fix-pr
 | `customer_endpoint_mapping_required` | Add the endpoint key at the cited auth routing path; every direct/federated issuer must map every customer endpoint used by the app. |
 | `customer_endpoint_unknown_mapping` | Remove the unknown or unused auth routing key, or use that exact declared `customerEndpoint` key from a reachable connector operation. |
 | `customer_endpoint_bridge_unsupported` | Replace the Firebase/Microsoft bridge with direct or federated OIDC before using auth-derived customer connector endpoints. |
+| `assistant_capability_unknown` | Name a tool, resource, or prompt this server declares in `embeddedAssistant({ capabilities })`, or remove the entry; capabilities reference declared components, not arbitrary names. |
+| `assistant_public_user_reference` | Remove the `${user...}` reference from this tool or drop it from the public assistant `capabilities`; a public website visitor is anonymous, so there is no signed-in user to read. |
+| `assistant_public_effect_unconfirmed` | Add `annotations.readOnly()` if this projected tool only reads, or `{ confirm: true }` if it causes an external effect; a public assistant never reaches an unconfirmed side effect. |
 | `customer_endpoint_action_unsupported` | Set exact `annotations.confirm: true` on the enclosing tool, or keep the customer-routed operation read-only; action hints alone do not enable confirmation. |
 | `customer_endpoint_surface_unsupported` | Move the customer-routed call into a tool fulfilment; routed resources, prompts, and ambient providers are unsupported. |
 | `customer_endpoint_credential_source_unsupported` | Remove the manifest connection binding; a customer-routed connector uses its declared delegated token exchange auth or no auth. |

package/skills/claude-code/references/connect-an-api.md

@@ -116,12 +116,12 @@ response: { tasks: '${response.items}' },
 HTTP operations default to a 1 MiB decoded-response limit. Narrow the upstream query, paginate, or
 reduce the requested dataset before raising it; a `response` mapping runs only after the raw body is
 buffered. When representative evidence proves one operation legitimately needs more, grant only that
-operation the required bytes, up to the 3 MiB authoring maximum:
+operation the required bytes, up to the 6 MiB authoring maximum:
 
 ```ts
 search: {
   type: 'read', method: 'GET', path: '/search',
-  limits: { maxResponseBytes: 3 * 1024 * 1024 },
+  limits: { maxResponseBytes: 6 * 1024 * 1024 },
   // input / output / response omitted
 },
 ```