@noodleseed/agent-kit 0.58.0 → 0.58.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@noodleseed/agent-kit",
-  "version": "0.58.0",
+  "version": "0.58.1",
   "private": false,
   "description": "Self-checking, self-updating agent skills for the Noodle Seed CLI. Authored in this repo by @noodle-borg/agent-kit; this is the published, independently-versioned canonical skills artifact the CLI fetches and verifies.",
   "license": "Apache-2.0",

package/skills/claude-code/SKILL.md

@@ -3,7 +3,7 @@ name: noodle-seed
 description: "Use when building, validating, testing, deploying, or operating a local or hosted Noodle Seed MCP server or app authored in TypeScript with the noodle CLI."
 ---
 
-<!-- noodle-skill version:0.58.0 hash:ec5bfcd0d8165205 -->
+<!-- noodle-skill version:0.58.1 hash:ec5bfcd0d8165205 -->
 
 # Noodle Seed
 

package/skills/claude-code/authoring-mcp-servers/SKILL.md

@@ -3,7 +3,7 @@ name: authoring-mcp-servers
 description: "Use when creating or extending a headless Noodle Seed MCP server, tool, resource, prompt, or typed model-facing capability."
 ---
 
-<!-- noodle-skill version:0.58.0 hash:0b2fd8c7e43fc69f -->
+<!-- noodle-skill version:0.58.1 hash:0b2fd8c7e43fc69f -->
 
 # authoring-mcp-servers
 

package/skills/claude-code/building-mcp-apps/SKILL.md

@@ -3,7 +3,7 @@ name: building-mcp-apps
 description: "Use when a Noodle Seed MCP App, widget, interactive card, visual interaction, or host-visible UI is the primary requested outcome."
 ---
 
-<!-- noodle-skill version:0.58.0 hash:f7fa54992c8d7692 -->
+<!-- noodle-skill version:0.58.1 hash:f7fa54992c8d7692 -->
 
 # building-mcp-apps
 

package/skills/claude-code/connecting-apis-to-mcp/SKILL.md

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

package/skills/claude-code/debugging-mcp-delivery/SKILL.md

@@ -3,7 +3,7 @@ name: debugging-mcp-delivery
 description: "Use when an existing Noodle Seed MCP project has a concrete validation, runtime, connector, App, host, deployment, or production failure."
 ---
 
-<!-- noodle-skill version:0.58.0 hash:aa715bae12041d7c -->
+<!-- noodle-skill version:0.58.1 hash:aa715bae12041d7c -->
 
 # debugging-mcp-delivery
 

package/skills/claude-code/deploying-mcp-services/SKILL.md

@@ -3,7 +3,7 @@ name: deploying-mcp-services
 description: "Use when the user explicitly requests a Noodle Seed hosted link, configuration write, deployment, access change, rollback, or connection write."
 ---
 
-<!-- noodle-skill version:0.58.0 hash:93e735b7ffb45df1 -->
+<!-- noodle-skill version:0.58.1 hash:93e735b7ffb45df1 -->
 
 # deploying-mcp-services
 

package/skills/claude-code/designing-mcp-products/SKILL.md

@@ -3,7 +3,7 @@ name: designing-mcp-products
 description: "Use when a Noodle Seed MCP product idea needs conversational fit, user benefit, scope, interaction, or evidence design before implementation."
 ---
 
-<!-- noodle-skill version:0.58.0 hash:76cce86729cffbee -->
+<!-- noodle-skill version:0.58.1 hash:76cce86729cffbee -->
 
 # designing-mcp-products
 

package/skills/claude-code/embedding-mcp-assistants/SKILL.md

@@ -3,7 +3,7 @@ name: embedding-mcp-assistants
 description: "Use when embedding a Noodle assistant into an existing SaaS or web application with browser, identity, session, and credential boundaries."
 ---
 
-<!-- noodle-skill version:0.58.0 hash:cc54a67f21c0ecdb -->
+<!-- noodle-skill version:0.58.1 hash:cc54a67f21c0ecdb -->
 
 # embedding-mcp-assistants
 

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

@@ -302,6 +302,23 @@ Complete sign-in in Devtools and load the tool list. That authenticated request
 PKCE, token issuance, issuer/signature verification, the stable audience, and exact-resource binding work
 together. Invoke a representative safe read when the configured customer API is available.
 
+### Test delegated exchange locally
+
+Local customer OIDC sign-in and delegated-exchange assertion trust are two distinct boundaries. OIDC proves
+the caller to the local MCP server; Devtools uses a separate local issuer only for the RFC 8693 assertion
+sent to the downstream token endpoint. This is the canonical local path and requires no `server.ts` change,
+flag, environment variable, or config surface.
+
+1. Configure the OIDC authorization server for the exact loopback callback and RFC 8707 resource. Do not add
+   the Devtools assertion key to OIDC issuer metadata or change its signing keys.
+2. Start Devtools, complete customer sign-in, and copy the displayed `{ issuer, jwks }` from **Local delegated exchange**.
+3. Pin both values only in the customer-owned development RFC 8693 token endpoint.
+4. Restrict that trust to development client credentials, audience, API, and data.
+5. Invoke the delegated `list_org_apps` tool until its binding reads **Exchange verified**.
+6. Use hosted preview or `noodle auth doctor --live` to prove the production platform issuer.
+
+**Never trust the Devtools issuer in production: anyone holding the local private key could impersonate a customer.**
+
 ## Configuration
 
 The embedded assistant uses a customer-supplied OpenAI Chat Completions-compatible endpoint. Configure its

package/skills/claude-code/executing-noodle-plans/SKILL.md

@@ -3,7 +3,7 @@ name: executing-noodle-plans
 description: "Use when the user asks to execute an approved, decision-complete implementation plan for a Noodle Seed project task by task with test-first changes, review, recovery, and final verification."
 ---
 
-<!-- noodle-skill version:0.58.0 hash:6a9f132ddb79352e -->
+<!-- noodle-skill version:0.58.1 hash:6a9f132ddb79352e -->
 
 # Execute a Noodle Seed implementation plan
 

package/skills/claude-code/publishing-mcp-integrations/SKILL.md

@@ -3,7 +3,7 @@ name: publishing-mcp-integrations
 description: "Use when preparing, reviewing, or submitting a Noodle Seed MCP integration to a host or app directory."
 ---
 
-<!-- noodle-skill version:0.58.0 hash:efffbf82007f935d -->
+<!-- noodle-skill version:0.58.1 hash:efffbf82007f935d -->
 
 # publishing-mcp-integrations
 

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

@@ -289,6 +289,19 @@ export async function tokenEndpoint(req: Request): Promise<Response> {
 }
 ```
 
+### Test delegated exchange locally
+
+Local customer OIDC sign-in and delegated-exchange assertion trust are two distinct boundaries. OIDC proves the caller to the local MCP server; Devtools uses a separate local issuer only for the RFC 8693 assertion sent to your downstream token endpoint. This requires no `server.ts` change or additional flag, environment variable, or config surface.
+
+1. Configure the OIDC authorization server for the exact loopback callback and RFC 8707 resource. Do not add the Devtools assertion key to OIDC issuer metadata or change its signing keys.
+2. Start Devtools, complete customer sign-in, and copy the displayed `{ issuer, jwks }` from **Local delegated exchange**.
+3. Pin both values only in the customer-owned development RFC 8693 token endpoint.
+4. Restrict that trust to development client credentials, audience, API, and data.
+5. Run the delegated tool until its binding reads **Exchange verified**.
+6. Use hosted preview or `noodle auth doctor --live` to prove the production platform issuer.
+
+**Never trust the Devtools issuer in production: anyone holding the local private key could impersonate a customer.**
+
 Diagnose statically with `noodle auth doctor`; set a short-lived real customer token only in `NOODLE_CUSTOMER_TOKEN` and add `--live --org <org> --app <app> --env <env>` to perform one exchange per delegated binding without invoking a business tool. Add `--version <version>` to test that exact pinned MCP resource. Common failures include structured `credential_unavailable` reasons such as `caller_identity_not_customer`. Direct/federated OIDC verification assigns the customer identity at the trusted verifier boundary; never ask an IdP to mint a Noodle-specific classification claim.
 
 ## Design tools for the model

package/skills/claude-code/reporting-noodle-feedback/SKILL.md

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

package/skills/claude-code/verifying-mcp-delivery/SKILL.md

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

package/skills/codex/SKILL.md

@@ -3,7 +3,7 @@ name: noodle-seed
 description: "Use when building, validating, testing, deploying, or operating a local or hosted Noodle Seed MCP server or app authored in TypeScript with the noodle CLI."
 ---
 
-<!-- noodle-skill version:0.58.0 hash:ec5bfcd0d8165205 -->
+<!-- noodle-skill version:0.58.1 hash:ec5bfcd0d8165205 -->
 
 # Noodle Seed
 

package/skills/codex/authoring-mcp-servers/SKILL.md

@@ -3,7 +3,7 @@ name: authoring-mcp-servers
 description: "Use when creating or extending a headless Noodle Seed MCP server, tool, resource, prompt, or typed model-facing capability."
 ---
 
-<!-- noodle-skill version:0.58.0 hash:0b2fd8c7e43fc69f -->
+<!-- noodle-skill version:0.58.1 hash:0b2fd8c7e43fc69f -->
 
 # authoring-mcp-servers
 

package/skills/codex/building-mcp-apps/SKILL.md

@@ -3,7 +3,7 @@ name: building-mcp-apps
 description: "Use when a Noodle Seed MCP App, widget, interactive card, visual interaction, or host-visible UI is the primary requested outcome."
 ---
 
-<!-- noodle-skill version:0.58.0 hash:f7fa54992c8d7692 -->
+<!-- noodle-skill version:0.58.1 hash:f7fa54992c8d7692 -->
 
 # building-mcp-apps
 

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

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

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

@@ -3,7 +3,7 @@ name: debugging-mcp-delivery
 description: "Use when an existing Noodle Seed MCP project has a concrete validation, runtime, connector, App, host, deployment, or production failure."
 ---
 
-<!-- noodle-skill version:0.58.0 hash:aa715bae12041d7c -->
+<!-- noodle-skill version:0.58.1 hash:aa715bae12041d7c -->
 
 # debugging-mcp-delivery
 

package/skills/codex/deploying-mcp-services/SKILL.md

@@ -3,7 +3,7 @@ name: deploying-mcp-services
 description: "Use when the user explicitly requests a Noodle Seed hosted link, configuration write, deployment, access change, rollback, or connection write."
 ---
 
-<!-- noodle-skill version:0.58.0 hash:93e735b7ffb45df1 -->
+<!-- noodle-skill version:0.58.1 hash:93e735b7ffb45df1 -->
 
 # deploying-mcp-services
 

package/skills/codex/designing-mcp-products/SKILL.md

@@ -3,7 +3,7 @@ name: designing-mcp-products
 description: "Use when a Noodle Seed MCP product idea needs conversational fit, user benefit, scope, interaction, or evidence design before implementation."
 ---
 
-<!-- noodle-skill version:0.58.0 hash:76cce86729cffbee -->
+<!-- noodle-skill version:0.58.1 hash:76cce86729cffbee -->
 
 # designing-mcp-products
 

package/skills/codex/embedding-mcp-assistants/SKILL.md

@@ -3,7 +3,7 @@ name: embedding-mcp-assistants
 description: "Use when embedding a Noodle assistant into an existing SaaS or web application with browser, identity, session, and credential boundaries."
 ---
 
-<!-- noodle-skill version:0.58.0 hash:cc54a67f21c0ecdb -->
+<!-- noodle-skill version:0.58.1 hash:cc54a67f21c0ecdb -->
 
 # embedding-mcp-assistants
 

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

@@ -302,6 +302,23 @@ Complete sign-in in Devtools and load the tool list. That authenticated request
 PKCE, token issuance, issuer/signature verification, the stable audience, and exact-resource binding work
 together. Invoke a representative safe read when the configured customer API is available.
 
+### Test delegated exchange locally
+
+Local customer OIDC sign-in and delegated-exchange assertion trust are two distinct boundaries. OIDC proves
+the caller to the local MCP server; Devtools uses a separate local issuer only for the RFC 8693 assertion
+sent to the downstream token endpoint. This is the canonical local path and requires no `server.ts` change,
+flag, environment variable, or config surface.
+
+1. Configure the OIDC authorization server for the exact loopback callback and RFC 8707 resource. Do not add
+   the Devtools assertion key to OIDC issuer metadata or change its signing keys.
+2. Start Devtools, complete customer sign-in, and copy the displayed `{ issuer, jwks }` from **Local delegated exchange**.
+3. Pin both values only in the customer-owned development RFC 8693 token endpoint.
+4. Restrict that trust to development client credentials, audience, API, and data.
+5. Invoke the delegated `list_org_apps` tool until its binding reads **Exchange verified**.
+6. Use hosted preview or `noodle auth doctor --live` to prove the production platform issuer.
+
+**Never trust the Devtools issuer in production: anyone holding the local private key could impersonate a customer.**
+
 ## Configuration
 
 The embedded assistant uses a customer-supplied OpenAI Chat Completions-compatible endpoint. Configure its

package/skills/codex/executing-noodle-plans/SKILL.md

@@ -3,7 +3,7 @@ name: executing-noodle-plans
 description: "Use when the user asks to execute an approved, decision-complete implementation plan for a Noodle Seed project task by task with test-first changes, review, recovery, and final verification."
 ---
 
-<!-- noodle-skill version:0.58.0 hash:6a9f132ddb79352e -->
+<!-- noodle-skill version:0.58.1 hash:6a9f132ddb79352e -->
 
 # Execute a Noodle Seed implementation plan
 

package/skills/codex/publishing-mcp-integrations/SKILL.md

@@ -3,7 +3,7 @@ name: publishing-mcp-integrations
 description: "Use when preparing, reviewing, or submitting a Noodle Seed MCP integration to a host or app directory."
 ---
 
-<!-- noodle-skill version:0.58.0 hash:efffbf82007f935d -->
+<!-- noodle-skill version:0.58.1 hash:efffbf82007f935d -->
 
 # publishing-mcp-integrations
 

package/skills/codex/references/authoring-workflow.md

@@ -289,6 +289,19 @@ export async function tokenEndpoint(req: Request): Promise<Response> {
 }
 ```
 
+### Test delegated exchange locally
+
+Local customer OIDC sign-in and delegated-exchange assertion trust are two distinct boundaries. OIDC proves the caller to the local MCP server; Devtools uses a separate local issuer only for the RFC 8693 assertion sent to your downstream token endpoint. This requires no `server.ts` change or additional flag, environment variable, or config surface.
+
+1. Configure the OIDC authorization server for the exact loopback callback and RFC 8707 resource. Do not add the Devtools assertion key to OIDC issuer metadata or change its signing keys.
+2. Start Devtools, complete customer sign-in, and copy the displayed `{ issuer, jwks }` from **Local delegated exchange**.
+3. Pin both values only in the customer-owned development RFC 8693 token endpoint.
+4. Restrict that trust to development client credentials, audience, API, and data.
+5. Run the delegated tool until its binding reads **Exchange verified**.
+6. Use hosted preview or `noodle auth doctor --live` to prove the production platform issuer.
+
+**Never trust the Devtools issuer in production: anyone holding the local private key could impersonate a customer.**
+
 Diagnose statically with `noodle auth doctor`; set a short-lived real customer token only in `NOODLE_CUSTOMER_TOKEN` and add `--live --org <org> --app <app> --env <env>` to perform one exchange per delegated binding without invoking a business tool. Add `--version <version>` to test that exact pinned MCP resource. Common failures include structured `credential_unavailable` reasons such as `caller_identity_not_customer`. Direct/federated OIDC verification assigns the customer identity at the trusted verifier boundary; never ask an IdP to mint a Noodle-specific classification claim.
 
 ## Design tools for the model

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.58.0 hash:0f404109f4845683 -->
+<!-- noodle-skill version:0.58.1 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.58.0 hash:6ef6ef551e26b78e -->
+<!-- noodle-skill version:0.58.1 hash:6ef6ef551e26b78e -->
 
 # verifying-mcp-delivery