@noodleseed/agent-kit 0.53.0 → 0.55.0

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

@@ -23,17 +23,46 @@ describe('customer-auth example', () => {
       name: 'Noodle Seed Assistant',
       colorScheme: 'auto',
     });
-    expect(manifest.server.auth).toMatchObject({
-      kind: 'bridge',
-      provider: 'firebase',
-      projectId: '${env.FIREBASE_PROJECT_ID}',
-      apiKey: '${env.FIREBASE_WEB_API_KEY}',
-      authDomain: '${env.FIREBASE_AUTH_DOMAIN}',
-      user: {
-        roles: 'claims.roles',
-        scopes: 'claims.scopes',
+    expect(manifest.server.auth).toEqual({
+      kind: 'oidc',
+      issuer: 'https://id.noodleseed.dev',
+      audience: 'https://org.cloud.noodleseed.dev/app/mcp',
+      claims: {
+        id: 'sub',
+        email: 'email',
+        name: 'name',
+        orgs: 'permissions.orgs',
+        roles: 'permissions.roles',
+        scopes: 'permissions.scopes',
+      },
+      routing: {
+        endpoints: {
+          customer_api: { claim: 'tenant.api_base_url' },
+        },
+      },
+    });
+    const catalog = app.toConnectorCatalog();
+    expect(catalog?.connectors).toHaveLength(1);
+    expect(catalog?.connectors[0]?.http).toMatchObject({
+      baseUrl: {
+        kind: 'customerEndpoint',
+        name: 'customer_api',
+        policy: { allowedHttpsHostSuffixes: ['api.noodleseed.dev'] },
+      },
+      auth: {
+        kind: 'delegatedTokenExchange',
+        tokenUrl: 'https://id.noodleseed.dev/oauth/token',
+        clientId: '${env.CUSTOMER_API_CLIENT_ID}',
+        clientSecret: 'CUSTOMER_API_CLIENT_SECRET',
       },
     });
+    expect(
+      Object.values(catalog?.connectors[0]?.http?.operations ?? {}).every(
+        (operation) => operation.type === 'read',
+      ),
+    ).toBe(true);
+    expect(catalog?.connectors[0]?.http).not.toHaveProperty('allowedOrigins');
+    expect(JSON.stringify({ manifest, catalog })).not.toContain('tenant-a.api.noodleseed.dev');
     expect(manifest.tools.find((tool) => tool.name === 'list_org_apps')?.authorization).toEqual({
       requiredScopes: ['org_apps:read'],
       allowedRoles: ['org_admin', 'org_member'],

package/skills/claude-code/examples/food-ordering/README.md

@@ -84,13 +84,14 @@ noodle connect inspector
 ## Deploy
 
 ```sh
-noodle link --org demo --app food-ordering
-noodle deploy --access owner-only
+noodle deploy --org demo --app food-ordering --env prod --access owner-only
 noodle open
 ```
 
-Use `--access org-members` for an org-wide internal demo. This example has no connector secrets and does not
-include tokens, caller-key mechanisms, or `.env.noodle` values.
+That one deploy command preflights the complete target, creates a missing app/environment, and verifies
+hosted readiness. If it is interrupted, rerun the same command to resume the unfinished operation without a
+duplicate deployment. Use `--access org-members` for an org-wide internal demo. This example has no
+connector secrets and does not include tokens, caller-key mechanisms, or `.env.noodle` values.
 
 ## Demo Assets
 

package/skills/claude-code/examples/google-bigquery/README.md

@@ -99,3 +99,9 @@ Compilation and tests need no Google credentials:
 noodle validate
 noodle test
 ```
+
+For a local run that needs the declared provider values, the exact project-root `.env` can contain
+`GOOGLE_WIF_PROVIDER` and `GOOGLE_SERVICE_ACCOUNT`; `noodle dev` uses matching declarations only as a
+read-only fallback, and scoped `.env.noodle` values override it. Never commit or ask an agent to read either
+file. Interactive deploy can offer a default-No import of matching missing names to the visible target;
+non-interactive and plugin deploys keep the value-free `noodle variables set ... --from-env` recovery path.

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.53.0 hash:6a9f132ddb79352e -->
+<!-- noodle-skill version:0.55.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.53.0 hash:efffbf82007f935d -->
+<!-- noodle-skill version:0.55.0 hash:efffbf82007f935d -->
 
 # publishing-mcp-integrations
 

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

@@ -8,6 +8,7 @@
 - Connectors
 - HTTP connector example (full server)
 - Customer OAuth for remote MCP clients
+- Auth-derived customer API endpoints
 - Per-tool authorization
 - Delegated downstream auth (call your API as the signed-in user)
 - Invocation context
@@ -109,6 +110,74 @@ For `customerAuth.oidc(...)` and `.federatedOidc(...)`, the application develope
 
 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.
 
+## Auth-derived customer API endpoints
+
+Use a customer endpoint when the verified IdP selects a different API base URL for each SaaS customer. The claim contains the complete base URL; tool input and `${user}` do not select it. Declare one named policy, use that reference as the connector `baseUrl`, and map its claim path in direct OIDC or on every federated issuer:
+
+```ts
+import { connector, customerAuth, customerEndpoint, secret, server, tool, variable, z } from '@noodleseed/one';
+
+const customerApi = customerEndpoint('customer_api', {
+  allowedHttpsHostSuffixes: ['api.noodleseed.dev'],
+});
+
+const api = connector('customer_api_connector').version('1.0.0').http({
+  baseUrl: customerApi,
+  auth: {
+    kind: 'delegatedTokenExchange',
+    tokenUrl: 'https://id.noodleseed.dev/oauth/token',
+    clientId: variable('CUSTOMER_API_CLIENT_ID'),
+    clientSecret: secret('CUSTOMER_API_CLIENT_SECRET'),
+  },
+  operations: {
+    list_records: {
+      type: 'read',
+      method: 'GET',
+      path: '/records',
+      input: z.object({}),
+      output: z.object({ records: z.array(z.unknown()).max(100) }),
+    },
+  },
+});
+
+export default server(
+  'customer_records',
+  {
+    title: 'Customer records',
+    version: '1.0.0',
+    use: { api },
+    auth: customerAuth.oidc({
+      issuer: 'https://id.noodleseed.dev',
+      audience: 'https://org.cloud.noodleseed.dev/app/mcp',
+      routing: {
+        endpoints: {
+          customer_api: { claim: 'tenant.api_base_url' },
+        },
+      },
+    }),
+  },
+  [
+    tool('list_records', {
+      description: 'List records for the signed-in customer.',
+      input: z.object({}),
+      output: z.object({ records: z.array(z.unknown()).max(100) }),
+      fulfil: ({ connectors }) => {
+        const result = connectors.api.listRecords();
+        return { records: result.records };
+      },
+    }),
+  ],
+);
+```
+
+`customerEndpoint` accepts exactly one non-empty policy arm: exact HTTPS origins, or HTTPS hostname suffixes. Exact policies may authorize an explicit non-default port; suffix policies allow port 443 and match only the exact host or dot-boundary subdomains. Do not add connector `allowedOrigins` to a customer-routed connector. Its fixed credential/token endpoints are validated independently and cannot come from caller claims.
+
+Every federated issuer must repeat every endpoint key used by the app, although each issuer may choose a different claim path. Endpoint names use lowercase letters, numbers, and underscores. Resolved claims must be exact absolute HTTPS URLs of at most 2,048 UTF-8 bytes with no userinfo, query, fragment, IP literal, special-use host, or unsafe whitespace/control characters. The runtime preserves a canonical optional base path.
+
+Resolved customer URLs are private routing authority: they never enter the manifest/artifact, `${user}`, logs, model output, widgets, confirmation review, cache keys, or delegated-token-exchange assertions. Routed read operations may be used by tools, including their declared nested connector calls. Customer-routed action operations fail compilation with `customer_endpoint_action_unsupported`; routed resources, prompts, and ambient context fail with `customer_endpoint_surface_unsupported` in this release.
+
+At runtime, a missing, malformed, or disallowed claim returns the same safe `connector_route_unavailable` tool error before credential lookup or connector egress. `tools/list` remains based only on roles and scopes, so route availability neither reveals tenant topology nor changes the existing authorization filter.
+
 ## Per-tool authorization
 
 Keep endpoint authentication in `customerAuth.*(...)`, then narrow individual tools with the optional typed `authorization` rule. Every `requiredScopes` value is required; any one `allowedRoles` value is sufficient; when both lists are present, both conditions apply. Omit `authorization` for an unrestricted tool. Do not invent a policy expression language or infer authorization from tool arguments, page context, connector output, email domains, or other unverified data.
@@ -135,7 +204,7 @@ Role values are trusted only from the explicitly configured claim path (or the p
 
 Use delegated connector auth when the downstream API must enforce its own per-user authorization — a shared service credential plus a forwarded user id would bypass it. Three shapes exist; pick by who owns the downstream:
 
-- **`delegatedTokenExchange`** — your own API. The platform signs a short-lived, verifiable assertion of the signed-in user and exchanges it at a token endpoint you implement (RFC 8693). Works with verified customer OIDC identities, the built-in Firebase/Microsoft adapters, and embedded-assistant sessions; no per-user OAuth enrollment.
+- **`delegatedTokenExchange`** — your own API. The platform signs a short-lived, verifiable assertion of the signed-in user and exchanges it at a token endpoint you implement (RFC 8693). It works with verified customer OIDC identities and the built-in Firebase/Microsoft adapters; no per-user OAuth enrollment. Embedded-assistant sessions support this exchange for static connectors. Customer-routed connectors require a direct or federated MCP OIDC request and fail closed in embedded-assistant sessions because those sessions carry no IdP endpoint claim.
 - **`delegatedOAuth` with `provider: "firebase" | "microsoft"`** — Noodle-managed bridge providers using stored per-user refresh tokens. Requires the matching `customerAuth` bridge; any other provider string is the compile error `unsupported_delegated_provider`.
 - **`delegatedSessionCookie`** — Firebase-managed session-cookie apps only; not a generic mechanism.
 
@@ -144,7 +213,7 @@ Use delegated connector auth when the downstream API must enforce its own per-us
 ```ts
 auth: {
   kind: 'delegatedTokenExchange',
-  tokenUrl: 'https://app.example.com/api/assistant/oauth/token', // origin must be in allowedOrigins
+  tokenUrl: 'https://app.example.com/api/assistant/oauth/token', // fixed HTTPS; static connectors also allowlist its origin
   clientId: variable('EXAMPLE_DELEG_CLIENT_ID'),
   clientSecret: secret('EXAMPLE_DELEG_CLIENT_SECRET'),
   scopes: ['time_off'],           // optional
@@ -167,7 +236,7 @@ scope=time_off            (space-joined, when configured)
 audience=example-api      (when configured)
 ```
 
-The `subject_token` claims: `iss` (platform issuer; JWKS at `{iss}/.well-known/jwks.json`), `sub` (verified user id), `aud` (your configured audience or the tokenUrl), `email`, `name`, `claims` (declared session claims), `tenant` (`org/app/env`), `deployment`, `iat`, `exp` (about 120 s), `jti`. Respond with `{ "access_token": "...", "token_type": "Bearer", "expires_in": 900 }`; the broker caches per user + connector + scopes until `expires_in` minus 300 s and presents the token downstream as `Authorization: Bearer`.
+The `subject_token` claims: `iss` (platform issuer; JWKS at `{iss}/.well-known/jwks.json`), `sub` (verified user id), `aud` (your configured audience or the tokenUrl), `email`, `name`, `claims` (declared session claims), `tenant` (`org/app/env`), `deployment`, `iat`, `exp` (about 120 s), `jti`. A routed exchange adds `route: { key, fingerprint }`, never the customer URL; credential cache and single-flight keys include that route binding. Respond with `{ "access_token": "...", "token_type": "Bearer", "expires_in": 900 }`; the broker caches per user + connector + scopes + route until `expires_in` minus 300 s and presents the token downstream as `Authorization: Bearer`.
 
 ### The downstream token endpoint (your backend)
 
@@ -292,4 +361,4 @@ To place the same server tools inside a SaaS web app, declare `assistant: embedd
 
 ## Boundaries
 
-Do not hand-author manifest JSON/YAML, runtime artifacts, connector IR, or hosted asset metadata. Do not read or copy secrets, bearer tokens, refresh tokens, static access keys, `.env.noodle`, or `~/.noodle/config.json`. Hosted access is identity-based — do not add static data-plane credential paths.
+Do not hand-author manifest JSON/YAML, runtime artifacts, connector IR, or hosted asset metadata. Do not read or copy secrets, bearer tokens, refresh tokens, static access keys, `.env`, `.env.noodle`, or `~/.noodle/config.json`. Hosted access is identity-based — do not add static data-plane credential paths.

package/skills/claude-code/references/compile-errors.md

@@ -63,5 +63,13 @@ Run `noodle validate` (add `--json` for the machine-readable envelope, `--fix-pr
 | `unsupported_credential_profile` | Select a credential profile declared by the connector and accepted by the operation; use the reported suggestions instead of inventing a profile name. |
 | `credential_scope_mismatch` | Declare a connection source whose scopes include every operation-required scope, or select an external exchange provider that can mint them. |
 | `credential_audience_mismatch` | Set the connection source audience to the operation-required audience exactly, or use an external exchange provider that can mint it. |
+| `customer_endpoint_auth_required` | Protect the app with direct or federated `customerAuth` OIDC and map every reachable `customerEndpoint` key under auth routing. |
+| `customer_endpoint_mapping_required` | Add the endpoint key at the cited auth routing path; every direct/federated issuer must map every customer endpoint used by the app. |
+| `customer_endpoint_unknown_mapping` | Remove the unknown or unused auth routing key, or use that exact declared `customerEndpoint` key from a reachable connector operation. |
+| `customer_endpoint_bridge_unsupported` | Replace the Firebase/Microsoft bridge with direct or federated OIDC before using auth-derived customer connector endpoints. |
+| `customer_endpoint_action_unsupported` | Use a read operation for this customer-routed call until route-bound action confirmation support is available. |
+| `customer_endpoint_surface_unsupported` | Move the customer-routed call into a tool fulfilment; routed resources, prompts, and ambient providers are unsupported. |
+| `customer_endpoint_credential_source_unsupported` | Remove the manifest connection binding; a customer-routed connector uses its declared delegated token exchange auth or no auth. |
+| `customer_endpoint_policy_conflict` | Give every reachable declaration of this endpoint key one identical policy, or rename keys whose allowed origins differ. |
 | `unused_connector_alias` | A declared connector alias is never called; remove the unused `use` entry or wire it into a tool. |
 | `arg_mismatch` | A connector call is missing or adds arguments; match the operation signature under `expected`/`got`. |

package/skills/claude-code/references/connect-an-api.md

@@ -163,7 +163,7 @@ noodle secrets set SOME_API_KEY --runtime cloud --scope env --org <org> --app <a
 
 `--runtime` is required whenever `--org`, `--app`, and `--env` together name a complete hosted target: a command that looks remote must never fall back to writing `.env.noodle`. Omitting it fails with `runtime_required` before anything is written.
 
-Local secrets live in `./.env.noodle` (never commit it). A required `secret(...)` or `variable(...)` that cannot resolve fails boot closed. `noodle tools call` / `noodle test` / `noodle dev` / `noodle devtools` stop before exposing an empty endpoint and print the exact effective target plus recovery command.
+Scoped local values live in `./.env.noodle`; the exact project-root `.env` is a read-only fallback for matching `secret("NAME")` / `variable("NAME")` declarations during local authoring. Never commit or print either file. Local authoring may read them only through this managed resolution path, and an interactive human `noodle deploy` may copy only missing declared `.env` names through its default-No import consent flow; agents and non-interactive runs use the value-free recovery commands instead. A required value that cannot resolve makes local commands stop before exposing an empty endpoint.
 
 ### Prove real output
 

package/skills/claude-code/references/deploy-and-ops.md

@@ -16,7 +16,7 @@ Do not broaden a request to prepare, inspect, diagnose, or validate into permiss
 
 ## Command and service contract
 
-Use `references/cli-commands.md` as the generated command, flag, and exit-code contract. Consult the live command catalog before acting, and treat the service response as the authority for resulting hosted state. This reference intentionally does not duplicate operational command sequences, defaults, or status semantics.
+Use `references/cli-commands.md` as the generated command, flag, and exit-code contract. Consult the live command catalog before acting, and treat the service response as the authority for resulting hosted state. For an authorized deployment, use the one canonical public flow and follow its structured configuration actions and resume command; do not replace it with an internal script or a hand-built sequence. This reference intentionally does not duplicate operational command sequences, defaults, or status semantics.
 
 ## Evidence and stop conditions
 

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

@@ -97,16 +97,13 @@ Give every business action a portable `tool(..., { title: "Complete task", descr
 
 ## Configure and deploy
 
-Local MCP authoring and tests need no account, but an external browser embed needs an active assistant-enabled deployment before a backend client can be created. Set the model values on the target org/app/env, then deploy:
+Local MCP authoring and tests need no account, but an external browser embed needs an active assistant-enabled deployment before a backend client can be created. Start with the canonical deploy:
 
 ```sh
-noodle variables set ASSISTANT_MODEL_BASE_URL --scope env --runtime cloud --org <org> --app <app> --env <env> --value <https-model-base-url>
-noodle variables set ASSISTANT_MODEL --scope env --runtime cloud --org <org> --app <app> --env <env> --value <model>
-noodle secrets set ASSISTANT_MODEL_API_KEY --scope env --runtime cloud --org <org> --app <app> --env <env> --from-env ASSISTANT_MODEL_API_KEY
 noodle deploy --org <org> --app <app> --env <env>
 ```
 
-Do not put these model values in the embedding SaaS environment. A production deployment may omit a local origin; include a loopback origin only when local browser integration is required.
+Deploy preflights the complete target before upload. In an interactive terminal it collects all missing model variables and secrets, then continues. In a non-interactive run it reports every missing name and safe `noodle variables set ... --from-env` / `noodle secrets set ... --from-env` action; perform every action and repeat the same deploy command. Values never appear in the preflight report or resume state. Do not put these model values in the embedding SaaS environment. A production deployment may omit a local origin; include a loopback origin only when local browser integration is required.
 
 ## Access modes and customer auth
 
@@ -499,7 +496,7 @@ The check reports only required and missing environment names, never their value
 
 Inspect the host repository for generated environment bindings after adding names. Run its existing generator, review the diff, commit generated types only when that repository requires them, then run the production-equivalent host build. Do not invent a framework command or add a second generator.
 
-Promotion checklist: provision each environment in the backend secret manager; map names through the CI environment and any secret allowlist or secrets file; run the presence-only preflight before asset upload; promote configuration before code; run the post-deploy probes from the JSON contract; rotate the assistant client and delegated credential independently, then rerun the same checks.
+Promotion checklist: provision each environment in the backend secret manager; map names through the CI environment and any secret allowlist or secrets file; run the presence-only host preflight; run the canonical deploy so its configuration preflight completes before asset upload; run the post-deploy probes from the JSON contract; rotate the assistant client and delegated credential independently, then rerun the same checks.
 
 Devtools privacy gate: default model and connector exercises to synthetic or mock data. Before Devtools Chat sends real connector data to an external model, disclose the data flow and obtain the user's approval. A local validation pass is not that approval.
 

package/skills/claude-code/references/sdk-surface.md

@@ -54,6 +54,7 @@ Platform helper connectors are explicit subpath imports from `@noodleseed/one/pl
 ### Other
 
 - `clientCredentials`
+- `customerEndpoint`
 - `embeddedAssistant`
 - `externalExchange`
 - `gmailConnector`

package/skills/claude-code/references/troubleshooting.md

@@ -8,7 +8,7 @@
 
 ## First moves
 
-Re-run the local gates before debugging in-host: `noodle validate`, `noodle check` (add `--target chatgpt` for ChatGPT-specific requirements), and `noodle doctor`. Confirm the CLI is current with `noodle update --check` and that the project-local skill is intact with `noodle agents doctor --json` — host metadata requirements evolve and fixes ship in the CLI/agent-kit. Never paste tokens, secrets, or `.env.noodle` values into prompts or logs while debugging.
+Re-run the local gates before debugging in-host: `noodle validate`, `noodle check` (add `--target chatgpt` for ChatGPT-specific requirements), and `noodle doctor`. Confirm the CLI is current with `noodle update --check` and that the project-local skill is intact with `noodle agents doctor --json` — host metadata requirements evolve and fixes ship in the CLI/agent-kit. Never paste tokens, secrets, or `.env` / `.env.noodle` values into prompts or logs while debugging.
 
 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`.
 

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.53.0 hash:0f404109f4845683 -->
+<!-- noodle-skill version:0.55.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.53.0 hash:6ef6ef551e26b78e -->
+<!-- noodle-skill version:0.55.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.53.0 hash:18e16a8fa4c68b86 -->
+<!-- noodle-skill version:0.55.0 hash:ec5bfcd0d8165205 -->
 
 # Noodle Seed
 
@@ -82,7 +82,7 @@ When you discover a bug, missing capability, misleading doc, or improvement idea
 
 ## Safety
 
-- Keep secrets, bearer tokens, refresh tokens, static access keys, `.env.noodle` values, and `~/.noodle/config.json` out of prompts, logs, docs, tests, and generated files.
+- Keep secrets, bearer tokens, refresh tokens, static access keys, `.env` / `.env.noodle` values, and `~/.noodle/config.json` out of prompts, logs, docs, tests, and generated files.
 - Never expose an internal launcher or private installation path, ask the user to paste a command the plugin can execute, or use an ad hoc shell/file-parsing pipeline to move a secret. Use the typed secret-from-environment tool or `noodle secrets set ... --from-env NAME`.
 - Do not hand-author manifest JSON/YAML, runtime artifacts, connector IR, or hosted asset metadata.
 - Do not add static data-plane credential paths; hosted access is identity-based.

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.53.0 hash:0b2fd8c7e43fc69f -->
+<!-- noodle-skill version:0.55.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.53.0 hash:f7fa54992c8d7692 -->
+<!-- noodle-skill version:0.55.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.53.0 hash:1e86b8704f407bd3 -->
+<!-- noodle-skill version:0.55.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.53.0 hash:aa715bae12041d7c -->
+<!-- noodle-skill version:0.55.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.53.0 hash:93e735b7ffb45df1 -->
+<!-- noodle-skill version:0.55.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.53.0 hash:76cce86729cffbee -->
+<!-- noodle-skill version:0.55.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.53.0 hash:cc54a67f21c0ecdb -->
+<!-- noodle-skill version:0.55.0 hash:cc54a67f21c0ecdb -->
 
 # embedding-mcp-assistants