@noodleseed/one 0.151.1 → 0.153.0

package/node_modules/@noodle-borg/agent-kit/dist/index.js

@@ -26,6 +26,18 @@ const MANAGED_FILE_BY_TARGET = {
     codex: 'AGENTS.md',
     'claude-code': 'CLAUDE.md',
 };
+const SKILL_REFERENCE_BY_PATH = new Map(SKILL_REFERENCES.map((reference) => [reference.relPath, reference]));
+function behaviorSkillReferenceFiles(skill) {
+    return [skill.primaryReference, ...skill.supportingReferences].map((path) => {
+        const reference = SKILL_REFERENCE_BY_PATH.get(path);
+        if (reference === undefined)
+            throw new Error(`missing behavior skill reference: ${path}`);
+        return {
+            relPath: reference.relPath,
+            render: () => reference.render(),
+        };
+    });
+}
 export const SKILL_REGISTRY = defineSkillRegistry([
     {
         name: 'noodle-seed',
@@ -51,7 +63,7 @@ export const SKILL_REGISTRY = defineSkillRegistry([
         version: AGENT_KIT_VERSION,
         supportedHosts: TARGETS,
         renderBody: (target) => renderBehaviorSkillBody(skill, target),
-        files: [],
+        files: behaviorSkillReferenceFiles(skill),
     })),
     { ...EXECUTING_NOODLE_PLANS_SKILL, version: AGENT_KIT_VERSION },
 ]);

package/node_modules/@noodle-borg/agent-kit/dist/plugin-bootstrap-skill.d.ts

@@ -1,7 +1,5 @@
 /** The plugin identifier — matches the project-local skill used after bootstrap. */
 export declare const PLUGIN_NAME = "noodle-seed";
-/** Cold-start discovery text shared by direct marketplace and official-directory projections. */
-export declare const BOOTSTRAP_SKILL_DESCRIPTION: string;
 /** Render the one adaptive skill shipped byte-identically to every plugin projection. */
 export declare function renderBootstrapSkill(version: string): string;
 //# sourceMappingURL=plugin-bootstrap-skill.d.ts.map

package/node_modules/@noodle-borg/agent-kit/dist/plugin-bootstrap-skill.js

@@ -3,7 +3,7 @@ import { PLUGIN_WINDOWS_SUPPORT } from './plugin-platform-support.js';
 /** The plugin identifier — matches the project-local skill used after bootstrap. */
 export const PLUGIN_NAME = 'noodle-seed';
 /** Cold-start discovery text shared by direct marketplace and official-directory projections. */
-export const BOOTSTRAP_SKILL_DESCRIPTION = 'Use when asked to build, create, or ship an MCP server, MCP app, AI app, or connector, or to ' +
+const BOOTSTRAP_SKILL_DESCRIPTION = 'Use when asked to build, create, or ship an MCP server, MCP app, AI app, or connector, or to ' +
     'make a product, API, or SaaS reachable by AI agents. Bootstraps Noodle Seed — TypeScript ' +
     'authoring with the noodle CLI, local validation and testing, and governed hosted deployment.';
 function bootstrapRouterBody() {

package/node_modules/@noodle-borg/agent-kit/dist/plugin-bundle.d.ts

@@ -1,4 +1,4 @@
-export { BOOTSTRAP_SKILL_DESCRIPTION, PLUGIN_NAME } from './plugin-bootstrap-skill.js';
+export { PLUGIN_NAME } from './plugin-bootstrap-skill.js';
 /** The public marketplace identifier (`/plugin install noodle-seed@noodleseed`). */
 export declare const MARKETPLACE_NAME = "noodleseed";
 /** Where the plugin lives inside the marketplace repo (relative sources must start with "./"). */

package/node_modules/@noodle-borg/agent-kit/dist/skill-authoring-refs.js

@@ -228,6 +228,14 @@ export function renderAuthoringWorkflowReference() {
         '',
         '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.',
         '',
+        '## Managed capability reuse',
+        '',
+        'Before authoring an HTTP connector for public-web search, page extraction, places/local search, routing, weather, translation, or media discovery, inspect the generated SDK surface reference. If the matching Noodle capability is actually exported, use its one documented declaration and generated tools directly—never wrap it, rename it, or build an assistant-only provider call. That single declaration is available to both the embedded assistant and external MCP agents under the same authorization and policy.',
+        '',
+        'Use `provider: noodleManaged()` in reusable capability intent and let the app/environment operator bind a supported BYO provider through managed configuration. Keep provider names, endpoints, and credentials out of `server.ts`. Live fares, inventory, bookings, pricing, orders, accounts, and payments remain connectors to authoritative systems. Source order is not truth: preserve citations, freshness, and rights evidence returned by the capability.',
+        '',
+        'A roadmap is not an SDK. If the capability is absent from the generated export list, do not invent an import or generic platform helper. With explicit developer agreement, a bounded application connector may prove the immediate use case; keep it application-specific and do not claim it as the canonical Noodle primitive.',
+        '',
         '## 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:",

package/node_modules/@noodle-borg/agent-kit/dist/skill-content.js

@@ -23,7 +23,7 @@ import { APP_DIRECTORY_COMPLIANCE_REFERENCE } from './skill-router.js';
 import { renderBuildAnMcpServerReference } from './skill-server-playbook-ref.js';
 import { renderToolDesignReference } from './skill-tool-design-ref.js';
 import { renderVerifyAndRecoverReference } from './skill-verification-ref.js';
-export { REFERENCE_INDEX_LINES, SKILL_DESCRIPTION, SKILL_ROUTES, skillRouterBody, } from './skill-router.js';
+export { skillRouterBody } from './skill-router.js';
 // ----------------------------------------------------------------------------
 // references/sdk-surface.md (GENERATED from SDK_EXPORTS + curated recipes)
 // ----------------------------------------------------------------------------
@@ -249,9 +249,9 @@ const SDK_AUTHORING_SIGNATURES = [
     '- `resource(name, { uri, description?, mimeType?, fulfil })` and `prompt(name, { description?, arguments?, fulfil })` expose MCP resources/prompts.',
     '- View metadata (`viewTitle`, `viewDescription`, `csp`, `domain`, `permissions`) belongs on the tool that renders it; `asset("./path")` packages local files.',
     '- `customerAuth.*(...)` belongs in `server` options when deployed customer callers need verified identity; inspect `examples/customer-auth` or `examples/sharepoint` before using it.',
-    '- `state` defines durable widget state handles; handle schemas may use `.optional()`/`.default()` — defaulted fields are optional on write, so a save that omits them still validates. `handoff` declares allowed external domains for safe host handoff.',
+    '- `state` defines durable widget state handles; handle schemas may use `.optional()`/`.default()` — defaulted fields are optional on write, so a save that omits them still validates. Add `claimOnAuthentication: true` only to an explicitly caller-scoped handle with a finite TTL when a mixed public assistant should atomically adopt that expiring draft on sign-in-ticket spend. `handoff` declares allowed external domains for safe host handoff.',
 ];
-export function renderSdkSurfaceReference() {
+function renderSdkSurfaceReference() {
     const remaining = new Set(SDK_EXPORTS);
     const sections = [];
     for (const group of SDK_GROUPS) {
@@ -290,7 +290,7 @@ export function renderSdkSurfaceReference() {
 // ----------------------------------------------------------------------------
 // references/cli-commands.md (GENERATED from CLI_COMMANDS + curated groups)
 // ----------------------------------------------------------------------------
-export function renderCliCommandsReference() {
+function renderCliCommandsReference() {
     const groupOrder = [...COMMAND_GROUP_ORDER, 'Other'];
     const byGroup = new Map();
     for (const name of CLI_COMMANDS) {
@@ -327,7 +327,7 @@ export function renderCliCommandsReference() {
 // ----------------------------------------------------------------------------
 // references/agent-contract.md (CURATED)
 // ----------------------------------------------------------------------------
-export function renderAgentContractReference() {
+function renderAgentContractReference() {
     return [
         '# Agent contract: --json, exit codes, output modes',
         '',
@@ -378,7 +378,7 @@ export function renderAgentContractReference() {
 // ----------------------------------------------------------------------------
 // references/compile-errors.md (GENERATED codes + curated fixes)
 // ----------------------------------------------------------------------------
-export function renderCompileErrorsReference() {
+function renderCompileErrorsReference() {
     const rows = COMPILE_ERROR_CODES.map((code) => [`\`${code}\``, ERROR_FIXES[code] ?? '—']);
     return [
         '# Fixing noodle validate errors',

package/node_modules/@noodle-borg/agent-kit/dist/skill-embedded-assistant-operations-ref.js

@@ -0,0 +1,78 @@
+/** Evidence, launch, and qualified-usage guidance appended to the embedded-assistant reference. */
+export function renderEmbeddedAssistantOperationsReference() {
+    return [
+        '',
+        '## Host readiness and promotion',
+        '',
+        'Run the non-mutating host preflight from the embedding application before its production build:',
+        '',
+        '```sh',
+        'noodle assistant embed --check --json',
+        'noodle assistant embed --check --json --require-env EXAMPLE_DELEG_CLIENT_SECRET',
+        '```',
+        '',
+        'The check reports only required and missing environment names, never their values. Pass `--surface public|mixed|authenticated` to match the deployment: `public` drops the backend client id/secret requirement (a public embed has neither), and `public`/`mixed` additionally require `script-src` — the one directive whose failure runs no widget code at all, so nothing can report it from inside the page. CSP directives verify against the service origin exactly, via the env placeholder, or through a covering wildcard (`https://*.example.com`); a dynamic expression is marked unverified instead of guessed. Additional `--require-env` names are application-owned; `--env-alias NAME=HOST_NAME` follows a host repo that names an env var differently.',
+        '',
+        'Read `evidence.levels` in order and stop at `evidence.firstUnproven`:',
+        '',
+        '| Level | What can prove it |',
+        '| --- | --- |',
+        '| Static host | `assistant embed --check`: environment-name presence, control-plane URL shape, canonical session-route/mount risks, same-origin endpoint shape, and statically visible CSP |',
+        "| Local contract | The host's existing local test/build: JSON signed-out `401`, signed-in session exchange, unchanged response, client-only mount, and cookie/CSRF behavior |",
+        '| Hosted session | `assistant doctor` plus one representative routed safe read against the exact deployment |',
+        '| Production browser | A real deployed browser completing keyboard submission, session exchange, one streamed turn, one interaction, and one linked App with console/network inspection |',
+        '| Operations | The launch, rollback, rotation, budget, usage, and qualified-outcome checks below |',
+        '',
+        '`static-host` is `passed` only when every canonical static diagnostic is ready or not applicable. It is `partial` when a custom or missing source location is not detected, and `failed` for a known blocker. A top-level `ready: true` means only that the check found no static blocker; static success is never local-contract, hosted-session, or production-browser proof.',
+        '',
+        'The value-free diagnostics distinguish `mcp-endpoint` (a deployment MCP URL was supplied where the control-plane service URL belongs), `html-redirect-risk` (the canonical API route appears to redirect instead of returning JSON), `ssr-risk` (the canonical mount is not provably client-only), and `cross-origin-risk` (the browser session endpoint would omit same-origin cookies). `not-detected` and `unverified` are evidence gaps, not passes. The listed `postDeployProbes` are next actions; this command does not execute them.',
+        '',
+        "There is no live or browser flag. Do not add one without human approval of its network, identity, data, timeout, and redaction contract; use the host's own test and browser tooling for later evidence levels.",
+        '',
+        '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 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.",
+        '',
+        '## Launch and qualified-usage proof',
+        '',
+        'Treat deployed capability, production-browser proof, actual qualified usage, and measured customer outcome as four separate claims. Passing one never proves the next.',
+        '',
+        '### Pre-launch checklist',
+        '',
+        '1. Run `noodle assistant embed --check --json` in the host repository and stop at `evidence.firstUnproven`; complete the host-owned local contract and production-browser checks described above.',
+        '2. Run `noodle assistant doctor --user-id <real-test-user> --origin <exact-origin> --org <org> --app <app> --env <env> --json`, then exercise one representative routed safe read. Use an approved synthetic account unless real customer data use was explicitly approved.',
+        '3. Run `noodle assistant appearance show --org <org> --app <app> --env <env> --json` and have the customer owner verify the rendered brand, keyboard path, reduced motion, narrow viewport, confirmation, input, and linked App view in the deployed browser.',
+        '4. Run `noodle assistant clients list --org <org> --app <app> --env <env> --json`; name the active credential owner and rehearse the secret-manager update and verification sequence for `noodle assistant clients rotate <client-id> --org <org> --app <app> --env <env> --json`. Rotation returns a new secret once; never put it in the PR, shell history, logs, or analytics.',
+        '5. For a public or mixed surface, inspect its live caps with `noodle assistant embeds list --org <org> --app <app> --env <env> --json`. Record the authorized kill switch, `noodle assistant budget set --surface <embed-id> --turns-per-day 0 --org <org> --app <app> --env <env> --json`, but do not execute it during a rehearsal.',
+        '6. Record the current and previous deployment identifiers and the named rollback owner. The recovery command is `noodle rollback <previous-deployment-id> --org <org> --app <app> --env <env> --json`; do not run it merely to prove syntax.',
+        '7. Have the customer workflow owner execute and sign off the behavioral acceptance fixture below against the production-equivalent environment.',
+        '',
+        '### Customer-owned behavioral acceptance fixture',
+        '',
+        'Use customer-recognizable inputs and expected business outcomes. Record only the minimum identifiers needed to reproduce a failure; do not paste raw conversations, secrets, or customer records into issue trackers.',
+        '',
+        '| Case | Customer-owned setup | Expected observable outcome |',
+        '| --- | --- | --- |',
+        '| normal | One common, authorized job with known data | Completes the named task and presents the business result or linked App clearly |',
+        '| ambiguous | A request with two materially different interpretations | Asks the smallest useful clarifying question before action |',
+        '| missing-data | Omit one required business field or make the read return no record | Requests only the missing input or states that no data exists; never invents it |',
+        '| unauthorized | Use a real test role lacking the required scope | Refuses or withholds the capability without leaking its result, arguments, or internal tool name |',
+        '| tenant-switch | Change the signed-in organization while the panel is open | Aborts and clears the prior principal session; no prior-tenant transcript, route, or result survives |',
+        '| confirmation | Propose one consequential operation, then test decline, cancel, and accept separately | Shows the complete non-sensitive action review; only explicit accept executes, at most once |',
+        '| recovery | Expire a session before execution and lose one interaction response after submission | Safe pre-execution re-exchange succeeds once; same-id/same-decision reconciliation returns the stored outcome without re-execution |',
+        '',
+        '### Post-launch checklist',
+        '',
+        '1. Run `noodle assistant usage --window 7d --org <org> --app <app> --env <env> --json` on an agreed cadence. It reports traffic, depth, engagement, latency, and tokens; it does not establish customer success.',
+        '2. Re-run the customer-owned fixture with named external users after any tool, permission, model, identity, renderer, or routing change. Record results by case and deployment, not as a single green launch claim.',
+        '3. Report task completion, refusal correctness, repeat usage, safety, latency, and abandonment separately: completed qualified attempts / qualified attempts; correct refusals / refusal cases; distinct returning qualified users; confirmed cross-tenant, duplicate-effect, or secret-exposure incidents; p50/p95 end-to-end time for the named job; and started qualified attempts with no completion or explicit refusal.',
+        '4. Treat raw turn volume as utilization evidence, not an outcome. A user can generate many turns because the assistant is useful, confused, slow, or unsafe.',
+        '5. Recheck caps and credential age. Run the rehearsed `noodle assistant clients rotate <client-id>` sequence only under the named owner, update the backend secret manager, rerun doctor and one browser turn, then revoke the superseded credential after the overlap window.',
+        '6. When an agreed safety, cost, or correctness threshold is crossed, use the recorded public-surface budget kill switch or the recorded deployment rollback. Verify the restored state with doctor, the browser path, and the affected acceptance cases.',
+        '',
+        'Do not add a platform-owned completion event or infer completion from a final assistant message. Any such schema requires a separate human-approved analytics and customer-data decision covering event semantics, customer consent, retention, access, deletion, tenant isolation, and whether the customer application or Noodle is authoritative.',
+    ];
+}
+//# sourceMappingURL=skill-embedded-assistant-operations-ref.js.map