@noodleseed/agent-kit 0.40.0 → 0.42.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@noodleseed/agent-kit",
-  "version": "0.40.0",
+  "version": "0.42.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.40.0 hash:2ea7d6dcc8358b35 -->
+<!-- noodle-skill version:0.42.0 hash:0c1ebd532b9c2499 -->
 
 # Noodle Seed
 
@@ -39,7 +39,7 @@ Negative routing examples: “Inspect hosted logs/status” → `inspect-hosted`
 
 ## Common machine loop
 
-The cold-agent commands speak the `--json` envelope. Parse machine state instead of scraping human prose; `references/agent-contract.md` owns the envelope and exit codes.
+Every `--json` command speaks the canonical envelope on stdout. Parse machine state instead of scraping human prose; `references/agent-contract.md` owns the envelope, streaming records, and exit codes.
 
 1. **Discover** — use `noodle commands --json` when the required command or flags are uncertain; don't read CLI source.
 2. **Author** — for build routes, edit the configured TypeScript entrypoint, usually `src/server.ts`.

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.40.0 hash:0b2fd8c7e43fc69f -->
+<!-- noodle-skill version:0.42.0 hash:0b2fd8c7e43fc69f -->
 
 # 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.40.0 hash:f7fa54992c8d7692 -->
+<!-- noodle-skill version:0.42.0 hash:f7fa54992c8d7692 -->
 
 # 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 credentials, an API URL, an OpenAPI document, or an observed response must become real Noodle Seed MCP behavior."
 ---
 
-<!-- noodle-skill version:0.40.0 hash:1e86b8704f407bd3 -->
+<!-- noodle-skill version:0.42.0 hash:1e86b8704f407bd3 -->
 
 # 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.40.0 hash:aa715bae12041d7c -->
+<!-- noodle-skill version:0.42.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.40.0 hash:93e735b7ffb45df1 -->
+<!-- noodle-skill version:0.42.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.40.0 hash:76cce86729cffbee -->
+<!-- noodle-skill version:0.42.0 hash:76cce86729cffbee -->
 
 # 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.40.0 hash:5d8f40f904d6ab4b -->
+<!-- noodle-skill version:0.42.0 hash:5d8f40f904d6ab4b -->
 
 # embedding-mcp-assistants
 

package/skills/claude-code/examples/customer-auth/README.md

@@ -169,7 +169,7 @@ customer backend. The model URL, model name, and model API key remain managed by
 
 The customer's authenticated backend calls `createAssistantSession(...)` from
 `@noodleseed/assistant/server`, passing the already-verified user and browser origin. The browser then uses
-the returned short-lived session through the Web Component or React wrapper:
+the returned short-lived session through the managed Web Component/React renderer or a customer-owned UI:
 
 ```bash
 pnpm add @noodleseed/assistant
@@ -185,6 +185,148 @@ import { NoodleAssistant } from '@noodleseed/assistant/react';
 />;
 ```
 
+For an entirely application-owned React renderer, use the renderer-free hook. It creates no custom element
+and returns the AI SDK transcript plus the canonical client commands:
+
+```tsx
+'use client';
+
+import { useState } from 'react';
+import { useNoodleAssistant } from '@noodleseed/assistant/react/client';
+
+export function CustomerAssistant({ principalKey }: { principalKey: string }) {
+  const [draft, setDraft] = useState('');
+  const { client, messages, status, error } = useNoodleAssistant({
+    sessionEndpoint: '/api/noodle-assistant/session',
+    principalKey,
+  });
+  const busy = status === 'submitted' || status === 'streaming';
+  const settle = (operation: Promise<void>) => {
+    void operation.catch(() => {
+      // The hook exposes this same structured failure through `error`.
+    });
+  };
+
+  return (
+    <section aria-label="Assistant" aria-busy={busy}>
+      {messages.map((message) => (
+        <article key={message.id} data-role={message.role}>
+          {message.parts.map((part, index) => {
+            if (part.type === 'text') return <p key={index}>{part.text}</p>;
+            if (part.type === 'data-confirmation') {
+              const review = part.data;
+              return (
+                <section key={review.id} aria-label="Review proposed action">
+                  <h3>{review.title ?? 'Review proposed action'}</h3>
+                  {review.description ? <p>{review.description}</p> : null}
+                  <pre aria-label="Proposed action arguments">
+                    {JSON.stringify(review.arguments ?? {}, null, 2)}
+                  </pre>
+                  <button
+                    disabled={busy || review.status !== 'pending'}
+                    onClick={() => settle(client.respond(review.id, { action: 'accept' }))}
+                  >
+                    Confirm
+                  </button>
+                  <button
+                    disabled={busy || review.status !== 'pending'}
+                    onClick={() => settle(client.respond(review.id, { action: 'decline' }))}
+                  >
+                    Don't proceed
+                  </button>
+                </section>
+              );
+            }
+            if (part.type === 'data-input-request') {
+              const request = part.data;
+              return (
+                <section key={request.id} aria-label="Assistant needs input">
+                  <p>{request.message}</p>
+                  <p>This renderer has not implemented the requested form.</p>
+                  <button
+                    disabled={busy || request.status !== 'pending'}
+                    onClick={() => settle(client.respond(request.id, { action: 'decline' }))}
+                  >
+                    Cancel request
+                  </button>
+                </section>
+              );
+            }
+            if (part.type === 'data-tool-result') {
+              return (
+                <pre key={part.data.id} aria-label={`${part.data.tool} result`}>
+                  {JSON.stringify(part.data.result, null, 2)}
+                </pre>
+              );
+            }
+            if (part.type === 'data-view') {
+              return (
+                <p key={part.data.id}>
+                  Trusted app view available: {part.data.title ?? part.data.resourceUri}
+                </p>
+              );
+            }
+            return <p key={index}>Unsupported assistant content.</p>;
+          })}
+        </article>
+      ))}
+      {error ? <p role="alert">{error.message}</p> : null}
+      <form
+        onSubmit={(event) => {
+          event.preventDefault();
+          const message = draft.trim();
+          if (!message) return;
+          setDraft('');
+          settle(client.sendMessage(message));
+        }}
+      >
+        <input
+          aria-label="Message"
+          value={draft}
+          onChange={(event) => setDraft(event.currentTarget.value)}
+        />
+        {busy ? (
+          <button type="button" onClick={() => client.abort()}>
+            Stop
+          </button>
+        ) : (
+          <button type="submit">Send</button>
+        )}
+      </form>
+    </section>
+  );
+}
+```
+
+`principalKey` stays in the browser. Change it whenever the authenticated user or tenant changes; the hook
+then aborts and clears the prior session and transcript. The sample fails closed on input requests until its
+fallback is replaced with a form generated from `requestedSchema`. A production renderer must show the
+complete confirmation review and both decisions. For `data-view`, map `resourceUri` or `tool` and the
+bounded/redacted result to a component already trusted by this application. Never inject `part.data.html`,
+assign it to `srcdoc`, or fetch a `ui://` URI.
+
+Outside React, subscribe to the DOM-free client directly. It exposes the same conversation as headless AI
+SDK `UIMessage` state, including typed confirmation, input, tool-result, and linked-view parts:
+
+```ts
+import { createAssistantClient } from '@noodleseed/assistant/client';
+
+const assistant = createAssistantClient({
+  sessionEndpoint: '/api/noodle-assistant/session',
+});
+
+assistant.subscribeChat((state) => {
+  renderUIMessageState(state);
+  for (const message of state.messages) {
+    for (const part of message.parts) {
+      if (part.type === 'data-confirmation' && part.data.status === 'pending') {
+        renderConfirmation(part.data, (response) => assistant.respond(part.data.id, response));
+      }
+    }
+  }
+});
+```
+
 `theme="auto"` follows the SaaS application. The server-level `branding` block is inherited by both MCP App
 widgets and the assistant; documented `--ns-assistant-*` semantic CSS variables remain the final integration
 escape hatch. There is no second assistant branding declaration.

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

@@ -12,6 +12,9 @@ guides and operates the validate, preview, deploy, inspect, and debug workflow.
 If that agent discovers a Noodle Seed product gap while working, the installed skill prepares a
 sanitized `noodle feedback` proposal, discovers current fields from `noodle commands --json`, and
 submits it only after showing the exact command and receiving explicit user approval.
+Every `--json` command writes its canonical success or failure envelope to stdout and leaves stderr
+empty. One-shot commands write one envelope; streaming commands write NDJSON snapshot, event, and
+terminal-failure envelopes so agents can parse each line independently.
 
 ```sh
 noodle dev examples/hello/src/server.ts --app hello

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.40.0 hash:efffbf82007f935d -->
+<!-- noodle-skill version:0.42.0 hash:efffbf82007f935d -->
 
 # publishing-mcp-integrations
 

package/skills/claude-code/references/agent-contract.md

@@ -1,6 +1,6 @@
 # Agent contract: --json, exit codes, output modes
 
-The cold-agent-path commands (`init`, `validate`, `test`, `check`, `tools`/`resources`/`prompts`, `deploy`, `metrics`, `events`, `agents`) are agent-native and return the envelope below; hosted admin/ops commands (`status`, `inspect`, `smoke`, `logs`, `update`) are still being normalized. Decide what to do next by parsing machine state — do not scrape human prose.
+Every `--json` command returns the canonical envelope below on stdout and keeps stderr empty. Decide what to do next by parsing machine state — do not scrape human prose.
 
 ## Contents
 
@@ -11,12 +11,13 @@ The cold-agent-path commands (`init`, `validate`, `test`, `check`, `tools`/`reso
 
 ## Response envelope
 
-A `--json` command returns exactly one JSON object:
+A one-shot `--json` command returns exactly one JSON object on stdout; stderr stays empty:
 
 - **Success**: `{ ok: true, data, warnings? }` — `data` is the command payload; `warnings?` is an optional array of non-fatal notes.
-- **Failure**: `{ ok: false, error: { code, message, cause?, fix, next, requestId? } }` — `code` is the stable machine code to branch on, `message` is human text, `cause?` is the underlying error, `fix` states the correction, `next` names the command to run next, `requestId?` correlates a hosted call.
+- **Failure**: `{ ok: false, error: { code, message, cause?, fix, next, requestId?, retryable?, retryAfterSeconds? } }` — `code` is the stable machine code to branch on, `message` is human text, `cause?` is the underlying error, `fix` states the correction, `next` names the command to run next, `requestId?` correlates a hosted call, and retry metadata tells automation whether and when to retry.
 - **Field errors** carry a dotted `path`: multi-error commands (e.g. `noodle validate`) nest them under `error.errors[]`, each `{ code, path, message }`. The top-level `error` still carries `code`/`message`/`fix`/`next`; the per-field `path`s live in `error.errors[]`.
 - **Repair prose is isolated**: ready-to-apply repair text appears only under `error.fixPrompt` (surfaced by `--fix-prompt`), never mixed into `message` or `data`.
+- **Streams are NDJSON envelopes**: the initial snapshot is `{ ok: true, data: { kind: "snapshot", snapshot } }`, subsequent records are `{ ok: true, data: { kind: "event", event } }`, and a terminal failure is the ordinary `{ ok: false, error }` envelope on its own line. Parse each line independently.
 
 ## Exit codes
 

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

@@ -248,7 +248,125 @@ Or import the package root once and mount `<noodle-assistant session-endpoint="/
 
 The component renders a custom element and must mount client-side. In a Next.js App Router tree, put the mount in a `"use client"` component; from a server component or the Pages Router, load it with `next/dynamic` and `ssr: false`.
 
-For a customer-owned renderer, use the DOM-free client. It keeps the session token in memory, streams the same typed events, and never registers a custom element:
+For a customer-owned React renderer, use the renderer-free hook. It owns client lifetime and React subscription while `client` remains the one command surface:
+
+```tsx
+"use client";
+
+import { useState } from "react";
+import { useNoodleAssistant } from "@noodleseed/assistant/react/client";
+
+export function CustomAssistant({ principalKey }: { principalKey: string }) {
+  const [draft, setDraft] = useState("");
+  const { client, messages, status, error } = useNoodleAssistant({
+    sessionEndpoint: "/api/assistant/session",
+    principalKey,
+    clientContext: () => ({
+      locale: navigator.language,
+      timeZone: Intl.DateTimeFormat().resolvedOptions().timeZone,
+    }),
+  });
+  const busy = status === "submitted" || status === "streaming";
+  const settle = (operation: Promise<void>) => {
+    void operation.catch(() => {
+      // The hook exposes this same structured failure through `error`.
+    });
+  };
+
+  return (
+    <section aria-label="Assistant" aria-busy={busy}>
+      {messages.map((message) => (
+        <article key={message.id} data-role={message.role}>
+          {message.parts.map((part, index) => {
+            if (part.type === "text") return <p key={index}>{part.text}</p>;
+            if (part.type === "data-confirmation") {
+              const review = part.data;
+              return (
+                <section key={review.id} aria-label="Review proposed action">
+                  <h3>{review.title ?? "Review proposed action"}</h3>
+                  {review.description ? <p>{review.description}</p> : null}
+                  <pre aria-label="Proposed action arguments">
+                    {JSON.stringify(review.arguments ?? {}, null, 2)}
+                  </pre>
+                  <button
+                    disabled={busy || review.status !== "pending"}
+                    onClick={() => settle(client.respond(review.id, { action: "accept" }))}
+                  >
+                    Confirm
+                  </button>
+                  <button
+                    disabled={busy || review.status !== "pending"}
+                    onClick={() => settle(client.respond(review.id, { action: "decline" }))}
+                  >
+                    Don't proceed
+                  </button>
+                </section>
+              );
+            }
+            if (part.type === "data-input-request") {
+              const request = part.data;
+              return (
+                <section key={request.id} aria-label="Assistant needs input">
+                  <p>{request.message}</p>
+                  <p>This renderer has not implemented the requested form.</p>
+                  <button
+                    disabled={busy || request.status !== "pending"}
+                    onClick={() => settle(client.respond(request.id, { action: "decline" }))}
+                  >
+                    Cancel request
+                  </button>
+                </section>
+              );
+            }
+            if (part.type === "data-tool-result") {
+              return (
+                <pre key={part.data.id} aria-label={`${part.data.tool} result`}>
+                  {JSON.stringify(part.data.result, null, 2)}
+                </pre>
+              );
+            }
+            if (part.type === "data-view") {
+              return (
+                <p key={part.data.id}>
+                  Trusted app view available: {part.data.title ?? part.data.resourceUri}
+                </p>
+              );
+            }
+            return <p key={index}>Unsupported assistant content.</p>;
+          })}
+        </article>
+      ))}
+      {error ? <p role="alert">{error.message}</p> : null}
+      <form
+        onSubmit={(event) => {
+          event.preventDefault();
+          const message = draft.trim();
+          if (!message) return;
+          setDraft("");
+          settle(client.sendMessage(message));
+        }}
+      >
+        <input
+          aria-label="Message"
+          value={draft}
+          onChange={(event) => setDraft(event.currentTarget.value)}
+        />
+        {busy ? (
+          <button type="button" onClick={() => client.abort()}>Stop</button>
+        ) : (
+          <button type="submit">Send</button>
+        )}
+      </form>
+    </section>
+  );
+}
+```
+
+`principalKey` is a browser-local identity for the authenticated user/tenant and is never sent to Noodle. Change it whenever that principal changes; the hook then aborts and clears the previous session and transcript. The hook does not register `<noodle-assistant>` or render Noodle markup.
+
+The sample fails closed on input requests until you replace that branch with a form generated from `requestedSchema`. A custom renderer must show the complete confirmation review and both decisions, handle every part it supports, and surface an explicit unsupported state for the rest. For `data-view`, map `resourceUri` or `tool` plus the bounded/redacted `result` to a component already trusted by the application. Never inject `part.data.html`, assign it to `srcdoc`, or fetch a `ui://` URI; the managed element alone supplies Noodle’s sandbox host. Do not wrap this client in another chat transport or invent user messages for interaction continuations.
+
+Outside React, use the same DOM-free client directly. It keeps the session token in memory, exposes a React-free `UIMessage` transcript with typed parts, and never registers a custom element:
 
 ```ts
 import { createAssistantClient } from "@noodleseed/assistant/client";
@@ -266,30 +384,39 @@ assistant.updateModelContext({
   structuredContent: { widget: { name: 'time-off', lifecycle: 'mounted' } },
 });
 
-let pendingId: string | undefined;
-let requestedSchema: unknown;
-assistant.subscribe((event) => {
-  renderAssistantEvent(event);
-  if (event.event === 'view_available') {
-    renderRegisteredView(event.data.resourceUri, event.data.result);
-  }
-  if ((event.event === 'tool_proposed' || event.event === 'input_requested') && typeof event.data.id === 'string') {
-    pendingId = event.data.id;
-    requestedSchema = event.event === 'input_requested' ? event.data.requestedSchema : undefined;
+let pending: { id: string; requestedSchema?: Readonly<Record<string, unknown>> } | undefined;
+assistant.subscribeChat((state) => {
+  renderUIMessageState(state);
+  pending = undefined;
+  for (const message of state.messages) {
+    for (const part of message.parts) {
+      if (part.type === 'data-confirmation' && part.data.status === 'pending') {
+        pending = { id: part.data.id };
+      }
+      if (part.type === 'data-input-request' && part.data.status === 'pending') {
+        pending = { id: part.data.id, requestedSchema: part.data.requestedSchema };
+      }
+      if (part.type === 'data-view') {
+        renderRegisteredView(part.data.resourceUri, part.data.result);
+      }
+    }
   }
 });
 
 await assistant.sendMessage("Book next Thursday and Friday off");
-if (pendingId) {
+if (pending) {
+  const requestedSchema = pending.requestedSchema;
   const resolution = requestedSchema
     ? { action: 'accept' as const, content: await renderPortableForm(requestedSchema) }
     : { action: 'accept' as const };
-  await assistant.respond(pendingId, resolution);
+  await assistant.respond(pending.id, resolution);
 }
 // The same pending id also accepts { action: 'decline' } or { action: 'cancel' }.
 ```
 
-`view_available` means a completed tool has a linked MCP App view. It carries the call/interaction id, tool, `ui://` identity, optional title, bounded/redacted public result, and—on current services—the self-contained bridged document. The standard element is an MCP Apps host and mounts that document behind a double iframe. It supports lifecycle, app tool/resource calls, ui/message, ui/update-model-context, links, resize, and inline/fullscreen; sampling, tasks, downloads, and remote DOM are not advertised. It also dispatches `assistant-view-available` for a customer-owned renderer.
+`subscribeChat` immediately emits a detached `{ messages, status, error? }` snapshot and then emits as `UIMessage.parts` change. Text uses `text`; Noodle confirmations, input requests, tool results, and linked views use `data-confirmation`, `data-input-request`, `data-tool-result`, and `data-view`. Interaction data moves through pending/submitting/accepted/declined/cancelled. Use raw `subscribe(...)` only for transport/session lifecycle events that are not transcript content.
+
+`data-view` means a completed tool has a linked MCP App view. It carries the call/interaction id, tool, `ui://` identity, optional title, bounded/redacted public result, and—on current services—the self-contained bridged document. The standard element is an MCP Apps host and mounts that document behind a double iframe; a customer renderer ignores it and maps the identity/result to an application-trusted component. The standard element supports lifecycle, app tool/resource calls, ui/message, ui/update-model-context, links, resize, and inline/fullscreen; sampling, tasks, downloads, and remote DOM are not advertised. It also dispatches `assistant-view-available` for a customer-owned renderer.
 
 `clientContext` and typed `pageContext` are recomputed for each turn. `updateContext(...)` remains the legacy session-exchange context; `updatePageContext(...)` replaces the fresh per-turn application hint. `updateModelContext({ content, structuredContent })` publishes one cohesive renderer snapshot for later message turns without starting a turn; every call replaces the prior snapshot rather than merging fields. These are untrusted data, not conversation history or authorization input, and the boundaries reject credential-shaped or unbounded updates. A message may re-exchange once after a pre-execution `401`; the client never auto-retries interaction decisions. `tool_proposed.arguments` is a complete schema-aware review projection and, for connector-backed tools, names the sole exact connector version/operation/resolved arguments. Sensitive/write-only fields are redacted; truncating or omitting any non-sensitive action field fails closed. Accept is bound to the server-held action and claims at most one execution attempt—clients cannot replace it. Normal terminal outcomes scrub private arguments and continuations immediately; only an accepted action still executing retains them for the one-hour unknown-outcome recovery window, after which it records `interaction_outcome_unknown` and scrubs. Without downstream idempotency this is not an exactly-once business-effect guarantee. To reconcile a lost response, explicitly repeat the same id and decision: the service returns its durable stored outcome without re-execution.
 
@@ -297,7 +424,7 @@ if (pendingId) {
 
 - Node.js 20+ for `@noodleseed/assistant/server`.
 - The package ships ESM and CommonJS with full export conditions; no bundler aliases, `transpilePackages`, or ambient type shims are needed. If resolution fails, the installed package version is outdated: update `@noodleseed/assistant` instead of adding workarounds.
-- TypeScript `moduleResolution` `bundler` or `node16` recommended; classic `node` also resolves the `/client`, `/react`, and `/server` subpaths.
+- TypeScript `moduleResolution` `bundler` or `node16` recommended; classic `node` also resolves the `/client`, `/react`, `/react/client`, and `/server` subpaths.
 
 ## Verify the boundary
 

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.40.0 hash:1e23938b39956ef8 -->
+<!-- noodle-skill version:0.42.0 hash:1e23938b39956ef8 -->
 
 # 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.40.0 hash:6ef6ef551e26b78e -->
+<!-- noodle-skill version:0.42.0 hash:6ef6ef551e26b78e -->
 
 # verifying-mcp-delivery
 

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.40.0 hash:2ea7d6dcc8358b35 -->
+<!-- noodle-skill version:0.42.0 hash:0c1ebd532b9c2499 -->
 
 # Noodle Seed
 
@@ -39,7 +39,7 @@ Negative routing examples: “Inspect hosted logs/status” → `inspect-hosted`
 
 ## Common machine loop
 
-The cold-agent commands speak the `--json` envelope. Parse machine state instead of scraping human prose; `references/agent-contract.md` owns the envelope and exit codes.
+Every `--json` command speaks the canonical envelope on stdout. Parse machine state instead of scraping human prose; `references/agent-contract.md` owns the envelope, streaming records, and exit codes.
 
 1. **Discover** — use `noodle commands --json` when the required command or flags are uncertain; don't read CLI source.
 2. **Author** — for build routes, edit the configured TypeScript entrypoint, usually `src/server.ts`.

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.40.0 hash:0b2fd8c7e43fc69f -->
+<!-- noodle-skill version:0.42.0 hash:0b2fd8c7e43fc69f -->
 
 # 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.40.0 hash:f7fa54992c8d7692 -->
+<!-- noodle-skill version:0.42.0 hash:f7fa54992c8d7692 -->
 
 # building-mcp-apps
 

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

@@ -3,7 +3,7 @@ name: connecting-apis-to-mcp
 description: "Use when credentials, an API URL, an OpenAPI document, or an observed response must become real Noodle Seed MCP behavior."
 ---
 
-<!-- noodle-skill version:0.40.0 hash:1e86b8704f407bd3 -->
+<!-- noodle-skill version:0.42.0 hash:1e86b8704f407bd3 -->
 
 # connecting-apis-to-mcp
 

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.40.0 hash:aa715bae12041d7c -->
+<!-- noodle-skill version:0.42.0 hash:aa715bae12041d7c -->
 
 # 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.40.0 hash:93e735b7ffb45df1 -->
+<!-- noodle-skill version:0.42.0 hash:93e735b7ffb45df1 -->
 
 # 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.40.0 hash:76cce86729cffbee -->
+<!-- noodle-skill version:0.42.0 hash:76cce86729cffbee -->
 
 # 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.40.0 hash:5d8f40f904d6ab4b -->
+<!-- noodle-skill version:0.42.0 hash:5d8f40f904d6ab4b -->
 
 # embedding-mcp-assistants