@noodleseed/agent-kit 0.48.2 → 0.50.0

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

@@ -110,7 +110,9 @@ Do not put these model values in the embedding SaaS environment. A production de
 
 ## Access modes and customer auth
 
-Session exchange authenticates with the backend client credentials, so the embed works under any `--access` mode. Add `--access customers` only when verified end customers should also call the MCP endpoint directly. That mode requires `server.auth`; `noodle deploy` preflights the rule locally and fails with `server_auth_required` before contacting the service. Fix by adding auth to server options:
+Session exchange authenticates with the backend client credentials, so the embed works under any `--access` mode. The assistant does not select direct MCP access or protected-resource discovery. If protected-resource metadata advertises an unexpected issuer, inspect the exact active deployment before changing auth by following `references/troubleshooting.md`.
+
+Add `--access customers` only when verified end customers should also call the MCP endpoint directly. That mode requires `server.auth`; `noodle deploy` preflights the rule locally and fails with `server_auth_required` before contacting the service. Fix by adding auth to server options:
 
 ```ts
 auth: customerAuth.federatedOidc({
@@ -154,7 +156,12 @@ export async function POST(request: Request) {
     clientId: process.env.NOODLE_ASSISTANT_CLIENT_ID!,
     clientSecret: process.env.NOODLE_ASSISTANT_CLIENT_SECRET!,
     origin: process.env.PUBLIC_APP_ORIGIN!,
-    user: { id: user.id, email: user.email, roles: user.roles },
+    user: {
+      id: user.id,
+      email: user.email,
+      roles: user.roles,
+      scopes: user.scopes,
+    },
     context,
     // Saved, backend-verified user preferences outrank browser hints.
     preferences: { locale: user.locale, timeZone: user.timeZone },
@@ -163,7 +170,7 @@ export async function POST(request: Request) {
 }
 ```
 
-Authenticate before exchange. Source `origin` from trusted server configuration or strictly match the request origin against the same exact allowlist; never accept an arbitrary request header. Treat page context as untrusted model context, never authorization. Forward the helper response unchanged.
+Authenticate before exchange. Pass backend-verified `user.roles` and OAuth-style `user.scopes` separately; they govern the same per-tool authorization rules as verified MCP bearer claims. Source `origin` from trusted server configuration or strictly match the request origin against the same exact allowlist; never accept an arbitrary request header. Treat page context as untrusted model context, never authorization. Forward the helper response unchanged.
 
 `serviceUrl` is the Noodle Seed control-plane base URL: the value `noodle assistant clients create` prints, also stored as `serviceUrl` in `deployment.json`. It is NOT the deployment MCP endpoint (`url`, which ends in `/v1/mcp` and rejects session exchange). Never probe or guess endpoints with real credentials.
 
@@ -204,7 +211,13 @@ The embedding developer defines what authenticated session context the assistant
 ```ts
 const session = await createAssistantSession({
   serviceUrl, clientId, clientSecret, origin,
-  user: { id: user.id, email: user.email, name: user.name },
+  user: {
+    id: user.id,
+    email: user.email,
+    name: user.name,
+    roles: user.roles,
+    scopes: user.scopes,
+  },
   claims: { displayName: user.name, accountTier: account.tier, region: account.region },
 });
 ```

package/skills/codex/references/troubleshooting.md

@@ -3,6 +3,7 @@
 ## Contents
 
 - First moves
+- Customer-auth metadata
 - Symptom map
 
 ## First moves
@@ -11,6 +12,12 @@ Re-run the local gates before debugging in-host: `noodle validate`, `noodle chec
 
 For protocol/conformance checks, the headless harness is `@mcpjam/cli`, not a `noodle` subcommand. Use it against a local `noodle dev` URL without an access token, or against hosted URLs through the host/OAuth flow printed by `noodle connect`.
 
+## Customer-auth metadata
+
+Adding `embeddedAssistant(...)` does not select the MCP access mode or authorization server. Before changing auth, inspect the exact active deployment with `noodle deployments list --org <org> --app <app> --env <env> --json` and match its active deployment ID, server version, and access mode to the endpoint being tested.
+
+For `customers` access, Direct or federated customer auth must advertise the configured tenant issuer; a managed Noodle bridge must advertise the Noodle authorization server. Owner-only access advertises the platform authorization server. If a direct or federated `customers` deployment still advertises the platform issuer, treat it as `customer_auth_state_inconsistent` and escalate with the endpoint, active deployment ID, and sanitized protected-resource metadata. Do not proxy, rewrite, rotate, or redeploy to hide the mismatch. Never share bearer tokens, refresh tokens, client secrets, or credential files.
+
 ## Symptom map
 
 | Symptom | Likely cause | Fix |

package/skills/codex/reporting-noodle-feedback/SKILL.md

@@ -3,7 +3,7 @@ name: reporting-noodle-feedback
 description: "Use when a Noodle Seed bug, misleading instruction, missing capability, or concrete product improvement should be proposed to the user."
 ---
 
-<!-- noodle-skill version:0.48.2 hash:0f404109f4845683 -->
+<!-- noodle-skill version:0.50.0 hash:0f404109f4845683 -->
 
 # reporting-noodle-feedback
 

package/skills/codex/verifying-mcp-delivery/SKILL.md

@@ -3,7 +3,7 @@ name: verifying-mcp-delivery
 description: "Use when proving a Noodle Seed MCP project works at a named compile, local, connector, App, host, deployment, or production evidence level."
 ---
 
-<!-- noodle-skill version:0.48.2 hash:6ef6ef551e26b78e -->
+<!-- noodle-skill version:0.50.0 hash:6ef6ef551e26b78e -->
 
 # verifying-mcp-delivery