@noodleseed/one 0.166.0 → 0.168.0

package/node_modules/@noodle-borg/agent-kit/dist/behavior-skills.js

@@ -147,11 +147,12 @@ export const BEHAVIOR_SKILLS = [
     },
     {
         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.',
-        outcome: 'Select one decision-complete assistant topology, then deliver the embed with identity and credential separation proven at the tested level.',
+        description: 'Use when embedding a Noodle assistant into an existing SaaS or web application, or improving signup or onboarding conversion with public-to-product onboarding, with browser, identity, session, and credential boundaries.',
+        outcome: 'Select one decision-complete assistant topology, including the dual-surface continuous-onboarding default when it fits, then deliver the embed with identity and credential separation proven at the tested level.',
         positiveTriggers: [
             'Embed the Noodle assistant in an existing web app.',
             'Wire browser mounting and session exchange.',
+            'Choose a first Noodle workflow for software where more signed-in users are valuable.',
         ],
         negativeTriggers: [
             'Do not use to build a standalone MCP App.',
@@ -163,6 +164,7 @@ export const BEHAVIOR_SKILLS = [
             'Access mode plus the identity, session, and server-owned routing boundary.',
             'Managed or custom renderer and its explicit product benefit.',
             'Model owner and requested local, hosted, or production evidence level.',
+            'For a first-workflow recommendation: evidence for a public visitor surface, account boundary, useful pre-account result, and authenticated outcome.',
         ],
         primaryReference: 'references/embedded-assistant.md',
         supportingReferences: ['references/authoring-workflow.md'],

package/node_modules/@noodle-borg/agent-kit/dist/generated/example-files.js

@@ -55,11 +55,11 @@ export const BUNDLED_EXAMPLE_FILES = [
     { relPath: "examples/acme-tasks/src/views/widget-style.css", content: ":root {\n  color-scheme: light dark;\n  font-family:\n    Inter, ui-sans-serif, system-ui, -apple-system, BlinkMacSystemFont, \"Segoe UI\", sans-serif;\n  --nw-bg: #ffffff;\n  --nw-surface: #f7f5ff;\n  --nw-text: #1c1830;\n  --nw-muted: #635d80;\n  --nw-border: #e2ddf5;\n  --nw-accent: #7c3aed;\n  --nw-accent-strong: #6d28d9;\n  --nw-accent-soft: #efe9ff;\n  --nw-high: #dc2626;\n  --nw-medium: #b45309;\n  --nw-low: #2563eb;\n  --nw-radius: 10px;\n  --nw-shadow: 0 18px 50px rgb(30 20 60 / 12%);\n}\n\n.dark,\n[data-theme=\"dark\"] {\n  --nw-bg: #161228;\n  --nw-surface: #1d1735;\n  --nw-text: #f2eeff;\n  --nw-muted: #a99fce;\n  --nw-border: #342a54;\n  --nw-accent: #a78bfa;\n  --nw-accent-strong: #8b5cf6;\n  --nw-accent-soft: #2a2148;\n  --nw-high: #f87171;\n  --nw-medium: #fbbf24;\n  --nw-low: #60a5fa;\n  --nw-shadow: 0 18px 50px rgb(0 0 0 / 32%);\n}\n\n* {\n  box-sizing: border-box;\n}\n\nbody {\n  margin: 0;\n  background: var(--nw-bg);\n  color: var(--nw-text);\n}\n\nbutton,\ninput,\nselect {\n  font: inherit;\n}\n\n.nw-shell {\n  min-height: 100vh;\n  padding: 14px;\n  background: var(--nw-bg);\n  color: var(--nw-text);\n}\n\n.nw-card {\n  max-width: 620px;\n  margin: 0 auto;\n  background: var(--nw-surface);\n  border: 1px solid var(--nw-border);\n  border-radius: var(--nw-radius);\n  box-shadow: var(--nw-shadow);\n  overflow: hidden;\n}\n\n.nw-header {\n  display: flex;\n  align-items: center;\n  gap: 12px;\n  padding: 16px;\n  border-bottom: 1px solid var(--nw-border);\n}\n\n.nw-icon svg {\n  width: 24px;\n  height: 24px;\n  fill: none;\n  stroke: var(--nw-accent);\n  stroke-width: 2;\n  stroke-linecap: round;\n  stroke-linejoin: round;\n}\n\n.nw-title-block {\n  flex: 1;\n  min-width: 0;\n}\n\n.nw-title {\n  margin: 0;\n  font-size: 17px;\n  font-weight: 700;\n}\n\n.nw-subtitle {\n  margin: 2px 0 0;\n  font-size: 13px;\n  color: var(--nw-muted);\n}\n\n.nw-chip {\n  padding: 4px 10px;\n  border-radius: 999px;\n  background: var(--nw-accent-soft);\n  color: var(--nw-accent-strong);\n  font-size: 12px;\n  font-weight: 600;\n}\n\n.nw-capture {\n  display: flex;\n  gap: 8px;\n  padding: 14px 16px 4px;\n}\n\n.nw-input {\n  flex: 1;\n  padding: 9px 12px;\n  border: 1px solid var(--nw-border);\n  border-radius: 10px;\n  background: var(--nw-bg);\n  color: var(--nw-text);\n}\n\n.nw-button {\n  display: inline-flex;\n  align-items: center;\n  gap: 6px;\n  padding: 9px 14px;\n  border: 1px solid var(--nw-border);\n  border-radius: 10px;\n  background: var(--nw-bg);\n  color: var(--nw-text);\n  cursor: pointer;\n}\n\n.nw-button-primary {\n  background: var(--nw-accent);\n  border-color: var(--nw-accent);\n  color: #ffffff;\n  font-weight: 600;\n}\n\n.nw-button-primary:disabled {\n  opacity: 0.6;\n  cursor: default;\n}\n\n.nw-list {\n  list-style: none;\n  margin: 0;\n  padding: 8px 16px 4px;\n  display: flex;\n  flex-direction: column;\n  gap: 8px;\n}\n\n.nw-task {\n  display: flex;\n  align-items: center;\n  gap: 10px;\n  padding: 10px 12px;\n  border: 1px solid var(--nw-border);\n  border-radius: 12px;\n  background: var(--nw-bg);\n}\n\n.nw-task-title {\n  flex: 1;\n  min-width: 0;\n}\n\n.nw-task-done {\n  opacity: 0.55;\n}\n\n.nw-task-done .nw-task-title {\n  text-decoration: line-through;\n}\n\n.nw-check {\n  width: 22px;\n  height: 22px;\n  border: 1.5px solid var(--nw-border);\n  border-radius: 999px;\n  background: transparent;\n  color: #ffffff;\n  cursor: pointer;\n  flex: none;\n}\n\n.nw-check-on {\n  background: var(--nw-accent);\n  border-color: var(--nw-accent);\n}\n\n.nw-priority {\n  padding: 5px 8px;\n  border: 1px solid var(--nw-border);\n  border-radius: 8px;\n  background: var(--nw-bg);\n  color: var(--nw-text);\n  font-size: 12px;\n  font-weight: 600;\n}\n\n.nw-priority-high {\n  color: var(--nw-high);\n}\n\n.nw-priority-medium {\n  color: var(--nw-medium);\n}\n\n.nw-priority-low {\n  color: var(--nw-low);\n}\n\n.nw-note {\n  margin: 0;\n  padding: 8px 16px 16px;\n  font-size: 12px;\n  color: var(--nw-muted);\n}\n" },
     { relPath: "examples/acme-tasks/test/server.test.ts", content: "import { describe, expect, it } from 'vitest';\nimport app from '../src/server.js';\n\ndescribe('acme-tasks example', () => {\n  it('exports a Noodle server definition', () => {\n    expect(typeof app.toManifest).toBe('function');\n  });\n\n  it('exposes a tool for each of the top-3 prioritized flows', async () => {\n    // Capture → add_task, Prioritize → list_today (+ set_priority helper), Complete → complete_task.\n    const text = JSON.stringify(await app.toManifest());\n    expect(text).toContain('add_task');\n    expect(text).toContain('list_today');\n    expect(text).toContain('complete_task');\n    expect(text).toContain('set_priority');\n  });\n\n  it('seeds today’s list highest-priority first', async () => {\n    const text = JSON.stringify(await app.toManifest());\n    expect(text).toMatch(/\"tasks\":\\[\\{\"id\":\"email_vendor\".*\"priority\":\"high\"/);\n  });\n\n  it('opts the conversational completion action into runtime confirmation', async () => {\n    const manifest = await app.toManifest();\n    const completeTask = manifest.tools.find((candidate) => candidate.name === 'complete_task');\n    const addTask = manifest.tools.find((candidate) => candidate.name === 'add_task');\n    const setPriority = manifest.tools.find((candidate) => candidate.name === 'set_priority');\n\n    expect(completeTask?.annotations?.confirm).toBe(true);\n    expect(addTask?.annotations).not.toHaveProperty('confirm');\n    expect(setPriority?.visibility).toEqual(['app']);\n  });\n\n  it('teaches its three product workflows through one host-neutral agent guide', async () => {\n    const manifest = await app.toManifest();\n    const guide = manifest.server.agentGuide;\n\n    expect(guide?.workflows.map((workflow) => workflow.id)).toEqual([\n      'review_tasks',\n      'capture_task',\n      'complete_task',\n    ]);\n    expect(\n      guide?.workflows.flatMap((workflow) => workflow.steps.map((step) => step.capability.name)),\n    ).toEqual(expect.arrayContaining(['list_today', 'set_priority', 'add_task', 'complete_task']));\n    expect(\n      guide?.workflows\n        .find((workflow) => workflow.id === 'review_tasks')\n        ?.steps.map((step) => step.capability.name),\n    ).toContain('set_priority');\n    expect(\n      guide?.examples.every((example) =>\n        guide.workflows.some((workflow) => workflow.id === example.workflow),\n      ),\n    ).toBe(true);\n    expect(guide?.boundaries.some((boundary) => boundary.toLowerCase().includes('confirm'))).toBe(\n      true,\n    );\n  });\n});\n" },
     { relPath: "examples/acme-tasks/vitest.config.ts", content: "import { defineConfig } from 'vitest/config';\n\n// Local config so `npm test` (vitest run) discovers this example's own tests instead of inheriting a\n// parent monorepo config's include globs.\nexport default defineConfig({\n  test: { include: ['test/**/*.test.ts'] },\n});\n" },
-    { relPath: "examples/customer-auth/README.md", content: "# Customer Auth - OIDC identity and customer-routed APIs\n\nFor a visitor who starts before signup, use the [Stateful Draft reference](../stateful-draft/README.md)\nalongside this authenticated backend integration.\n\nThis curated example owns the customer/end-user authentication capability slot. It proves that a SaaS app\ncan protect an MCP endpoint with direct OIDC, retain role/scope-based tool authorization, and route ordinary\nreads and confirmed actions to the API origin selected by the verified customer's identity provider.\n\nIt also owns the customer-branded embedded-assistant presentation showcase. Direct MCP calls obtain the\nroute from the verified OIDC claim; embedded sessions obtain it from the authenticated customer backend's\nsession exchange. Both paths keep the URL outside tool/model/browser-visible state. The built-in card hides\nits optional technical Additional details disclosure while retaining the business review and confirmation\ncontrols; this presentation setting does not weaken the exact runtime confirmation boundary.\n\nThe public developer entrypoint is [`src/server.ts`](src/server.ts). It exposes a deliberately small MCP\nsurface for organization discovery and app lifecycle operations:\n\n- `list_my_organizations` lists the NoodleSeed.com organizations the signed-in customer belongs to (no\n  arguments — the org set comes from the verified customer session).\n- `list_org_apps` lists apps for one of those organizations through that tenant's API. It is visible and\n  callable only when the verified customer has the `org_apps:read` scope and either the `org_admin` or\n  `org_member` role.\n- `archive_org_app` archives one app only after exact runtime confirmation. It requires the\n  `org_apps:write` scope and `org_admin` role.\n\nThe tools chain: `list_my_organizations` surfaces the `org_id`s the customer can act on,\n`list_org_apps` takes one of those ids, and `archive_org_app` accepts the selected app id. Tool code remains\nindependent of the selected origin.\n\nThe server also declares one typed `agentGuide` for those product workflows. The deployed embedded assistant\nuses it automatically: each turn keeps only complete workflows supported by the verified session's roles,\nscopes, and model-visible tools. An organization member can receive organization/app review guidance, while\nonly an administrator with `org_apps:write` receives the complete archive workflow and its confirmation\nboundary. The guide stays server-side, so the Web Component, React renderer, headless hook, and public client\nneed no new option and receive no raw skill content. See\n[using a product guide at runtime](https://docs.noodleseed.dev/docs/guides/product-agent-guides#use-the-guide-at-runtime)\nfor the public behavior guide.\n\nA skill-aware external agent connected directly to the same tenant MCP URL receives the same\ncomplete-workflow filtering through the modern draft MCP Skills extension. Members and administrators may\ntherefore receive different `SKILL.md` and MCP-surface bytes, each with matching caller-specific digests.\nThis reuses the configured customer OAuth boundary; it does not require a second skill installation or auth\nsystem, and it is not a claim that every external host currently implements the draft extension. The\nsame [runtime guide](https://docs.noodleseed.dev/docs/guides/product-agent-guides#use-the-guide-at-runtime)\nexplains this preview boundary.\n\n## Declare the customer endpoint\n\n`customerEndpoint` names one private routing authority and bounds the origins an IdP may select:\n\n```ts\nconst customerApi = customerEndpoint('customer_api', {\n  allowedHttpsHostSuffixes: ['api.noodleseed.dev'],\n});\n```\n\nUse either non-empty `allowedHttpsHostSuffixes` or non-empty `allowedHttpsOrigins`, never both. Exact-origin\npolicies may include a non-default port. Suffix policies match only the exact hostname or dot-boundary\nsubdomains on port 443. A routed connector must not add `allowedOrigins`; its endpoint policy is the egress\nallowlist.\n\nThe connector uses that declaration as its normal base URL. Its token endpoint remains a fixed, independently\nvalidated HTTPS URL:\n\n```ts\nconst api = connector('noodleseed_app_api')\n  .version('1.0.0')\n  .http({\n    baseUrl: customerApi,\n    auth: {\n      kind: 'delegatedTokenExchange',\n      tokenUrl: 'https://id.noodleseed.dev/oauth/token',\n      clientId: variable('CUSTOMER_API_CLIENT_ID'),\n      clientSecret: secret('CUSTOMER_API_CLIENT_SECRET'),\n      scopes: ['organizations:read', 'org_apps:read', 'org_apps:write'],\n      audience: 'noodleseed-customer-api',\n    },\n    operations: {\n      // read and action operations...\n    },\n  });\n```\n\n`delegatedTokenExchange` consumes a verified customer caller; an MCP access mode does not create one. The\nserver must declare `customerAuth.*(...)` or `embeddedAssistant(...)` so Noodle Seed can establish the caller\nsubject, issuer, and audience. Otherwise `noodle validate`, `noodle auth doctor`, and deploy fail early with\n`delegated_token_exchange_identity_required`, before secrets are resolved or any connector egress. A\nsuccessful local Devtools exchange is not evidence that the hosted server has an identity source. Devtools\nsupplies a separate, loopback-only local identity context that is never accepted by hosted deployment.\n\nAt both connector and operation level, auth must be omitted or use `delegatedTokenExchange`. The compiler\nvalidates the concrete connector definition emitted from TypeScript, including connector defaults and\noperation overrides, and reports the exact failing auth path and kind. Do not keep a bearer, API-key,\nclient-credentials, or managed-provider fallback for local mode; use operation fakes while leaving auth\ndeclarative.\n\n## Map the endpoint from verified OIDC\n\nThe IdP claim contains the complete base URL, including an optional base path. Routing is separate from the\npublic `${user}` expression scope:\n\n```ts\nauth: customerAuth.oidc({\n  issuer: 'https://id.noodleseed.dev',\n  audience: 'noodleseed-customer-auth-prod',\n  claims: {\n    id: 'sub',\n    email: 'email',\n    name: 'name',\n    orgs: 'permissions.orgs',\n    roles: 'permissions.roles',\n    scopes: 'permissions.scopes',\n  },\n  routing: {\n    endpoints: {\n      customer_api: { claim: 'tenant.api_base_url' },\n    },\n  },\n}),\n```\n\nFor federated OIDC, put the same endpoint map on every issuer. Claim paths may differ, but each issuer must\nmap every endpoint the app uses:\n\n```ts\nauth: customerAuth.federatedOidc({\n  issuers: [\n    {\n      issuer: 'https://id.customer-a.com',\n      audience: 'noodleseed-customer-auth-prod',\n      routing: {\n        endpoints: {\n          customer_api: { claim: 'tenant.api_base_url' },\n        },\n      },\n    },\n    {\n      issuer: 'https://login.customer-b.com',\n      audience: 'noodleseed-customer-auth-prod',\n      routing: {\n        endpoints: {\n          customer_api: { claim: 'organization.routes.customer_api' },\n        },\n      },\n    },\n  ],\n}),\n```\n\nAt runtime, Noodle Seed validates the configured stable audience, associates the caller with the exact\ntransport-derived MCP resource, projects the route into private request state, applies its policy, and\nfreezes it for the call. Missing, malformed, or\ndisallowed claims return `connector_route_unavailable` before credential lookup or connector egress.\nResolved URLs never enter artifacts, `${user}`, logs, model output, widgets, public confirmation review,\nbroker cache keys, or delegated exchange assertions.\n\nRouted reads work in tools, including declared nested calls. Routed actions require exact\n`annotations.confirm: true`; otherwise they fail with `customer_endpoint_action_unsupported`. Routed\nresources, prompts, and ambient context fail with `customer_endpoint_surface_unsupported`.\n\nThe flagship's routed action uses the normal TypeScript action helper:\n\n```ts\ntool('archive_org_app', {\n  authorization: {\n    requiredScopes: ['org_apps:write'],\n    allowedRoles: ['org_admin'],\n  },\n  annotations: annotations.openAction({ destructive: false, confirm: true }),\n  // input, output, and the normal connectors.app_api.archiveOrgApp(...) call...\n});\n```\n\nThe flagship also opts into the current stateless hosted MCP path:\n\n```ts\ninteractions: {\n  confirmationFallback: 'host',\n},\n```\n\nA bidirectional client that negotiated form elicitation can complete the standard confirmation exchange\ninstead. The explicit host fallback trusts the MCP host to have collected native write approval before the\ntool call reaches Noodle Seed; it is never inferred from client identity and does not replace auth, policy,\nor accurate action/destructive annotations. Omit the fallback when connected hosts are not trusted to\nprovide that approval. If neither standard confirmation nor the fallback is available, the action fails\nclosed with `interaction_unavailable`.\n\nPreparation stores only sorted route `{ key, fingerprint }` bindings in its private server-held\ncontinuation; the public review exposes none of them. Acceptance re-resolves the current request route and\nreturns `invalid_continuation` if it is missing or changed, before policy, credentials, or egress. A match\nreuses the current frozen snapshot for the action and all nested or later reads.\n\nThe application developer owns the direct/federated authorization server. It must publish its path-inserted\nRFC 8414 document as direct HTTP 200 JSON with exact issuer and HTTPS authorization/token/registration/JWKS\nendpoints, authorization-code and refresh grants, PKCE S256, public-client auth method `none`, RFC 8707\nresource handling, and public signing keys. It validates each exact MCP resource on authorize, code exchange,\nand refresh, then maps approved versions of this app/environment to `noodleseed-customer-auth-prod`. Other\napps and environments use distinct audiences.\n\nRun `noodle auth doctor src/server.ts` before sharing. Its bounded, read-only probes never register a client.\nAdding the embedded assistant does not choose or rewrite MCP customer auth. Its authenticated backend may\nbind `routing.endpoints.customer_api` during assistant-session exchange from server-owned membership data;\ndirect MCP requests continue to resolve the same endpoint from the configured verified OIDC claim.\n\n## Per-tool authorization remains independent\n\nThe mapped `roles` and `scopes` paths are read only after OIDC verification. The restricted tool declares its\nrule beside the rest of its public contract:\n\n```ts\ntool('list_org_apps', {\n  authorization: {\n    requiredScopes: ['org_apps:read'],\n    allowedRoles: ['org_admin', 'org_member'],\n  },\n  // input, output, and fulfilment...\n});\n```\n\nEvery required scope must be present and at least one allowed role must match. When both lists are declared,\nboth conditions apply. Route availability never changes `tools/list`: discovery remains based only on\nroles/scopes. A restricted tool is omitted for an ineligible customer and a guessed direct call still fails\nclosed.\n\nTool code calls the connector normally:\n\n```ts\nfulfil({ input, connectors }) {\n  const apps = connectors.app_api.listOrgApps({\n    org_id: input.org_id,\n    skip: input.skip,\n    limit: input.limit,\n  });\n\n  return { result: apps.result };\n}\n```\n\nThe broker exchanges a short-lived, platform-signed assertion at the fixed token endpoint and caches the\nresult by caller, connector, scopes, and a route fingerprint. The assertion carries only the route key and\nfingerprint, never the URL. The MCP access token is never forwarded to the customer API. The exchange wire\ncontract lives in docs/spec/connectors.md.\n\nFirebase and Microsoft remain supported managed adapters; their provider-specific contracts and tests live\nin docs/spec/auth-and-policy.md and the SharePoint flagship.\n\n## Supabase direct-OIDC access-token hook\n\nDynamic Client Registration lets any OAuth client register, so the presence of `client_id` is not approval.\nKeep an operator-controlled client-to-audience map and rewrite `aud` only for an exact mapped client. For a\ndynamically registered client, review its generated client ID, name, and exact redirect URIs in the consent\nflow before adding the mapping. Each new registration needs its own row; never approve by name or prefix.\n\nReplace `<approved-oauth-client-id>` with the reviewed client ID and `<stable-mcp-audience>` with the exact\nvalue configured in `customerAuth.oidc`:\n\n```sql\ncreate table if not exists public.mcp_oauth_client_audiences (\n  client_id text primary key check (btrim(client_id) <> ''),\n  audience text not null check (btrim(audience) <> '')\n);\n\nrevoke all on table public.mcp_oauth_client_audiences from authenticated, anon, public;\ngrant usage on schema public to supabase_auth_admin;\ngrant select on table public.mcp_oauth_client_audiences to supabase_auth_admin;\n\ninsert into public.mcp_oauth_client_audiences (client_id, audience)\nvalues ('<approved-oauth-client-id>', '<stable-mcp-audience>')\non conflict (client_id) do update set audience = excluded.audience;\n\ncreate or replace function public.mcp_access_token_hook(event jsonb)\nreturns jsonb\nlanguage plpgsql\nstable\nas $$\ndeclare\n  claims jsonb := coalesce(event->'claims', '{}'::jsonb);\n  oauth_client_id text := nullif(btrim(claims->>'client_id'), '');\n  mapped_audience text;\nbegin\n  if oauth_client_id is not null then\n    select mapping.audience\n      into mapped_audience\n      from public.mcp_oauth_client_audiences as mapping\n      where mapping.client_id = oauth_client_id;\n  end if;\n\n  if mapped_audience is not null then\n    claims := jsonb_set(\n      claims,\n      '{aud}',\n      to_jsonb(mapped_audience),\n      true\n    );\n  end if;\n\n  return jsonb_build_object('claims', claims);\nend;\n$$;\n\ngrant execute on function public.mcp_access_token_hook(jsonb) to supabase_auth_admin;\nrevoke execute on function public.mcp_access_token_hook(jsonb) from authenticated, anon, public;\n```\n\n| Token source | Mapping | Resulting `aud` |\n| --- | --- | --- |\n| Approved OAuth client | Exact client row | Mapped stable MCP audience |\n| Unrelated or unknown OAuth client | No row | Original Supabase audience |\n| Browser session | No `client_id` | Original Supabase audience |\n\nSelect this function under Supabase Auth Hooks before completing the interactive verification below.\n\n## Validate\n\n```bash\nnoodle validate examples/customer-auth/src/server.ts --json\nnoodle auth doctor examples/customer-auth/src/server.ts --json\nnoodle test examples/customer-auth/src/server.ts --json\n```\n\nThe doctor proves metadata and JWKS readiness without registering a client. For this protected app,\n`noodle test` proves the anonymous 401 plus exact protected-resource metadata boundary and reports\n`interactiveRequired: true`; neither command proves token issuance or audience verification.\n\nAgainst a deployed customer-protected environment, set a short-lived real customer token only in\n`NOODLE_CUSTOMER_TOKEN` and add `--live --org <org> --app <app> --env <env>`. The live doctor performs\ncredential exchanges without invoking any business tool. Add `--version 1` when testing a pinned version;\nthe reported customer resource must match that versioned MCP endpoint.\n\n## Run locally\n\n```bash\nnoodle devtools examples/customer-auth/src/server.ts\n```\n\nComplete sign-in in Devtools and load the tool list. That authenticated request is the local proof that DCR,\nPKCE, token issuance, issuer/signature verification, the stable audience, and exact-resource binding work\ntogether. Invoke a representative safe read when the configured customer API is available.\n\n### Test delegated exchange locally\n\nLocal customer OIDC sign-in and delegated-exchange assertion trust are two distinct boundaries. OIDC proves\nthe caller to the local MCP server; Devtools uses a separate local issuer only for the RFC 8693 assertion\nsent to the downstream token endpoint. This is the canonical local path and requires no `server.ts` change,\nflag, environment variable, or config surface.\n\n1. Configure the OIDC authorization server for the exact loopback callback and RFC 8707 resource. Do not add\n   the Devtools assertion key to OIDC issuer metadata or change its signing keys.\n2. Start Devtools, complete customer sign-in, and copy the displayed `{ issuer, jwks }` from **Local delegated exchange**.\n3. Pin both values only in the customer-owned development RFC 8693 token endpoint.\n4. Restrict that trust to development client credentials, audience, API, and data.\n5. Invoke the delegated `list_org_apps` tool until its binding reads **Exchange verified**.\n6. Use hosted preview or `noodle auth doctor --live` to prove the production platform issuer.\n\n**Never trust the Devtools issuer in production: anyone holding the local private key could impersonate a customer.**\n\n## Configuration\n\nThe embedded assistant uses a customer-supplied Responses-compatible endpoint, selected explicitly with\n`transport: 'responses'` in `src/server.ts`. Use `transport: 'chat-completions'` or omit the field for a\nChat Completions endpoint. Noodle never falls back between them. Configure its managed values at the Noodle\ndeployment environment; none of these values belongs in the customer web application environment, and the\nAPI key never reaches the browser:\n\nThe assistant session carries a verified user, tenant, deployment, roles, and scopes. For this flagship's\nrouted tools, the embedding backend resolves the signed-in user's cluster from server-owned membership data\nand passes `routing: { endpoints: { customer_api: cluster.apiBaseUrl } }` to\n`createAssistantSession`. Noodle validates and privately stores that route; it is not returned to the\nbrowser. Do not copy the route into page context, session claims, tool input, or model instructions.\n\nThe authenticated assistant surface also declares `accountTier` as a model-visible session claim. Pass it\nfrom the same backend-owned account record as `claims: { accountTier: account.tier }`; undeclared claims are\ndropped. This is personalization context, not authorization: the verified roles/scopes beside each tool and\nthe server-owned customer route remain the enforcement boundaries. The public\n[runtime guide](https://docs.noodleseed.dev/docs/guides/product-agent-guides#use-the-guide-at-runtime)\nexplains how verified session claims constrain the guide content available to the model.\n\n```bash\nnoodle variables set ASSISTANT_ORIGIN https://app.example.com --scope env\nnoodle variables set ASSISTANT_MODEL_BASE_URL https://model.example.com/v1 --scope env\nnoodle variables set ASSISTANT_MODEL your-model --scope env\nnoodle secrets set ASSISTANT_MODEL_API_KEY --scope env\nnoodle variables set CUSTOMER_API_CLIENT_ID your-broker-client-id --scope env\nnoodle secrets set CUSTOMER_API_CLIENT_SECRET --scope env\nnoodle check --target embedded-assistant src/server.ts\n```\n\n`ASSISTANT_ORIGIN` is the operator-owned production embedding origin, so one source can serve every customer\nwithout an application fork. Assistant origins are exact. Production embedding origins must use HTTPS; plain HTTP is accepted only for\nloopback development origins such as `http://localhost:3000`, `http://127.0.0.1:3000`, or\n`http://[::1]:3000`. `noodle dev` serves the MCP project, not that separate embedding application.\n\nThe bounded `presentation` object configures the panel, launcher, header, composer, and messages. Its\nprimitives derive colors from shared server `branding`; raw HTML, CSS, inline SVG, renderer classes, and\ncallbacks are not accepted. This example omits `presentation.panel.surface`, so the renderer keeps the\nopaque default panel treatment while the example's light/dark `branding` surfaces provide its customer colors;\nset the bounded surface to `glass` only when translucency is intentional.\n\nThese TypeScript values remain the reusable developer defaults. After deployment, an environment operator\ncan adjust theme, logo, launcher style, position, and the bounded color palette from the Console's\n**Assistant** tab or `noodle assistant appearance` without changing the customer's embed code. See the\n[embedded assistant guide](https://docs.noodleseed.dev/docs/guides/embedded-assistant) for precedence and reset\nbehavior.\n\nCreate the backend credential after deployment. The CLI writes it to a mode-0600 file and never prints the\nsecret:\n\n```bash\nnoodle assistant clients create --name web --org noodleseed --app customer-auth --env prod\n```\n\nOnly the Noodle service URL, assistant client ID, and assistant client secret belong in the authenticated\ncustomer backend. The model URL, model name, and model API key remain managed by the Noodle deployment.\n\nThe customer's authenticated backend calls `createAssistantSession(...)` from\n`@noodleseed/assistant/server`, passing the already-verified user and browser origin. The browser then uses\nthe returned short-lived session through the managed Web Component/React renderer or a customer-owned UI:\n\n```bash\npnpm add @noodleseed/assistant\n```\n\n```tsx\nimport { NoodleAssistant } from '@noodleseed/assistant/react';\n\n<NoodleAssistant\n  sessionEndpoint=\"/api/noodle-assistant/session\"\n  theme={resolvedTheme}\n  onSessionExpired={() => console.info('Assistant session renewed')}\n/>;\n```\n\n`resolvedTheme` is the application's current `'light' | 'dark'` value. Use `theme=\"auto\"` only when the\nbrowser operating-system preference is intentionally authoritative.\n\n### Minimal fail-closed custom renderer skeleton\n\nUse the renderer-free hook only when the product has a concrete reason to own the conversation UI. This\nminimal skeleton keeps the canonical client and App host, but intentionally refuses confirmation and input\nacceptance until the application implements their complete schema-aware presentation. Start with the managed\nrenderer unless the application accepts every obligation below.\n\n```tsx\n'use client';\n\nimport { useEffect, useState } from 'react';\nimport { NoodleAppView } from '@noodleseed/assistant/react';\nimport { useNoodleAssistant } from '@noodleseed/assistant/react/client';\n\nexport function CustomerAssistant({\n  principalKey,\n  resolvedTheme,\n  onSignInRequested,\n}: {\n  principalKey: string;\n  resolvedTheme: 'light' | 'dark';\n  onSignInRequested: (request: {\n    signInTicket: string;\n    expiresAt: string;\n  }) => Promise<'started' | 'cancelled'>;\n}) {\n  const [draft, setDraft] = useState('');\n  const [sessionNotice, setSessionNotice] = useState('');\n  const [turnNotice, setTurnNotice] = useState('');\n  const [pendingSignInTicket, setPendingSignInTicket] = useState<string>();\n  const { client, messages, suggestions, status, error } = useNoodleAssistant({\n    sessionEndpoint: '/api/noodle-assistant/session',\n    principalKey,\n  });\n  const busy = status === 'submitted' || status === 'streaming';\n  const settle = (operation: Promise<void>) => {\n    void operation.catch(() => {\n      // The hook exposes this same structured failure through `error`.\n    });\n  };\n  useEffect(\n    () =>\n      client.subscribe((event) => {\n        if (event.event === 'session_expired') setSessionNotice('Session expired.');\n        if (event.event === 'session_started' || event.event === 'session_reset') {\n          setSessionNotice('');\n        }\n      }),\n    [client],\n  );\n\n  return (\n    <section aria-label=\"Assistant\" aria-busy={busy}>\n      {messages.map((message) => (\n        <article key={message.id} data-role={message.role}>\n          {message.parts.map((part, index) => {\n            if (part.type === 'text') return <p key={index}>{part.text}</p>;\n            if (part.type === 'data-confirmation') {\n              const review = part.data;\n              return (\n                <section key={review.id} aria-label=\"Review proposed action\">\n                  <h3>{review.title ?? 'Review proposed action'}</h3>\n                  {review.description ? <p>{review.description}</p> : null}\n                  <p>This custom renderer has not implemented a complete schema-aware review.</p>\n                  <button\n                    disabled={busy || review.status !== 'pending'}\n                    onClick={() => settle(client.respond(review.id, { action: 'decline' }))}\n                  >\n                    Don't proceed\n                  </button>\n                  <button\n                    disabled={busy || review.status !== 'pending'}\n                    onClick={() => settle(client.respond(review.id, { action: 'cancel' }))}\n                  >\n                    Cancel\n                  </button>\n                </section>\n              );\n            }\n            if (part.type === 'data-input-request') {\n              const request = part.data;\n              return (\n                <section key={request.id} aria-label=\"Assistant needs input\">\n                  <p>{request.message}</p>\n                  {/* request.requestedSchema is the sole input-form contract. */}\n                  <p>This custom renderer has not implemented the requested schema form.</p>\n                  <button\n                    disabled={busy || request.status !== 'pending'}\n                    onClick={() => settle(client.respond(request.id, { action: 'decline' }))}\n                  >\n                    Don't proceed\n                  </button>\n                  <button\n                    disabled={busy || request.status !== 'pending'}\n                    onClick={() => settle(client.respond(request.id, { action: 'cancel' }))}\n                  >\n                    Cancel\n                  </button>\n                </section>\n              );\n            }\n            if (part.type === 'data-tool-result') {\n              return (\n                <p key={part.data.id} role=\"status\">\n                  A result is available, but this renderer has no trusted presentation for it.\n                </p>\n              );\n            }\n            if (part.type === 'data-view') {\n              return (\n                <NoodleAppView\n                  key={`${part.data.id}:${part.data.resourceUri}`}\n                  client={client}\n                  view={part.data}\n                  theme={resolvedTheme}\n                />\n              );\n            }\n            if (part.type === 'data-sign-in') {\n              const request = part.data;\n              return (\n                <section key={request.id} aria-label=\"Sign in required\">\n                  <p>Continue with your account to use this capability.</p>\n                  <button\n                    disabled={busy || pendingSignInTicket !== undefined}\n                    onClick={() => {\n                      setPendingSignInTicket(request.signInTicket);\n                      void Promise.resolve()\n                        .then(() =>\n                          onSignInRequested({\n                            signInTicket: request.signInTicket,\n                            expiresAt: request.expiresAt,\n                          }),\n                        )\n                        .then(\n                          (result) => {\n                            if (result === 'cancelled') setPendingSignInTicket(undefined);\n                          },\n                          () => setPendingSignInTicket(undefined),\n                        );\n                    }}\n                  >\n                    Sign in\n                  </button>\n                </section>\n              );\n            }\n            return <p key={index}>Unsupported assistant content.</p>;\n          })}\n        </article>\n      ))}\n      <p role=\"status\" aria-live=\"polite\">\n        {sessionNotice || turnNotice || (busy ? 'Assistant is working' : '')}\n      </p>\n      {suggestions?.prompts.length ? (\n        <nav aria-label=\"Suggested messages\">\n          {suggestions.prompts.map((prompt) => (\n            <button\n              key={prompt}\n              type=\"button\"\n              disabled={busy}\n              onClick={() => {\n                setTurnNotice('');\n                settle(client.sendMessage(prompt));\n              }}\n            >\n              {prompt}\n            </button>\n          ))}\n        </nav>\n      ) : null}\n      {error ? <p role=\"alert\">The assistant could not complete that request.</p> : null}\n      <form\n        onSubmit={(event) => {\n          event.preventDefault();\n          const message = draft.trim();\n          if (!message) return;\n          setDraft('');\n          setTurnNotice('');\n          settle(client.sendMessage(message));\n        }}\n      >\n        <input\n          aria-label=\"Message\"\n          value={draft}\n          onChange={(event) => setDraft(event.currentTarget.value)}\n        />\n        {busy ? (\n          <button\n            type=\"button\"\n            onClick={() => {\n              client.abort();\n              setTurnNotice('Response stopped. This does not undo a started action.');\n            }}\n          >\n            Stop\n          </button>\n        ) : (\n          <button type=\"submit\">Send</button>\n        )}\n      </form>\n    </section>\n  );\n}\n```\n\n`principalKey` stays in the browser. Change it whenever the authenticated user or tenant changes; the hook\nthen aborts and clears the prior session and transcript. The sample does not render Confirm until the host\nimplements a complete schema-aware review, and it does not accept elicitation until a portable form covers\n`requestedSchema`; use the managed renderer instead of shipping either unsupported branch. Suggestions are\nhook-owned and submit ordinary messages through `client.sendMessage`.\n\n`data-sign-in` has no status and is never passed to `client.respond`. Bind `signInTicket` to the host's\nshort-lived login transaction without putting it in URLs, logs, analytics, or durable browser storage. Resolve\nthe callback as `started` only after the host owns one active transaction; return `cancelled` or reject when no\ntransaction started so the renderer restores the sign-in affordance. A\nmixed renderer uses separate public and authenticated clients: the public shell uses `embedId`, `serviceUrl`,\nand a visitor principal key; after login, the destination mounts a new client against the same-origin session\nendpoint under the user/tenant principal key. Never pass both source options or mutate the public client's\nsource in place. `session_expired` is observational: the client owns its single safe pre-execution re-exchange.\nNever add a generic Retry button or replay an interaction decision automatically.\n\nFor `data-tool-result`, do not expose technical tool names or raw JSON. Prefer the linked `data-view`;\notherwise map a known bounded result to application-trusted UI or keep the explicit unsupported state. For\n`data-view`, use `<noodle-app-view>` or its React `NoodleAppView` adapter. The element's semantic lifecycle\nidentity is the client plus `view.id` plus `view.resourceUri`, so payload/callback rerenders keep the iframe\nand only a different view, disconnect, or App teardown request retires the bridge.\nApp views remain inline by default: the host advertises only inline presentation and rejects a widget's\nfullscreen request. A customer-owned renderer may opt in explicitly with `allowFullscreen` on\n`NoodleAppView` or `allow-fullscreen` on `<noodle-app-view>` only when fullscreen is part of its intended\nexperience. When fullscreen is accepted, the shared host adds a top-right exit control that returns the same\nmounted App to inline mode without discarding its state.\nNever inject `part.data.html`, assign it to `srcdoc`, fetch a `ui://` URI, or reproduce the bridge directly. Pages with a\nContent-Security-Policy must include the Noodle service origin in both `connect-src` and `frame-src`.\n\nBefore the production-equivalent host build, run the presence-only handoff check:\n\n```sh\nnoodle assistant embed --check --json\n```\n\nAdd application-owned delegated-exchange requirements with repeatable `--require-env NAME` flags. The JSON\nreports required and missing names, CSP status, and post-deploy probes without returning environment values\nor writing scaffold files. Map the names through the production secret manager, CI environment, and any\nsecret allowlist; regenerate existing framework-owned environment binding types before the build. Default\nDevtools/model exercises to synthetic data, and obtain approval before sending real connector data to an\nexternal model.\n\nRead `evidence.levels` in order: static host, local contract, hosted session, production browser, then\noperations. Stop at `evidence.firstUnproven`. A static result may be `passed`, `partial`, or `failed`; even\ntop-level `ready: true` means only that no static blocker was detected. It never proves the local session\ncontract or a production-browser flow. Value-free diagnostics call out an MCP endpoint used as the service\nURL, an HTML redirect risk, an SSR mount risk, and a cross-origin session endpoint. The command has no live\nor browser flag; its `postDeployProbes` are next actions, not executed evidence.\n\nAfter deployment, use the assistant doctor to verify the embed client, exact model transport, and static\nsession boundary:\n\n```sh\nnoodle assistant doctor --user-id <real-test-user> --origin \"$PUBLIC_APP_ORIGIN\" --org <org> --app <app> --env <env>\n```\n\nThe doctor makes one bounded synthetic model request without business tools or customer conversation data;\nfailures show only a redacted category, status, and retryability. It does not invent or test an\napplication-specific customer route. Prove routed assistant tools by\nhaving the authenticated embedding backend pass the user's server-verified endpoint during session\nexchange, then invoke one representative safe read.\n\nDo not send a first turn on mount by default. React effect cleanup can suppress one provisional Strict Mode\neffect, but it cannot make a remount, dependency change, or client replacement idempotent. Require an\nexplicit user action unless the host owns durable one-shot state and an application idempotency key that\nmakes repeated sends safe.\n\nFor a chat-first custom host, raw `tool_started` supplies the direct call `id` and technical tool name. Map\nknown tools to concise application copy and use a neutral fallback. Reserve a stable `role=\"status\"` region\nfor thinking, tool activity, and the view skeleton; switch to the ready `<noodle-app-view>` (or React\n`NoodleAppView`) on `view_available` or to `role=\"alert\"` on error. Decorative skeleton shapes stay hidden from assistive technology, and shimmer\nor transition motion is disabled under `prefers-reduced-motion`.\n\nUse `${view.id}:${view.resourceUri}` as transport identity. Different call IDs are distinct invocations and\nmust not be deduplicated generically. If this application intentionally owns one current panel for a known\nresource, declare an application-owned slot for that resource and replace only that slot.\n\n### Framework-neutral DOM client\n\nSubscribe to the DOM-free client directly without a component wrapper and use the isolated App host.\nIt exposes the same conversation as headless AI SDK `UIMessage` state, including typed confirmation, input,\ntool-result, and linked-view parts:\n\n```html\n<div id=\"assistant-app-views\"></div>\n```\n\n```ts\nimport '@noodleseed/assistant/app-view';\nimport {\n  type AssistantViewAvailableDetail,\n  type NoodleAppViewElement,\n} from '@noodleseed/assistant/app-view';\nimport { createAssistantClient } from '@noodleseed/assistant/client';\n\nconst assistant = createAssistantClient({\n  sessionEndpoint: '/api/noodle-assistant/session',\n});\nconst appViews = document.querySelector('#assistant-app-views');\nif (!appViews) throw new Error('Missing App views host');\nconst mountedViews = new Map<string, NoodleAppViewElement>();\nconst readResolvedTheme = (): 'light' | 'dark' =>\n  document.documentElement.classList.contains('dark') ? 'dark' : 'light';\nlet resolvedTheme: 'light' | 'dark' = readResolvedTheme();\nconst syncResolvedTheme = () => {\n  resolvedTheme = readResolvedTheme();\n  for (const mountedView of mountedViews.values()) mountedView.theme = resolvedTheme;\n};\nnew MutationObserver(syncResolvedTheme).observe(document.documentElement, {\n  attributes: true,\n  attributeFilter: ['class'],\n});\nconst appViewFor = (view: AssistantViewAvailableDetail) => {\n  const key = `${view.id}:${view.resourceUri}`;\n  let appView = mountedViews.get(key);\n  if (!appView) {\n    appView = document.createElement('noodle-app-view') as NoodleAppViewElement;\n    appView.client = assistant;\n    mountedViews.set(key, appView);\n    appViews.append(appView);\n  }\n  appView.theme = resolvedTheme;\n  return appView;\n};\n\nassistant.subscribeChat((state) => {\n  renderUIMessageState(state, {\n    respond: (id, response) => assistant.respond(id, response),\n  });\n  const activeViewKeys = new Set<string>();\n  for (const message of state.messages) {\n    for (const part of message.parts) {\n      if (part.type === 'data-view') {\n        const key = `${part.data.id}:${part.data.resourceUri}`;\n        activeViewKeys.add(key);\n        appViewFor(part.data).view = part.data;\n      }\n    }\n  }\n  for (const [key, mountedView] of mountedViews) {\n    if (!activeViewKeys.has(key)) {\n      mountedView.remove();\n      mountedViews.delete(key);\n    }\n  }\n});\n```\n\n`renderUIMessageState` is application code. It must present a complete schema-aware confirmation or input\nform and require an explicit user gesture before using `respond`; never call `respond` while scanning a\ntranscript snapshot.\n\n`theme=\"auto\"` follows the operating-system preference, not a SaaS-owned toggle. Pass the resolved\n`light`/`dark` theme to `NoodleAssistant` and `<noodle-app-view>`/`NoodleAppView`; updates reach mounted MCP Apps without a\nremount. CSS custom properties inherit through the host, and documented `--ns-assistant-*` variables remain\nthe final integration escape hatch. Server `branding` is shared by widgets and the assistant; there is no\nsecond branding declaration. Text streams progressively. Expired turns re-exchange and retry once;\nconfirmations never replay automatically.\n\nThe customer IdP must place the full tenant API base URL in `tenant.api_base_url`. For example, one verified\ncustomer may receive `https://customer-a.api.noodleseed.dev/v1` and another\n`https://customer-b.api.noodleseed.dev/v1`; both satisfy the declared suffix policy. Application code,\ndeployment variables, and connector arguments do not select the tenant route.\n\n`CUSTOMER_API_CLIENT_ID` and `CUSTOMER_API_CLIENT_SECRET` authenticate only the broker to the fixed exchange\nendpoint. They are not customer API bearer tokens. The exchange endpoint verifies the platform-signed\nsubject assertion and mints a short-lived token scoped to the signed-in user and route binding.\n\n## Launch and qualified-usage proof\n\nUse the [embedded assistant guide](https://docs.noodleseed.dev/docs/guides/embedded-assistant) for the complete\npre-launch, browser-proof, qualified-usage, recovery, measurement, and operator procedure; do not copy those\ncommands into this example. Keep deployed capability, production-browser proof, qualified usage, and measured\noutcome separate; raw turn volume is utilization rather than outcome. Platform-owned completion events still\nrequire a separate human-approved analytics and customer-data contract.\n\n## Deploy customer-protected to Noodle Seed Cloud\n\n```bash\nnoodle deploy examples/customer-auth/src/server.ts \\\n  --org noodleseed \\\n  --app customer-auth \\\n  --env prod \\\n  --access customers\n```\n\nEndpoint:\n\n```text\nhttps://cloud.noodleseed.dev/o/noodleseed/customer-auth/mcp\n```\n\n## MCP Primitives\n\n- Tool `list_my_organizations`: calls `GET /api/organizations` and returns the organizations the signed-in\n  customer is a member of. Takes no arguments; the org set is scoped by the verified customer session.\n- Tool `list_org_apps`: calls `GET /api/organizations/{org_id}/apps` for one organization `org_id`.\n- Tool `archive_org_app`: after confirmation, calls\n  `POST /api/organizations/{org_id}/apps/{app_id}/archive`.\n\n## Auth boundary\n\nNoodle Seed verifies the configured OIDC issuer and stable audience, then binds the exact transport-derived\nMCP resource before reading identity or routing claims. Public caller identity contains the user/role/scope\nprojection; the customer route remains private request state.\n\nConnector-backed tools ask the broker for a route-bound delegated credential; only the endpoint key and\nfingerprint enter broker cache/single-flight state or the assertion. The route claim and inbound MCP bearer\ntoken never reach tools, connectors, widgets, model output, or downstream systems. Confirmed actions keep\nthe same URL-blind binding only in private continuation state and reject acceptance-time drift.\n" },
+    { relPath: "examples/customer-auth/README.md", content: "# Customer Auth - OIDC identity and customer-routed APIs\n\nFor a visitor who starts before signup, use the [Stateful Draft reference](../stateful-draft/README.md)\nalongside this authenticated backend integration.\n\nThis curated example owns the customer/end-user authentication capability slot. It proves that a SaaS app\ncan protect an MCP endpoint with direct OIDC, retain role/scope-based tool authorization, and route ordinary\nreads and confirmed actions to the API origin selected by the verified customer's identity provider.\n\nDirect MCP calls obtain the private route from verified OIDC claims; embedded sessions obtain it from the authenticated backend. Both keep routes out of model and browser state.\n\nThe public developer entrypoint is [`src/server.ts`](src/server.ts). It exposes a deliberately small MCP\nsurface for organization discovery and app lifecycle operations:\n\n- `help` explains the product without customer identity.\n- `list_my_organizations` publicly advertises its descriptor but requires `organizations:read` to list the signed-in customer’s organizations.\n- `list_org_apps` uses `authorization.discovery: 'public'` to expose its descriptor on an anonymously\n  accessible endpoint. Execution still requires `org_apps:read` and `org_admin` or `org_member`. Visibility\n  grants no permissions, records, role disclosure, or product-guide eligibility. ChatGPT sign-in is unproven.\n- `archive_org_app` archives one app only after exact runtime confirmation. It requires the\n  `org_apps:write` scope and `org_admin` role.\n\nThe tools chain: `list_my_organizations` surfaces the `org_id`s the customer can act on,\n`list_org_apps` takes one of those ids, and `archive_org_app` accepts the selected app id. Tool code remains\nindependent of the selected origin.\n\nThe typed `agentGuide` retains only complete workflows the verified caller can execute. Public descriptor discovery does not grant workflow access. See the [runtime guide](https://docs.noodleseed.dev/docs/guides/product-agent-guides#use-the-guide-at-runtime) for embedded behavior and the draft MCP Skills preview.\n\n## Declare the customer endpoint\n\n`customerEndpoint` names one private routing authority and bounds the origins an IdP may select:\n\n```ts\nconst customerApi = customerEndpoint('customer_api', {\n  allowedHttpsHostSuffixes: ['api.noodleseed.dev'],\n});\n```\n\nUse either non-empty `allowedHttpsHostSuffixes` or non-empty `allowedHttpsOrigins`, never both. Exact-origin\npolicies may include a non-default port. Suffix policies match only the exact hostname or dot-boundary\nsubdomains on port 443. A routed connector must not add `allowedOrigins`; its endpoint policy is the egress\nallowlist.\n\nThe connector uses that declaration as its normal base URL. Its token endpoint remains a fixed, independently\nvalidated HTTPS URL:\n\n```ts\nconst api = connector('noodleseed_app_api')\n  .version('1.0.0')\n  .http({\n    baseUrl: customerApi,\n    auth: {\n      kind: 'delegatedTokenExchange',\n      tokenUrl: 'https://id.noodleseed.dev/oauth/token',\n      clientId: variable('CUSTOMER_API_CLIENT_ID'),\n      clientSecret: secret('CUSTOMER_API_CLIENT_SECRET'),\n      scopes: ['organizations:read', 'org_apps:read', 'org_apps:write'],\n      audience: 'noodleseed-customer-api',\n    },\n    operations: {\n      // read and action operations...\n    },\n  });\n```\n\n`delegatedTokenExchange` consumes a verified customer caller; an MCP access mode does not create one. The\nserver must declare `customerAuth.*(...)` or `embeddedAssistant(...)` so Noodle Seed can establish the caller\nsubject, issuer, and audience. Otherwise `noodle validate`, `noodle auth doctor`, and deploy fail early with\n`delegated_token_exchange_identity_required`, before secrets are resolved or any connector egress. A\nsuccessful local Devtools exchange is not evidence that the hosted server has an identity source. Devtools\nsupplies a separate, loopback-only local identity context that is never accepted by hosted deployment.\n\nAt both connector and operation level, auth must be omitted or use `delegatedTokenExchange`. The compiler\nvalidates the concrete connector definition emitted from TypeScript, including connector defaults and\noperation overrides, and reports the exact failing auth path and kind. Do not keep a bearer, API-key,\nclient-credentials, or managed-provider fallback for local mode; use operation fakes while leaving auth\ndeclarative.\n\n## Map the endpoint from verified OIDC\n\nThe IdP claim contains the complete base URL, including an optional base path. Routing is separate from the\npublic `${user}` expression scope:\n\n```ts\nauth: customerAuth.oidc({\n  issuer: 'https://id.noodleseed.dev',\n  audience: 'noodleseed-customer-auth-prod',\n  claims: {\n    id: 'sub',\n    email: 'email',\n    name: 'name',\n    orgs: 'permissions.orgs',\n    roles: 'permissions.roles',\n    scopes: 'permissions.scopes',\n  },\n  routing: {\n    endpoints: {\n      customer_api: { claim: 'tenant.api_base_url' },\n    },\n  },\n}),\n```\n\nFor federated OIDC, put the same endpoint map on every issuer. Claim paths may differ, but each issuer must\nmap every endpoint the app uses:\n\n```ts\nauth: customerAuth.federatedOidc({\n  issuers: [\n    {\n      issuer: 'https://id.customer-a.com',\n      audience: 'noodleseed-customer-auth-prod',\n      routing: {\n        endpoints: {\n          customer_api: { claim: 'tenant.api_base_url' },\n        },\n      },\n    },\n    {\n      issuer: 'https://login.customer-b.com',\n      audience: 'noodleseed-customer-auth-prod',\n      routing: {\n        endpoints: {\n          customer_api: { claim: 'organization.routes.customer_api' },\n        },\n      },\n    },\n  ],\n}),\n```\n\nAt runtime, Noodle Seed validates the configured stable audience, associates the caller with the exact\ntransport-derived MCP resource, projects the route into private request state, applies its policy, and\nfreezes it for the call. Missing, malformed, or\ndisallowed claims return `connector_route_unavailable` before credential lookup or connector egress.\nResolved URLs never enter artifacts, `${user}`, logs, model output, widgets, public confirmation review,\nbroker cache keys, or delegated exchange assertions.\n\nRouted reads work in tools, including declared nested calls. Routed actions require exact\n`annotations.confirm: true`; otherwise they fail with `customer_endpoint_action_unsupported`. Routed\nresources, prompts, and ambient context fail with `customer_endpoint_surface_unsupported`.\n\nThe flagship's routed action uses the normal TypeScript action helper:\n\n```ts\ntool('archive_org_app', {\n  authorization: {\n    requiredScopes: ['org_apps:write'],\n    allowedRoles: ['org_admin'],\n  },\n  annotations: annotations.openAction({ destructive: false, confirm: true }),\n  // input, output, and the normal connectors.app_api.archiveOrgApp(...) call...\n});\n```\n\nThe flagship also opts into the current stateless hosted MCP path:\n\n```ts\ninteractions: {\n  confirmationFallback: 'host',\n},\n```\n\nA bidirectional client that negotiated form elicitation can complete the standard confirmation exchange\ninstead. The explicit host fallback trusts the MCP host to have collected native write approval before the\ntool call reaches Noodle Seed; it is never inferred from client identity and does not replace auth, policy,\nor accurate action/destructive annotations. Omit the fallback when connected hosts are not trusted to\nprovide that approval. If neither standard confirmation nor the fallback is available, the action fails\nclosed with `interaction_unavailable`.\n\nPreparation stores only sorted route `{ key, fingerprint }` bindings in its private server-held\ncontinuation; the public review exposes none of them. Acceptance re-resolves the current request route and\nreturns `invalid_continuation` if it is missing or changed, before policy, credentials, or egress. A match\nreuses the current frozen snapshot for the action and all nested or later reads.\n\nThe application developer owns the direct/federated authorization server. It must publish its path-inserted\nRFC 8414 document as direct HTTP 200 JSON with exact issuer and HTTPS authorization/token/registration/JWKS\nendpoints, authorization-code and refresh grants, PKCE S256, public-client auth method `none`, RFC 8707\nresource handling, and public signing keys. It validates each exact MCP resource on authorize, code exchange,\nand refresh, then maps approved versions of this app/environment to `noodleseed-customer-auth-prod`. Other\napps and environments use distinct audiences.\n\nRun `noodle auth doctor src/server.ts` before sharing. Its bounded, read-only probes never register a client.\nAdding the embedded assistant does not choose or rewrite MCP customer auth. Its authenticated backend may\nbind `routing.endpoints.customer_api` during assistant-session exchange from server-owned membership data;\ndirect MCP requests continue to resolve the same endpoint from the configured verified OIDC claim.\n\n## Per-tool authorization remains independent\n\nThe mapped `roles` and `scopes` paths are read only after OIDC verification. The restricted tool declares its\nrule beside the rest of its public contract:\n\n```ts\ntool('list_org_apps', {\n  authorization: {\n    discovery: 'public',\n    requiredScopes: ['org_apps:read'],\n    allowedRoles: ['org_admin', 'org_member'],\n  },\n  // input, output, and fulfilment...\n});\n```\n\nEvery required scope must be present and at least one allowed role must match. When both lists are declared,\nboth conditions apply. In mixed customer mode, `discovery: 'public'` exposes this descriptor before sign-in;\nexecution still requires those scopes and roles. Other restricted tools remain filtered by authorization.\nRoute availability never changes discovery, and unauthorized direct calls fail closed.\n\nTool code calls the connector normally:\n\n```ts\nfulfil({ input, connectors }) {\n  const apps = connectors.app_api.listOrgApps({\n    org_id: input.org_id,\n    skip: input.skip,\n    limit: input.limit,\n  });\n\n  return { result: apps.result };\n}\n```\n\nThe broker exchanges a short-lived, platform-signed assertion at the fixed token endpoint and caches the\nresult by caller, connector, scopes, and a route fingerprint. The assertion carries only the route key and\nfingerprint, never the URL. The MCP access token is never forwarded to the customer API. The exchange wire\ncontract lives in docs/spec/connectors.md.\n\nFirebase and Microsoft remain supported managed adapters; their provider-specific contracts and tests live\nin docs/spec/auth-and-policy.md and the SharePoint flagship.\n\n## Supabase direct-OIDC access-token hook\n\nDynamic Client Registration lets any OAuth client register, so the presence of `client_id` is not approval.\nKeep an operator-controlled client-to-audience map and rewrite `aud` only for an exact mapped client. For a\ndynamically registered client, review its generated client ID, name, and exact redirect URIs in the consent\nflow before adding the mapping. Each new registration needs its own row; never approve by name or prefix.\n\nReplace `<approved-oauth-client-id>` with the reviewed client ID and `<stable-mcp-audience>` with the exact\nvalue configured in `customerAuth.oidc`:\n\n```sql\ncreate table if not exists public.mcp_oauth_client_audiences (\n  client_id text primary key check (btrim(client_id) <> ''),\n  audience text not null check (btrim(audience) <> '')\n);\n\nrevoke all on table public.mcp_oauth_client_audiences from authenticated, anon, public;\ngrant usage on schema public to supabase_auth_admin;\ngrant select on table public.mcp_oauth_client_audiences to supabase_auth_admin;\n\ninsert into public.mcp_oauth_client_audiences (client_id, audience)\nvalues ('<approved-oauth-client-id>', '<stable-mcp-audience>')\non conflict (client_id) do update set audience = excluded.audience;\n\ncreate or replace function public.mcp_access_token_hook(event jsonb)\nreturns jsonb\nlanguage plpgsql\nstable\nas $$\ndeclare\n  claims jsonb := coalesce(event->'claims', '{}'::jsonb);\n  oauth_client_id text := nullif(btrim(claims->>'client_id'), '');\n  mapped_audience text;\nbegin\n  if oauth_client_id is not null then\n    select mapping.audience\n      into mapped_audience\n      from public.mcp_oauth_client_audiences as mapping\n      where mapping.client_id = oauth_client_id;\n  end if;\n\n  if mapped_audience is not null then\n    claims := jsonb_set(\n      claims,\n      '{aud}',\n      to_jsonb(mapped_audience),\n      true\n    );\n  end if;\n\n  return jsonb_build_object('claims', claims);\nend;\n$$;\n\ngrant execute on function public.mcp_access_token_hook(jsonb) to supabase_auth_admin;\nrevoke execute on function public.mcp_access_token_hook(jsonb) from authenticated, anon, public;\n```\n\n| Token source | Mapping | Resulting `aud` |\n| --- | --- | --- |\n| Approved OAuth client | Exact client row | Mapped stable MCP audience |\n| Unrelated or unknown OAuth client | No row | Original Supabase audience |\n| Browser session | No `client_id` | Original Supabase audience |\n\nSelect this function under Supabase Auth Hooks before completing the interactive verification below.\n\n## Validate\n\n```bash\nnoodle validate examples/customer-auth/src/server.ts --json\nnoodle auth doctor examples/customer-auth/src/server.ts --json\nnoodle test examples/customer-auth/src/server.ts --json\n```\n\nThe doctor proves metadata and JWKS readiness without registering a client. For this protected app,\n`noodle test` proves the anonymous 401 plus exact protected-resource metadata boundary and reports\n`interactiveRequired: true`; neither command proves token issuance or audience verification.\n\nAgainst a deployed customer-protected environment, set a short-lived real customer token only in\n`NOODLE_CUSTOMER_TOKEN` and add `--live --org <org> --app <app> --env <env>`. The live doctor performs\ncredential exchanges without invoking any business tool. Add `--version 1` when testing a pinned version;\nthe reported customer resource must match that versioned MCP endpoint.\n\n## Run locally\n\n```bash\nnoodle devtools examples/customer-auth/src/server.ts\n```\n\nComplete sign-in in Devtools and load the tool list. That authenticated request is the local proof that DCR,\nPKCE, token issuance, issuer/signature verification, the stable audience, and exact-resource binding work\ntogether. Invoke a representative safe read when the configured customer API is available.\n\n### Test delegated exchange locally\n\nLocal customer OIDC sign-in and delegated-exchange assertion trust are two distinct boundaries. OIDC proves\nthe caller to the local MCP server; Devtools uses a separate local issuer only for the RFC 8693 assertion\nsent to the downstream token endpoint. This is the canonical local path and requires no `server.ts` change,\nflag, environment variable, or config surface.\n\n1. Configure the OIDC authorization server for the exact loopback callback and RFC 8707 resource. Do not add\n   the Devtools assertion key to OIDC issuer metadata or change its signing keys.\n2. Start Devtools, complete customer sign-in, and copy the displayed `{ issuer, jwks }` from **Local delegated exchange**.\n3. Pin both values only in the customer-owned development RFC 8693 token endpoint.\n4. Restrict that trust to development client credentials, audience, API, and data.\n5. Invoke the delegated `list_org_apps` tool until its binding reads **Exchange verified**.\n6. Use hosted preview or `noodle auth doctor --live` to prove the production platform issuer.\n\n**Never trust the Devtools issuer in production: anyone holding the local private key could impersonate a customer.**\n\n## Configuration\n\nThe embedded assistant uses a customer-supplied Responses-compatible endpoint, selected explicitly with\n`transport: 'responses'` in `src/server.ts`. Use `transport: 'chat-completions'` or omit the field for a\nChat Completions endpoint. Noodle never falls back between them. Configure its managed values at the Noodle\ndeployment environment; none of these values belongs in the customer web application environment, and the\nAPI key never reaches the browser:\n\nThe assistant session carries a verified user, tenant, deployment, roles, and scopes. For this flagship's\nrouted tools, the embedding backend resolves the signed-in user's cluster from server-owned membership data\nand passes `routing: { endpoints: { customer_api: cluster.apiBaseUrl } }` to\n`createAssistantSession`. Noodle validates and privately stores that route; it is not returned to the\nbrowser. Do not copy the route into page context, session claims, tool input, or model instructions.\n\nThe authenticated assistant surface also declares `accountTier` as a model-visible session claim. Pass it\nfrom the same backend-owned account record as `claims: { accountTier: account.tier }`; undeclared claims are\ndropped. This is personalization context, not authorization: the verified roles/scopes beside each tool and\nthe server-owned customer route remain the enforcement boundaries. The public\n[runtime guide](https://docs.noodleseed.dev/docs/guides/product-agent-guides#use-the-guide-at-runtime)\nexplains how verified session claims constrain the guide content available to the model.\n\n```bash\nnoodle variables set ASSISTANT_ORIGIN https://app.example.com --scope env\nnoodle variables set ASSISTANT_MODEL_BASE_URL https://model.example.com/v1 --scope env\nnoodle variables set ASSISTANT_MODEL your-model --scope env\nnoodle secrets set ASSISTANT_MODEL_API_KEY --scope env\nnoodle variables set CUSTOMER_API_CLIENT_ID your-broker-client-id --scope env\nnoodle secrets set CUSTOMER_API_CLIENT_SECRET --scope env\nnoodle check --target embedded-assistant src/server.ts\n```\n\n`ASSISTANT_ORIGIN` is the operator-owned production embedding origin, so one source can serve every customer\nwithout an application fork. Assistant origins are exact. Production embedding origins must use HTTPS; plain HTTP is accepted only for\nloopback development origins such as `http://localhost:3000`, `http://127.0.0.1:3000`, or\n`http://[::1]:3000`. `noodle dev` serves the MCP project, not that separate embedding application.\n\nThe bounded `presentation` object configures the panel, launcher, header, composer, and messages. Its\nprimitives derive colors from shared server `branding`; raw HTML, CSS, inline SVG, renderer classes, and\ncallbacks are not accepted. This example omits `presentation.panel.surface`, so the renderer keeps the\nopaque default panel treatment while the example's light/dark `branding` surfaces provide its customer colors;\nset the bounded surface to `glass` only when translucency is intentional.\n\nThese TypeScript values remain the reusable developer defaults. After deployment, an environment operator\ncan adjust theme, logo, launcher style, position, and the bounded color palette from the Console's\n**Assistant** tab or `noodle assistant appearance` without changing the customer's embed code. See the\n[embedded assistant guide](https://docs.noodleseed.dev/docs/guides/embedded-assistant) for precedence and reset\nbehavior.\n\nCreate the backend credential after deployment. The CLI writes it to a mode-0600 file and never prints the\nsecret:\n\n```bash\nnoodle assistant clients create --name web --org noodleseed --app customer-auth --env prod\n```\n\nOnly the Noodle service URL, assistant client ID, and assistant client secret belong in the authenticated\ncustomer backend. The model URL, model name, and model API key remain managed by the Noodle deployment.\n\nThe customer's authenticated backend calls `createAssistantSession(...)` from\n`@noodleseed/assistant/server`, passing the already-verified user and browser origin. The browser then uses\nthe returned short-lived session through the managed Web Component/React renderer or a customer-owned UI:\n\n```bash\npnpm add @noodleseed/assistant\n```\n\n```tsx\nimport { NoodleAssistant } from '@noodleseed/assistant/react';\n\n<NoodleAssistant\n  sessionEndpoint=\"/api/noodle-assistant/session\"\n  theme={resolvedTheme}\n  onSessionExpired={() => console.info('Assistant session renewed')}\n/>;\n```\n\n`resolvedTheme` is the application's current `'light' | 'dark'` value. Use `theme=\"auto\"` only when the\nbrowser operating-system preference is intentionally authoritative.\n\n### Minimal fail-closed custom renderer skeleton\n\nUse the renderer-free hook only when the product has a concrete reason to own the conversation UI. This\nminimal skeleton keeps the canonical client and App host, but intentionally refuses confirmation and input\nacceptance until the application implements their complete schema-aware presentation. Start with the managed\nrenderer unless the application accepts every obligation below.\n\n```tsx\n'use client';\n\nimport { useEffect, useState } from 'react';\nimport { NoodleAppView } from '@noodleseed/assistant/react';\nimport { useNoodleAssistant } from '@noodleseed/assistant/react/client';\n\nexport function CustomerAssistant({\n  principalKey,\n  resolvedTheme,\n  onSignInRequested,\n}: {\n  principalKey: string;\n  resolvedTheme: 'light' | 'dark';\n  onSignInRequested: (request: {\n    signInTicket: string;\n    expiresAt: string;\n  }) => Promise<'started' | 'cancelled'>;\n}) {\n  const [draft, setDraft] = useState('');\n  const [sessionNotice, setSessionNotice] = useState('');\n  const [turnNotice, setTurnNotice] = useState('');\n  const [pendingSignInTicket, setPendingSignInTicket] = useState<string>();\n  const { client, messages, suggestions, status, error } = useNoodleAssistant({\n    sessionEndpoint: '/api/noodle-assistant/session',\n    principalKey,\n  });\n  const busy = status === 'submitted' || status === 'streaming';\n  const settle = (operation: Promise<void>) => {\n    void operation.catch(() => {\n      // The hook exposes this same structured failure through `error`.\n    });\n  };\n  useEffect(\n    () =>\n      client.subscribe((event) => {\n        if (event.event === 'session_expired') setSessionNotice('Session expired.');\n        if (event.event === 'session_started' || event.event === 'session_reset') {\n          setSessionNotice('');\n        }\n      }),\n    [client],\n  );\n\n  return (\n    <section aria-label=\"Assistant\" aria-busy={busy}>\n      {messages.map((message) => (\n        <article key={message.id} data-role={message.role}>\n          {message.parts.map((part, index) => {\n            if (part.type === 'text') return <p key={index}>{part.text}</p>;\n            if (part.type === 'data-confirmation') {\n              const review = part.data;\n              return (\n                <section key={review.id} aria-label=\"Review proposed action\">\n                  <h3>{review.title ?? 'Review proposed action'}</h3>\n                  {review.description ? <p>{review.description}</p> : null}\n                  <p>This custom renderer has not implemented a complete schema-aware review.</p>\n                  <button\n                    disabled={busy || review.status !== 'pending'}\n                    onClick={() => settle(client.respond(review.id, { action: 'decline' }))}\n                  >\n                    Don't proceed\n                  </button>\n                  <button\n                    disabled={busy || review.status !== 'pending'}\n                    onClick={() => settle(client.respond(review.id, { action: 'cancel' }))}\n                  >\n                    Cancel\n                  </button>\n                </section>\n              );\n            }\n            if (part.type === 'data-input-request') {\n              const request = part.data;\n              return (\n                <section key={request.id} aria-label=\"Assistant needs input\">\n                  <p>{request.message}</p>\n                  {/* request.requestedSchema is the sole input-form contract. */}\n                  <p>This custom renderer has not implemented the requested schema form.</p>\n                  <button\n                    disabled={busy || request.status !== 'pending'}\n                    onClick={() => settle(client.respond(request.id, { action: 'decline' }))}\n                  >\n                    Don't proceed\n                  </button>\n                  <button\n                    disabled={busy || request.status !== 'pending'}\n                    onClick={() => settle(client.respond(request.id, { action: 'cancel' }))}\n                  >\n                    Cancel\n                  </button>\n                </section>\n              );\n            }\n            if (part.type === 'data-tool-result') {\n              return (\n                <p key={part.data.id} role=\"status\">\n                  A result is available, but this renderer has no trusted presentation for it.\n                </p>\n              );\n            }\n            if (part.type === 'data-view') {\n              return (\n                <NoodleAppView\n                  key={`${part.data.id}:${part.data.resourceUri}`}\n                  client={client}\n                  view={part.data}\n                  theme={resolvedTheme}\n                />\n              );\n            }\n            if (part.type === 'data-sign-in') {\n              const request = part.data;\n              return (\n                <section key={request.id} aria-label=\"Sign in required\">\n                  <p>Continue with your account to use this capability.</p>\n                  <button\n                    disabled={busy || pendingSignInTicket !== undefined}\n                    onClick={() => {\n                      setPendingSignInTicket(request.signInTicket);\n                      void Promise.resolve()\n                        .then(() =>\n                          onSignInRequested({\n                            signInTicket: request.signInTicket,\n                            expiresAt: request.expiresAt,\n                          }),\n                        )\n                        .then(\n                          (result) => {\n                            if (result === 'cancelled') setPendingSignInTicket(undefined);\n                          },\n                          () => setPendingSignInTicket(undefined),\n                        );\n                    }}\n                  >\n                    Sign in\n                  </button>\n                </section>\n              );\n            }\n            return <p key={index}>Unsupported assistant content.</p>;\n          })}\n        </article>\n      ))}\n      <p role=\"status\" aria-live=\"polite\">\n        {sessionNotice || turnNotice || (busy ? 'Assistant is working' : '')}\n      </p>\n      {suggestions?.prompts.length ? (\n        <nav aria-label=\"Suggested messages\">\n          {suggestions.prompts.map((prompt) => (\n            <button\n              key={prompt}\n              type=\"button\"\n              disabled={busy}\n              onClick={() => {\n                setTurnNotice('');\n                settle(client.sendMessage(prompt));\n              }}\n            >\n              {prompt}\n            </button>\n          ))}\n        </nav>\n      ) : null}\n      {error ? <p role=\"alert\">The assistant could not complete that request.</p> : null}\n      <form\n        onSubmit={(event) => {\n          event.preventDefault();\n          const message = draft.trim();\n          if (!message) return;\n          setDraft('');\n          setTurnNotice('');\n          settle(client.sendMessage(message));\n        }}\n      >\n        <input\n          aria-label=\"Message\"\n          value={draft}\n          onChange={(event) => setDraft(event.currentTarget.value)}\n        />\n        {busy ? (\n          <button\n            type=\"button\"\n            onClick={() => {\n              client.abort();\n              setTurnNotice('Response stopped. This does not undo a started action.');\n            }}\n          >\n            Stop\n          </button>\n        ) : (\n          <button type=\"submit\">Send</button>\n        )}\n      </form>\n    </section>\n  );\n}\n```\n\n`principalKey` stays in the browser. Change it whenever the authenticated user or tenant changes; the hook\nthen aborts and clears the prior session and transcript. The sample does not render Confirm until the host\nimplements a complete schema-aware review, and it does not accept elicitation until a portable form covers\n`requestedSchema`; use the managed renderer instead of shipping either unsupported branch. Suggestions are\nhook-owned and submit ordinary messages through `client.sendMessage`.\n\n`data-sign-in` has no status and is never passed to `client.respond`. Bind `signInTicket` to the host's\nshort-lived login transaction without putting it in URLs, logs, analytics, or durable browser storage. Resolve\nthe callback as `started` only after the host owns one active transaction; return `cancelled` or reject when no\ntransaction started so the renderer restores the sign-in affordance. A\nmixed renderer uses separate public and authenticated clients: the public shell uses `embedId`, `serviceUrl`,\nand a visitor principal key; after login, the destination mounts a new client against the same-origin session\nendpoint under the user/tenant principal key. Never pass both source options or mutate the public client's\nsource in place. `session_expired` is observational: the client owns its single safe pre-execution re-exchange.\nNever add a generic Retry button or replay an interaction decision automatically.\n\nFor `data-tool-result`, do not expose technical tool names or raw JSON. Prefer the linked `data-view`;\notherwise map a known bounded result to application-trusted UI or keep the explicit unsupported state. For\n`data-view`, use `<noodle-app-view>` or its React `NoodleAppView` adapter. The element's semantic lifecycle\nidentity is the client plus `view.id` plus `view.resourceUri`, so payload/callback rerenders keep the iframe\nand only a different view, disconnect, or App teardown request retires the bridge.\nApp views remain inline by default: the host advertises only inline presentation and rejects a widget's\nfullscreen request. A customer-owned renderer may opt in explicitly with `allowFullscreen` on\n`NoodleAppView` or `allow-fullscreen` on `<noodle-app-view>` only when fullscreen is part of its intended\nexperience. When fullscreen is accepted, the shared host adds a top-right exit control that returns the same\nmounted App to inline mode without discarding its state.\nNever inject `part.data.html`, assign it to `srcdoc`, fetch a `ui://` URI, or reproduce the bridge directly. Pages with a\nContent-Security-Policy must include the Noodle service origin in both `connect-src` and `frame-src`.\n\nBefore the production-equivalent host build, run the presence-only handoff check:\n\n```sh\nnoodle assistant embed --check --json\n```\n\nAdd application-owned delegated-exchange requirements with repeatable `--require-env NAME` flags. The JSON\nreports required and missing names, CSP status, and post-deploy probes without returning environment values\nor writing scaffold files. Map the names through the production secret manager, CI environment, and any\nsecret allowlist; regenerate existing framework-owned environment binding types before the build. Default\nDevtools/model exercises to synthetic data, and obtain approval before sending real connector data to an\nexternal model.\n\nRead `evidence.levels` in order: static host, local contract, hosted session, production browser, then\noperations. Stop at `evidence.firstUnproven`. A static result may be `passed`, `partial`, or `failed`; even\ntop-level `ready: true` means only that no static blocker was detected. It never proves the local session\ncontract or a production-browser flow. Value-free diagnostics call out an MCP endpoint used as the service\nURL, an HTML redirect risk, an SSR mount risk, and a cross-origin session endpoint. The command has no live\nor browser flag; its `postDeployProbes` are next actions, not executed evidence.\n\nAfter deployment, use the assistant doctor to verify the embed client, exact model transport, and static\nsession boundary:\n\n```sh\nnoodle assistant doctor --user-id <real-test-user> --origin \"$PUBLIC_APP_ORIGIN\" --org <org> --app <app> --env <env>\n```\n\nThe doctor makes one bounded synthetic model request without business tools or customer conversation data;\nfailures show only a redacted category, status, and retryability. It does not invent or test an\napplication-specific customer route. Prove routed assistant tools by\nhaving the authenticated embedding backend pass the user's server-verified endpoint during session\nexchange, then invoke one representative safe read.\n\nDo not send a first turn on mount by default. React effect cleanup can suppress one provisional Strict Mode\neffect, but it cannot make a remount, dependency change, or client replacement idempotent. Require an\nexplicit user action unless the host owns durable one-shot state and an application idempotency key that\nmakes repeated sends safe.\n\nFor a chat-first custom host, raw `tool_started` supplies the direct call `id` and technical tool name. Map\nknown tools to concise application copy and use a neutral fallback. Reserve a stable `role=\"status\"` region\nfor thinking, tool activity, and the view skeleton; switch to the ready `<noodle-app-view>` (or React\n`NoodleAppView`) on `view_available` or to `role=\"alert\"` on error. Decorative skeleton shapes stay hidden from assistive technology, and shimmer\nor transition motion is disabled under `prefers-reduced-motion`.\n\nUse `${view.id}:${view.resourceUri}` as transport identity. Different call IDs are distinct invocations and\nmust not be deduplicated generically. If this application intentionally owns one current panel for a known\nresource, declare an application-owned slot for that resource and replace only that slot.\n\n### Framework-neutral DOM client\n\nSubscribe to the DOM-free client directly without a component wrapper and use the isolated App host.\nIt exposes the same conversation as headless AI SDK `UIMessage` state, including typed confirmation, input,\ntool-result, and linked-view parts:\n\n```html\n<div id=\"assistant-app-views\"></div>\n```\n\n```ts\nimport '@noodleseed/assistant/app-view';\nimport {\n  type AssistantViewAvailableDetail,\n  type NoodleAppViewElement,\n} from '@noodleseed/assistant/app-view';\nimport { createAssistantClient } from '@noodleseed/assistant/client';\n\nconst assistant = createAssistantClient({\n  sessionEndpoint: '/api/noodle-assistant/session',\n});\nconst appViews = document.querySelector('#assistant-app-views');\nif (!appViews) throw new Error('Missing App views host');\nconst mountedViews = new Map<string, NoodleAppViewElement>();\nconst readResolvedTheme = (): 'light' | 'dark' =>\n  document.documentElement.classList.contains('dark') ? 'dark' : 'light';\nlet resolvedTheme: 'light' | 'dark' = readResolvedTheme();\nconst syncResolvedTheme = () => {\n  resolvedTheme = readResolvedTheme();\n  for (const mountedView of mountedViews.values()) mountedView.theme = resolvedTheme;\n};\nnew MutationObserver(syncResolvedTheme).observe(document.documentElement, {\n  attributes: true,\n  attributeFilter: ['class'],\n});\nconst appViewFor = (view: AssistantViewAvailableDetail) => {\n  const key = `${view.id}:${view.resourceUri}`;\n  let appView = mountedViews.get(key);\n  if (!appView) {\n    appView = document.createElement('noodle-app-view') as NoodleAppViewElement;\n    appView.client = assistant;\n    mountedViews.set(key, appView);\n    appViews.append(appView);\n  }\n  appView.theme = resolvedTheme;\n  return appView;\n};\n\nassistant.subscribeChat((state) => {\n  renderUIMessageState(state, {\n    respond: (id, response) => assistant.respond(id, response),\n  });\n  const activeViewKeys = new Set<string>();\n  for (const message of state.messages) {\n    for (const part of message.parts) {\n      if (part.type === 'data-view') {\n        const key = `${part.data.id}:${part.data.resourceUri}`;\n        activeViewKeys.add(key);\n        appViewFor(part.data).view = part.data;\n      }\n    }\n  }\n  for (const [key, mountedView] of mountedViews) {\n    if (!activeViewKeys.has(key)) {\n      mountedView.remove();\n      mountedViews.delete(key);\n    }\n  }\n});\n```\n\n`renderUIMessageState` is application code. It must present a complete schema-aware confirmation or input\nform and require an explicit user gesture before using `respond`; never call `respond` while scanning a\ntranscript snapshot.\n\n`theme=\"auto\"` follows the operating-system preference, not a SaaS-owned toggle. Pass the resolved\n`light`/`dark` theme to `NoodleAssistant` and `<noodle-app-view>`/`NoodleAppView`; updates reach mounted MCP Apps without a\nremount. CSS custom properties inherit through the host, and documented `--ns-assistant-*` variables remain\nthe final integration escape hatch. Server `branding` is shared by widgets and the assistant; there is no\nsecond branding declaration. Text streams progressively. Expired turns re-exchange and retry once;\nconfirmations never replay automatically.\n\nThe customer IdP must place the full tenant API base URL in `tenant.api_base_url`. For example, one verified\ncustomer may receive `https://customer-a.api.noodleseed.dev/v1` and another\n`https://customer-b.api.noodleseed.dev/v1`; both satisfy the declared suffix policy. Application code,\ndeployment variables, and connector arguments do not select the tenant route.\n\n`CUSTOMER_API_CLIENT_ID` and `CUSTOMER_API_CLIENT_SECRET` authenticate only the broker to the fixed exchange\nendpoint. They are not customer API bearer tokens. The exchange endpoint verifies the platform-signed\nsubject assertion and mints a short-lived token scoped to the signed-in user and route binding.\n\n## Launch and qualified-usage proof\n\nFor launch, browser verification, and qualified usage, follow the [embedded assistant guide](https://docs.noodleseed.dev/docs/guides/embedded-assistant).\n\n## Deploy customer-protected to Noodle Seed Cloud\n\n```bash\nnoodle deploy examples/customer-auth/src/server.ts \\\n  --org noodleseed \\\n  --app customer-auth \\\n  --env prod \\\n  --access customers\n```\n\nEndpoint:\n\n```text\nhttps://cloud.noodleseed.dev/o/noodleseed/customer-auth/mcp\n```\n\n## Preview anonymous Help with customer sign-in\n\nUse `noodle dev examples/customer-auth/src/server.ts --access mixed`. Help remains available before sign-in;\nprotected reads advertise descriptors and require their verified scopes/roles to execute. Customer mode\nremains the default. Local Devtools retries a protected call after successful sign-in; cancellation executes\nnothing and leaves Help available. With a hosted service, a new target may use\n`--access mixed` only after every customer tool has an authorization rule. For an existing customer-only\ntarget, preserve its org/app/env, endpoint, issuer, and audience. Follow the public guide: verify an inactive\n`customers` record for the exact version, creating it by unchanged secured redeploy if absent; add and\nvalidate every tool rule; deploy the prepared source as `customers`; recheck the rollback; then adopt mixed\naccess. On pilot failure, use\n`noodle rollback <deployment-id>` with the same org/app/env. This app-history rollback is separate from the\ncompatible hosted service-release floor. Keep the public Help endpoint through the post-deployment ChatGPT\nand customer API pilot. Local behavior and wire checks do not prove that host\njourney. See the\n[customer auth rollback and adoption procedure](https://docs.noodleseed.dev/docs/guides/customer-auth#preserve-an-app-rollback-target-and-adopt)\nfor the exact commands and checks.\n\n## Auth boundary\n\nNoodle Seed verifies the configured OIDC issuer and stable audience, then binds the exact transport-derived\nMCP resource before reading identity or routing claims. Public caller identity contains the user/role/scope\nprojection; the customer route remains private request state.\n\nConnector-backed tools ask the broker for a route-bound delegated credential; only the endpoint key and\nfingerprint enter broker cache/single-flight state or the assertion. The route claim and inbound MCP bearer\ntoken never reach tools, connectors, widgets, model output, or downstream systems. Confirmed actions keep\nthe same URL-blind binding only in private continuation state and reject acceptance-time drift.\n" },
     { relPath: "examples/customer-auth/noodle.json", content: "{\n  \"entrypoint\": \"src/server.ts\",\n  \"name\": \"customer-auth\"\n}\n" },
     { relPath: "examples/customer-auth/package.json", content: "{\n  \"name\": \"customer-auth\",\n  \"version\": \"0.1.0\",\n  \"private\": true,\n  \"type\": \"module\",\n  \"scripts\": {\n    \"test\": \"vitest run\",\n    \"validate\": \"noodle validate\",\n    \"dev\": \"noodle dev\",\n    \"deploy\": \"noodle deploy\"\n  },\n  \"devDependencies\": {\n    \"@noodleseed/one\": \"latest\",\n    \"vitest\": \"latest\"\n  }\n}\n" },
-    { relPath: "examples/customer-auth/src/server.ts", content: "import {\n  annotations,\n  authenticatedWebsite,\n  connector,\n  customerAuth,\n  customerEndpoint,\n  embeddedAssistant,\n  openAICompatible,\n  secret,\n  server,\n  tool,\n  variable,\n  z,\n} from '@noodleseed/one';\n\nconst customerApi = customerEndpoint('customer_api', {\n  allowedHttpsHostSuffixes: ['api.noodleseed.dev'],\n});\nconst assistantOrigin = variable('ASSISTANT_ORIGIN');\n\nconst noodleseedApi = connector('noodleseed_app_api')\n  .version('1.0.0')\n  .http({\n    baseUrl: customerApi,\n    auth: {\n      kind: 'delegatedTokenExchange',\n      tokenUrl: 'https://id.noodleseed.dev/oauth/token',\n      clientId: variable('CUSTOMER_API_CLIENT_ID'),\n      clientSecret: secret('CUSTOMER_API_CLIENT_SECRET'),\n      scopes: ['organizations:read', 'org_apps:read', 'org_apps:write'],\n      audience: 'noodleseed-customer-api',\n    },\n    operations: {\n      list_org_apps: {\n        type: 'read',\n        method: 'GET',\n        path: '/api/organizations/${args.org_id}/apps',\n        query: ['skip', 'limit'],\n        input: z.object({\n          org_id: z.string(),\n          skip: z.number().optional(),\n          limit: z.number().optional(),\n        }),\n        output: z.object({ result: z.unknown().optional() }),\n        response: {\n          result: '${response}',\n        },\n      },\n      list_organizations: {\n        type: 'read',\n        method: 'GET',\n        path: '/api/organizations',\n        output: z.object({ organizations: z.array(z.unknown()).optional() }),\n        response: {\n          organizations: '${response.organizations}',\n        },\n      },\n      archive_org_app: {\n        type: 'action',\n        method: 'POST',\n        path: '/api/organizations/${args.org_id}/apps/${args.app_id}/archive',\n        input: z.object({\n          org_id: z.string(),\n          app_id: z.string(),\n        }),\n        output: z.object({ archived: z.boolean() }),\n        response: {\n          archived: '${response.archived}',\n        },\n      },\n    },\n  });\n\nconst CUSTOMER_AUTH_AGENT_GUIDE = {\n  description:\n    'Use the signed-in customer context to discover organizations, review their Noodle Seed apps, and archive a selected app when authorized.',\n  useWhen: [\n    'A signed-in customer asks which organizations or apps they can access.',\n    'An organization administrator asks to archive one selected app.',\n  ],\n  workflows: [\n    {\n      id: 'find_organizations',\n      title: 'Find the customer organizations',\n      intent: 'Ground later organization-scoped work in the verified customer membership.',\n      steps: [\n        {\n          capability: { kind: 'tool', name: 'list_my_organizations' },\n          guidance: 'Use an organization identifier returned by this read in later steps.',\n        },\n      ],\n    },\n    {\n      id: 'review_organization_apps',\n      title: 'Review apps in one organization',\n      steps: [\n        { capability: { kind: 'tool', name: 'list_my_organizations' } },\n        {\n          capability: { kind: 'tool', name: 'list_org_apps' },\n          guidance: 'List apps only for an organization returned for the signed-in customer.',\n        },\n      ],\n    },\n    {\n      id: 'archive_organization_app',\n      title: 'Archive one organization app',\n      steps: [\n        { capability: { kind: 'tool', name: 'list_my_organizations' } },\n        { capability: { kind: 'tool', name: 'list_org_apps' } },\n        {\n          capability: { kind: 'tool', name: 'archive_org_app' },\n          guidance: 'Archive only the exact app the customer selected after confirmation.',\n        },\n      ],\n    },\n  ],\n  boundaries: [\n    'Never infer an organization or app identifier that was not returned for the signed-in customer.',\n    'Never claim an app was archived until the confirmed action succeeds.',\n  ],\n  examples: [\n    { prompt: 'Which organizations can I access?', workflow: 'find_organizations' },\n    { prompt: 'Show me the apps in this organization.', workflow: 'review_organization_apps' },\n    { prompt: 'Archive the app I selected.', workflow: 'archive_organization_app' },\n  ],\n} as const;\n\nexport default server(\n  'noodleseed_customer_auth',\n  {\n    title: 'NoodleSeed.com Customer Auth',\n    version: '1.0.0',\n    branding: {\n      name: 'Noodle Seed Assistant',\n      accent: '#E85D24',\n      surface: '#FFFFFF',\n      surfaceDark: '#171310',\n      colorScheme: 'auto',\n      theme: {\n        light: { accentText: '#FFFFFF', text: '#1C1714' },\n        dark: { accent: '#FF8A4C', accentText: '#1C100A', text: '#FFF8F2' },\n      },\n    },\n    use: { app_api: noodleseedApi },\n    agentGuide: CUSTOMER_AUTH_AGENT_GUIDE,\n    interactions: { confirmationFallback: 'host' },\n    auth: customerAuth.oidc({\n      issuer: 'https://id.noodleseed.dev',\n      audience: 'noodleseed-customer-auth-prod',\n      claims: {\n        id: 'sub',\n        email: 'email',\n        name: 'name',\n        orgs: 'permissions.orgs',\n        roles: 'permissions.roles',\n        scopes: 'permissions.scopes',\n      },\n      routing: {\n        endpoints: {\n          customer_api: { claim: 'tenant.api_base_url' },\n        },\n      },\n    }),\n    instructions:\n      'Direct/federated MCP OIDC demo. The customer IdP proves identity and privately selects the tenant API base URL, while the broker supplies delegated credentials and confirmed actions stay bound to the reviewed route.',\n    assistant: embeddedAssistant({\n      model: openAICompatible({\n        baseUrl: variable('ASSISTANT_MODEL_BASE_URL'),\n        model: variable('ASSISTANT_MODEL'),\n        apiKey: secret('ASSISTANT_MODEL_API_KEY'),\n        transport: 'responses',\n      }),\n      // Production origins are exact HTTPS; http://localhost:<port> is allowed for local development.\n      access: authenticatedWebsite({\n        origins: [assistantOrigin, 'https://dev.noodleseed.com', 'http://localhost:3000'],\n        sessionClaims: {\n          accountTier: { exposeToModel: true },\n        },\n      }),\n      theme: 'auto',\n      layout: { mode: 'floating', position: 'bottom-center', panelWidth: 970 },\n      behavior: { showPoweredBy: true, showConfirmationDetails: false },\n      labels: {\n        welcomeHeading: 'How can I help with Noodle Seed?',\n        launcherPlaceholder: 'Ask Noodle Seed anything',\n        composerPlaceholder: 'Ask about your apps…',\n      },\n      presentation: {\n        panel: { elevation: 'soft', border: 'subtle' },\n        launcher: {\n          style: 'pill',\n          icon: 'brand-mark',\n          status: 'session',\n          effect: 'pulse',\n        },\n        header: {\n          mark: 'status',\n          badge: { text: 'Workspace online', tone: 'success', indicator: true },\n        },\n        composer: { leadingIcon: 'brand-mark', shape: 'pill' },\n      },\n    }),\n  },\n  [\n    tool('list_org_apps', {\n      title: 'List organization apps',\n      description: 'List NoodleSeed.com apps for an organization from its customer API.',\n      authorization: {\n        requiredScopes: ['org_apps:read'],\n        allowedRoles: ['org_admin', 'org_member'],\n      },\n      input: z.object({\n        org_id: z.string().meta({ title: 'Organization' }),\n        skip: z.number().int().min(0).optional().meta({ title: 'Starting item' }),\n        limit: z.number().int().min(1).max(100).optional().meta({ title: 'Maximum results' }),\n      }),\n      output: z.object({\n        result: z.unknown(),\n      }),\n      annotations: annotations.readOnly(),\n      fulfil({ input, connectors }) {\n        const apps = connectors.app_api.listOrgApps({\n          org_id: input.org_id,\n          skip: input.skip,\n          limit: input.limit,\n        });\n        return {\n          result: apps.result,\n        };\n      },\n    }),\n    tool('list_my_organizations', {\n      title: 'List my organizations',\n      description: 'List the NoodleSeed.com organizations the signed-in customer belongs to.',\n      contextProvider: true,\n      input: z.object({}),\n      // The customer API returns every organization for the signed-in customer in one response, with no\n      // page parameter to pass through, so the bound is declared on the shape. A customer belongs to a\n      // handful of organizations; `noodle check` reports an unbounded list as\n      // `tool_design_output_bounds`.\n      output: z.object({\n        organizations: z.array(z.unknown()).max(100),\n      }),\n      annotations: annotations.readOnly(),\n      fulfil({ connectors }) {\n        const organizations = connectors.app_api.listOrganizations();\n        return {\n          organizations: organizations.organizations,\n        };\n      },\n    }),\n    tool('archive_org_app', {\n      title: 'Archive organization app',\n      description: 'Archive one NoodleSeed.com app through its customer API after confirmation.',\n      authorization: {\n        requiredScopes: ['org_apps:write'],\n        allowedRoles: ['org_admin'],\n      },\n      input: z.object({\n        org_id: z.string().meta({ title: 'Organization' }),\n        app_id: z.string().meta({ title: 'App' }),\n      }),\n      output: z.object({\n        archived: z.boolean(),\n      }),\n      annotations: annotations.openAction({ destructive: false, confirm: true }),\n      fulfil({ input, connectors }) {\n        const result = connectors.app_api.archiveOrgApp({\n          org_id: input.org_id,\n          app_id: input.app_id,\n        });\n        return {\n          archived: result.archived,\n        };\n      },\n    }),\n  ],\n);\n" },
-    { relPath: "examples/customer-auth/test/server.test.ts", content: "import { describe, expect, it } from 'vitest';\nimport app from '../src/server.js';\n\ndescribe('customer-auth example', () => {\n  it('exports a customer-authenticated, customer-branded embedded assistant', async () => {\n    expect(typeof app.toManifest).toBe('function');\n    const manifest = await app.toManifest();\n    expect(manifest.server.assistant).toMatchObject({\n      model: { kind: 'openai-compatible', apiKey: 'ASSISTANT_MODEL_API_KEY' },\n      layout: { mode: 'floating' },\n      presentation: {\n        panel: { elevation: 'soft', border: 'subtle' },\n        launcher: { icon: 'brand-mark', status: 'session', effect: 'pulse' },\n        header: { mark: 'status', badge: { text: 'Workspace online', tone: 'success' } },\n      },\n    });\n    expect(manifest.server.assistant?.allowedOrigins).toEqual([\n      '${env.ASSISTANT_ORIGIN}',\n      'https://dev.noodleseed.com',\n      'http://localhost:3000',\n    ]);\n    expect(manifest.server.assistant?.sessionClaims).toEqual({\n      accountTier: { exposeToModel: true },\n    });\n    expect(manifest.server.branding).toMatchObject({\n      name: 'Noodle Seed Assistant',\n      colorScheme: 'auto',\n    });\n    expect(manifest.server.auth).toEqual({\n      kind: 'oidc',\n      issuer: 'https://id.noodleseed.dev',\n      audience: 'noodleseed-customer-auth-prod',\n      claims: {\n        id: 'sub',\n        email: 'email',\n        name: 'name',\n        orgs: 'permissions.orgs',\n        roles: 'permissions.roles',\n        scopes: 'permissions.scopes',\n      },\n      routing: {\n        endpoints: {\n          customer_api: { claim: 'tenant.api_base_url' },\n        },\n      },\n    });\n    expect(manifest.server.interactions).toEqual({ confirmationFallback: 'host' });\n    expect(manifest.server.agentGuide?.workflows.map((workflow) => workflow.id)).toEqual([\n      'find_organizations',\n      'review_organization_apps',\n      'archive_organization_app',\n    ]);\n    expect(\n      manifest.server.agentGuide?.workflows.find(\n        (workflow) => workflow.id === 'archive_organization_app',\n      )?.steps,\n    ).toEqual([\n      { capability: { kind: 'tool', name: 'list_my_organizations' } },\n      { capability: { kind: 'tool', name: 'list_org_apps' } },\n      {\n        capability: { kind: 'tool', name: 'archive_org_app' },\n        guidance: 'Archive only the exact app the customer selected after confirmation.',\n      },\n    ]);\n    const catalog = app.toConnectorCatalog();\n    expect(catalog?.connectors).toHaveLength(1);\n    expect(catalog?.connectors[0]?.http).toMatchObject({\n      baseUrl: {\n        kind: 'customerEndpoint',\n        name: 'customer_api',\n        policy: { allowedHttpsHostSuffixes: ['api.noodleseed.dev'] },\n      },\n      auth: {\n        kind: 'delegatedTokenExchange',\n        tokenUrl: 'https://id.noodleseed.dev/oauth/token',\n        clientId: '${env.CUSTOMER_API_CLIENT_ID}',\n        clientSecret: 'CUSTOMER_API_CLIENT_SECRET',\n      },\n    });\n    expect(catalog?.connectors[0]?.operations).toMatchObject({\n      list_org_apps: { type: 'read' },\n      list_organizations: { type: 'read' },\n      archive_org_app: { type: 'action', method: 'POST' },\n    });\n    expect(catalog?.connectors[0]?.http).not.toHaveProperty('allowedOrigins');\n    expect(JSON.stringify({ manifest, catalog })).not.toContain('tenant-a.api.noodleseed.dev');\n    expect(manifest.tools.find((tool) => tool.name === 'list_org_apps')?.authorization).toEqual({\n      requiredScopes: ['org_apps:read'],\n      allowedRoles: ['org_admin', 'org_member'],\n    });\n    expect(\n      manifest.tools.find((tool) => tool.name === 'list_my_organizations')?.authorization,\n    ).toBeUndefined();\n    expect(manifest.tools.find((tool) => tool.name === 'archive_org_app')).toMatchObject({\n      authorization: {\n        requiredScopes: ['org_apps:write'],\n        allowedRoles: ['org_admin'],\n      },\n      annotations: {\n        readOnlyHint: false,\n        destructiveHint: false,\n        openWorldHint: true,\n        confirm: true,\n      },\n    });\n    expect(\n      manifest.tools.find((tool) => tool.name === 'list_org_apps')?.annotations?.readOnlyHint,\n    ).toBe(true);\n  });\n});\n" },
+    { relPath: "examples/customer-auth/src/server.ts", content: "import {\n  annotations,\n  authenticatedWebsite,\n  connector,\n  customerAuth,\n  customerEndpoint,\n  embeddedAssistant,\n  openAICompatible,\n  secret,\n  server,\n  tool,\n  variable,\n  z,\n} from '@noodleseed/one';\n\nconst customerApi = customerEndpoint('customer_api', {\n  allowedHttpsHostSuffixes: ['api.noodleseed.dev'],\n});\nconst assistantOrigin = variable('ASSISTANT_ORIGIN');\n\nconst noodleseedApi = connector('noodleseed_app_api')\n  .version('1.0.0')\n  .http({\n    baseUrl: customerApi,\n    auth: {\n      kind: 'delegatedTokenExchange',\n      tokenUrl: 'https://id.noodleseed.dev/oauth/token',\n      clientId: variable('CUSTOMER_API_CLIENT_ID'),\n      clientSecret: secret('CUSTOMER_API_CLIENT_SECRET'),\n      scopes: ['organizations:read', 'org_apps:read', 'org_apps:write'],\n      audience: 'noodleseed-customer-api',\n    },\n    operations: {\n      list_org_apps: {\n        type: 'read',\n        method: 'GET',\n        path: '/api/organizations/${args.org_id}/apps',\n        query: ['skip', 'limit'],\n        input: z.object({\n          org_id: z.string(),\n          skip: z.number().optional(),\n          limit: z.number().optional(),\n        }),\n        output: z.object({ result: z.unknown().optional() }),\n        response: {\n          result: '${response}',\n        },\n      },\n      list_organizations: {\n        type: 'read',\n        method: 'GET',\n        path: '/api/organizations',\n        output: z.object({ organizations: z.array(z.unknown()).optional() }),\n        response: {\n          organizations: '${response.organizations}',\n        },\n      },\n      archive_org_app: {\n        type: 'action',\n        method: 'POST',\n        path: '/api/organizations/${args.org_id}/apps/${args.app_id}/archive',\n        input: z.object({\n          org_id: z.string(),\n          app_id: z.string(),\n        }),\n        output: z.object({ archived: z.boolean() }),\n        response: {\n          archived: '${response.archived}',\n        },\n      },\n    },\n  });\n\nconst CUSTOMER_AUTH_AGENT_GUIDE = {\n  description:\n    'Use the signed-in customer context to discover organizations, review their Noodle Seed apps, and archive a selected app when authorized.',\n  useWhen: [\n    'A signed-in customer asks which organizations or apps they can access.',\n    'An organization administrator asks to archive one selected app.',\n  ],\n  workflows: [\n    {\n      id: 'find_organizations',\n      title: 'Find the customer organizations',\n      intent: 'Ground later organization-scoped work in the verified customer membership.',\n      steps: [\n        {\n          capability: { kind: 'tool', name: 'list_my_organizations' },\n          guidance: 'Use an organization identifier returned by this read in later steps.',\n        },\n      ],\n    },\n    {\n      id: 'review_organization_apps',\n      title: 'Review apps in one organization',\n      steps: [\n        { capability: { kind: 'tool', name: 'list_my_organizations' } },\n        {\n          capability: { kind: 'tool', name: 'list_org_apps' },\n          guidance: 'List apps only for an organization returned for the signed-in customer.',\n        },\n      ],\n    },\n    {\n      id: 'archive_organization_app',\n      title: 'Archive one organization app',\n      steps: [\n        { capability: { kind: 'tool', name: 'list_my_organizations' } },\n        { capability: { kind: 'tool', name: 'list_org_apps' } },\n        {\n          capability: { kind: 'tool', name: 'archive_org_app' },\n          guidance: 'Archive only the exact app the customer selected after confirmation.',\n        },\n      ],\n    },\n  ],\n  boundaries: [\n    'Never infer an organization or app identifier that was not returned for the signed-in customer.',\n    'Never claim an app was archived until the confirmed action succeeds.',\n  ],\n  examples: [\n    { prompt: 'Which organizations can I access?', workflow: 'find_organizations' },\n    { prompt: 'Show me the apps in this organization.', workflow: 'review_organization_apps' },\n    { prompt: 'Archive the app I selected.', workflow: 'archive_organization_app' },\n  ],\n} as const;\n\nexport default server(\n  'noodleseed_customer_auth',\n  {\n    title: 'NoodleSeed.com Customer Auth',\n    version: '1.0.0',\n    branding: {\n      name: 'Noodle Seed Assistant',\n      accent: '#E85D24',\n      surface: '#FFFFFF',\n      surfaceDark: '#171310',\n      colorScheme: 'auto',\n      theme: {\n        light: { accentText: '#FFFFFF', text: '#1C1714' },\n        dark: { accent: '#FF8A4C', accentText: '#1C100A', text: '#FFF8F2' },\n      },\n    },\n    use: { app_api: noodleseedApi },\n    agentGuide: CUSTOMER_AUTH_AGENT_GUIDE,\n    interactions: { confirmationFallback: 'host' },\n    auth: customerAuth.oidc({\n      issuer: 'https://id.noodleseed.dev',\n      audience: 'noodleseed-customer-auth-prod',\n      claims: {\n        id: 'sub',\n        email: 'email',\n        name: 'name',\n        orgs: 'permissions.orgs',\n        roles: 'permissions.roles',\n        scopes: 'permissions.scopes',\n      },\n      routing: {\n        endpoints: {\n          customer_api: { claim: 'tenant.api_base_url' },\n        },\n      },\n    }),\n    instructions:\n      'Direct/federated MCP OIDC demo. The customer IdP proves identity and privately selects the tenant API base URL, while the broker supplies delegated credentials and confirmed actions stay bound to the reviewed route.',\n    assistant: embeddedAssistant({\n      model: openAICompatible({\n        baseUrl: variable('ASSISTANT_MODEL_BASE_URL'),\n        model: variable('ASSISTANT_MODEL'),\n        apiKey: secret('ASSISTANT_MODEL_API_KEY'),\n        transport: 'responses',\n      }),\n      // Production origins are exact HTTPS; http://localhost:<port> is allowed for local development.\n      access: authenticatedWebsite({\n        origins: [assistantOrigin, 'https://dev.noodleseed.com', 'http://localhost:3000'],\n        sessionClaims: {\n          accountTier: { exposeToModel: true },\n        },\n      }),\n      theme: 'auto',\n      layout: { mode: 'floating', position: 'bottom-center', panelWidth: 970 },\n      behavior: { showPoweredBy: true, showConfirmationDetails: false },\n      labels: {\n        welcomeHeading: 'How can I help with Noodle Seed?',\n        launcherPlaceholder: 'Ask Noodle Seed anything',\n        composerPlaceholder: 'Ask about your apps…',\n      },\n      presentation: {\n        panel: { elevation: 'soft', border: 'subtle' },\n        launcher: {\n          style: 'pill',\n          icon: 'brand-mark',\n          status: 'session',\n          effect: 'pulse',\n        },\n        header: {\n          mark: 'status',\n          badge: { text: 'Workspace online', tone: 'success', indicator: true },\n        },\n        composer: { leadingIcon: 'brand-mark', shape: 'pill' },\n      },\n    }),\n  },\n  [\n    tool('help', {\n      title: 'Help with organizations and apps',\n      description: 'Explain what customers can do before they sign in.',\n      input: z.object({}),\n      output: z.object({ help: z.string() }),\n      annotations: annotations.readOnly(),\n      fulfil() {\n        return {\n          help: 'Sign in to browse your organizations and apps. Archiving an app requires an administrator and confirmation.',\n        };\n      },\n    }),\n    tool('list_org_apps', {\n      title: 'List organization apps',\n      description: 'List NoodleSeed.com apps for an organization from its customer API.',\n      authorization: {\n        discovery: 'public',\n        requiredScopes: ['org_apps:read'],\n        allowedRoles: ['org_admin', 'org_member'],\n      },\n      input: z.object({\n        org_id: z.string().meta({ title: 'Organization' }),\n        skip: z.number().int().min(0).optional().meta({ title: 'Starting item' }),\n        limit: z.number().int().min(1).max(100).optional().meta({ title: 'Maximum results' }),\n      }),\n      output: z.object({\n        result: z.unknown(),\n      }),\n      annotations: annotations.readOnly(),\n      fulfil({ input, connectors }) {\n        const apps = connectors.app_api.listOrgApps({\n          org_id: input.org_id,\n          skip: input.skip,\n          limit: input.limit,\n        });\n        return {\n          result: apps.result,\n        };\n      },\n    }),\n    tool('list_my_organizations', {\n      title: 'List my organizations',\n      description: 'List the NoodleSeed.com organizations the signed-in customer belongs to.',\n      authorization: { discovery: 'public', requiredScopes: ['organizations:read'] },\n      contextProvider: true,\n      input: z.object({}),\n      // The API returns all of the caller's organizations without pagination; bound the output shape.\n      output: z.object({\n        organizations: z.array(z.unknown()).max(100),\n      }),\n      annotations: annotations.readOnly(),\n      fulfil({ connectors }) {\n        const organizations = connectors.app_api.listOrganizations();\n        return {\n          organizations: organizations.organizations,\n        };\n      },\n    }),\n    tool('archive_org_app', {\n      title: 'Archive organization app',\n      description: 'Archive one NoodleSeed.com app through its customer API after confirmation.',\n      authorization: {\n        requiredScopes: ['org_apps:write'],\n        allowedRoles: ['org_admin'],\n      },\n      input: z.object({\n        org_id: z.string().meta({ title: 'Organization' }),\n        app_id: z.string().meta({ title: 'App' }),\n      }),\n      output: z.object({\n        archived: z.boolean(),\n      }),\n      annotations: annotations.openAction({ destructive: false, confirm: true }),\n      fulfil({ input, connectors }) {\n        const result = connectors.app_api.archiveOrgApp({\n          org_id: input.org_id,\n          app_id: input.app_id,\n        });\n        return {\n          archived: result.archived,\n        };\n      },\n    }),\n  ],\n);\n" },
+    { relPath: "examples/customer-auth/test/server.test.ts", content: "import { describe, expect, it } from 'vitest';\nimport app from '../src/server.js';\n\ndescribe('customer-auth example', () => {\n  it('exports a customer-authenticated, customer-branded embedded assistant', async () => {\n    expect(typeof app.toManifest).toBe('function');\n    const manifest = await app.toManifest();\n    expect(manifest.server.assistant).toMatchObject({\n      model: { kind: 'openai-compatible', apiKey: 'ASSISTANT_MODEL_API_KEY' },\n      layout: { mode: 'floating' },\n      presentation: {\n        panel: { elevation: 'soft', border: 'subtle' },\n        launcher: { icon: 'brand-mark', status: 'session', effect: 'pulse' },\n        header: { mark: 'status', badge: { text: 'Workspace online', tone: 'success' } },\n      },\n    });\n    expect(manifest.server.assistant?.allowedOrigins).toEqual([\n      '${env.ASSISTANT_ORIGIN}',\n      'https://dev.noodleseed.com',\n      'http://localhost:3000',\n    ]);\n    expect(manifest.server.assistant?.sessionClaims).toEqual({\n      accountTier: { exposeToModel: true },\n    });\n    expect(manifest.server.branding).toMatchObject({\n      name: 'Noodle Seed Assistant',\n      colorScheme: 'auto',\n    });\n    expect(manifest.server.auth).toEqual({\n      kind: 'oidc',\n      issuer: 'https://id.noodleseed.dev',\n      audience: 'noodleseed-customer-auth-prod',\n      claims: {\n        id: 'sub',\n        email: 'email',\n        name: 'name',\n        orgs: 'permissions.orgs',\n        roles: 'permissions.roles',\n        scopes: 'permissions.scopes',\n      },\n      routing: {\n        endpoints: {\n          customer_api: { claim: 'tenant.api_base_url' },\n        },\n      },\n    });\n    expect(manifest.server.interactions).toEqual({ confirmationFallback: 'host' });\n    expect(manifest.server.agentGuide?.workflows.map((workflow) => workflow.id)).toEqual([\n      'find_organizations',\n      'review_organization_apps',\n      'archive_organization_app',\n    ]);\n    expect(\n      manifest.server.agentGuide?.workflows.find(\n        (workflow) => workflow.id === 'archive_organization_app',\n      )?.steps,\n    ).toEqual([\n      { capability: { kind: 'tool', name: 'list_my_organizations' } },\n      { capability: { kind: 'tool', name: 'list_org_apps' } },\n      {\n        capability: { kind: 'tool', name: 'archive_org_app' },\n        guidance: 'Archive only the exact app the customer selected after confirmation.',\n      },\n    ]);\n    const catalog = app.toConnectorCatalog();\n    expect(catalog?.connectors).toHaveLength(1);\n    expect(catalog?.connectors[0]?.http).toMatchObject({\n      baseUrl: {\n        kind: 'customerEndpoint',\n        name: 'customer_api',\n        policy: { allowedHttpsHostSuffixes: ['api.noodleseed.dev'] },\n      },\n      auth: {\n        kind: 'delegatedTokenExchange',\n        tokenUrl: 'https://id.noodleseed.dev/oauth/token',\n        clientId: '${env.CUSTOMER_API_CLIENT_ID}',\n        clientSecret: 'CUSTOMER_API_CLIENT_SECRET',\n      },\n    });\n    expect(catalog?.connectors[0]?.operations).toMatchObject({\n      list_org_apps: { type: 'read' },\n      list_organizations: { type: 'read' },\n      archive_org_app: { type: 'action', method: 'POST' },\n    });\n    expect(catalog?.connectors[0]?.http).not.toHaveProperty('allowedOrigins');\n    expect(JSON.stringify({ manifest, catalog })).not.toContain('tenant-a.api.noodleseed.dev');\n    expect(manifest.tools.find((tool) => tool.name === 'list_org_apps')?.authorization).toEqual({\n      discovery: 'public',\n      requiredScopes: ['org_apps:read'],\n      allowedRoles: ['org_admin', 'org_member'],\n    });\n    expect(\n      manifest.tools.find((tool) => tool.name === 'list_my_organizations')?.authorization,\n    ).toEqual({ discovery: 'public', requiredScopes: ['organizations:read'] });\n    const help = manifest.tools.find((tool) => tool.name === 'help');\n    expect(help).toBeDefined();\n    expect(help?.authorization).toBeUndefined();\n    expect(help?.annotations?.readOnlyHint).toBe(true);\n    expect(manifest.tools.find((tool) => tool.name === 'archive_org_app')).toMatchObject({\n      authorization: {\n        requiredScopes: ['org_apps:write'],\n        allowedRoles: ['org_admin'],\n      },\n      annotations: {\n        readOnlyHint: false,\n        destructiveHint: false,\n        openWorldHint: true,\n        confirm: true,\n      },\n    });\n    expect(\n      manifest.tools.find((tool) => tool.name === 'list_org_apps')?.annotations?.readOnlyHint,\n    ).toBe(true);\n  });\n});\n" },
     { relPath: "examples/customer-auth/vitest.config.ts", content: "import { defineConfig } from 'vitest/config';\n\n// Keep the flagship's own contract test executable instead of inheriting the monorepo package-only glob.\nexport default defineConfig({\n  test: { include: ['test/**/*.test.ts'] },\n});\n" },
     { relPath: "examples/food-ordering/README.md", content: "# Food Ordering\n\n**Owns:** The flagship consumer ordering MCP App example: React view authoring, app-only helper tools,\ncaller-scoped cart state handles, invocation context, model-visible widget state/lifecycle, packaged image\nassets, portable structured elicitation, checkout handoff policy, host actions, CSP/permissions metadata,\nproduct-agent guidance, host-neutral distribution metadata, and widget preview coverage.\n\nFood Ordering is a generic, synthetic version of a live marketplace ordering app. It lets a user search\nstores, browse menus, customize an item, build a multi-line cart, review the order, and hand off checkout to\nan allowlisted example domain. It does not use real restaurant APIs, real checkout, customer credentials, or\nprivate customer data.\n\n## What It Shows\n\n| Capability | Example |\n| :--- | :--- |\n| Public entry tool | `open_ordering` returns structured fallback content and renders the React widget |\n| Product and distribution projections | `agentGuide` supplies grounded cross-capability guidance; `distribution` supplies listing, publisher, legal, image, and review facts separately from the runtime manifest |\n| App-only helper tools | `search_stores`, `load_menu`, `load_item`, `read_cart`, `sync_cart`, `prepare_checkout`; mutating widget-owned helpers use `confirm: false` (equivalent to omission) and execute directly because action hints alone never gate |\n| Durable cart state | `server(..., { state: { handles: { cart } }, use: { state } })` with caller scope, revision checks, and explicit ticket-bound adoption when an anonymous visitor authenticates |\n| React app runtime kit | `@noodleseed/one/react` supplies app flow, shell/nav/view, async state, form, quantity, choice, and handoff primitives |\n| Multi-step widget flow | One React shell navigates stores, menu, item customization, cart, review, and handoff views through `useAppFlow` |\n| Invocation context | `server.context` sets locale/time-zone defaults, derives an ambient service area/date, and exposes optional host-supplied coordinates to tools and the reserved `noodle_context` MCP adapter; location is an untrusted convenience hint, never an authorization signal or a substitute for explicit input |\n| Structured missing input | `plan_order` uses `ctx.elicit` to collect a fulfilment method and date through embedded/headless forms, standard bidirectional elicitation, a linked MCP App form, or an exact structured conversational retry on stateless hosts |\n| Model-visible widget state | `useUpdateModelContext` publishes one cohesive replacement snapshot when supported; `useWidgetLifecycle` auto-publishes mounted/cancelled/dismissed and reports author-owned submitted milestones for future context (not host-presentation proof), while the user-triggered submit pairs `useSendFollowUpMessage` for an immediate reply |\n| Handoff | `handoff.allowedDomains` allows only `https://orders.example.com` checkout URLs |\n| Progressive enhancement | Non-Apps hosts still receive stores, featured items, and a readable fallback summary |\n| Fail-closed hydration | The React view treats only the unhydrated, pre-result `{}` envelope as pending; a hydrated empty success remains distinct. It surfaces `isError`, validates required records and identifiers, and withholds ordering actions from malformed results |\n| Upstream MCP composition | This synthetic example keeps its data local. For the canonical frozen-tool import, governed upstream invocation, response normalization, and Noodle-owned widget pattern, use the repository's `shopify-storefront` flagship rather than copying another composition surface here |\n\nThe example is intentionally richer than the generated starter, but each inline view still follows the\nsame default: one immediate purpose, one primary action, at most one subordinate action, and progressive\ndisclosure for the rest. Preview it at 280px before adding navigation or local CSS; loading, empty, stale,\nerror/retry, and success states must remain readable without nested vertical scrolling.\n\nLike the comprehensive default `noodle init my-app` scaffold, this flagship keeps the server feature-rich\nwhile making each individual widget view focused; server capability breadth and screen density are separate.\nThe compiled initial widget should normally remain under the 1 MiB performance recommendation; Noodle Seed's\nhard ceilings are 10 MiB per compiled widget and 20 MiB across one deployment. Run `noodle check` to see raw\nand gzip-estimated sizes. Deploy requests are gzip-compressed as one stream so repeated self-contained React\nruntime bytes deduplicate on the wire without a cross-tenant CDN. Keep menu images or large live datasets in assets/resources and app-only tools\nrather than embedding them into the initial HTML bundle.\n\n## Local Author Loop\n\n```sh\nnoodle validate\nnoodle test\nnoodle dev\n```\n\nThe same `server.ts` declares `distribution` metadata for host adapters. It references real packaged images\nand keeps listing copy, support/legal URLs, and positive/negative review scenarios outside the canonical App\nPackage and Runtime Artifact. Explicit OpenAI and Claude adapters project those facts with the generated\nproduct skill; installable plugin archives and directory-submission dossiers remain separate outputs.\n\nIn another terminal:\n\n```sh\nnoodle tools list\nnoodle tools call open_ordering --args '{\"customer\":\"Asha\",\"query\":\"noodles\"}'\nnoodle tools call summarize_ordering_options --args '{}'\n```\n\nWhen a developer finalizes visual feedback in the local Design experience, a coding agent can inspect the\nlatest project-local brief without a path or session id:\n\n```sh\nnoodle design inspect --latest --json\n```\n\nThe agent should locate the captured elements in this example's authored React source, preserve the listed\nbehavior and accessibility constraints, and verify every acceptance check before changing unrelated UI.\n\nFor Apps metadata conformance, start `noodle dev`, copy the loopback MCP endpoint, then run:\n\n```sh\nnpx @mcpjam/cli@latest apps conformance --url http://127.0.0.1:<port>/o/demo/food-ordering/mcp --quiet --format json\n```\n\n## Export an OpenAI plugin\n\nThis flagship includes the guided workflows, listing metadata, review cases, and image assets needed to test\nOpenAI export. See the public [product-agent guide](https://docs.noodleseed.dev/docs/guides/product-agent-guides#export-an-openai-package)\nfor the current package workflow and boundaries.\n\nAgainst its deployed MCP URL, generate the Food Ordering submission candidate with:\n\n```sh\nnoodle export plugin openai \\\n  --state submission \\\n  --mcp-url https://food-ordering.noodleseed.app/mcp \\\n  --category \"Food & Drink\" \\\n  --output food-ordering-openai.zip\n```\n\nExtract `food-ordering-openai.zip` before using the portal. Upload\n`submission/chatgpt-app-submission.json` to the Codex-assisted import field and\n`submission/food-ordering-skill.zip` to **With MCP → Skills**. The outer ZIP is the complete review kit and\nis not itself a valid skill upload; `submission/README.md` repeats the portal steps.\n\nAfter registering that same URL in ChatGPT developer mode, substitute its real technical ID to generate the\nFood Ordering local test package:\n\n```sh\nnoodle export plugin openai \\\n  --state local \\\n  --mcp-url https://food-ordering.noodleseed.app/mcp \\\n  --category \"Food & Drink\" \\\n  --registered-app-id plugin_asdk_app_0123456789abcdef0123456789abcdef \\\n  --output food-ordering-openai-local.zip\n```\n\n## Export for Claude\n\nClaude Code plugin packaging and Anthropic Connector Directory review are separate outputs. Generate the\ninstallable plugin repository with:\n\n```sh\nnoodle export plugin claude \\\n  --mcp-url https://food-ordering.noodleseed.app/mcp \\\n  --output food-ordering-claude.zip\n```\n\nGenerate the credential-free operator dossier for the remote Connector Directory with:\n\n```sh\nnoodle export connector claude \\\n  --mcp-url https://food-ordering.noodleseed.app/mcp \\\n  --auth none \\\n  --category \"Food & Drink\" \\\n  --output food-ordering-anthropic-connector.zip\n```\n\nThe dossier is deliberately marked `portalUploadable: false`: it gathers the listing, tool annotations,\nuse cases, allowed-link candidates, test-account guidance, and MCP App screenshot evidence, but a human must\nverify ownership/compliance and enter the final answers in Anthropic's portal. The plugin ZIP does not\ncontain this dossier.\n\n## Client Setup\n\nUse the CLI to print the exact setup flow for your MCP client:\n\n```sh\nnoodle connect claude\nnoodle connect chatgpt\nnoodle connect inspector\n```\n\n## Deploy\n\n```sh\nnoodle deploy --org demo --app food-ordering --env prod --access owner-only\nnoodle open\n```\n\nThat one deploy command preflights the complete target, creates a missing app/environment, and verifies\nhosted readiness. If it is interrupted, rerun the same command to resume the unfinished operation without a\nduplicate deployment. Use `--access org-members` for an org-wide internal demo. This example has no\nconnector secrets and does not include tokens, caller-key mechanisms, or `.env.noodle` values.\n\n### Publish an immutable host archive\n\nOnly when this demo is intentionally being prepared for an external directory, deploy it with exact public\naccess and use the returned deployment ID to publish the matching local source:\n\n```sh\nnoodle deploy --org demo --app food-ordering --env prod --access public\nnoodle distributions publish <deployment-id> src/server.ts --target openai --category \"Food & Drink\"\nnoodle distributions list <deployment-id> --target openai\nnoodle distributions readiness <distribution-id> --status ready --note \"Archive and review evidence checked\"\nnoodle distributions release <distribution-id> --visibility private\nnoodle distributions grant <distribution-id> --expires-in 900\nnoodle distributions download <distribution-id> --output food-ordering-openai.zip\n```\n\nPublish fails if local `src/server.ts` no longer compiles to that deployment's package snapshot. Readiness is\nan explicit operator claim, the private release keeps anonymous discovery off, and the grant prints one\nsensitive exact-version reviewer URL. Record `noodle distributions review` only after a human observes the\nreal portal state. Public Noodle delivery, rollback, deprecation, and terminal revocation are separate explicit\nactions; none submits to a directory or claims acceptance.\n\n## Demo Assets\n\nThe packaged demo images live under `assets/`. The current app uses `assets/noodle-bowl.jpg` as the server\nbranding image. Its three distribution screenshots are real, response-only MCP App captures from Noodle\nDevtools at 2× device scale; each is 1640×970 PNG and has the producing user prompt next to its `asset(...)`\nreference in `server.ts`.\n\nImage sources:\n\n- `assets/noodle-bowl.jpg` — Unsplash photo\n  [`IRv8V9Hb8gI`](https://unsplash.com/photos/IRv8V9Hb8gI), downloaded from Unsplash.\n- `assets/food-ordering-stores.png` — store-discovery state produced by “Help me build a noodle order for\n  pickup.”\n- `assets/food-ordering-menu.png` — Harbor Noodles menu state produced by “Show me the Harbor Noodles\n  menu.”\n- `assets/food-ordering-handoff.png` — checkout-handoff state produced by “Review my spicy miso bowl order\n  before checkout.”\n\nThe Unsplash branding photo is free to use under the [Unsplash License](https://unsplash.com/license);\nattribution is not required, but the source note is kept here for provenance.\n" },
     { relPath: "examples/food-ordering/noodle.json", content: "{\n  \"entrypoint\": \"src/server.ts\",\n  \"name\": \"food-ordering\",\n  \"template\": \"widget\"\n}\n" },

package/node_modules/@noodle-borg/agent-kit/dist/plugin-bootstrap-skill.js

@@ -5,7 +5,8 @@ import { NOODLE_WORDMARK } from './welcome-wordmark.js';
 export const PLUGIN_NAME = 'noodle-seed';
 /** Cold-start discovery text shared by direct marketplace and official-directory projections. */
 const BOOTSTRAP_SKILL_DESCRIPTION = 'Use when asked to build, create, or ship an MCP server, MCP app, AI app, or connector, or to ' +
-    'make a product, API, or SaaS reachable by AI agents. Bootstraps Noodle Seed — TypeScript ' +
+    'make a product, API, or SaaS reachable by AI agents, or when a software business wants to improve ' +
+    'signup or onboarding conversion or choose a first Noodle workflow. Bootstraps Noodle Seed — TypeScript ' +
     'authoring with the noodle CLI, local validation and testing, and governed hosted deployment.';
 function bootstrapRouterBody() {
     return [
@@ -41,6 +42,12 @@ function bootstrapRouterBody() {
             `${PLUGIN_WINDOWS_SUPPORT.installCommand}` +
             '`; never expose a private plugin path as a workaround.',
         '',
+        '## First-workflow default',
+        '',
+        'When the user wants to get started but has not chosen a workflow, inspect the available product and repository context. If more signed-up or signed-in users are valuable and the product has a public visitor entry point, an existing account boundary, a genuine useful result that can be delivered before signup, and a meaningful next action inside the authenticated product, recommend public-to-product continuous onboarding as the first workflow.',
+        '',
+        'This default is not limited to B2B SaaS. Do not infer fit from the industry label alone, and do not manufacture pre-signup value or pressure. If the evidence is incomplete, ask only for the smallest missing fit fact. After project setup, route the accepted recommendation to `embedding-mcp-assistants`; the project-local playbook owns the two-surface design and exact implementation.',
+        '',
         '## Cold start (no project yet)',
         '',
         '1. New or empty directory: use `noodle-readiness.setup_project` with `mode: "initialize"`, or inline-execute the public fallback `noodle init --json`. This prepares the SaaS profile, installs pinned project-local tooling, and runs local checks. Preserve the existing package manager; use `install: false` / `--no-install` only for explicitly files-only work.',

package/node_modules/@noodle-borg/agent-kit/dist/skill-authoring-auth-ref.js

@@ -99,7 +99,7 @@ export function renderCustomerAuthAuthoringSections() {
         '',
         'Resolved customer URLs are private routing authority: they never enter the manifest/artifact, `${user}`, logs, model output, widgets, public confirmation review, cache keys, or delegated-token-exchange assertions. Routed reads may be used by tools, including declared nested calls. A routed action—including one reached through a connector wrapper—requires exact `annotations.confirm: true`; omitted or `false` fails with `customer_endpoint_action_unsupported`. Routed resources, prompts, and ambient context fail with `customer_endpoint_surface_unsupported`.',
         '',
-        'At runtime, an initially missing, malformed, or disallowed claim returns the same safe `connector_route_unavailable` tool error before credential lookup or connector egress. Preparation stores only sorted route `{ key, fingerprint }` bindings in the private server-held continuation. Acceptance re-resolves the current request routes; a missing or changed binding returns `invalid_continuation` before policy, credentials, or egress, then the matching frozen snapshot is reused for the action and nested/later calls. `tools/list` remains based only on roles and scopes, so route availability neither reveals tenant topology nor changes the existing authorization filter.',
+        'At runtime, an initially missing, malformed, or disallowed claim returns the same safe `connector_route_unavailable` tool error before credential lookup or connector egress. Preparation stores only sorted route `{ key, fingerprint }` bindings in the private server-held continuation. Acceptance re-resolves the current request routes; a missing or changed binding returns `invalid_continuation` before policy, credentials, or egress, then the matching frozen snapshot is reused for the action and nested/later calls. `tools/list` follows the scope/role discovery rule and its explicit public-descriptor opt-in, so route availability neither reveals tenant topology nor changes execution authorization.',
         '',
         '## Per-tool authorization',
         '',
@@ -121,7 +121,10 @@ export function renderCustomerAuthAuthoringSections() {
         '})',
         '```',
         '',
-        'Role values are trusted only from the explicitly configured claim path (or the platform-private bridge role claim). Direct OIDC scopes default to standard `scope`, `scp`, or `scopes` claims unless `claims.scopes` is configured. Embedded-assistant backends pass verified `user.roles` and `user.scopes` separately during `createAssistantSession(...)`; page context never grants either. Claim values must be a string or string array; malformed or oversized values fail closed. Eligible tools remain in authored order in `tools/list`; ineligible tools are omitted and a guessed direct call is still denied before argument validation or connector execution. Scope denials use MCP OAuth step-up metadata without disclosing role names.',
+        "Use `authorization.discovery: 'public'` on a nonempty scope/role rule to expose its MCP descriptor before sign-in. Omission and explicit 'authorized' preserve filtered discovery and compile identically. Visibility grants no execution or product-skill eligibility; scopes remain ALL and roles ANY. Noodle derives securitySchemes; never author them.",
+        'For mixed customer preview, keep server customerAuth and adopt on the same org/app/env, endpoint, issuer and audience; keep the separate public Help endpoint during the pilot, and never create overlapping active issuer/audience ownership. Before any mixed deploy or access change, leave only Help unrestricted, add authorization to every customer tool, and validate plus preview with `noodle dev --access mixed`. For an existing customer-only app, first run `noodle deployments list --org <org> --app <app> --env <env> --json` and inspect an inactive `customers` record for the exact server version. If none exists, record the active ID, redeploy the unchanged secured source to the same version with `--access customers`, then list and inspect again to prove that ID is now inactive; recording it alone preserves nothing. Next deploy the policy-prepared source with `--access customers`, verify the original rollback record remains inactive, and only then run `noodle access set mixed ... --version <version>`. On pilot failure use `noodle rollback <deployment-id> --org <org> --app <app> --env <env> --reason <text>`. This app-history rollback differs from the compatible hosted service-release floor. Invalid supplied credentials fail, with no platform-human fallback. Broker exchange remains required. Local Devtools retries after successful sign-in and leaves Help available after cancellation without executing the protected tool. After deployment, test anonymous discovery, sign-in, cancellation, authenticated retry and expiry in the actual host before customer cutover; local/SDK checks do not prove ChatGPT or another host.',
+        '',
+        'Role values are trusted only from the explicitly configured claim path (or the platform-private bridge role claim). Direct OIDC scopes default to standard `scope`, `scp`, or `scopes` claims unless `claims.scopes` is configured. Embedded-assistant backends pass verified `user.roles` and `user.scopes` separately during `createAssistantSession(...)`; page context never grants either. Claim values must be a string or string array; malformed or oversized values fail closed. Tools retain authored order in `tools/list`; protected descriptors are omitted unless explicitly public, and an unauthorized direct call is still denied before argument validation or connector execution. Scope denials use MCP OAuth step-up metadata without disclosing role names.',
         '',
         '## Delegated downstream auth (call your API as the signed-in user)',
         '',

package/node_modules/@noodle-borg/agent-kit/dist/skill-embedded-assistant-ref.js

@@ -9,6 +9,7 @@ export function renderEmbeddedAssistantReference() {
         '',
         '- Architecture',
         '- Select the architecture before code',
+        '- First-workflow default: continuous onboarding',
         '- Install into the existing application',
         '- Author and validate',
         '- Product workflow guidance',
@@ -69,6 +70,25 @@ export function renderEmbeddedAssistantReference() {
         '',
         'The architecture brief must state the selected topology, why it fits the named user and job, the two code owners and two local processes, credential and identity flow, routing authority, model owner, files expected to change, and the first requested evidence boundary. If identity/session ownership, exact origin, tenant-routing authority, model ownership, or evidence target is unavailable, return a blocked architecture brief naming the missing owner or decision and do not edit either codebase.',
         '',
+        '### First-workflow default: continuous onboarding',
+        '',
+        'When a customer asks what to build first, inspect the available product and repository evidence before asking them to choose from a menu. This default is not limited to B2B SaaS: it applies to any software or digital service where converting an anonymous visitor into a legitimately useful authenticated relationship is valuable.',
+        '',
+        'Recommend continuous onboarding by default when all four fit signals are present:',
+        '',
+        '1. A public visitor surface exists where the assistant can begin without identity.',
+        '2. The product already has signup or sign-in that the customer application owns.',
+        '3. The assistant can deliver a genuine useful result before account creation, using only information the visitor chooses to provide.',
+        '4. A meaningful authenticated product outcome can continue from that work and finish through the customer’s authorized API.',
+        '',
+        'When the evidence is clear, recommend one assistant on two customer-owned surfaces rather than presenting an unranked workflow menu: a mixed public surface using `publicWebsite({ signIn: true })` and an in-product `authenticatedWebsite(...)` surface. The public experience produces and, when needed, temporarily saves the useful reviewed draft; identity is requested only when it unlocks the next step; the authenticated experience adopts that state, resumes the interrupted request, and separately confirms the final business action. This gives the customer one concrete first workflow while establishing both its public-site and in-product integration boundaries.',
+        '',
+        'Treat both mounts as one first-workflow delivery scope. Do not call it complete when only the public or only the authenticated surface works; report that evidence as partial and name the missing mount. The two surfaces may live in separate customer repositories and release independently, so “one scope” is not a claim of atomic deployment.',
+        '',
+        'Do not recommend this default when there is no genuine pre-account value, no customer-owned account boundary, no meaningful authenticated continuation, or no feasible public and product mount. Ask only for the smallest missing fit fact instead of making the user classify the company. Keep signup optional until identity is truly required, never imply that prior effort obligates registration, and treat improved conversion as a hypothesis to measure—not a guarantee. This design does not guarantee a conversion lift.',
+        '',
+        'Once selected, begin with the bundled [stateful-draft example](../examples/stateful-draft/README.md) and the public [signup-continuity guide](https://docs.noodleseed.dev/docs/guides/signup-continuity). Adapt the draft to the smallest useful customer-specific result; do not invent a universal SaaS schema or replace the customer’s identity provider and product API.',
+        '',
         '## Install into the existing application',
         '',
         'Configure or reuse an existing capability before generating files. Public embedding uses the existing script or embed ID and needs no customer backend session/config route. Reuse application APIs and business functions; generate a thin handler only where the approved architecture identifies a missing stable boundary.',

package/node_modules/@noodle-borg/agent-kit/dist/skill-router.js

@@ -3,7 +3,8 @@
 // one-level reference tree rendered by skill-content.ts.
 import { BEHAVIOR_SKILLS } from './behavior-skills.js';
 export const SKILL_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.';
+    'MCP server or app authored in TypeScript with the noodle CLI, or improving signup or onboarding ' +
+    'conversion or selecting a first Noodle workflow for an account-growth product.';
 export const APP_DIRECTORY_COMPLIANCE_REFERENCE = 'references/app-directory-compliance.md';
 export const SKILL_ROUTES = [
     {
@@ -68,7 +69,7 @@ export const SKILL_ROUTES = [
     },
     {
         id: 'embed-assistant',
-        intent: 'Embed a Noodle assistant in an existing SaaS or web application',
+        intent: 'Embed a Noodle assistant in an existing SaaS or web application, including public-to-product continuous onboarding',
         skill: 'embedding-mcp-assistants',
         exitCondition: 'The requested embed boundary works with verified identity and credential separation at the tested level.',
     },
@@ -147,6 +148,12 @@ export function skillRouterBody(_target) {
         '',
         'Negative routing examples: “Inspect hosted logs/status” → `inspect-hosted` (read-only). “Prepare for deployment” → the applicable build or verification route; with existing access it may inspect `deploy preflight`, then stop with a handoff. Preparation does not authorize `link`, hosted config, publication, rollback, host writes, or submission. “Keep this local” → a build or verification route, never a hosted route.',
         '',
+        '## First-workflow heuristic',
+        '',
+        'When the user asks what to build first or gives only a broad growth goal, inspect the repository and product context before asking them to invent a workflow. Do not classify the business or choose a design from an industry label alone.',
+        '',
+        'If the evidence shows a public visitor surface, an existing signup or sign-in boundary, a useful pre-account result the assistant can genuinely produce, and a meaningful authenticated outcome inside the product—and more authenticated users are valuable—recommend public-to-product continuous onboarding and route to `embedding-mcp-assistants`. This recommendation is not limited to B2B SaaS. If one of those facts is unclear, ask only for the smallest missing fit fact; if the pattern does not fit, route by the user’s actual outcome instead.',
+        '',
         ...routeTableLines(),
         '',
         '## Common machine loop',

package/node_modules/@noodle-borg/agent-kit/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@noodle-borg/agent-kit",
-  "version": "0.102.0",
+  "version": "0.104.0",
   "license": "Apache-2.0",
   "type": "module",
   "engines": {

package/node_modules/@noodle-borg/agent-packaging/dist/product-skill-types.d.ts

@@ -84,6 +84,7 @@ export interface ProductSkillTool {
     readonly behavior: ProductSkillToolBehavior;
     readonly visibility: readonly ('model' | 'app')[];
     readonly authorization?: {
+        readonly discovery?: 'public' | undefined;
         readonly requiredScopes?: readonly string[] | undefined;
         readonly allowedRoles?: readonly string[] | undefined;
     } | undefined;

package/node_modules/@noodle-borg/agent-packaging/dist/product-skill-validation.js

@@ -188,6 +188,10 @@ function isVisibility(value) {
 function isValidAuthorization(value) {
     if (!isRecord(value))
         return false;
+    if (Object.keys(value).some((key) => !['requiredScopes', 'allowedRoles', 'discovery'].includes(key)))
+        return false;
+    if (value.discovery !== undefined && value.discovery !== 'public')
+        return false;
     const scopesValid = value.requiredScopes === undefined ||
         boundedArray(value.requiredScopes, 1, MAX_AUTHORIZATION_VALUES, (scope) => boundedProse(scope, MAX_SCOPE_CHARS));
     const rolesValid = value.allowedRoles === undefined ||

package/node_modules/@noodle-borg/app-package/dist/schema.js

@@ -56,6 +56,7 @@ const branding = z
     .strict();
 const authorization = z
     .object({
+    discovery: z.literal('public').optional(),
     requiredScopes: z
         .array(z
         .string()

package/node_modules/@noodle-borg/app-package/dist/types.d.ts

@@ -47,6 +47,7 @@ export interface AppPackageTool {
     };
     readonly visibility: readonly ('model' | 'app')[];
     readonly authorization?: {
+        readonly discovery?: 'public' | undefined;
         readonly requiredScopes?: readonly string[] | undefined;
         readonly allowedRoles?: readonly string[] | undefined;
     } | undefined;

package/node_modules/@noodle-borg/authoring/dist/server.d.ts

@@ -132,7 +132,7 @@ export interface ToolOptions {
     /** Human-readable action name shown by MCP hosts and confirmation surfaces. */
     readonly title?: string;
     readonly description: string;
-    /** Verified caller claims required to discover and invoke this tool. */
+    /** Verified caller claims required to invoke this tool; discovery is restricted by default. */
     readonly authorization?: ToolAuthorizationOptions;
     /** Designate this ordinary zero-input MCP tool as the application context provider. */
     readonly contextProvider?: true;
@@ -168,6 +168,8 @@ export interface ToolOptions {
     readonly fulfil: (ctx: ToolContext) => unknown | Promise<unknown>;
 }
 export interface ToolAuthorizationOptions {
+    /** Expose the descriptor before authorization; never grants execution permission. */
+    readonly discovery?: 'authorized' | 'public';
     /** Every scope must be present on the verified caller. */
     readonly requiredScopes?: readonly string[];
     /** At least one role must be present on the verified caller. */

package/node_modules/@noodle-borg/authoring/dist/server.js

@@ -53,6 +53,8 @@ export function server(name, options, definitions = []) {
     return new ServerBuilder(name, options, use, provides, tools, resources, prompts, widgets);
 }
 export function tool(name, options) {
+    if ('securitySchemes' in options)
+        throw new Error('Use authorization, not raw securitySchemes');
     return { kind: 'tool', name, options };
 }
 export function resource(name, options) {
@@ -126,6 +128,7 @@ class ServerBuilder {
         const tools = [];
         for (const tool of this.tools) {
             const recorded = await recordTool(tool.options.fulfil, this.connectors);
+            const { discovery, requiredScopes, allowedRoles, ...authorization } = tool.options.authorization ?? {};
             tools.push({
                 name: tool.name,
                 ...(tool.options.title ? { title: tool.options.title } : {}),
@@ -133,12 +136,10 @@ class ServerBuilder {
                 ...(tool.options.authorization
                     ? {
                         authorization: {
-                            ...(tool.options.authorization.requiredScopes
-                                ? { requiredScopes: [...tool.options.authorization.requiredScopes] }
-                                : {}),
-                            ...(tool.options.authorization.allowedRoles
-                                ? { allowedRoles: [...tool.options.authorization.allowedRoles] }
-                                : {}),
+                            ...(requiredScopes ? { requiredScopes: [...requiredScopes] } : {}),
+                            ...(allowedRoles ? { allowedRoles: [...allowedRoles] } : {}),
+                            ...authorization,
+                            ...(discovery === undefined || discovery === 'authorized' ? {} : { discovery }),
                         },
                     }
                     : {}),