@noodleseed/agent-kit 0.44.1 → 0.46.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@noodleseed/agent-kit",
-  "version": "0.44.1",
+  "version": "0.46.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.44.1 hash:cd6ca0d915e6acb9 -->
+<!-- noodle-skill version:0.46.0 hash:cd6ca0d915e6acb9 -->
 
 # 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.44.1 hash:0b2fd8c7e43fc69f -->
+<!-- noodle-skill version:0.46.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.44.1 hash:f7fa54992c8d7692 -->
+<!-- noodle-skill version:0.46.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.44.1 hash:1e86b8704f407bd3 -->
+<!-- noodle-skill version:0.46.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.44.1 hash:aa715bae12041d7c -->
+<!-- noodle-skill version:0.46.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.44.1 hash:93e735b7ffb45df1 -->
+<!-- noodle-skill version:0.46.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.44.1 hash:76cce86729cffbee -->
+<!-- noodle-skill version:0.46.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.44.1 hash:5d8f40f904d6ab4b -->
+<!-- noodle-skill version:0.46.0 hash:5d8f40f904d6ab4b -->
 
 # embedding-mcp-assistants
 

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

@@ -193,11 +193,14 @@ import { NoodleAssistant } from '@noodleseed/assistant/react';
 
 <NoodleAssistant
   sessionEndpoint="/api/noodle-assistant/session"
-  theme="auto"
+  theme={resolvedTheme}
   onSessionExpired={() => console.info('Assistant session renewed')}
 />;
 ```
 
+`resolvedTheme` is the application's current `'light' | 'dark'` value. Use `theme="auto"` only when the
+browser operating-system preference is intentionally authoritative.
+
 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:
 
@@ -205,9 +208,16 @@ and returns the AI SDK transcript plus the canonical client commands:
 'use client';
 
 import { useState } from 'react';
+import { NoodleAppView } from '@noodleseed/assistant/react';
 import { useNoodleAssistant } from '@noodleseed/assistant/react/client';
 
-export function CustomerAssistant({ principalKey }: { principalKey: string }) {
+export function CustomerAssistant({
+  principalKey,
+  resolvedTheme,
+}: {
+  principalKey: string;
+  resolvedTheme: 'light' | 'dark';
+}) {
   const [draft, setDraft] = useState('');
   const { client, messages, status, error } = useNoodleAssistant({
     sessionEndpoint: '/api/noodle-assistant/session',
@@ -274,9 +284,12 @@ export function CustomerAssistant({ principalKey }: { principalKey: string }) {
             }
             if (part.type === 'data-view') {
               return (
-                <p key={part.data.id}>
-                  Trusted app view available: {part.data.title ?? part.data.resourceUri}
-                </p>
+                <NoodleAppView
+                  key={`${part.data.id}:${part.data.resourceUri}`}
+                  client={client}
+                  view={part.data}
+                  theme={resolvedTheme}
+                />
               );
             }
             return <p key={index}>Unsupported assistant content.</p>;
@@ -315,8 +328,12 @@ export function CustomerAssistant({ principalKey }: { principalKey: string }) {
 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.
+bounded/redacted result to a component already trusted by this application only when intentionally replacing
+the linked App with a native UI. Otherwise use `NoodleAppView`; JSON result data is not the App UI. Its
+semantic lifecycle identity is the client plus `view.id` plus `view.resourceUri`, so parent payload/callback
+rerenders keep the iframe and only a different view or unmount tears down the bridge.
+Never inject `part.data.html`, assign it to `srcdoc`, fetch a `ui://` URI, or reproduce the bridge directly. Pages with a
+Content-Security-Policy must include the Noodle service origin in both `connect-src` and `frame-src`.
 
 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:
@@ -340,9 +357,13 @@ assistant.subscribeChat((state) => {
 });
 ```
 
-`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.
+`theme="auto"` follows the browser operating-system preference, not a SaaS-owned theme toggle. Pass the
+application's resolved `light`/`dark` theme to both `NoodleAssistant` and `NoodleAppView`; later updates
+reach mounted MCP Apps without remounting them. CSS custom properties inherit through the assistant host, so
+typed appearance roles may reuse existing application tokens with `var(--app-token)`. 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.
 The end-user UI contains only customer branding.
 Text streams progressively. Expired turns re-exchange through the authenticated backend and retry once;
 consent-bound tool confirmations never replay automatically.

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.44.1 hash:6a9f132ddb79352e -->
+<!-- noodle-skill version:0.46.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.44.1 hash:efffbf82007f935d -->
+<!-- noodle-skill version:0.46.0 hash:efffbf82007f935d -->
 
 # publishing-mcp-integrations
 

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

@@ -82,7 +82,7 @@ assistant: embeddedAssistant({
 
 The Atlas-style product treatment above is the maximum deployment-configurable presentation. The bounded surface covers panel treatment, launcher icon/size/session pulse, header mark/status badge, composer controls, and message treatment; it does not accept custom header actions, structured empty-state layouts, footers, spectacle variants/effects, or tenant code.
 
-Omitted fields retain the quiet premium baseline. For exact application-owned color roles, pass the typed React `appearance={{ light: { panel: { surface, text, border }, composer: {...}, confirmation: {...}, primaryButton: {...} }, dark: {...} }}` prop or assign the same object to `element.appearance`. It covers canvas, panel, header, messages, composer, suggestions, confirmation, buttons, launcher, code, and the MCP App frame. Exact colors are preserved and low contrast emits `assistant-appearance-warning`. Precedence is host appearance object, host slots/public `--ns-assistant-*` variables, deployed semantic presentation, then defaults. Prefer `server.ts` configuration first so every embedding app receives the same assistant after redeploy.
+Omitted fields retain the quiet premium baseline. For exact application-owned color roles, pass the typed React `appearance={{ light: { panel: { surface, text, border }, composer: {...}, confirmation: {...}, primaryButton: {...} }, dark: {...} }}` prop or assign the same object to `element.appearance`. CSS custom properties inherit through the assistant host, so those values may reuse existing application tokens such as `surface: "var(--app-surface)"` without copying literals. The appearance surface covers canvas, panel, header, messages, composer, suggestions, confirmation, buttons, launcher, code, and the MCP App frame; the package README publishes the complete role-to-`--ns-assistant-*` map. Exact parseable literal colors are preserved and low contrast emits `assistant-appearance-warning`; contrast for unresolved CSS references remains host-owned. Precedence is host appearance object, host slots/public variables, deployed semantic presentation, then defaults. Prefer `server.ts` configuration first so every embedding app receives the same assistant after redeploy.
 
 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. Do not put JSON or implementation names in business-facing copy.
 
@@ -241,11 +241,13 @@ Use the React wrapper in React applications:
 ```tsx
 import { NoodleAssistant } from "@noodleseed/assistant/react";
 
-<NoodleAssistant sessionEndpoint="/api/assistant/session" theme="auto" />;
+<NoodleAssistant sessionEndpoint="/api/assistant/session" theme={resolvedTheme} />;
 ```
 
 Or import the package root once and mount `<noodle-assistant session-endpoint="/api/assistant/session" theme="auto"></noodle-assistant>`. Mount only inside the authenticated application surface.
 
+`theme="auto"` follows the browser operating-system preference. If the SaaS application owns a theme toggle, obtain its resolved application theme (`"light"` or `"dark"`), pass `theme={resolvedTheme}` to `NoodleAssistant`, and update the custom element's `theme` attribute when that value changes.
+
 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 React renderer, use the renderer-free hook. It owns client lifetime and React subscription while `client` remains the one command surface:
@@ -254,9 +256,10 @@ For a customer-owned React renderer, use the renderer-free hook. It owns client
 "use client";
 
 import { useState } from "react";
+import { NoodleAppView } from "@noodleseed/assistant/react";
 import { useNoodleAssistant } from "@noodleseed/assistant/react/client";
 
-export function CustomAssistant({ principalKey }: { principalKey: string }) {
+export function CustomAssistant({ principalKey, resolvedTheme }: { principalKey: string; resolvedTheme: "light" | "dark" }) {
   const [draft, setDraft] = useState("");
   const { client, messages, status, error } = useNoodleAssistant({
     sessionEndpoint: "/api/assistant/session",
@@ -327,9 +330,12 @@ export function CustomAssistant({ principalKey }: { principalKey: string }) {
             }
             if (part.type === "data-view") {
               return (
-                <p key={part.data.id}>
-                  Trusted app view available: {part.data.title ?? part.data.resourceUri}
-                </p>
+                <NoodleAppView
+                  key={`${part.data.id}:${part.data.resourceUri}`}
+                  client={client}
+                  view={part.data}
+                  theme={resolvedTheme}
+                />
               );
             }
             return <p key={index}>Unsupported assistant content.</p>;
@@ -364,7 +370,9 @@ export function CustomAssistant({ principalKey }: { principalKey: string }) {
 
 `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.
+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`, use `NoodleAppView` to render the linked App or deliberately map `resourceUri`/tool plus the bounded redacted `result` to an application-trusted native component. JSON result data is not the linked App UI. Never inject `part.data.html`, assign it to `srcdoc`, fetch a `ui://` URI, or reproduce the bridge with a direct Ext Apps dependency. Do not wrap this client in another chat transport or invent user messages for interaction continuations.
+
+`NoodleAppView` owns one bridge for the semantic view identity: client + `view.id` + `view.resourceUri`. It retains the iframe across fresh payload/callback/theme rerenders, reads current payloads through refs, publishes later resolved-theme changes through MCP Apps host context, and sends standard App teardown only when that semantic identity changes or the component unmounts. Pass the same resolved application theme used by the conversation shell. Do not key an ancestor by a view object or callback. If the embedding page sets Content-Security-Policy, include the Noodle service origin in both `connect-src` and `frame-src`.
 
 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:
 
@@ -416,7 +424,7 @@ if (pending) {
 
 `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.
+`data-view` means a completed tool has a linked MCP App view. In a customer-owned React renderer, pass that typed part and the existing client to `NoodleAppView`; it retains one bridge for client + `view.id` + `view.resourceUri` and requests standard App teardown on semantic replacement or unmount. Deliberately map the bounded result to an application-trusted native component only when replacing the linked App UI.
 
 `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.
 

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.44.1 hash:0f404109f4845683 -->
+<!-- noodle-skill version:0.46.0 hash:0f404109f4845683 -->
 
 # 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.44.1 hash:6ef6ef551e26b78e -->
+<!-- noodle-skill version:0.46.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.44.1 hash:cd6ca0d915e6acb9 -->
+<!-- noodle-skill version:0.46.0 hash:cd6ca0d915e6acb9 -->
 
 # 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.44.1 hash:0b2fd8c7e43fc69f -->
+<!-- noodle-skill version:0.46.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.44.1 hash:f7fa54992c8d7692 -->
+<!-- noodle-skill version:0.46.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.44.1 hash:1e86b8704f407bd3 -->
+<!-- noodle-skill version:0.46.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.44.1 hash:aa715bae12041d7c -->
+<!-- noodle-skill version:0.46.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.44.1 hash:93e735b7ffb45df1 -->
+<!-- noodle-skill version:0.46.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.44.1 hash:76cce86729cffbee -->
+<!-- noodle-skill version:0.46.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.44.1 hash:5d8f40f904d6ab4b -->
+<!-- noodle-skill version:0.46.0 hash:5d8f40f904d6ab4b -->
 
 # embedding-mcp-assistants
 

package/skills/codex/examples/customer-auth/README.md

@@ -193,11 +193,14 @@ import { NoodleAssistant } from '@noodleseed/assistant/react';
 
 <NoodleAssistant
   sessionEndpoint="/api/noodle-assistant/session"
-  theme="auto"
+  theme={resolvedTheme}
   onSessionExpired={() => console.info('Assistant session renewed')}
 />;
 ```
 
+`resolvedTheme` is the application's current `'light' | 'dark'` value. Use `theme="auto"` only when the
+browser operating-system preference is intentionally authoritative.
+
 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:
 
@@ -205,9 +208,16 @@ and returns the AI SDK transcript plus the canonical client commands:
 'use client';
 
 import { useState } from 'react';
+import { NoodleAppView } from '@noodleseed/assistant/react';
 import { useNoodleAssistant } from '@noodleseed/assistant/react/client';
 
-export function CustomerAssistant({ principalKey }: { principalKey: string }) {
+export function CustomerAssistant({
+  principalKey,
+  resolvedTheme,
+}: {
+  principalKey: string;
+  resolvedTheme: 'light' | 'dark';
+}) {
   const [draft, setDraft] = useState('');
   const { client, messages, status, error } = useNoodleAssistant({
     sessionEndpoint: '/api/noodle-assistant/session',
@@ -274,9 +284,12 @@ export function CustomerAssistant({ principalKey }: { principalKey: string }) {
             }
             if (part.type === 'data-view') {
               return (
-                <p key={part.data.id}>
-                  Trusted app view available: {part.data.title ?? part.data.resourceUri}
-                </p>
+                <NoodleAppView
+                  key={`${part.data.id}:${part.data.resourceUri}`}
+                  client={client}
+                  view={part.data}
+                  theme={resolvedTheme}
+                />
               );
             }
             return <p key={index}>Unsupported assistant content.</p>;
@@ -315,8 +328,12 @@ export function CustomerAssistant({ principalKey }: { principalKey: string }) {
 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.
+bounded/redacted result to a component already trusted by this application only when intentionally replacing
+the linked App with a native UI. Otherwise use `NoodleAppView`; JSON result data is not the App UI. Its
+semantic lifecycle identity is the client plus `view.id` plus `view.resourceUri`, so parent payload/callback
+rerenders keep the iframe and only a different view or unmount tears down the bridge.
+Never inject `part.data.html`, assign it to `srcdoc`, fetch a `ui://` URI, or reproduce the bridge directly. Pages with a
+Content-Security-Policy must include the Noodle service origin in both `connect-src` and `frame-src`.
 
 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:
@@ -340,9 +357,13 @@ assistant.subscribeChat((state) => {
 });
 ```
 
-`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.
+`theme="auto"` follows the browser operating-system preference, not a SaaS-owned theme toggle. Pass the
+application's resolved `light`/`dark` theme to both `NoodleAssistant` and `NoodleAppView`; later updates
+reach mounted MCP Apps without remounting them. CSS custom properties inherit through the assistant host, so
+typed appearance roles may reuse existing application tokens with `var(--app-token)`. 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.
 The end-user UI contains only customer branding.
 Text streams progressively. Expired turns re-exchange through the authenticated backend and retry once;
 consent-bound tool confirmations never replay automatically.

package/skills/codex/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.44.1 hash:6a9f132ddb79352e -->
+<!-- noodle-skill version:0.46.0 hash:6a9f132ddb79352e -->
 
 # Execute a Noodle Seed implementation plan
 

package/skills/codex/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.44.1 hash:efffbf82007f935d -->
+<!-- noodle-skill version:0.46.0 hash:efffbf82007f935d -->
 
 # publishing-mcp-integrations
 

package/skills/codex/references/embedded-assistant.md

@@ -82,7 +82,7 @@ assistant: embeddedAssistant({
 
 The Atlas-style product treatment above is the maximum deployment-configurable presentation. The bounded surface covers panel treatment, launcher icon/size/session pulse, header mark/status badge, composer controls, and message treatment; it does not accept custom header actions, structured empty-state layouts, footers, spectacle variants/effects, or tenant code.
 
-Omitted fields retain the quiet premium baseline. For exact application-owned color roles, pass the typed React `appearance={{ light: { panel: { surface, text, border }, composer: {...}, confirmation: {...}, primaryButton: {...} }, dark: {...} }}` prop or assign the same object to `element.appearance`. It covers canvas, panel, header, messages, composer, suggestions, confirmation, buttons, launcher, code, and the MCP App frame. Exact colors are preserved and low contrast emits `assistant-appearance-warning`. Precedence is host appearance object, host slots/public `--ns-assistant-*` variables, deployed semantic presentation, then defaults. Prefer `server.ts` configuration first so every embedding app receives the same assistant after redeploy.
+Omitted fields retain the quiet premium baseline. For exact application-owned color roles, pass the typed React `appearance={{ light: { panel: { surface, text, border }, composer: {...}, confirmation: {...}, primaryButton: {...} }, dark: {...} }}` prop or assign the same object to `element.appearance`. CSS custom properties inherit through the assistant host, so those values may reuse existing application tokens such as `surface: "var(--app-surface)"` without copying literals. The appearance surface covers canvas, panel, header, messages, composer, suggestions, confirmation, buttons, launcher, code, and the MCP App frame; the package README publishes the complete role-to-`--ns-assistant-*` map. Exact parseable literal colors are preserved and low contrast emits `assistant-appearance-warning`; contrast for unresolved CSS references remains host-owned. Precedence is host appearance object, host slots/public variables, deployed semantic presentation, then defaults. Prefer `server.ts` configuration first so every embedding app receives the same assistant after redeploy.
 
 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. Do not put JSON or implementation names in business-facing copy.
 
@@ -241,11 +241,13 @@ Use the React wrapper in React applications:
 ```tsx
 import { NoodleAssistant } from "@noodleseed/assistant/react";
 
-<NoodleAssistant sessionEndpoint="/api/assistant/session" theme="auto" />;
+<NoodleAssistant sessionEndpoint="/api/assistant/session" theme={resolvedTheme} />;
 ```
 
 Or import the package root once and mount `<noodle-assistant session-endpoint="/api/assistant/session" theme="auto"></noodle-assistant>`. Mount only inside the authenticated application surface.
 
+`theme="auto"` follows the browser operating-system preference. If the SaaS application owns a theme toggle, obtain its resolved application theme (`"light"` or `"dark"`), pass `theme={resolvedTheme}` to `NoodleAssistant`, and update the custom element's `theme` attribute when that value changes.
+
 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 React renderer, use the renderer-free hook. It owns client lifetime and React subscription while `client` remains the one command surface:
@@ -254,9 +256,10 @@ For a customer-owned React renderer, use the renderer-free hook. It owns client
 "use client";
 
 import { useState } from "react";
+import { NoodleAppView } from "@noodleseed/assistant/react";
 import { useNoodleAssistant } from "@noodleseed/assistant/react/client";
 
-export function CustomAssistant({ principalKey }: { principalKey: string }) {
+export function CustomAssistant({ principalKey, resolvedTheme }: { principalKey: string; resolvedTheme: "light" | "dark" }) {
   const [draft, setDraft] = useState("");
   const { client, messages, status, error } = useNoodleAssistant({
     sessionEndpoint: "/api/assistant/session",
@@ -327,9 +330,12 @@ export function CustomAssistant({ principalKey }: { principalKey: string }) {
             }
             if (part.type === "data-view") {
               return (
-                <p key={part.data.id}>
-                  Trusted app view available: {part.data.title ?? part.data.resourceUri}
-                </p>
+                <NoodleAppView
+                  key={`${part.data.id}:${part.data.resourceUri}`}
+                  client={client}
+                  view={part.data}
+                  theme={resolvedTheme}
+                />
               );
             }
             return <p key={index}>Unsupported assistant content.</p>;
@@ -364,7 +370,9 @@ export function CustomAssistant({ principalKey }: { principalKey: string }) {
 
 `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.
+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`, use `NoodleAppView` to render the linked App or deliberately map `resourceUri`/tool plus the bounded redacted `result` to an application-trusted native component. JSON result data is not the linked App UI. Never inject `part.data.html`, assign it to `srcdoc`, fetch a `ui://` URI, or reproduce the bridge with a direct Ext Apps dependency. Do not wrap this client in another chat transport or invent user messages for interaction continuations.
+
+`NoodleAppView` owns one bridge for the semantic view identity: client + `view.id` + `view.resourceUri`. It retains the iframe across fresh payload/callback/theme rerenders, reads current payloads through refs, publishes later resolved-theme changes through MCP Apps host context, and sends standard App teardown only when that semantic identity changes or the component unmounts. Pass the same resolved application theme used by the conversation shell. Do not key an ancestor by a view object or callback. If the embedding page sets Content-Security-Policy, include the Noodle service origin in both `connect-src` and `frame-src`.
 
 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:
 
@@ -416,7 +424,7 @@ if (pending) {
 
 `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.
+`data-view` means a completed tool has a linked MCP App view. In a customer-owned React renderer, pass that typed part and the existing client to `NoodleAppView`; it retains one bridge for client + `view.id` + `view.resourceUri` and requests standard App teardown on semantic replacement or unmount. Deliberately map the bounded result to an application-trusted native component only when replacing the linked App UI.
 
 `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.
 

package/skills/codex/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.44.1 hash:0f404109f4845683 -->
+<!-- noodle-skill version:0.46.0 hash:0f404109f4845683 -->
 
 # reporting-noodle-feedback
 

package/skills/codex/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.44.1 hash:6ef6ef551e26b78e -->
+<!-- noodle-skill version:0.46.0 hash:6ef6ef551e26b78e -->
 
 # verifying-mcp-delivery