@noodleseed/agent-kit 0.29.0 → 0.30.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/manifest.json CHANGED
@@ -1,9 +1,9 @@
1
1
  {
2
- "packageVersion": "0.29.0",
2
+ "packageVersion": "0.30.0",
3
3
  "files": [
4
4
  {
5
5
  "path": "skills/codex/SKILL.md",
6
- "sha256": "748275d8f350af4390d07fccb571bedf0ea6dc9c7c074f28fe3a493f41bcbef1",
6
+ "sha256": "1c4dd7e2af79db3ca212106bf8764db5471ba828861cc1b438be777665d02b41",
7
7
  "agentTarget": "codex"
8
8
  },
9
9
  {
@@ -28,12 +28,12 @@
28
28
  },
29
29
  {
30
30
  "path": "skills/codex/references/authoring-workflow.md",
31
- "sha256": "d553234ffd7c4d8d22624123b6c91f359f8643ae305584742b241763c8868eeb",
31
+ "sha256": "719b5ba7b04ce8c96129ac00809683889552b1bb56cba3a2ce11b9f9466ae672",
32
32
  "agentTarget": "codex"
33
33
  },
34
34
  {
35
35
  "path": "skills/codex/references/embedded-assistant.md",
36
- "sha256": "7b9de2f1033291312b2b4cc58bffa3e1cb0c8eeed6a77505daab5dc492bb00db",
36
+ "sha256": "ae70a4fdac98b74c59897f16691d3655c94bdd0b06510329b84b651b2333d33a",
37
37
  "agentTarget": "codex"
38
38
  },
39
39
  {
@@ -278,7 +278,7 @@
278
278
  },
279
279
  {
280
280
  "path": "skills/codex/examples/food-ordering/README.md",
281
- "sha256": "41fdd5b9ca345a5f0daf4633cb53e65f11d1f211f283f6ba902db3366f872809",
281
+ "sha256": "013e0734831996d692c3ec314c7457156818089ace8e39ab79a5bf6d74262631",
282
282
  "agentTarget": "codex"
283
283
  },
284
284
  {
@@ -378,7 +378,7 @@
378
378
  },
379
379
  {
380
380
  "path": "skills/claude-code/SKILL.md",
381
- "sha256": "4b22a1c1b1f113567d61aa9ccddb1b47c61f07c899dc195577dde61535508dfd",
381
+ "sha256": "e4a9d32883a8d9b2d0dbb8f758977beb8a8334e93321d4eb50bad5db94e478ae",
382
382
  "agentTarget": "claude-code"
383
383
  },
384
384
  {
@@ -403,12 +403,12 @@
403
403
  },
404
404
  {
405
405
  "path": "skills/claude-code/references/authoring-workflow.md",
406
- "sha256": "d553234ffd7c4d8d22624123b6c91f359f8643ae305584742b241763c8868eeb",
406
+ "sha256": "719b5ba7b04ce8c96129ac00809683889552b1bb56cba3a2ce11b9f9466ae672",
407
407
  "agentTarget": "claude-code"
408
408
  },
409
409
  {
410
410
  "path": "skills/claude-code/references/embedded-assistant.md",
411
- "sha256": "7b9de2f1033291312b2b4cc58bffa3e1cb0c8eeed6a77505daab5dc492bb00db",
411
+ "sha256": "ae70a4fdac98b74c59897f16691d3655c94bdd0b06510329b84b651b2333d33a",
412
412
  "agentTarget": "claude-code"
413
413
  },
414
414
  {
@@ -653,7 +653,7 @@
653
653
  },
654
654
  {
655
655
  "path": "skills/claude-code/examples/food-ordering/README.md",
656
- "sha256": "41fdd5b9ca345a5f0daf4633cb53e65f11d1f211f283f6ba902db3366f872809",
656
+ "sha256": "013e0734831996d692c3ec314c7457156818089ace8e39ab79a5bf6d74262631",
657
657
  "agentTarget": "claude-code"
658
658
  },
659
659
  {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@noodleseed/agent-kit",
3
- "version": "0.29.0",
3
+ "version": "0.30.0",
4
4
  "private": false,
5
5
  "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.",
6
6
  "license": "Apache-2.0",
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  name: noodle-seed
3
3
  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.
4
- version: 0.29.0
4
+ version: 0.30.0
5
5
  hash: b4fc528d406e2149
6
6
  ---
7
7
 
@@ -20,7 +20,7 @@ private customer data.
20
20
  | React app runtime kit | `@noodleseed/one/react` supplies app flow, shell/nav/view, async state, form, quantity, choice, and handoff primitives |
21
21
  | Multi-step widget flow | One React shell navigates stores, menu, item customization, cart, review, and handoff views through `useAppFlow` |
22
22
  | Invocation context | `server.context` sets locale/time-zone defaults, derives an ambient service area/date, and makes the same snapshot available to tools and the reserved `noodle_context` MCP adapter |
23
- | Structured missing input | `plan_order` uses `ctx.elicit` to collect a fulfilment method and date in embedded/headless renderers and bidirectional MCP adapters; the stateless hosted MCP endpoint does not yet carry the server-initiated exchange |
23
+ | Structured missing input | `plan_order` uses `ctx.elicit` to collect a fulfilment method and date through embedded/headless forms, standard bidirectional elicitation, a linked MCP App form, or an exact structured conversational retry on stateless hosts |
24
24
  | Model-visible widget state | `useUpdateModelContext` publishes one cohesive replacement snapshot when supported; `useWidgetLifecycle` auto-publishes mounted/cancelled/dismissed and reports author-owned submitted milestones for future context (not host-presentation proof), while the user-triggered submit pairs `useSendFollowUpMessage` for an immediate reply |
25
25
  | Handoff | `handoff.allowedDomains` allows only `https://orders.example.com` checkout URLs |
26
26
  | Progressive enhancement | Non-Apps hosts still receive stores, featured items, and a readable fallback summary |
@@ -34,7 +34,8 @@ Like the comprehensive default `noodle init my-app` scaffold, this flagship keep
34
34
  while making each individual widget view focused; server capability breadth and screen density are separate.
35
35
  The compiled initial widget should normally remain under the 1 MiB performance recommendation; Noodle Seed's
36
36
  hard ceilings are 10 MiB per compiled widget and 20 MiB across one deployment. Run `noodle check` to see raw
37
- and gzip-estimated sizes, and keep menu images or large live datasets in assets/resources and app-only tools
37
+ and gzip-estimated sizes. Deploy requests are gzip-compressed as one stream so repeated self-contained React
38
+ runtime bytes deduplicate on the wire without a cross-tenant CDN. Keep menu images or large live datasets in assets/resources and app-only tools
38
39
  rather than embedding them into the initial HTML bundle.
39
40
 
40
41
  ## Local Author Loop
@@ -273,7 +273,7 @@ tool('prepare_time_off', {
273
273
  });
274
274
  ```
275
275
 
276
- Use a stable lowercase/number/underscore id and a flat form of string/number/integer/boolean, string choices or multi-select, with optional `email`, `uri`, `date`, or `date-time` formats. Nested objects and credential-shaped fields fail with `invalid_elicitation_schema`. Every interactive flow must place all `ctx.elicit` calls before its first connector operation or compilation fails with `invalid_elicitation_flow`. Embedded/headless clients receive `input_requested`; bidirectional MCP transports map the primitive to standard form `elicitation/create`. An adapter that cannot carry the request returns a structured non-executing `interaction_unavailable` result. Accept validates and resumes without rerunning completed steps; invalid content returns `arg_invalid` and leaves the same interaction pending; decline/cancel stop. Elicitation gathers missing input and does not replace confirmation. In a flow marked `confirm: true`, every eligible `input_requested` precedes `tool_proposed`; the final proposal reviews the original input, elicited values, and sole exact connector action. Accept is bound to that action and only then may execution start. A confirmable flow may contain at most one connector operation; additional operations fail with `invalid_confirmation_flow`. MCP uses final standard form confirmation on capable bidirectional transports and fails closed otherwise. Setting `interactions: { confirmationFallback: "host" }` in the server options explicitly trusts native host approval only when confirmation transport is unavailable and no elicited input is needed; it is never inferred from client name and does not replace authorization. Omitted or `false` annotations execute directly; hints alone never gate. `annotations.action({ confirm: true })` explicitly enables confirmation; `annotations.action({ confirm: false })` explicitly preserves direct execution.
276
+ Use a stable lowercase/number/underscore id and a flat form of string/number/integer/boolean, string choices or multi-select, with optional `email`, `uri`, `date`, or `date-time` formats. Nested objects and credential-shaped fields fail with `invalid_elicitation_schema`. Every interactive flow must place all `ctx.elicit` calls before its first connector operation or compilation fails with `invalid_elicitation_flow`. Embedded/headless clients receive `input_requested`; bidirectional MCP transports map the primitive to standard form `elicitation/create`. On stateless hosts, the adapter returns a structured non-executing `interaction_unavailable` result; linked Apps render its business-user form and retry in request `_meta`, while models can use the advertised reserved retry field. Accept validates and replays only the operation-free input prefix; invalid content returns `arg_invalid`, and decline/cancel stop. Elicitation gathers missing input and does not replace confirmation. In a flow marked `confirm: true`, every eligible `input_requested` precedes `tool_proposed`; the final proposal reviews the original input, elicited values, and sole exact connector action. Accept is bound to that action and only then may execution start. A confirmable flow may contain at most one connector operation; additional operations fail with `invalid_confirmation_flow`. MCP uses final standard form confirmation on capable bidirectional transports and fails closed otherwise. Setting `interactions: { confirmationFallback: "host" }` in the server options explicitly trusts native host approval only when confirmation transport is unavailable and after every elicited field is collected; it is never inferred from client name and does not replace authorization. Omitted or `false` annotations execute directly; hints alone never gate. `annotations.action({ confirm: true })` explicitly enables confirmation; `annotations.action({ confirm: false })` explicitly preserves direct execution.
277
277
 
278
278
  ## Compute connector example
279
279
 
@@ -120,6 +120,14 @@ noodle assistant clients create --name web --org <org> --app <app> --env <env>
120
120
 
121
121
  The CLI writes `{ clientId, clientSecret }` to a mode-`0600` file and prints only its path. Move the values into the SaaS backend secret manager without printing or committing them. Rotation invalidates the previous secret.
122
122
 
123
+ Validate the active deployment, backend credential, exact origin, and delegated credential exchanges without invoking a business tool:
124
+
125
+ ```sh
126
+ noodle assistant doctor --origin "$PUBLIC_APP_ORIGIN" --org <org> --app <app> --env <env>
127
+ ```
128
+
129
+ The doctor reads `NOODLE_ASSISTANT_CLIENT_ID` / `NOODLE_ASSISTANT_CLIENT_SECRET` or the saved mode-0600 client file and never prints the secret. Pass `--user-id <real-test-user>` only when the downstream exchange requires an existing application user.
130
+
123
131
  ## Integrate the customer backend
124
132
 
125
133
  Read the customer repository lockfile or `packageManager` field and install `@noodleseed/assistant` with that existing package manager; never introduce a second lockfile.
@@ -176,7 +184,7 @@ The callback records declarative fulfilment at author time; the shared runtime e
176
184
 
177
185
  ## Structured missing input
178
186
 
179
- A tool authored with `ctx.elicit({ id, message, input })` produces `input_requested` when it reaches missing input. Built-in and headless renderers present it and call `respond(id, { action: "accept", content })`; decline/cancel stop. Accepted content is schema-validated and completed steps are not rerun; invalid content returns `arg_invalid` and keeps the interaction pending. Elicitation gathers an input and does not approve a later write. Every interactive flow collects elicited input before its first connector operation; every eligible `input_requested` precedes `tool_proposed`. In a `confirm: true` flow, the final proposal reviews original input, elicited values, and the sole exact connector action; a confirmable flow has at most one connector operation. Accept is bound to that action. Bidirectional MCP and the embedded assistant use the same advertised endpoints and interaction-event protocol: missing input maps to standard `elicitation/create`, and an adapter that cannot carry that request fails safely with a structured non-executing result. The same negotiated channel carries the final affirmative confirmation. Setting `interactions: { confirmationFallback: "host" }` in server options explicitly trusts native host approval only when confirmation transport is unavailable and no elicited input is required; embedded/headless confirmation remains Noodle-owned. Omitted or false annotations execute directly; hints never gate.
187
+ A tool authored with `ctx.elicit({ id, message, input })` produces `input_requested` when it reaches missing input. Built-in and headless renderers present it and call `respond(id, { action: "accept", content })`; decline/cancel stop. Accepted content is schema-validated and completed steps are not rerun; invalid content returns `arg_invalid` and keeps the interaction pending. Elicitation gathers an input and does not approve a later write. Every interactive flow collects elicited input before its first connector operation; every eligible `input_requested` precedes `tool_proposed`. In a `confirm: true` flow, the final proposal reviews original input, elicited values, and the sole exact connector action; a confirmable flow has at most one connector operation. Accept is bound to that action. Bidirectional MCP maps missing input to standard `elicitation/create`. On a stateless host, a linked MCP App presents the same normal-user form and re-calls the tool through standard `tools/call`, carrying replay answers in request `_meta` so approval copy contains only business fields; without Apps, the model receives the exact structured schema and an advertised reserved retry field. Both paths replay only the operation-free input prefix and never expose runtime continuation or environment state. Setting `interactions: { confirmationFallback: "host" }` explicitly trusts native host approval only after every elicited field is collected and only when confirmation transport is unavailable; embedded/headless confirmation remains Noodle-owned. Omitted or false annotations execute directly; hints never gate.
180
188
 
181
189
  ## Verified session context (identity and claims)
182
190
 
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  name: noodle-seed
3
3
  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.
4
- version: 0.29.0
4
+ version: 0.30.0
5
5
  hash: cd25535e1d6dbf4f
6
6
  ---
7
7
 
@@ -20,7 +20,7 @@ private customer data.
20
20
  | React app runtime kit | `@noodleseed/one/react` supplies app flow, shell/nav/view, async state, form, quantity, choice, and handoff primitives |
21
21
  | Multi-step widget flow | One React shell navigates stores, menu, item customization, cart, review, and handoff views through `useAppFlow` |
22
22
  | Invocation context | `server.context` sets locale/time-zone defaults, derives an ambient service area/date, and makes the same snapshot available to tools and the reserved `noodle_context` MCP adapter |
23
- | Structured missing input | `plan_order` uses `ctx.elicit` to collect a fulfilment method and date in embedded/headless renderers and bidirectional MCP adapters; the stateless hosted MCP endpoint does not yet carry the server-initiated exchange |
23
+ | Structured missing input | `plan_order` uses `ctx.elicit` to collect a fulfilment method and date through embedded/headless forms, standard bidirectional elicitation, a linked MCP App form, or an exact structured conversational retry on stateless hosts |
24
24
  | Model-visible widget state | `useUpdateModelContext` publishes one cohesive replacement snapshot when supported; `useWidgetLifecycle` auto-publishes mounted/cancelled/dismissed and reports author-owned submitted milestones for future context (not host-presentation proof), while the user-triggered submit pairs `useSendFollowUpMessage` for an immediate reply |
25
25
  | Handoff | `handoff.allowedDomains` allows only `https://orders.example.com` checkout URLs |
26
26
  | Progressive enhancement | Non-Apps hosts still receive stores, featured items, and a readable fallback summary |
@@ -34,7 +34,8 @@ Like the comprehensive default `noodle init my-app` scaffold, this flagship keep
34
34
  while making each individual widget view focused; server capability breadth and screen density are separate.
35
35
  The compiled initial widget should normally remain under the 1 MiB performance recommendation; Noodle Seed's
36
36
  hard ceilings are 10 MiB per compiled widget and 20 MiB across one deployment. Run `noodle check` to see raw
37
- and gzip-estimated sizes, and keep menu images or large live datasets in assets/resources and app-only tools
37
+ and gzip-estimated sizes. Deploy requests are gzip-compressed as one stream so repeated self-contained React
38
+ runtime bytes deduplicate on the wire without a cross-tenant CDN. Keep menu images or large live datasets in assets/resources and app-only tools
38
39
  rather than embedding them into the initial HTML bundle.
39
40
 
40
41
  ## Local Author Loop
@@ -273,7 +273,7 @@ tool('prepare_time_off', {
273
273
  });
274
274
  ```
275
275
 
276
- Use a stable lowercase/number/underscore id and a flat form of string/number/integer/boolean, string choices or multi-select, with optional `email`, `uri`, `date`, or `date-time` formats. Nested objects and credential-shaped fields fail with `invalid_elicitation_schema`. Every interactive flow must place all `ctx.elicit` calls before its first connector operation or compilation fails with `invalid_elicitation_flow`. Embedded/headless clients receive `input_requested`; bidirectional MCP transports map the primitive to standard form `elicitation/create`. An adapter that cannot carry the request returns a structured non-executing `interaction_unavailable` result. Accept validates and resumes without rerunning completed steps; invalid content returns `arg_invalid` and leaves the same interaction pending; decline/cancel stop. Elicitation gathers missing input and does not replace confirmation. In a flow marked `confirm: true`, every eligible `input_requested` precedes `tool_proposed`; the final proposal reviews the original input, elicited values, and sole exact connector action. Accept is bound to that action and only then may execution start. A confirmable flow may contain at most one connector operation; additional operations fail with `invalid_confirmation_flow`. MCP uses final standard form confirmation on capable bidirectional transports and fails closed otherwise. Setting `interactions: { confirmationFallback: "host" }` in the server options explicitly trusts native host approval only when confirmation transport is unavailable and no elicited input is needed; it is never inferred from client name and does not replace authorization. Omitted or `false` annotations execute directly; hints alone never gate. `annotations.action({ confirm: true })` explicitly enables confirmation; `annotations.action({ confirm: false })` explicitly preserves direct execution.
276
+ Use a stable lowercase/number/underscore id and a flat form of string/number/integer/boolean, string choices or multi-select, with optional `email`, `uri`, `date`, or `date-time` formats. Nested objects and credential-shaped fields fail with `invalid_elicitation_schema`. Every interactive flow must place all `ctx.elicit` calls before its first connector operation or compilation fails with `invalid_elicitation_flow`. Embedded/headless clients receive `input_requested`; bidirectional MCP transports map the primitive to standard form `elicitation/create`. On stateless hosts, the adapter returns a structured non-executing `interaction_unavailable` result; linked Apps render its business-user form and retry in request `_meta`, while models can use the advertised reserved retry field. Accept validates and replays only the operation-free input prefix; invalid content returns `arg_invalid`, and decline/cancel stop. Elicitation gathers missing input and does not replace confirmation. In a flow marked `confirm: true`, every eligible `input_requested` precedes `tool_proposed`; the final proposal reviews the original input, elicited values, and sole exact connector action. Accept is bound to that action and only then may execution start. A confirmable flow may contain at most one connector operation; additional operations fail with `invalid_confirmation_flow`. MCP uses final standard form confirmation on capable bidirectional transports and fails closed otherwise. Setting `interactions: { confirmationFallback: "host" }` in the server options explicitly trusts native host approval only when confirmation transport is unavailable and after every elicited field is collected; it is never inferred from client name and does not replace authorization. Omitted or `false` annotations execute directly; hints alone never gate. `annotations.action({ confirm: true })` explicitly enables confirmation; `annotations.action({ confirm: false })` explicitly preserves direct execution.
277
277
 
278
278
  ## Compute connector example
279
279
 
@@ -120,6 +120,14 @@ noodle assistant clients create --name web --org <org> --app <app> --env <env>
120
120
 
121
121
  The CLI writes `{ clientId, clientSecret }` to a mode-`0600` file and prints only its path. Move the values into the SaaS backend secret manager without printing or committing them. Rotation invalidates the previous secret.
122
122
 
123
+ Validate the active deployment, backend credential, exact origin, and delegated credential exchanges without invoking a business tool:
124
+
125
+ ```sh
126
+ noodle assistant doctor --origin "$PUBLIC_APP_ORIGIN" --org <org> --app <app> --env <env>
127
+ ```
128
+
129
+ The doctor reads `NOODLE_ASSISTANT_CLIENT_ID` / `NOODLE_ASSISTANT_CLIENT_SECRET` or the saved mode-0600 client file and never prints the secret. Pass `--user-id <real-test-user>` only when the downstream exchange requires an existing application user.
130
+
123
131
  ## Integrate the customer backend
124
132
 
125
133
  Read the customer repository lockfile or `packageManager` field and install `@noodleseed/assistant` with that existing package manager; never introduce a second lockfile.
@@ -176,7 +184,7 @@ The callback records declarative fulfilment at author time; the shared runtime e
176
184
 
177
185
  ## Structured missing input
178
186
 
179
- A tool authored with `ctx.elicit({ id, message, input })` produces `input_requested` when it reaches missing input. Built-in and headless renderers present it and call `respond(id, { action: "accept", content })`; decline/cancel stop. Accepted content is schema-validated and completed steps are not rerun; invalid content returns `arg_invalid` and keeps the interaction pending. Elicitation gathers an input and does not approve a later write. Every interactive flow collects elicited input before its first connector operation; every eligible `input_requested` precedes `tool_proposed`. In a `confirm: true` flow, the final proposal reviews original input, elicited values, and the sole exact connector action; a confirmable flow has at most one connector operation. Accept is bound to that action. Bidirectional MCP and the embedded assistant use the same advertised endpoints and interaction-event protocol: missing input maps to standard `elicitation/create`, and an adapter that cannot carry that request fails safely with a structured non-executing result. The same negotiated channel carries the final affirmative confirmation. Setting `interactions: { confirmationFallback: "host" }` in server options explicitly trusts native host approval only when confirmation transport is unavailable and no elicited input is required; embedded/headless confirmation remains Noodle-owned. Omitted or false annotations execute directly; hints never gate.
187
+ A tool authored with `ctx.elicit({ id, message, input })` produces `input_requested` when it reaches missing input. Built-in and headless renderers present it and call `respond(id, { action: "accept", content })`; decline/cancel stop. Accepted content is schema-validated and completed steps are not rerun; invalid content returns `arg_invalid` and keeps the interaction pending. Elicitation gathers an input and does not approve a later write. Every interactive flow collects elicited input before its first connector operation; every eligible `input_requested` precedes `tool_proposed`. In a `confirm: true` flow, the final proposal reviews original input, elicited values, and the sole exact connector action; a confirmable flow has at most one connector operation. Accept is bound to that action. Bidirectional MCP maps missing input to standard `elicitation/create`. On a stateless host, a linked MCP App presents the same normal-user form and re-calls the tool through standard `tools/call`, carrying replay answers in request `_meta` so approval copy contains only business fields; without Apps, the model receives the exact structured schema and an advertised reserved retry field. Both paths replay only the operation-free input prefix and never expose runtime continuation or environment state. Setting `interactions: { confirmationFallback: "host" }` explicitly trusts native host approval only after every elicited field is collected and only when confirmation transport is unavailable; embedded/headless confirmation remains Noodle-owned. Omitted or false annotations execute directly; hints never gate.
180
188
 
181
189
  ## Verified session context (identity and claims)
182
190