@noodleseed/agent-kit 0.69.0 → 0.71.0

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.69.0 hash:11523cb33b9473c0 -->
+<!-- noodle-skill version:0.71.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.69.0 hash:9fd67d4d24328e15 -->
+<!-- noodle-skill version:0.71.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.69.0 hash:21bbd3ec441ffd30 -->
+<!-- noodle-skill version:0.71.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.69.0 hash:0fa48a82fe836cf0 -->
+<!-- noodle-skill version:0.71.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.69.0 hash:aa715bae12041d7c -->
+<!-- noodle-skill version:0.71.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.69.0 hash:93e735b7ffb45df1 -->
+<!-- noodle-skill version:0.71.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.69.0 hash:78a6f181b61f92f1 -->
+<!-- noodle-skill version:0.71.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.69.0 hash:cc54a67f21c0ecdb -->
+<!-- noodle-skill version:0.71.0 hash:cc54a67f21c0ecdb -->
 
 # embedding-mcp-assistants
 

package/skills/codex/examples/acme-discovery/src/knowledge/faq.txt

@@ -0,0 +1,10 @@
+ACME GETAWAYS FAQ
+
+Q: Does the assistant book and take payment?
+A: No. The assistant shapes the trip and hands off to Acmes own checkout with a signed link.
+
+Q: How current are prices?
+A: Starting prices come from Acmes live site; the assistant cites the page it used.
+
+Q: Can I compare destinations?
+A: Yes, ask for a shortlist by vibe, month, or budget.

package/skills/codex/examples/acme-discovery/src/knowledge/product.md

@@ -0,0 +1,7 @@
+# Acme Getaways product guide
+
+Acme Getaways curates four destination types: beach, mountains, culture, and city escapes. Every listing shows a real starting price and the best months to travel. Bookings, payments, and date selection happen on Acmes own site through a signed handoff link; the assistant never takes payment details.
+
+## Cancellation and support
+
+All trips can be cancelled free within 48 hours of the handoff. Support runs seven days a week through the chat on book.acme.example.

package/skills/codex/examples/acme-discovery/src/server.ts

@@ -1,10 +1,13 @@
 import {
   annotations,
   embeddedAssistant,
+  file,
+  knowledge,
   openAICompatible,
   publicWebsite,
   secret,
   server,
+  site,
   tool,
   variable,
   z,
@@ -196,6 +199,27 @@ const shortlistGetaway = tool('shortlist_getaway', {
   }),
 });
 
+// Grounding beyond the catalog: two controlled files answer policy/pricing/support questions with
+// citations, and Acme's live public site stays current through its search provider — no sync job,
+// no handwritten search tool. One declaration, one generated `search_destinations` capability.
+const destinations = knowledge('destinations', {
+  title: 'Acme Getaways destinations',
+  description: 'Public destination, pricing, cancellation, and support information.',
+  documents: [
+    file('./knowledge/product.md', {
+      title: 'Product guide',
+      sourceUrl: 'https://getaways.acme.example/product',
+    }),
+    file('./knowledge/faq.txt', { title: 'FAQ' }),
+  ],
+  sites: [
+    site({
+      origin: 'https://getaways.acme.example',
+      include: ['/destinations/**', '/pricing', '/support'],
+    }),
+  ],
+});
+
 export default server(
   'acme_discovery',
   {
@@ -217,7 +241,8 @@ export default server(
     // The same three tools also serve Acme's own marketing site, with no second tool set and no
     // session backend: a visitor with no account gets the discovery carousel and the booking
     // handoff. `capabilities` is the whole externally reachable surface — short enough to review in
-    // one glance, and closed by default when a tool is added to the server later.
+    // one glance, and closed by default when a tool is added to the server later. The knowledge
+    // component projects its generated search capability the same way a tool does.
     assistant: embeddedAssistant({
       model: openAICompatible({
         baseUrl: variable('ASSISTANT_MODEL_BASE_URL'),
@@ -226,11 +251,12 @@ export default server(
       }),
       access: publicWebsite({
         origins: ['https://getaways.acme.example'],
-        capabilities: [discoverGetaways, createHandoff, shortlistGetaway],
+        capabilities: [destinations, discoverGetaways, createHandoff, shortlistGetaway],
       }),
       layout: { mode: 'floating', position: 'bottom-right' },
       labels: { welcomeHeading: 'Where would you like to go?' },
     }),
+    knowledge: [destinations],
   },
   [discoverGetaways, createHandoff, shortlistGetaway],
 );

package/skills/codex/examples/acme-discovery/test/server.test.ts

@@ -21,4 +21,14 @@ describe('acme-discovery example', () => {
     expect(text).toContain('create_handoff');
     expect(text).toContain('shortlist_getaway');
   });
+
+  it('declares the grounded knowledge component and its live site scope', async () => {
+    const manifest = (await app.toManifest()) as { server: { knowledge?: unknown[] } };
+    // One declaration: controlled files plus the live public site, compiled later into the
+    // generated `search_destinations` capability with citations.
+    expect(manifest.server.knowledge).toHaveLength(1);
+    const text = JSON.stringify(manifest);
+    expect(text).toContain('knowledge/product.md');
+    expect(text).toContain('https://getaways.acme.example');
+  });
 });

package/skills/codex/examples/food-ordering/README.md

@@ -50,8 +50,8 @@ noodle dev
 
 The same `server.ts` declares `distribution` metadata for host adapters. It references real packaged images
 and keeps listing copy, support/legal URLs, and positive/negative review scenarios outside the canonical App
-Package and Runtime Artifact. The OpenAI adapter can now project those facts and the generated product skill
-into separate local-testing or public-submission archives. A Claude package remains a separate adapter.
+Package and Runtime Artifact. Explicit OpenAI and Claude adapters project those facts with the generated
+product skill; installable plugin archives and directory-submission dossiers remain separate outputs.
 
 In another terminal:
 
@@ -93,6 +93,11 @@ noodle export plugin openai \
   --output food-ordering-openai.zip
 ```
 
+Extract `food-ordering-openai.zip` before using the portal. Upload
+`submission/chatgpt-app-submission.json` to the Codex-assisted import field and
+`submission/food-ordering-skill.zip` to **With MCP → Skills**. The outer ZIP is the complete review kit and
+is not itself a valid skill upload; `submission/README.md` repeats the portal steps.
+
 After registering that same URL in ChatGPT developer mode, substitute its real technical ID to generate the
 Food Ordering local test package:
 
@@ -105,6 +110,32 @@ noodle export plugin openai \
   --output food-ordering-openai-local.zip
 ```
 
+## Export for Claude
+
+Claude Code plugin packaging and Anthropic Connector Directory review are separate outputs. Generate the
+installable plugin repository with:
+
+```sh
+noodle export plugin claude \
+  --mcp-url https://food-ordering.noodleseed.app/mcp \
+  --output food-ordering-claude.zip
+```
+
+Generate the credential-free operator dossier for the remote Connector Directory with:
+
+```sh
+noodle export connector claude \
+  --mcp-url https://food-ordering.noodleseed.app/mcp \
+  --auth none \
+  --category "Food & Drink" \
+  --output food-ordering-anthropic-connector.zip
+```
+
+The dossier is deliberately marked `portalUploadable: false`: it gathers the listing, tool annotations,
+use cases, allowed-link candidates, test-account guidance, and MCP App screenshot evidence, but a human must
+verify ownership/compliance and enter the final answers in Anthropic's portal. The plugin ZIP does not
+contain this dossier.
+
 ## Client Setup
 
 Use the CLI to print the exact setup flow for your MCP client:
@@ -129,19 +160,21 @@ connector secrets and does not include tokens, caller-key mechanisms, or `.env.n
 
 ## Demo Assets
 
-The packaged demo images live under `assets/` and are public web assets when deployed. The current app uses
-`assets/noodle-bowl.jpg` as the server branding image.
+The packaged demo images live under `assets/`. The current app uses `assets/noodle-bowl.jpg` as the server
+branding image. Its three distribution screenshots are real, response-only MCP App captures from Noodle
+Devtools at 2× device scale; each is 1640×970 PNG and has the producing user prompt next to its `asset(...)`
+reference in `server.ts`.
 
 Image sources:
 
 - `assets/noodle-bowl.jpg` — Unsplash photo
   [`IRv8V9Hb8gI`](https://unsplash.com/photos/IRv8V9Hb8gI), downloaded from Unsplash.
-- `assets/lentil-soup.jpg` — Unsplash image
-  [`photo-1510431198580-7727c9fa1e3a`](https://images.unsplash.com/photo-1510431198580-7727c9fa1e3a), downloaded from Unsplash.
-- `assets/mint-lemonade.jpg` — Unsplash photo
-  [`X7Nx327NtuA`](https://unsplash.com/photos/X7Nx327NtuA) by Imad 786.
-- `assets/lentil-soup-openai.png` and `assets/mint-lemonade-openai.png` — PNG screenshot renditions
-  produced from the two corresponding Unsplash references for OpenAI plugin packaging.
-
-Unsplash photos are free to use under the [Unsplash License](https://unsplash.com/license); attribution is
-not required, but source notes are kept here for provenance.
+- `assets/food-ordering-stores.png` — store-discovery state produced by “Help me build a noodle order for
+  pickup.”
+- `assets/food-ordering-menu.png` — Harbor Noodles menu state produced by “Show me the Harbor Noodles
+  menu.”
+- `assets/food-ordering-handoff.png` — checkout-handoff state produced by “Review my spicy miso bowl order
+  before checkout.”
+
+The Unsplash branding photo is free to use under the [Unsplash License](https://unsplash.com/license);
+attribution is not required, but the source note is kept here for provenance.

package/skills/codex/examples/food-ordering/src/server.ts

@@ -2,8 +2,9 @@ import { annotations, asset, connector, resource, server, tool, z } from '@noodl
 import { FOOD_ORDERING_AGENT_GUIDE } from './agent-guide.js';
 
 const heroImage = asset('assets/noodle-bowl.jpg');
-const menuScreenshot = asset('assets/lentil-soup-openai.png');
-const cartScreenshot = asset('assets/mint-lemonade-openai.png');
+const storesScreenshot = asset('assets/food-ordering-stores.png');
+const menuScreenshot = asset('assets/food-ordering-menu.png');
+const handoffScreenshot = asset('assets/food-ordering-handoff.png');
 
 const state = connector('noodle_state')
   .version('1.0.0')
@@ -208,7 +209,7 @@ export default server(
     agentGuide: FOOD_ORDERING_AGENT_GUIDE,
     distribution: {
       listing: {
-        summary: 'Browse local food, build a cart, and review checkout in conversation.',
+        summary: 'Build a pickup noodle order.',
         description:
           'Food Ordering is a synthetic MCP App that demonstrates store discovery, menu browsing, a caller-scoped cart, fulfilment planning, and explicit checkout handoff.',
         keywords: ['food', 'ordering', 'delivery'],
@@ -228,8 +229,21 @@ export default server(
       assets: {
         icon: { source: heroImage, alt: 'Food Ordering noodle bowl' },
         screenshots: [
-          { source: menuScreenshot, alt: 'A featured lentil soup menu item' },
-          { source: cartScreenshot, alt: 'A mint lemonade shown with the order' },
+          {
+            source: storesScreenshot,
+            alt: 'Food Ordering MCP App showing nearby stores',
+            prompt: 'Help me build a noodle order for pickup.',
+          },
+          {
+            source: menuScreenshot,
+            alt: 'Food Ordering MCP App showing the Harbor Noodles menu',
+            prompt: 'Show me the Harbor Noodles menu.',
+          },
+          {
+            source: handoffScreenshot,
+            alt: 'Food Ordering MCP App reviewing a checkout handoff',
+            prompt: 'Review my spicy miso bowl order before checkout.',
+          },
         ],
       },
       review: {
@@ -242,31 +256,37 @@ export default server(
             expected:
               'The ordering app opens with stores and menu items; checkout remains a handoff.',
             shouldInvoke: true,
+            tools: ['open_ordering'],
           },
           {
             id: 'browse_menu',
             prompt: 'Show me vegetarian menu options nearby.',
             expected: 'The app shows matching stores and bounded menu choices.',
             shouldInvoke: true,
+            tools: ['search_stores', 'load_menu'],
           },
           {
             id: 'compare_options',
             prompt: 'Compare the quickest open food options for me.',
             expected: 'The app grounds its comparison in the synthetic store data.',
             shouldInvoke: true,
+            tools: ['search_stores', 'summarize_ordering_options'],
           },
           {
             id: 'plan_pickup',
             prompt: 'Plan a pickup order for Friday.',
             expected: 'The app collects the missing fulfilment details before planning the order.',
             shouldInvoke: true,
+            tools: ['plan_order'],
           },
           {
             id: 'review_checkout',
             prompt: 'Review my cart before I continue to checkout.',
             expected: 'The app shows the cart and keeps payment on the explicit external handoff.',
             shouldInvoke: true,
+            tools: ['read_cart', 'prepare_checkout'],
           },
+          // Negative scenarios are non-invocation cases, so they never declare expected tools.
           {
             id: 'unrelated_weather',
             prompt: 'Will it rain tomorrow?',
@@ -373,6 +393,7 @@ export default server(
       permissions: { clipboardWrite: {} },
     }),
     tool('search_stores', {
+      title: 'Search stores',
       visibility: ['app'],
       description: 'Filter synthetic restaurants for the ordering widget.',
       annotations: readOnly,
@@ -384,6 +405,7 @@ export default server(
       fulfil: () => ({ stores }),
     }),
     tool('load_menu', {
+      title: 'Load store menu',
       visibility: ['app'],
       description: 'Load synthetic menu categories and items for one store.',
       annotations: readOnly,
@@ -396,6 +418,7 @@ export default server(
       fulfil: ({ input }) => ({ storeId: input.storeId, stores, items: menu }),
     }),
     tool('load_item', {
+      title: 'Load menu item',
       visibility: ['app'],
       description: 'Load item details and modifier options for the ordering widget.',
       annotations: readOnly,
@@ -404,6 +427,7 @@ export default server(
       fulfil: ({ input }) => ({ itemId: input.itemId, items: menu }),
     }),
     tool('read_cart', {
+      title: 'Read ordering cart',
       visibility: ['app'],
       description: 'Read the caller-scoped ordering cart state.',
       annotations: readOnly,
@@ -419,6 +443,7 @@ export default server(
       },
     }),
     tool('sync_cart', {
+      title: 'Update ordering cart',
       visibility: ['app'],
       description: 'Patch the caller-scoped ordering cart with the widget cart mirror.',
       annotations: action,
@@ -439,6 +464,7 @@ export default server(
       },
     }),
     tool('prepare_checkout', {
+      title: 'Prepare checkout handoff',
       visibility: ['app'],
       description: 'Prepare the caller-scoped cart for checkout handoff.',
       annotations: action,

package/skills/codex/examples/food-ordering/test/server.test.ts

@@ -24,6 +24,7 @@ describe('food-ordering example', () => {
       connectors?: Record<string, { id: string; version: string }>;
       tools: Array<{
         name: string;
+        title?: string;
         visibility?: string[];
         annotations?: Record<string, unknown>;
         output?: unknown;
@@ -103,6 +104,7 @@ describe('food-ordering example', () => {
       },
     });
     expect(manifest.widgets?.map((widget) => widget.name)).toContain('capabilities_card');
+    expect(manifest.tools.every((tool) => typeof tool.title === 'string')).toBe(true);
   });
 
   it('projects host distribution metadata separately from the runtime manifest', () => {
@@ -110,7 +112,23 @@ describe('food-ordering example', () => {
     expect(distribution).toMatchObject({
       schemaVersion: 1,
       listing: { summary: expect.stringContaining('Browse local food') },
-      assets: { icon: { alt: 'Food Ordering noodle bowl' }, screenshots: expect.any(Array) },
+      assets: {
+        icon: { alt: 'Food Ordering noodle bowl' },
+        screenshots: [
+          expect.objectContaining({
+            alt: 'Food Ordering MCP App showing nearby stores',
+            prompt: 'Help me build a noodle order for pickup.',
+          }),
+          expect.objectContaining({
+            alt: 'Food Ordering MCP App showing the Harbor Noodles menu',
+            prompt: 'Show me the Harbor Noodles menu.',
+          }),
+          expect.objectContaining({
+            alt: 'Food Ordering MCP App reviewing a checkout handoff',
+            prompt: 'Review my spicy miso bowl order before checkout.',
+          }),
+        ],
+      },
     });
     const scenarios = distribution?.review.scenarios ?? [];
     expect(scenarios.filter(({ shouldInvoke }) => shouldInvoke).map(({ id }) => id)).toEqual([
@@ -125,5 +143,10 @@ describe('food-ordering example', () => {
       'unrelated_email',
       'unrelated_travel',
     ]);
+    expect(
+      scenarios
+        .filter(({ shouldInvoke }) => !shouldInvoke)
+        .every((scenario) => !('tools' in scenario)),
+    ).toBe(true);
   });
 });

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

@@ -13,6 +13,10 @@ When an installed Noodle Developer plugin drives this example, its skill perform
 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
 this source while Noodle guides and operates the validate, preview, deploy, inspect, and debug workflow.
+Plugin sign-in uses one compact consent for the Developer MCP resource; it does not ask the user to
+choose organizations or environments. For remote inspection, the agent calls `get_context`, resolves
+the intended organization from the request or this project, and passes that explicit `org` to every
+scoped tool. The local CLI may keep its own default organization for command convenience.
 For an approved implementation plan, the installed `executing-noodle-plans` skill owns the
 test-first task, review, recovery, and final-verification loop.
 If that agent discovers a Noodle Seed product gap while working, the installed skill prepares a

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.69.0 hash:6a9f132ddb79352e -->
+<!-- noodle-skill version:0.71.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.69.0 hash:efffbf82007f935d -->
+<!-- noodle-skill version:0.71.0 hash:efffbf82007f935d -->
 
 # publishing-mcp-integrations
 

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

@@ -405,6 +405,26 @@ Author managed config as `secret("NAME")` / `variable("NAME")` and operate it wi
 
 To place the same server tools inside a SaaS web app, declare `assistant: embeddedAssistant(...)` alongside the one server-level brand kit. Read `embedded-assistant.md` before integrating: it owns the HTTPS-origin rule, managed model configuration, required deploy-before-client sequence, customer-backend exchange, browser mount, and verification checklist.
 
+## Knowledge components
+
+Ground an assistant in controlled documents and the customer's live public site with one declaration — never a handwritten `search`/`fetch` tool pair, a provider name, a sync job, or an index manifest. Declare `knowledge(...)` with `file(...)` documents (UTF-8 `.md`/`.txt`, project-root relative, ≤100 files, ≤1 MiB each, ≤25 MiB per component) and `site(...)` live scopes (exact HTTPS origin plus positive path globs), pass the declaration in the server's `knowledge` array, and include it in a public website surface's `capabilities` to project the generated `search_<name>` capability:
+
+```ts
+const product = knowledge('product', {
+  title: 'Product knowledge',
+  description: 'Public product, pricing, and support information.',
+  documents: [
+    file('./knowledge/product.md', { title: 'Product guide' }),
+    file('./knowledge/faq.txt', { title: 'FAQ' }),
+  ],
+  sites: [
+    site({ origin: 'https://www.acme.example', include: ['/docs/**', '/pricing'] }),
+  ],
+});
+```
+
+The compiler validates and hashes every document at build time (bad extensions, root escapes, symlinks, oversize, and non-UTF-8 fail `noodle validate` with the exact path); deployment publishes versioned files transactionally with the app and the provider keeps live-site content current. Component names are lowercase snake-case; each component implies exactly one generated bounded search capability with cited results.
+
 ## 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`, `.env.noodle`, or `~/.noodle/config.json`. Hosted access is identity-based — do not add static data-plane credential paths.

package/skills/codex/references/compile-errors.md

@@ -56,6 +56,8 @@ Run `noodle validate` (add `--json` for the machine-readable envelope, `--fix-pr
 | `invalid_asset` | Fix the `asset("./path")` reference; the file must exist and be a supported asset type. |
 | `invalid_capability_requirement` | Correct the declared capability/permission requirement to a supported value. |
 | `state_secret_field` | Remove the secret-shaped field from widget/handle state; secrets must never be stored in state or sent to widgets. |
+| `invalid_knowledge` | Fix the `knowledge()` declaration: documents must be existing UTF-8 `.md`/`.txt` files inside the project root (no symlinks), within the 100-file / 1 MiB / 25 MiB bounds, and sites need an exact HTTPS origin plus at least one include glob. |
+| `knowledge_unhashed` | Compile from the project root (`noodle validate`/`noodle dev`) so declared knowledge documents can be read and hashed. |
 | `unknown_connector_alias` | The tool calls a connector alias not declared in `use`/`provides`; add it or fix the alias (see `suggestions`). |
 | `connector_not_in_catalog` | The referenced connector is not in the resolved catalog; add it to the project connectors or correct the reference. |
 | `unknown_operation` | The connector has no such operation; use an operation declared on that connector (see `didYouMean`/`suggestions`). |

package/skills/codex/references/inspect-hosted.md

@@ -16,7 +16,7 @@ This route is read-only. It never authorizes `login`, `logout`, `link`, `target
 1. Resolve the requested org, app, environment, and deployment from existing non-secret context. Do not change the effective target to make inspection easier.
 2. Choose the narrowest read-only command: `noodle target show`, `noodle status`, `noodle inspect`, `noodle smoke`, `noodle metrics --agent-output`, `noodle events --json`, `noodle logs`, or `noodle audit`.
 3. Prefer machine output when the selected command supports it. Record the target, revision/deployment ID, timestamp, result, and any request ID without exposing secrets or customer payloads.
-4. When the installed Developer MCP is available, use its deployment inspection or diagnosis tool only for the selected org/app/env. Treat it as evidence gathering, not mutation authority.
+4. When the installed Developer MCP is available, call `get_context` to read the signed-in user’s current organizations and roles. Resolve the intended organization from the request or project context, then pass that explicit `org` to every scoped inspection or diagnosis tool. Never infer a remote default, and never ask the user to preselect organizations during OAuth. Treat the connection as live evidence gathering, not mutation authority.
 5. If a command fails, distinguish missing authentication/access from unhealthy application behavior. Do not repair, relink, redeploy, rotate config, or roll back under this route.
 
 ## Stop conditions

package/skills/codex/references/publishing.md

@@ -23,14 +23,18 @@ Prepare evidence for a reachable production MCP endpoint, accurate capability de
 
 When the user explicitly prepares host packaging, author the host-neutral `distribution` option in the same `server.ts`; do not add it during an ordinary build that has no distribution goal. It contains listing, publisher, support, legal, assets, and review facts that cannot be derived safely from MCP capability descriptions.
 
-Reference real packaged images with `asset(...)`, write useful alt text, and include realistic positive and negative review scenarios. Keep reviewer credentials, tokens, secrets, personal data, and test-account passwords out of metadata and source control; supply any authorized reviewer credential out of band.
+Reference real packaged images with `asset(...)`, write useful alt text, and include realistic positive and negative review scenarios. Name the exact expected MCP tools in each positive scenario’s `tools` array. A negative scenario is a non-invocation case: set `shouldInvoke: false` and do not define `tools`. For each MCP App screenshot, add the separate user `prompt` that produces that exact state. Capture only the rendered MCP App response—never the enclosing website, Devtools shell, host conversation, or an unrelated product photo—and meet the selected directory’s current format, dimension, and count limits. Keep reviewer credentials, tokens, secrets, personal data, and test-account passwords out of metadata and source control; supply any authorized reviewer credential out of band.
 
 `distribution` is projected separately. It leaves the canonical App Package and Runtime Artifact unchanged, so editing listing copy cannot change deployment execution or product-skill identity. A product package still needs the separately judged `agentGuide`; do not duplicate capability schemas or workflow truth in listing metadata.
 
 The shared framework can validate metadata and resolved image bytes, run an available target adapter, and create a reproducible archive. Target-specific availability and exact flags live in `references/cli-commands.md` and the live command catalog (`noodle commands --json`); never invent an unlisted target, bundle, filename, or acceptance claim.
 
+When a directory has separate installable-plugin and remote-connector submission projections, generate each with its own exact live-catalog command. Never combine their archives or describe an operator dossier as directly portal-uploadable.
+
 Local or repository testing and public-directory submission are distinct packaging states with distinct required inputs. An export command only compiles local source and writes the requested archive. It does not deploy, register, upload, submit, review, or publish the package.
 
+When an export reports `uploadArtifacts`, treat its output archive as an outer review kit. Extract it, follow the generated instructions, and upload only the named inner artifacts to their matching fields. Never substitute the outer kit for a nested single-purpose upload.
+
 ## Directory-specific evidence
 
 Read the selected directory’s current official submission documentation at review time. Record each additional requirement separately from the shared checklist, including listing fields, identity verification, test credentials, screenshots, policy declarations, review limits, and appeal or resubmission steps. Never project one directory’s requirements onto another.

package/skills/codex/references/sdk-surface.md

@@ -58,10 +58,13 @@ Platform helper connectors are explicit subpath imports from `@noodleseed/one/pl
 - `customerEndpoint`
 - `embeddedAssistant`
 - `externalExchange`
+- `file`
 - `gmailConnector`
+- `knowledge`
 - `managedSecret`
 - `openAICompatible`
 - `publicWebsite`
+- `site`
 
 ## Authoring signatures
 

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.69.0 hash:0f404109f4845683 -->
+<!-- noodle-skill version:0.71.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.69.0 hash:6ef6ef551e26b78e -->
+<!-- noodle-skill version:0.71.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.69.0 hash:eccc3c158dcafba8 -->
+<!-- noodle-skill version:0.71.0 hash:eccc3c158dcafba8 -->
 
 # wrapping-existing-applications