@noodleseed/agent-kit 0.56.0 → 0.57.0

package/package.json

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

package/skills/claude-code/SKILL.md

@@ -3,7 +3,7 @@ name: noodle-seed
 description: "Use when building, validating, testing, deploying, or operating a local or hosted Noodle Seed MCP server or app authored in TypeScript with the noodle CLI."
 ---
 
-<!-- noodle-skill version:0.56.0 hash:ec5bfcd0d8165205 -->
+<!-- noodle-skill version:0.57.0 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.56.0 hash:0b2fd8c7e43fc69f -->
+<!-- noodle-skill version:0.57.0 hash:0b2fd8c7e43fc69f -->
 
 # authoring-mcp-servers
 

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

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

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

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

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

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

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

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

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

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

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

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

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

@@ -68,7 +68,7 @@ public `${user}` expression scope:
 ```ts
 auth: customerAuth.oidc({
   issuer: 'https://id.noodleseed.dev',
-  audience: 'https://org.cloud.noodleseed.dev/app/mcp',
+  audience: 'noodleseed-customer-auth-prod',
   claims: {
     id: 'sub',
     email: 'email',
@@ -93,7 +93,7 @@ auth: customerAuth.federatedOidc({
   issuers: [
     {
       issuer: 'https://id.customer-a.com',
-      audience: 'https://org.cloud.noodleseed.dev/app/mcp',
+      audience: 'noodleseed-customer-auth-prod',
       routing: {
         endpoints: {
           customer_api: { claim: 'tenant.api_base_url' },
@@ -102,7 +102,7 @@ auth: customerAuth.federatedOidc({
     },
     {
       issuer: 'https://login.customer-b.com',
-      audience: 'https://org.cloud.noodleseed.dev/app/mcp',
+      audience: 'noodleseed-customer-auth-prod',
       routing: {
         endpoints: {
           customer_api: { claim: 'organization.routes.customer_api' },
@@ -113,8 +113,9 @@ auth: customerAuth.federatedOidc({
 }),
 ```
 
-At runtime, Noodle Seed validates both the configured audience and exact MCP resource, projects the route
-into private request state, applies its policy, and freezes it for the call. Missing, malformed, or
+At runtime, Noodle Seed validates the configured stable audience, associates the caller with the exact
+transport-derived MCP resource, projects the route into private request state, applies its policy, and
+freezes it for the call. Missing, malformed, or
 disallowed claims return `connector_route_unavailable` before credential lookup or connector egress.
 Resolved URLs never enter artifacts, `${user}`, logs, model output, widgets, public confirmation review,
 broker cache keys, or delegated exchange assertions.
@@ -159,8 +160,9 @@ reuses the current frozen snapshot for the action and all nested or later reads.
 The application developer owns the direct/federated authorization server. It must publish its path-inserted
 RFC 8414 document as direct HTTP 200 JSON with exact issuer and HTTPS authorization/token/registration/JWKS
 endpoints, authorization-code and refresh grants, PKCE S256, public-client auth method `none`, RFC 8707
-resource handling, and public signing keys. Access tokens must include the exact MCP resource audience; there
-is no audience fallback.
+resource handling, and public signing keys. It validates each exact MCP resource on authorize, code exchange,
+and refresh, then maps approved versions of this app/environment to `noodleseed-customer-auth-prod`. Other
+apps and environments use distinct audiences.
 
 Run `noodle auth doctor src/server.ts` before sharing. Its bounded, read-only probes never register a client.
 Adding the embedded assistant does not choose or rewrite MCP customer auth.
@@ -216,7 +218,8 @@ noodle validate examples/customer-auth/src/server.ts
 
 Against a deployed customer-protected environment, set a short-lived real customer token only in
 `NOODLE_CUSTOMER_TOKEN` and add `--live --org <org> --app <app> --env <env>`. The live doctor performs
-credential exchanges without invoking any business tool.
+credential exchanges without invoking any business tool. Add `--version 1` when testing a pinned version;
+the reported customer resource must match that versioned MCP endpoint.
 
 ## Run locally
 
@@ -528,9 +531,9 @@ https://cloud.noodleseed.dev/o/noodleseed/customer-auth/mcp
 
 ## Auth boundary
 
-Noodle Seed verifies the configured OIDC issuer, audience, and exact MCP resource before reading identity or
-routing claims. Public caller identity contains the user/role/scope projection; the customer route remains
-private request state.
+Noodle Seed verifies the configured OIDC issuer and stable audience, then binds the exact transport-derived
+MCP resource before reading identity or routing claims. Public caller identity contains the user/role/scope
+projection; the customer route remains private request state.
 
 Connector-backed tools ask the broker for a route-bound delegated credential; only the endpoint key and
 fingerprint enter broker cache/single-flight state or the assertion. The route claim and inbound MCP bearer

package/skills/claude-code/examples/customer-auth/src/server.ts

@@ -89,7 +89,7 @@ export default server(
     interactions: { confirmationFallback: 'host' },
     auth: customerAuth.oidc({
       issuer: 'https://id.noodleseed.dev',
-      audience: 'https://org.cloud.noodleseed.dev/app/mcp',
+      audience: 'noodleseed-customer-auth-prod',
       claims: {
         id: 'sub',
         email: 'email',

package/skills/claude-code/examples/customer-auth/test/server.test.ts

@@ -26,7 +26,7 @@ describe('customer-auth example', () => {
     expect(manifest.server.auth).toEqual({
       kind: 'oidc',
       issuer: 'https://id.noodleseed.dev',
-      audience: 'https://org.cloud.noodleseed.dev/app/mcp',
+      audience: 'noodleseed-customer-auth-prod',
       claims: {
         id: 'sub',
         email: 'email',

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

@@ -5,6 +5,10 @@ connectors, secrets, flows, widgets, or handoff policy. It still uses the curren
 so new authors see where server-level branding belongs. Use it to smoke the author loop
 (`noodle validate` / `noodle dev`) or a first deploy.
 
+Protocol negotiation deliberately does not appear in `src/server.ts` or `noodle.json`. MCP versions
+are platform-owned: the same deployed app automatically serves compatible legacy clients and modern
+clients from its existing endpoint, without an app setting or redeploy.
+
 When an installed Noodle Developer plugin drives this example, its skill performs mapped lifecycle
 steps through the supported `noodle-readiness` tools and reports only stable public `noodle ...`
 commands as recovery text. Do not install or update a global CLI: the coding agent writes and tests

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.56.0 hash:6a9f132ddb79352e -->
+<!-- noodle-skill version:0.57.0 hash:6a9f132ddb79352e -->
 
 # Execute a Noodle Seed implementation plan
 

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

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

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

@@ -108,7 +108,7 @@ More: `auth.kind` is `bearer` | `apiKey` (needs `header`) | `clientCredentials`
 
 For `customerAuth.oidc(...)` and `.federatedOidc(...)`, the application developer owns the standards-compliant authorization server. Noodle verifies its access tokens; it does not proxy discovery, create OAuth clients, or repair the upstream server. For issuer `https://id.example.com/oauth`, publish the path-inserted RFC 8414 document at `https://id.example.com/.well-known/oauth-authorization-server/oauth` as direct unauthenticated HTTP 200 JSON — never a login redirect.
 
-That metadata must expose HTTPS `authorization_endpoint`, `token_endpoint`, `jwks_uri`, and RFC 7591 `registration_endpoint`; advertise authorization-code and refresh-token grants, Dynamic Client Registration, PKCE with `code_challenge_methods_supported: ["S256"]`, and public clients with `token_endpoint_auth_methods_supported: ["none"]`. Implement RFC 8707 `resource`, mint access-token `aud` for the exact MCP resource URL, and publish only public signing keys in JWKS. Run `noodle auth doctor src/server.ts`; its issuer-readiness probes perform bounded read-only GET checks and never register a client. A successful `noodle deploy --access customers` reports the same readiness without turning a diagnostic failure into a failed deployment.
+That metadata must expose HTTPS `authorization_endpoint`, `token_endpoint`, `jwks_uri`, and RFC 7591 `registration_endpoint`; advertise authorization-code and refresh-token grants, Dynamic Client Registration, PKCE with `code_challenge_methods_supported: ["S256"]`, and public clients with `token_endpoint_auth_methods_supported: ["none"]`. Validate the exact RFC 8707 `resource` on authorize, code exchange, and refresh, then map approved versions of one app/environment to the stable audience configured in `customerAuth`; use distinct audiences across apps and environments. Publish only public signing keys in JWKS. Run `noodle auth doctor src/server.ts`; its issuer-readiness probes perform bounded read-only GET checks and never register a client. A successful `noodle deploy --access customers` reports the same readiness without turning a diagnostic failure into a failed deployment.
 
 ## Auth-derived customer API endpoints
 
@@ -156,7 +156,7 @@ export default server(
     interactions: { confirmationFallback: 'host' },
     auth: customerAuth.oidc({
       issuer: 'https://id.noodleseed.dev',
-      audience: 'https://org.cloud.noodleseed.dev/app/mcp',
+      audience: 'noodleseed-customer-records-prod',
       routing: {
         endpoints: {
           customer_api: { claim: 'tenant.api_base_url' },
@@ -287,7 +287,7 @@ export async function tokenEndpoint(req: Request): Promise<Response> {
 }
 ```
 
-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. 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.
+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/references/build-an-mcp-server.md

@@ -23,6 +23,7 @@ Establish only the inputs needed for the requested stopping point. Follow `refer
 2. **Define the product contract.** For each job, write the user phrase, the intent-shaped tool or resource, its minimal typed input, the useful output, read/write effect, and backing operation. Design for user intent, not a 1:1 API endpoint wrapper.
 3. **Choose the smallest implementation.** Use native tools, resources, or prompts for local/static behavior; add a connector only when external data or actions are required. Keep response output small and model-readable.
 4. **Author in TypeScript.** Follow `references/authoring-workflow.md` for connector and flow patterns, `references/tool-design.md` for the model-facing tool surface, and `references/sdk-surface.md` for exact builders. These are this route’s complete canonical support set; use the router lookup catalog only when observed evidence names a different concern.
+   MCP protocol versions are platform-owned and negotiated automatically at the serving endpoint. Do not add protocol-version settings to server options, `noodle.json`, app manifests, or deployment configuration.
 5. **Validate and repair.** Run `noodle validate --json`. Parse `error.errors[]`, repair the cited `path`, and rerun validation. Consult the lookup catalog only for the specific reported error code; do not open another reference speculatively.
 6. **Run the local smoke.** After validation succeeds, run `noodle test --json` and repair any failure at that evidence layer.
 7. **Prove external behavior.** For connector-backed reads, set credentials through the effective local target and run a safe representative `noodle tools call`. Confirm populated mapped fields from real output, not merely successful registration.

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.56.0 hash:0f404109f4845683 -->
+<!-- noodle-skill version:0.57.0 hash:0f404109f4845683 -->
 
 # reporting-noodle-feedback
 

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

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

package/skills/codex/SKILL.md

@@ -3,7 +3,7 @@ name: noodle-seed
 description: "Use when building, validating, testing, deploying, or operating a local or hosted Noodle Seed MCP server or app authored in TypeScript with the noodle CLI."
 ---
 
-<!-- noodle-skill version:0.56.0 hash:ec5bfcd0d8165205 -->
+<!-- noodle-skill version:0.57.0 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.56.0 hash:0b2fd8c7e43fc69f -->
+<!-- noodle-skill version:0.57.0 hash:0b2fd8c7e43fc69f -->
 
 # authoring-mcp-servers
 

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

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

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

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

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

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

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

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

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

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

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

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

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

@@ -68,7 +68,7 @@ public `${user}` expression scope:
 ```ts
 auth: customerAuth.oidc({
   issuer: 'https://id.noodleseed.dev',
-  audience: 'https://org.cloud.noodleseed.dev/app/mcp',
+  audience: 'noodleseed-customer-auth-prod',
   claims: {
     id: 'sub',
     email: 'email',
@@ -93,7 +93,7 @@ auth: customerAuth.federatedOidc({
   issuers: [
     {
       issuer: 'https://id.customer-a.com',
-      audience: 'https://org.cloud.noodleseed.dev/app/mcp',
+      audience: 'noodleseed-customer-auth-prod',
       routing: {
         endpoints: {
           customer_api: { claim: 'tenant.api_base_url' },
@@ -102,7 +102,7 @@ auth: customerAuth.federatedOidc({
     },
     {
       issuer: 'https://login.customer-b.com',
-      audience: 'https://org.cloud.noodleseed.dev/app/mcp',
+      audience: 'noodleseed-customer-auth-prod',
       routing: {
         endpoints: {
           customer_api: { claim: 'organization.routes.customer_api' },
@@ -113,8 +113,9 @@ auth: customerAuth.federatedOidc({
 }),
 ```
 
-At runtime, Noodle Seed validates both the configured audience and exact MCP resource, projects the route
-into private request state, applies its policy, and freezes it for the call. Missing, malformed, or
+At runtime, Noodle Seed validates the configured stable audience, associates the caller with the exact
+transport-derived MCP resource, projects the route into private request state, applies its policy, and
+freezes it for the call. Missing, malformed, or
 disallowed claims return `connector_route_unavailable` before credential lookup or connector egress.
 Resolved URLs never enter artifacts, `${user}`, logs, model output, widgets, public confirmation review,
 broker cache keys, or delegated exchange assertions.
@@ -159,8 +160,9 @@ reuses the current frozen snapshot for the action and all nested or later reads.
 The application developer owns the direct/federated authorization server. It must publish its path-inserted
 RFC 8414 document as direct HTTP 200 JSON with exact issuer and HTTPS authorization/token/registration/JWKS
 endpoints, authorization-code and refresh grants, PKCE S256, public-client auth method `none`, RFC 8707
-resource handling, and public signing keys. Access tokens must include the exact MCP resource audience; there
-is no audience fallback.
+resource handling, and public signing keys. It validates each exact MCP resource on authorize, code exchange,
+and refresh, then maps approved versions of this app/environment to `noodleseed-customer-auth-prod`. Other
+apps and environments use distinct audiences.
 
 Run `noodle auth doctor src/server.ts` before sharing. Its bounded, read-only probes never register a client.
 Adding the embedded assistant does not choose or rewrite MCP customer auth.
@@ -216,7 +218,8 @@ noodle validate examples/customer-auth/src/server.ts
 
 Against a deployed customer-protected environment, set a short-lived real customer token only in
 `NOODLE_CUSTOMER_TOKEN` and add `--live --org <org> --app <app> --env <env>`. The live doctor performs
-credential exchanges without invoking any business tool.
+credential exchanges without invoking any business tool. Add `--version 1` when testing a pinned version;
+the reported customer resource must match that versioned MCP endpoint.
 
 ## Run locally
 
@@ -528,9 +531,9 @@ https://cloud.noodleseed.dev/o/noodleseed/customer-auth/mcp
 
 ## Auth boundary
 
-Noodle Seed verifies the configured OIDC issuer, audience, and exact MCP resource before reading identity or
-routing claims. Public caller identity contains the user/role/scope projection; the customer route remains
-private request state.
+Noodle Seed verifies the configured OIDC issuer and stable audience, then binds the exact transport-derived
+MCP resource before reading identity or routing claims. Public caller identity contains the user/role/scope
+projection; the customer route remains private request state.
 
 Connector-backed tools ask the broker for a route-bound delegated credential; only the endpoint key and
 fingerprint enter broker cache/single-flight state or the assertion. The route claim and inbound MCP bearer

package/skills/codex/examples/customer-auth/src/server.ts

@@ -89,7 +89,7 @@ export default server(
     interactions: { confirmationFallback: 'host' },
     auth: customerAuth.oidc({
       issuer: 'https://id.noodleseed.dev',
-      audience: 'https://org.cloud.noodleseed.dev/app/mcp',
+      audience: 'noodleseed-customer-auth-prod',
       claims: {
         id: 'sub',
         email: 'email',

package/skills/codex/examples/customer-auth/test/server.test.ts

@@ -26,7 +26,7 @@ describe('customer-auth example', () => {
     expect(manifest.server.auth).toEqual({
       kind: 'oidc',
       issuer: 'https://id.noodleseed.dev',
-      audience: 'https://org.cloud.noodleseed.dev/app/mcp',
+      audience: 'noodleseed-customer-auth-prod',
       claims: {
         id: 'sub',
         email: 'email',

package/skills/codex/examples/hello/README.md

@@ -5,6 +5,10 @@ connectors, secrets, flows, widgets, or handoff policy. It still uses the curren
 so new authors see where server-level branding belongs. Use it to smoke the author loop
 (`noodle validate` / `noodle dev`) or a first deploy.
 
+Protocol negotiation deliberately does not appear in `src/server.ts` or `noodle.json`. MCP versions
+are platform-owned: the same deployed app automatically serves compatible legacy clients and modern
+clients from its existing endpoint, without an app setting or redeploy.
+
 When an installed Noodle Developer plugin drives this example, its skill performs mapped lifecycle
 steps through the supported `noodle-readiness` tools and reports only stable public `noodle ...`
 commands as recovery text. Do not install or update a global CLI: the coding agent writes and tests

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.56.0 hash:6a9f132ddb79352e -->
+<!-- noodle-skill version:0.57.0 hash:6a9f132ddb79352e -->
 
 # Execute a Noodle Seed implementation plan
 

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

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

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

@@ -108,7 +108,7 @@ More: `auth.kind` is `bearer` | `apiKey` (needs `header`) | `clientCredentials`
 
 For `customerAuth.oidc(...)` and `.federatedOidc(...)`, the application developer owns the standards-compliant authorization server. Noodle verifies its access tokens; it does not proxy discovery, create OAuth clients, or repair the upstream server. For issuer `https://id.example.com/oauth`, publish the path-inserted RFC 8414 document at `https://id.example.com/.well-known/oauth-authorization-server/oauth` as direct unauthenticated HTTP 200 JSON — never a login redirect.
 
-That metadata must expose HTTPS `authorization_endpoint`, `token_endpoint`, `jwks_uri`, and RFC 7591 `registration_endpoint`; advertise authorization-code and refresh-token grants, Dynamic Client Registration, PKCE with `code_challenge_methods_supported: ["S256"]`, and public clients with `token_endpoint_auth_methods_supported: ["none"]`. Implement RFC 8707 `resource`, mint access-token `aud` for the exact MCP resource URL, and publish only public signing keys in JWKS. Run `noodle auth doctor src/server.ts`; its issuer-readiness probes perform bounded read-only GET checks and never register a client. A successful `noodle deploy --access customers` reports the same readiness without turning a diagnostic failure into a failed deployment.
+That metadata must expose HTTPS `authorization_endpoint`, `token_endpoint`, `jwks_uri`, and RFC 7591 `registration_endpoint`; advertise authorization-code and refresh-token grants, Dynamic Client Registration, PKCE with `code_challenge_methods_supported: ["S256"]`, and public clients with `token_endpoint_auth_methods_supported: ["none"]`. Validate the exact RFC 8707 `resource` on authorize, code exchange, and refresh, then map approved versions of one app/environment to the stable audience configured in `customerAuth`; use distinct audiences across apps and environments. Publish only public signing keys in JWKS. Run `noodle auth doctor src/server.ts`; its issuer-readiness probes perform bounded read-only GET checks and never register a client. A successful `noodle deploy --access customers` reports the same readiness without turning a diagnostic failure into a failed deployment.
 
 ## Auth-derived customer API endpoints
 
@@ -156,7 +156,7 @@ export default server(
     interactions: { confirmationFallback: 'host' },
     auth: customerAuth.oidc({
       issuer: 'https://id.noodleseed.dev',
-      audience: 'https://org.cloud.noodleseed.dev/app/mcp',
+      audience: 'noodleseed-customer-records-prod',
       routing: {
         endpoints: {
           customer_api: { claim: 'tenant.api_base_url' },
@@ -287,7 +287,7 @@ export async function tokenEndpoint(req: Request): Promise<Response> {
 }
 ```
 
-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. 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.
+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/references/build-an-mcp-server.md

@@ -23,6 +23,7 @@ Establish only the inputs needed for the requested stopping point. Follow `refer
 2. **Define the product contract.** For each job, write the user phrase, the intent-shaped tool or resource, its minimal typed input, the useful output, read/write effect, and backing operation. Design for user intent, not a 1:1 API endpoint wrapper.
 3. **Choose the smallest implementation.** Use native tools, resources, or prompts for local/static behavior; add a connector only when external data or actions are required. Keep response output small and model-readable.
 4. **Author in TypeScript.** Follow `references/authoring-workflow.md` for connector and flow patterns, `references/tool-design.md` for the model-facing tool surface, and `references/sdk-surface.md` for exact builders. These are this route’s complete canonical support set; use the router lookup catalog only when observed evidence names a different concern.
+   MCP protocol versions are platform-owned and negotiated automatically at the serving endpoint. Do not add protocol-version settings to server options, `noodle.json`, app manifests, or deployment configuration.
 5. **Validate and repair.** Run `noodle validate --json`. Parse `error.errors[]`, repair the cited `path`, and rerun validation. Consult the lookup catalog only for the specific reported error code; do not open another reference speculatively.
 6. **Run the local smoke.** After validation succeeds, run `noodle test --json` and repair any failure at that evidence layer.
 7. **Prove external behavior.** For connector-backed reads, set credentials through the effective local target and run a safe representative `noodle tools call`. Confirm populated mapped fields from real output, not merely successful registration.

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