@noodleseed/agent-kit 0.66.0 → 0.68.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@noodleseed/agent-kit",
-  "version": "0.66.0",
+  "version": "0.68.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.66.0 hash:13ddce01769caae4 -->
+<!-- noodle-skill version:0.68.0 hash:13ddce01769caae4 -->
 
 # 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.66.0 hash:11523cb33b9473c0 -->
+<!-- noodle-skill version:0.68.0 hash:11523cb33b9473c0 -->
 
 # 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.66.0 hash:9fd67d4d24328e15 -->
+<!-- noodle-skill version:0.68.0 hash:9fd67d4d24328e15 -->
 
 # 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 all four API-evidence inputs exist—and only then: API base URL, authentication scheme, representative safe read, and observed response."
 ---
 
-<!-- noodle-skill version:0.66.0 hash:21bbd3ec441ffd30 -->
+<!-- noodle-skill version:0.68.0 hash:21bbd3ec441ffd30 -->
 
 # connecting-apis-to-mcp
 

package/skills/claude-code/creating-product-agent-guides/SKILL.md

@@ -3,7 +3,7 @@ name: creating-product-agent-guides
 description: "Use when a Noodle Seed MCP server needs a new or revised product agent guide, App Package skill, or explicit product-skill regeneration."
 ---
 
-<!-- noodle-skill version:0.66.0 hash:0fa48a82fe836cf0 -->
+<!-- noodle-skill version:0.68.0 hash:0fa48a82fe836cf0 -->
 
 # creating-product-agent-guides
 

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.66.0 hash:aa715bae12041d7c -->
+<!-- noodle-skill version:0.68.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.66.0 hash:93e735b7ffb45df1 -->
+<!-- noodle-skill version:0.68.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.66.0 hash:78a6f181b61f92f1 -->
+<!-- noodle-skill version:0.68.0 hash:78a6f181b61f92f1 -->
 
 # 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.66.0 hash:cc54a67f21c0ecdb -->
+<!-- noodle-skill version:0.68.0 hash:cc54a67f21c0ecdb -->
 
 # embedding-mcp-assistants
 

package/skills/claude-code/examples/acme-discovery/README.md

@@ -27,8 +27,8 @@ There is no second tool set and no second app — one `server.ts`, projected ont
 `capabilities` is the entire externally reachable surface, so it stays short enough to review at a glance
 and closed by default: a tool added to this server later is unreachable from the website until someone
 lists it. A tool that needed a signed-in user could not be listed here at all (the compiler rejects it);
-serving those to visitors means `publicWebsite({ ..., signIn: true })`, which lets a visitor sign in
-mid-conversation through Acme's own login.
+serve those from `authenticatedWebsite({ origins })` instead, where Acme's own backend proves who the
+visitor is. Mid-conversation sign-in on a public surface is not available yet.
 
 ## Design spec (write this before the code)
 

package/skills/claude-code/examples/acme-tasks/README.md

@@ -72,6 +72,29 @@ noodle tools call complete_task --args '{"task":"review_pr","title":"Review the
 noodle check --target chatgpt
 ```
 
+## Product agent guide
+
+[`src/agent-guide.ts`](src/agent-guide.ts) expresses the same three prioritized workflows as one host-neutral
+`agentGuide`. It supplies product judgment such as grounding and confirmation while the compiler derives
+capability schemas, annotations, visibility, and widget relationships from `server.ts`. The guide does not
+weaken `complete_task` confirmation or make the app-only `set_priority` tool model-visible.
+
+Preview the generated Codex and Claude Code product skills before installing them:
+
+```sh
+noodle agents setup --json
+noodle agents setup --write
+```
+
+After changing a workflow or capability, regeneration is explicit so a normal Noodle workflow-skill update
+cannot overwrite the app product skill or local modifications:
+
+```sh
+noodle agents setup --regenerate-app-skill --json
+noodle agents setup --write --regenerate-app-skill
+noodle agents doctor --json
+```
+
 ## Deploy
 
 ```sh

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.66.0 hash:6a9f132ddb79352e -->
+<!-- noodle-skill version:0.68.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.66.0 hash:efffbf82007f935d -->
+<!-- noodle-skill version:0.68.0 hash:efffbf82007f935d -->
 
 # publishing-mcp-integrations
 

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

@@ -84,19 +84,11 @@ At most one public surface (`public` or `mixed`) and at most one authenticated s
 
 A public surface **must** declare `capabilities`: the exact positive allowlist it may reach. It is required by the type, and it is the whole externally reachable surface — a reviewer should read it in one screenful. Anything absent stays private, and a capability added to the server later is excluded until someone lists it. `authenticatedWebsite` may also take `capabilities` to narrow the in-app surface; omitted, it projects the whole server.
 
-### Mixed surfaces: let a visitor sign in mid-conversation
+### Mixed surfaces: not available yet
 
-Add `signIn: true` to a public surface when some capabilities need a signed-in user. The surface becomes `mixed`: anonymous visitors start immediately, and an identity-dependent capability becomes a **sign-in trigger** rather than a compile error — the same shape ChatGPT and Claude use for connectors that work with or without a linked account.
+`publicWebsite({ signIn: true })` **throws**. Mid-conversation sign-in has no runtime: nothing offers the visitor a way to sign in, so an identity-dependent capability on such a surface would simply be refused — and accepting it would also give up the compile-time guard that plain `public` provides. The option stays declared so the vocabulary and wire shape are settled.
 
-```ts
-access: publicWebsite({
-  origins: ["https://www.example.com"],
-  capabilities: [answerProductQuestion, requestDemo, myOrders],
-  signIn: true,   // `myOrders` reads ${user}; visitors sign in to reach it
-}),
-```
-
-Elevation runs through the **host application’s own login**, never a Noodle-operated one: the page signs the visitor in and its backend exchanges that verified user for an elevated session on the same conversation. Do not build a second identity provider for this.
+Until it ships, split the audiences: keep anonymous-safe capabilities on `publicWebsite`, and serve identity-dependent ones from `authenticatedWebsite({ origins })`, where the embedding backend proves who the visitor is. One assistant can declare both.
 
 A connector-backed side effect needs **two** independent declarations to be reachable from a public or mixed surface: inclusion in `capabilities` **and** `{ confirm: true }` on the operation. Signing in proves who the visitor is; it does not pre-authorize an effect, so confirmation still applies on a mixed surface. Confirmation is never authentication or business authorization — the customer backend still owns payload validation, abuse controls, and idempotency. Local or session-only widget state needs no confirmation.
 

package/skills/claude-code/references/product-agent-guides.md

@@ -8,7 +8,7 @@ Do not wait for the user to name `agentGuide`. During every MCP server or App bu
 
 Author a guide when any of these conditions applies:
 
-- A request for an App Package, product skill, plugin, or agent distribution requires one.
+- A request for an App Package or app product skill requires one. A marketplace plugin or customer-agent distribution would also need this source, but those per-app distribution surfaces are not available in this foundation.
 - Multiple capabilities participate in one user workflow, especially when order or purpose matters.
 - Safe or useful operation depends on product-specific ordering, grounding, clarification, boundaries, or representative examples that capability descriptions cannot express.
 
@@ -16,6 +16,12 @@ A product with a single self-explanatory capability may omit the guide when its
 
 Make the judgment from the user’s stated outcome and grounded product evidence. If a guide is warranted but a decision-changing workflow or boundary is unknown, ask only for that missing product input; never fabricate it. The user should not need to know this feature name to receive the benefit.
 
+## Scope boundaries
+
+Noodle workflow skills teach a coding agent how to build and operate Noodle projects. The generated app product skill is team-local guidance for using one product. A marketplace plugin is a separate host distribution bundle.
+
+Per-app marketplace plugin generation and customer-agent distribution are not available in this foundation. If the user asks for either, explain the boundary and stop at the local App Package and product-skill workflow. Do not claim a listing, submission bundle, hosted distribution, or customer-agent projection.
+
 ## Creation workflow
 
 1. **Inspect grounded capability evidence.** Read the configured TypeScript entrypoint (`server.ts` or `src/server.ts`) and identify its exact declared tools, resources, prompts, descriptions, visibility, annotations, authorization, and widget relationships. Treat schemas and compiled annotations as facts. Never invent or guess a tool, resource, prompt, capability kind, workflow, or weaker write boundary.

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

package/skills/claude-code/wrapping-existing-applications/SKILL.md

@@ -3,7 +3,7 @@ name: wrapping-existing-applications
 description: "Use when an existing application has no stable usable API and needs a read-only, identity-first Noodle Seed integration plan before implementation."
 ---
 
-<!-- noodle-skill version:0.66.0 hash:eccc3c158dcafba8 -->
+<!-- noodle-skill version:0.68.0 hash:eccc3c158dcafba8 -->
 
 # wrapping-existing-applications
 

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.66.0 hash:13ddce01769caae4 -->
+<!-- noodle-skill version:0.68.0 hash:13ddce01769caae4 -->
 
 # 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.66.0 hash:11523cb33b9473c0 -->
+<!-- noodle-skill version:0.68.0 hash:11523cb33b9473c0 -->
 
 # 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.66.0 hash:9fd67d4d24328e15 -->
+<!-- noodle-skill version:0.68.0 hash:9fd67d4d24328e15 -->
 
 # building-mcp-apps
 

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

@@ -3,7 +3,7 @@ name: connecting-apis-to-mcp
 description: "Use when all four API-evidence inputs exist—and only then: API base URL, authentication scheme, representative safe read, and observed response."
 ---
 
-<!-- noodle-skill version:0.66.0 hash:21bbd3ec441ffd30 -->
+<!-- noodle-skill version:0.68.0 hash:21bbd3ec441ffd30 -->
 
 # connecting-apis-to-mcp
 

package/skills/codex/creating-product-agent-guides/SKILL.md

@@ -3,7 +3,7 @@ name: creating-product-agent-guides
 description: "Use when a Noodle Seed MCP server needs a new or revised product agent guide, App Package skill, or explicit product-skill regeneration."
 ---
 
-<!-- noodle-skill version:0.66.0 hash:0fa48a82fe836cf0 -->
+<!-- noodle-skill version:0.68.0 hash:0fa48a82fe836cf0 -->
 
 # creating-product-agent-guides
 

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.66.0 hash:aa715bae12041d7c -->
+<!-- noodle-skill version:0.68.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.66.0 hash:93e735b7ffb45df1 -->
+<!-- noodle-skill version:0.68.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.66.0 hash:78a6f181b61f92f1 -->
+<!-- noodle-skill version:0.68.0 hash:78a6f181b61f92f1 -->
 
 # 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.66.0 hash:cc54a67f21c0ecdb -->
+<!-- noodle-skill version:0.68.0 hash:cc54a67f21c0ecdb -->
 
 # embedding-mcp-assistants
 

package/skills/codex/examples/acme-discovery/README.md

@@ -27,8 +27,8 @@ There is no second tool set and no second app — one `server.ts`, projected ont
 `capabilities` is the entire externally reachable surface, so it stays short enough to review at a glance
 and closed by default: a tool added to this server later is unreachable from the website until someone
 lists it. A tool that needed a signed-in user could not be listed here at all (the compiler rejects it);
-serving those to visitors means `publicWebsite({ ..., signIn: true })`, which lets a visitor sign in
-mid-conversation through Acme's own login.
+serve those from `authenticatedWebsite({ origins })` instead, where Acme's own backend proves who the
+visitor is. Mid-conversation sign-in on a public surface is not available yet.
 
 ## Design spec (write this before the code)
 

package/skills/codex/examples/acme-tasks/README.md

@@ -72,6 +72,29 @@ noodle tools call complete_task --args '{"task":"review_pr","title":"Review the
 noodle check --target chatgpt
 ```
 
+## Product agent guide
+
+[`src/agent-guide.ts`](src/agent-guide.ts) expresses the same three prioritized workflows as one host-neutral
+`agentGuide`. It supplies product judgment such as grounding and confirmation while the compiler derives
+capability schemas, annotations, visibility, and widget relationships from `server.ts`. The guide does not
+weaken `complete_task` confirmation or make the app-only `set_priority` tool model-visible.
+
+Preview the generated Codex and Claude Code product skills before installing them:
+
+```sh
+noodle agents setup --json
+noodle agents setup --write
+```
+
+After changing a workflow or capability, regeneration is explicit so a normal Noodle workflow-skill update
+cannot overwrite the app product skill or local modifications:
+
+```sh
+noodle agents setup --regenerate-app-skill --json
+noodle agents setup --write --regenerate-app-skill
+noodle agents doctor --json
+```
+
 ## Deploy
 
 ```sh

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.66.0 hash:6a9f132ddb79352e -->
+<!-- noodle-skill version:0.68.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.66.0 hash:efffbf82007f935d -->
+<!-- noodle-skill version:0.68.0 hash:efffbf82007f935d -->
 
 # publishing-mcp-integrations
 

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

@@ -84,19 +84,11 @@ At most one public surface (`public` or `mixed`) and at most one authenticated s
 
 A public surface **must** declare `capabilities`: the exact positive allowlist it may reach. It is required by the type, and it is the whole externally reachable surface — a reviewer should read it in one screenful. Anything absent stays private, and a capability added to the server later is excluded until someone lists it. `authenticatedWebsite` may also take `capabilities` to narrow the in-app surface; omitted, it projects the whole server.
 
-### Mixed surfaces: let a visitor sign in mid-conversation
+### Mixed surfaces: not available yet
 
-Add `signIn: true` to a public surface when some capabilities need a signed-in user. The surface becomes `mixed`: anonymous visitors start immediately, and an identity-dependent capability becomes a **sign-in trigger** rather than a compile error — the same shape ChatGPT and Claude use for connectors that work with or without a linked account.
+`publicWebsite({ signIn: true })` **throws**. Mid-conversation sign-in has no runtime: nothing offers the visitor a way to sign in, so an identity-dependent capability on such a surface would simply be refused — and accepting it would also give up the compile-time guard that plain `public` provides. The option stays declared so the vocabulary and wire shape are settled.
 
-```ts
-access: publicWebsite({
-  origins: ["https://www.example.com"],
-  capabilities: [answerProductQuestion, requestDemo, myOrders],
-  signIn: true,   // `myOrders` reads ${user}; visitors sign in to reach it
-}),
-```
-
-Elevation runs through the **host application’s own login**, never a Noodle-operated one: the page signs the visitor in and its backend exchanges that verified user for an elevated session on the same conversation. Do not build a second identity provider for this.
+Until it ships, split the audiences: keep anonymous-safe capabilities on `publicWebsite`, and serve identity-dependent ones from `authenticatedWebsite({ origins })`, where the embedding backend proves who the visitor is. One assistant can declare both.
 
 A connector-backed side effect needs **two** independent declarations to be reachable from a public or mixed surface: inclusion in `capabilities` **and** `{ confirm: true }` on the operation. Signing in proves who the visitor is; it does not pre-authorize an effect, so confirmation still applies on a mixed surface. Confirmation is never authentication or business authorization — the customer backend still owns payload validation, abuse controls, and idempotency. Local or session-only widget state needs no confirmation.
 

package/skills/codex/references/product-agent-guides.md

@@ -8,7 +8,7 @@ Do not wait for the user to name `agentGuide`. During every MCP server or App bu
 
 Author a guide when any of these conditions applies:
 
-- A request for an App Package, product skill, plugin, or agent distribution requires one.
+- A request for an App Package or app product skill requires one. A marketplace plugin or customer-agent distribution would also need this source, but those per-app distribution surfaces are not available in this foundation.
 - Multiple capabilities participate in one user workflow, especially when order or purpose matters.
 - Safe or useful operation depends on product-specific ordering, grounding, clarification, boundaries, or representative examples that capability descriptions cannot express.
 
@@ -16,6 +16,12 @@ A product with a single self-explanatory capability may omit the guide when its
 
 Make the judgment from the user’s stated outcome and grounded product evidence. If a guide is warranted but a decision-changing workflow or boundary is unknown, ask only for that missing product input; never fabricate it. The user should not need to know this feature name to receive the benefit.
 
+## Scope boundaries
+
+Noodle workflow skills teach a coding agent how to build and operate Noodle projects. The generated app product skill is team-local guidance for using one product. A marketplace plugin is a separate host distribution bundle.
+
+Per-app marketplace plugin generation and customer-agent distribution are not available in this foundation. If the user asks for either, explain the boundary and stop at the local App Package and product-skill workflow. Do not claim a listing, submission bundle, hosted distribution, or customer-agent projection.
+
 ## Creation workflow
 
 1. **Inspect grounded capability evidence.** Read the configured TypeScript entrypoint (`server.ts` or `src/server.ts`) and identify its exact declared tools, resources, prompts, descriptions, visibility, annotations, authorization, and widget relationships. Treat schemas and compiled annotations as facts. Never invent or guess a tool, resource, prompt, capability kind, workflow, or weaker write boundary.

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

package/skills/codex/wrapping-existing-applications/SKILL.md

@@ -3,7 +3,7 @@ name: wrapping-existing-applications
 description: "Use when an existing application has no stable usable API and needs a read-only, identity-first Noodle Seed integration plan before implementation."
 ---
 
-<!-- noodle-skill version:0.66.0 hash:eccc3c158dcafba8 -->
+<!-- noodle-skill version:0.68.0 hash:eccc3c158dcafba8 -->
 
 # wrapping-existing-applications