@noodleseed/one 0.163.0 → 0.165.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.
Files changed (106) hide show
  1. package/dist/banner.d.ts +6 -0
  2. package/dist/banner.d.ts.map +1 -0
  3. package/dist/banner.js +29 -0
  4. package/dist/banner.js.map +1 -0
  5. package/dist/commands/project-setup.d.ts.map +1 -1
  6. package/dist/commands/project-setup.js +2 -0
  7. package/dist/commands/project-setup.js.map +1 -1
  8. package/dist/commands/solutions-coordination.d.ts +5 -0
  9. package/dist/commands/solutions-coordination.d.ts.map +1 -0
  10. package/dist/commands/solutions-coordination.js +94 -0
  11. package/dist/commands/solutions-coordination.js.map +1 -0
  12. package/dist/commands/solutions-ops.d.ts.map +1 -1
  13. package/dist/commands/solutions-ops.js +8 -4
  14. package/dist/commands/solutions-ops.js.map +1 -1
  15. package/dist/first-run.d.ts.map +1 -1
  16. package/dist/first-run.js +2 -0
  17. package/dist/first-run.js.map +1 -1
  18. package/node_modules/@noodle-borg/agent-kit/dist/curated/error-fixes.js +2 -0
  19. package/node_modules/@noodle-borg/agent-kit/dist/generated/example-files.js +3 -3
  20. package/node_modules/@noodle-borg/agent-kit/dist/generated/surface.js +2 -0
  21. package/node_modules/@noodle-borg/agent-kit/dist/index.d.ts +1 -0
  22. package/node_modules/@noodle-borg/agent-kit/dist/index.js +1 -0
  23. package/node_modules/@noodle-borg/agent-kit/dist/plugin-bootstrap-skill.js +10 -0
  24. package/node_modules/@noodle-borg/agent-kit/dist/skill-authoring-refs.js +4 -1
  25. package/node_modules/@noodle-borg/agent-kit/dist/welcome-wordmark.d.ts +3 -0
  26. package/node_modules/@noodle-borg/agent-kit/dist/welcome-wordmark.js +10 -0
  27. package/node_modules/@noodle-borg/agent-kit/package.json +1 -1
  28. package/node_modules/@noodle-borg/assistant-gateway/dist/embed-store.d.ts +4 -0
  29. package/node_modules/@noodle-borg/assistant-gateway/dist/in-memory-embed-store.d.ts +4 -0
  30. package/node_modules/@noodle-borg/assistant-gateway/dist/in-memory-embed-store.js +6 -2
  31. package/node_modules/@noodle-borg/assistant-gateway/package.json +1 -1
  32. package/node_modules/@noodle-borg/authoring/dist/config.d.ts +8 -2
  33. package/node_modules/@noodle-borg/authoring/dist/config.js +28 -1
  34. package/node_modules/@noodle-borg/authoring/dist/connectors.d.ts +37 -0
  35. package/node_modules/@noodle-borg/authoring/dist/connectors.js +4 -0
  36. package/node_modules/@noodle-borg/authoring/dist/index.d.ts +1 -1
  37. package/node_modules/@noodle-borg/authoring/dist/server.js +1 -0
  38. package/node_modules/@noodle-borg/cli-catalog/dist/catalog-data-solution-flags.js +83 -0
  39. package/node_modules/@noodle-borg/cli-catalog/dist/catalog-data-solutions.js +70 -92
  40. package/node_modules/@noodle-borg/compiler/dist/artifact/operation-ref.d.ts +2 -0
  41. package/node_modules/@noodle-borg/compiler/dist/artifact/version.d.ts +4 -1
  42. package/node_modules/@noodle-borg/compiler/dist/artifact/version.js +4 -1
  43. package/node_modules/@noodle-borg/compiler/dist/catalog/types.d.ts +7 -0
  44. package/node_modules/@noodle-borg/compiler/dist/errors.d.ts +1 -1
  45. package/node_modules/@noodle-borg/compiler/dist/fulfilment-emit.js +15 -2
  46. package/node_modules/@noodle-borg/compiler/dist/nested-operations.js +71 -0
  47. package/node_modules/@noodle-borg/compute/dist/code-connector.js +14 -2
  48. package/node_modules/@noodle-borg/compute/dist/deterministic-helpers.js +138 -0
  49. package/node_modules/@noodle-borg/compute/dist/quickjs-engine.js +48 -0
  50. package/node_modules/@noodle-borg/compute/dist/sandbox-eval.js +39 -5
  51. package/node_modules/@noodle-borg/compute/dist/worker-entry.js +7 -0
  52. package/node_modules/@noodle-borg/compute/dist/worker-pool.js +14 -3
  53. package/node_modules/@noodle-borg/connector-defs/dist/compile-http.js +31 -2
  54. package/node_modules/@noodle-borg/connector-defs/dist/compile.d.ts +1 -1
  55. package/node_modules/@noodle-borg/connector-defs/dist/compile.js +20 -0
  56. package/node_modules/@noodle-borg/connector-defs/dist/schema.d.ts +84 -0
  57. package/node_modules/@noodle-borg/connector-defs/dist/schema.js +44 -1
  58. package/node_modules/@noodle-borg/connector-http/dist/http-connector.d.ts +7 -0
  59. package/node_modules/@noodle-borg/connector-http/dist/http-connector.js +34 -6
  60. package/node_modules/@noodle-borg/connector-http/dist/http-response.d.ts +8 -1
  61. package/node_modules/@noodle-borg/connector-http/dist/http-response.js +19 -10
  62. package/node_modules/@noodle-borg/connector-http/dist/index.d.ts +1 -1
  63. package/node_modules/@noodle-borg/control-plane/dist/contracts.d.ts +2 -0
  64. package/node_modules/@noodle-borg/control-plane/dist/deploy-gates.js +1 -0
  65. package/node_modules/@noodle-borg/module/dist/contract.d.ts +2 -0
  66. package/node_modules/@noodle-borg/runtime/dist/connector/types.d.ts +7 -1
  67. package/node_modules/@noodle-borg/runtime/dist/connector-snapshot.js +8 -0
  68. package/node_modules/@noodle-borg/runtime/dist/execute.d.ts +2 -0
  69. package/node_modules/@noodle-borg/runtime/dist/index.d.ts +1 -0
  70. package/node_modules/@noodle-borg/runtime/dist/nested-operation-host.js +25 -0
  71. package/node_modules/@noodle-borg/runtime/dist/operation-coordination-execution.js +50 -0
  72. package/node_modules/@noodle-borg/runtime/dist/operation-coordination.d.ts +34 -0
  73. package/node_modules/@noodle-borg/runtime/dist/operation-evidence.d.ts +4 -0
  74. package/node_modules/@noodle-borg/runtime/dist/operation-execution.js +173 -94
  75. package/node_modules/@noodle-borg/service/dist/application-activity.js +152 -18
  76. package/node_modules/@noodle-borg/service/dist/application-runtime-target.js +15 -2
  77. package/node_modules/@noodle-borg/service/dist/business-information/definition-resolver.js +19 -0
  78. package/node_modules/@noodle-borg/service/dist/business-information/in-memory-store.js +1 -1
  79. package/node_modules/@noodle-borg/service/dist/business-information/managed-solution-blueprints.js +7 -0
  80. package/node_modules/@noodle-borg/service/dist/business-information/managed-solution-executable.js +11 -1
  81. package/node_modules/@noodle-borg/service/dist/business-information/model.js +2 -2
  82. package/node_modules/@noodle-borg/service/dist/business-information/portable.js +1 -1
  83. package/node_modules/@noodle-borg/service/dist/business-information/profiles.js +37 -1
  84. package/node_modules/@noodle-borg/service/dist/credential-binding-index.js +19 -1
  85. package/node_modules/@noodle-borg/service/dist/deployment-execution.js +1 -1
  86. package/node_modules/@noodle-borg/service/dist/operation-coordination.js +185 -0
  87. package/node_modules/@noodle-borg/service/dist/operation-evidence.js +3 -1
  88. package/node_modules/@noodle-borg/service/dist/routes/business-information-activity.js +48 -53
  89. package/node_modules/@noodle-borg/service/dist/routes/business-information-dispatch.js +2 -1
  90. package/node_modules/@noodle-borg/service/dist/routes/business-information-installation.js +51 -17
  91. package/node_modules/@noodle-borg/service/dist/routes/business-information-paths.js +6 -4
  92. package/node_modules/@noodle-borg/service/dist/routes/business-information-staff.js +4 -3
  93. package/node_modules/@noodle-borg/service/dist/routes/business-information.js +11 -6
  94. package/node_modules/@noodle-borg/service/dist/routes/control-plane.js +14 -1
  95. package/node_modules/@noodle-borg/service/dist/routes/deploy-public-embed.js +7 -2
  96. package/node_modules/@noodle-borg/service/dist/service.js +2 -1
  97. package/node_modules/@noodle-borg/service/dist/solution-installation-activation.js +58 -3
  98. package/node_modules/@noodle-borg/service/package.json +1 -1
  99. package/node_modules/@noodle-borg/wire-contracts/dist/business-information.d.ts +52 -0
  100. package/node_modules/@noodle-borg/wire-contracts/dist/business-information.js +6 -0
  101. package/node_modules/@noodle-borg/wire-contracts/dist/index.d.ts +1 -0
  102. package/node_modules/@noodle-borg/wire-contracts/dist/index.js +1 -0
  103. package/node_modules/@noodle-borg/wire-contracts/dist/operation-coordination.d.ts +59 -0
  104. package/node_modules/@noodle-borg/wire-contracts/dist/operation-coordination.js +51 -0
  105. package/node_modules/@noodleseed/assistant/package.json +1 -1
  106. package/package.json +2 -2
@@ -16,14 +16,14 @@ export const BUNDLED_EXAMPLE_NAMES = [
16
16
  ];
17
17
  /** Real example sources vendored from `examples/<name>`, written under `examples/` in the skill tree. */
18
18
  export const BUNDLED_EXAMPLE_FILES = [
19
- { relPath: "examples/acme-bistro/README.md", content: "# Acme Bistro — ordering with payment handoff\n\nFictional [`menu/cart`](src/server.ts) with off-app payment: card data stays outside the app.\n\n`SERVICE_NOTICE` settings and native `guest_requests` demonstrate status, field exposure and notes. `submit_guest_request` requires an authorized installation and returns a receipt\nfor staff review. The installed skill's `references/authoring-workflow.md` owns setup and source contracts.\nExternal collections declare a bounded connector scan; provider changes remain ordinary tools.\n\nStaff can clear optional `guestReference` in Portal or an authored\n`connectors.records.updateRecord({ collection: 'guest_requests', id, expectedRevision, patch: {}, unset: ['guestReference'] })`.\nRequired fields cannot be removed; `null` is a value, not deletion.\n\n## Design deliverables\n\n- [UX Document](design/UX-Document.md)\n- [Browser wireframe and compliance audit](design/wireframe.html)\n- [Partner API contract](design/api-contract.md)\n\n## Run\n\nUse `noodle validate`, `noodle test`, and `noodle dev` for the local menu/cart.\nNative submission requires installed storage, grants and public intake.\n" },
19
+ { relPath: "examples/acme-bistro/README.md", content: "# Acme Bistro — ordering with payment handoff\n\nFictional [`menu/cart`](src/server.ts) with off-app payment: card data stays outside the app.\n\n`GUEST_EXPERIENCE` settings use `guestExperience.field('notice')` to select a typed business value; native `guest_requests` demonstrate status, field exposure and notes. `submit_guest_request` requires an authorized installation and returns a receipt\nfor staff review. The installed skill's `references/authoring-workflow.md` owns setup and source contracts.\nExternal collections declare a bounded connector scan; provider changes remain ordinary tools.\n\nStaff can clear optional `guestReference` in Portal or an authored\n`connectors.records.updateRecord({ collection: 'guest_requests', id, expectedRevision, patch: {}, unset: ['guestReference'] })`.\nRequired fields cannot be removed; `null` is a value, not deletion.\n\n## Design deliverables\n\n- [UX Document](design/UX-Document.md)\n- [Browser wireframe and compliance audit](design/wireframe.html)\n- [Partner API contract](design/api-contract.md)\n\n## Run\n\nUse `noodle validate`, `noodle test`, and `noodle dev` for the local menu/cart.\nNative submission requires installed storage, grants and public intake.\n" },
20
20
  { relPath: "examples/acme-bistro/design/UX-Document.md", content: "# Acme Bistro ChatGPT App — User Flow & Experience Document\n\n**Prepared by:** Noodle Seed\n**Scope:** Diners browse the Acme Bistro menu, build and confirm an order inside ChatGPT, then hand off once to a signed checkout link to pay — the card never touches the app.\n**Status:** Design specification (v1)\n**Funnel boundary:** IN the app — menu, order building, order confirmation, and the checkout hand-off, all in-chat. OFF-app — **payment only**, on Acme Bistro's PCI-scoped checkout at `pay.acme.example`. **No per-user OAuth in this app**; the connector runs on Acme's own service credentials, and the diner authenticates (if at all) only on the payment page.\n\n---\n\n## 0. The One-Paragraph Thesis\n\nA hungry diner opens ChatGPT and types *\"order me two margheritas and a lemon tart from Acme Bistro.\"* Today that intent scatters across a search, a delivery-app download, a menu scroll, and a checkout form. Acme Bistro collapses it into one conversation: the model reads the live menu, parses the order out of plain language, renders a running cart the diner can nudge with a tap or a sentence, and — only when the order is right — mints a **signed, expiring payment link** that opens Acme's own checkout. We own the entire pre-payment experience; Acme owns the money. That split is deliberate and it is the product: the app never sees a card number, so Acme's PCI scope never grows, yet the diner completes a real, paid-intent order without leaving the chat. For a single restaurant, this is the cheapest possible storefront on the fastest-growing surface — one `server.ts`, no app to install, and every order arrives at Acme's checkout already built. If you can convincingly finish this order in a sentence, you have out-competed every tap-driven ordering app on the one axis they cannot copy: language.\n\n---\n\n## 1. Acme Bistro Product Overview (Knowledge Base)\n\n**Acme Bistro is a single fictional neighbourhood restaurant** offering a short, curated menu for pickup ordering. Unlike a marketplace aggregator, there is one kitchen, one menu, and one checkout — which makes the conversational surface tight and the guardrails simple. The ChatGPT App is Acme's storefront on ChatGPT: it shows the menu, builds the order, and passes a ready cart to Acme's payment page.\n\n### 1.1 The Menu (authoritative — the app must know this exactly)\n\n| Item | ID | Price (USD) | Course |\n|------|-----|-------------|--------|\n| Stone-baked Margherita | `stone_pizza` | $14 | Mains |\n| Harvest Roast Bowl | `roast_bowl` | $13 | Mains |\n| House Garden Salad | `house_salad` | $11 | Starters |\n| Lemon Tart | `lemon_tart` | $8 | Desserts |\n| Sparkling Water | `sparkling` | $4 | Drinks |\n\nPrices are whole-dollar and fixed for v1. The **backend owns pricing** — the widget sums line items for display, but the amount that reaches checkout is recomputed and re-validated by Acme at `pay.acme.example`. The menu is small enough to render in a single inline widget with no pagination.\n\n### 1.2 The End-to-End Model (the defining choice)\n\nEvery other decision follows from one line: **the order is built and confirmed in chat; only payment hands off.** There is no in-chat card capture, no wallet, no stored payment method. When the diner is ready, the app calls `create_checkout`, which returns a **signed deep link** carrying a url-safe cart token and the numeric total; ChatGPT opens it, and Acme's checkout takes the card. The MCP server is never in the payment path.\n\n### 1.3 Business Model & Why Acme Wants This\n\nAcme's bottleneck is reach, not kitchen capacity: a neighbourhood restaurant has no realistic way onto a conversational surface without building an app. The ChatGPT App removes that bottleneck for the cost of one authored server. **Attribution is built in** — every checkout link carries `src=chatgpt`, so Acme can measure exactly how much revenue the conversational storefront drives against their existing web orders.\n\n---\n\n## 2. Competitive Landscape — Food Ordering on ChatGPT\n\n| Pattern | Examples | Strength | Gap Acme fills |\n|---------|----------|----------|----------------|\n| **Marketplace aggregators** | Large delivery apps | Vast networks, delivery logistics | Menu markups, no single-restaurant intimacy, heavy handoff to a separate app |\n| **Reservation / discovery** | Booking + reviews apps | Strong discovery inventory | No ordering, no checkout |\n| **Acme Bistro (this app)** | — | One kitchen, honest single-menu pricing, full order built in chat, payment on Acme's own PCI checkout | — |\n\n**Acme's position:** Acme is not trying to be a marketplace. Its advantage inside ChatGPT is **directness** — a diner who already wants Acme's food gets from craving to a paid-ready cart in one conversation, with the restaurant's own prices and the restaurant's own checkout. The single-restaurant scope is a feature: no ranking to game, no cross-restaurant carts, no ambiguity about whose menu the model is grounding on.\n\n---\n\n## 3. Target User Personas\n\n### Persona A — \"The Regular\"\nOrders from Acme every week and knows the menu. Wants the shortest possible path: *\"the usual — two margheritas and a sparkling water.\"* Values speed and an accurate cart over discovery.\n\n### Persona B — \"The Craver\"\nArrives with an appetite, not a specific dish: *\"something light from Acme\"* or *\"what mains do you have?\"* Needs the menu surfaced fast and an opinionated nudge toward the roast bowl or the salad.\n\n### Persona C — \"The Careful Orderer\"\nHas a dietary constraint and asks before adding: *\"is the garden salad vegetarian?\"* Needs honest, non-guessing answers grounded only in what the menu data actually states — and a clear defer-to-restaurant when it doesn't.\n\n### Persona D — \"The Group Coordinator\"\nOrdering for two or three people with a running budget: *\"add a margherita, a roast bowl, a salad, and a lemon tart — what's the total?\"* Needs a live, legible cart total and easy quantity edits before committing to pay.\n\n---\n\n## 4. Conversational User Flow\n\n### 4.1 Entry Points\n\nNatural phrases that should trigger the app:\n\n```\n\"Show me the Acme Bistro menu\"\n\"Order two margheritas and a lemon tart from Acme\"\n\"I want something light from Acme Bistro\"\n\"What mains does Acme have?\"\n\"Add a sparkling water to my Acme order\"\n\"What's my Acme total?\"\n\"Check out and pay for my Acme order\"\n```\n\n### 4.2 Flow Architecture\n\n```\n┌──────────────────────────────────────────────┐\n│ USER ENTERS CHAT │\n│ (natural-language prompt) │\n└───────────────────────┬────────────────────────┘\n │\n ▼\n ┌─────────────────────────────┐\n │ show_menu (widget) │\n │ MenuCart renders: 5 items, │\n │ steppers, live total, CTA │\n └──────────────┬───────────────┘\n │\n ┌───────────────┼────────────────┐\n ▼ ▼ ▼\n┌──────────────┐ ┌──────────────┐ ┌──────────────┐\n│ add_to_cart │ │remove_from_ │ │ taps in │\n│ (NL: \"two │ │cart (NL or │ │ the widget │\n│ margheritas\")│ │ − button) │ │ (+ / −) │\n└──────┬───────┘ └──────┬───────┘ └──────┬───────┘\n └────────────────┼────────────────┘\n ▼\n ┌─────────────────────────────┐\n │ Live cart + running total │\n │ (summed in the widget) │\n └──────────────┬───────────────┘\n │ \"check out & pay\"\n ▼\n ┌─────────────────────────────┐\n │ create_checkout │\n │ → signed, expiring link to │\n │ pay.acme.example │\n └──────────────┬───────────────┘\n ▼ (OFF-APP)\n ┌─────────────────────────────┐\n │ Acme PCI checkout · card │\n │ entered here, never in chat │\n └─────────────────────────────┘\n```\n\n### 4.3 Detailed Conversational Scenarios\n\n#### Scenario 1 — Natural-language order (Persona A/D)\n\n```\nUSER: Order me two margheritas and a lemon tart from Acme Bistro.\n\nAPP: [tool: show_menu {customer:\"Guest\"}] → renders MenuCart\n [tool: add_to_cart {item:\"stone_pizza\", quantity:2}]\n [tool: add_to_cart {item:\"lemon_tart\", quantity:1}]\n\n Here's your Acme Bistro order — two Stone-baked Margheritas\n and a Lemon Tart. That's $36 so far. Want a drink or a side,\n or shall I take you to checkout to pay?\n\n [MenuCart widget]\n ┌────────────────────────────────────────────┐\n │ 🍽 Acme Bistro 2 in cart │\n │ Stone-baked Margherita Mains $14 [−]2[+]│\n │ Harvest Roast Bowl Mains $13 [−]0[+]│\n │ House Garden Salad Starters$11 [−]0[+]│\n │ Lemon Tart Desserts $8 [−]1[+]│\n │ Sparkling Water Drinks $4 [−]0[+]│\n │ ────────────────────────────────────────── │\n │ Total $36 [ 💳 Check out & pay ] │\n │ Payment happens on acme.example — your card │\n │ is never entered in chat. │\n └────────────────────────────────────────────┘\n```\n\n#### Scenario 2 — Add and edit (Persona D)\n\n```\nUSER: Add a sparkling water too.\n\nAPP: [tool: add_to_cart {item:\"sparkling\", quantity:1}]\n Added a Sparkling Water — your total is $40 for four items.\n\nUSER: Actually drop one margherita.\n\nAPP: [tool: remove_from_cart {item:\"stone_pizza\"}]\n Done — one Margherita, one Lemon Tart, one Sparkling Water.\n New total $26. Ready to pay whenever you are.\n```\n\n#### Scenario 3 — Dietary question, honest answer (Persona C)\n\n```\nUSER: Is the garden salad vegetarian?\n\nAPP: The House Garden Salad is on our Starters menu at $11. I can\n tell you what's on the menu, but I can't confirm ingredient-\n level details like preparation or cross-contact — for\n allergy or dietary certainty, please check with Acme Bistro\n directly before ordering. Want me to add it anyway, or show\n you the other starters and mains?\n```\n\n#### Scenario 4 — Checkout handoff (all personas)\n\n```\nUSER: Check out and pay.\n\nAPP: [tool: create_checkout {customer:\"Guest\",\n cartToken:\"stone_pizzax2-lemon_tartx1-sparklingx1\", total:40}]\n\n Your order's ready — two Margheritas, a Lemon Tart, and a\n Sparkling Water, $40 total. I've opened Acme's secure\n checkout to take payment. Your card is entered on\n acme.example, never here in chat.\n\n [opens https://pay.acme.example/checkout?cart=\n stone_pizzax2-lemon_tartx1-sparklingx1&total=40&src=chatgpt]\n```\n\n---\n\n## 5. UI Widget Specifications\n\n> The widget is authored as a Noodle Seed React `view` (`tool` → `MenuCart`), styled with **vanilla CSS cascade layers** so it inherits the host's light/dark theme and adapts to ChatGPT's surface. Compliance is verified with `noodle check --target chatgpt`.\n\n### 5.1 Design System Compliance\n\nAcme authors **one** brand surface through the server `branding` tokens; everything else defers to host-provided semantic tokens (text, background, border, success/warning), so the widget looks native in ChatGPT.\n\n| Category | Source | Value |\n|----------|--------|-------|\n| Text / background / border | Host semantic tokens (via cascade layers) | Host-provided, theme-aware |\n| Brand accent | `branding.accent` | `#B91C1C` (Acme red) — **primary CTA + logo mark only** |\n| Surface (light) | `branding.surface` | `#FEF3F2` |\n| Surface (dark) | `branding.surfaceDark` | `#1A1211` |\n| Radius / density | `branding.radius` / `branding.density` | `lg` / `comfortable` |\n\n**Enforced rules:** system font stack; monochromatic outlined icons (the plate mark, the card glyph); WCAG AA contrast on all text/surface pairs (Acme red is used only as a fill behind light text or as a 1px mark, never as body text on white); no nested scroll (the 5-item menu fits without an inner scroller); brand accent restricted to the primary **Check out & pay** button and the header mark.\n\n### 5.2 Display Mode Strategy\n\n| User intent | Display mode | Rationale |\n|-------------|--------------|-----------|\n| Browse the menu / build an order | **Inline Card** (`MenuCart`) | Five items + steppers + total fit an inline card; no drill-in, no pagination |\n| Confirm total & pay | **Inline Card** (same widget, primary CTA) | The CTA opens the off-app checkout; no in-chat payment surface |\n| Payment | **None (off-app browser)** | Deliberately not a widget — card capture stays on Acme's PCI page |\n\nModes deliberately **not** used: no Carousel (a single flat menu doesn't need one), no Fullscreen (five items don't warrant it), no Picture-in-Picture (there is no live-tracking phase in v1 — fulfilment happens after payment on Acme's side).\n\n### 5.3 Widget Specifications\n\n#### ★ `MenuCart` — Inline Card\n**Purpose:** the entire in-chat experience — menu, order building, live total, and the checkout hand-off — in one widget.\n\n| Spec | Value |\n|------|-------|\n| Header | Plate mark, \"Acme Bistro\" title, status subtitle, cart chip (`N in cart` / `Fullscreen`) |\n| Menu rows | One per item: name, course, price, and a `[− qty +]` stepper |\n| Total | Live subtotal summed in React from the session-local cart |\n| Primary action | **Check out & pay** (brand red) — disabled while the cart is empty or checkout is pending; opens the signed link via `openExternal` |\n| Reassurance | Fine-print note: \"Payment happens on acme.example — your card is never entered in chat.\" |\n| Edge states | Empty cart (CTA disabled), pending checkout (\"Opening checkout…\"), dark theme variant |\n\n**Two-users note:** every row is model-fillable — the model reflects *\"two margheritas\"* into `add_to_cart {item:\"stone_pizza\", quantity:2}`, and the same widget a human taps updates identically.\n\n---\n\n## 6. Tool Definitions (App Backend)\n\n### ★ Tool 1: `show_menu` — `tool`\n**Input:** `{ customer?: string = \"Guest\" }`\n**Output:** `{ status, customer, items[] }` where each item is `{ id, name, price, kind }`.\n**Renders:** the `MenuCart` widget.\n**Annotations:** read-only.\n**Triggers:** any menu / ordering intent (\"show me Acme's menu\", \"order from Acme\").\n\n### Tool 2: `add_to_cart` — `tool`\n**Input:** `{ customer?, item: <menu id> = \"stone_pizza\", quantity?: int ≥1 = 1, notes?: string }`\n**Output:** `{ status, item, quantity, notes }`.\n**Annotations:** local write (non-destructive).\n**Triggers:** natural-language additions (\"add two margheritas\", \"and a lemon tart\"). Widget-facing helper — reflects NL selections into the visible cart.\n\n### Tool 3: `remove_from_cart` — `tool`\n**Input:** `{ customer?, item: <menu id> = \"stone_pizza\" }`\n**Output:** `{ status, item }`.\n**Annotations:** local write (non-destructive).\n**Triggers:** \"drop one margherita\", \"remove the salad\", or the widget's `−` button.\n\n### ★ Tool 4: `create_checkout` — model-visible `tool`\n**Input:** `{ customer?, cartToken: string = \"cart\", total: number ≥0 = 0 }`\n**Output:** `{ status, summary, checkoutUrl }`.\n**Annotations:** open-link (external action).\n**Behaviour:** returns a signed deep link — `https://pay.acme.example/checkout?cart=<cartToken>&total=<total>&src=chatgpt`. The card never reaches this app. `handoff.allowedDomains` includes `pay.acme.example`, so the compiler derives the ChatGPT redirect domain and the link opens without a safe-link warning.\n**Triggers:** \"check out\", \"pay\", \"I'm done\".\n\nTools are atomic and model-friendly: `show_menu` reads, the two cart tools write locally, `create_checkout` opens the one external link. There is no `submit_order` or `capture_payment` tool by design — order fulfilment and payment are Acme's, past the boundary.\n\n---\n\n## 7. Conversation Design Principles\n\n### 7.1 Tone of Voice\nWarm, concise, and restaurant-first — like a counter host who knows the menu. State prices and totals as plain facts (\"that's $36 so far\"), recommend when it helps (\"the roast bowl is the heartier main\"), and never oversell.\n\n### 7.2 Guardrails (non-negotiable)\n- **Never invent menu items or prices.** Ground every dish and amount in the `show_menu` data — only the five items, only their listed prices.\n- **Never confirm allergen or dietary safety.** State what the menu says (course, name, price); for ingredient-level or cross-contact questions, defer to Acme Bistro directly. Never assert \"this is vegetarian/gluten-free\" without a menu flag that says so.\n- **Never take payment in chat.** No card numbers, no CVV, no wallet. Payment is the one off-app step; if a user pastes card details, decline and point them to the checkout link.\n- **Never promise fulfilment the app can't see.** The app builds and hands off the order; pickup timing and order status live on Acme's side after payment.\n- **Always show the honest total before checkout**, and restate that payment happens on `acme.example`.\n\n### 7.3 Memory Strategy\nRemember the diner's in-session cart and name. There is no cross-session account (no per-user auth) — a returning diner starts a fresh order, though the model may recall a prior order *within the same conversation* to speed a reorder.\n\n### 7.4 Multi-Turn Intelligence\nThe model infers item + quantity from language (\"a couple of margheritas\" → `quantity:2`), keeps a running total in view, and asks only when genuinely ambiguous (\"did you mean the margherita or the roast bowl?\"). It never asks for a field it can default.\n\n---\n\n## 8. End-to-End User Journey Map\n\n**Phase 1 — Menu (first 5–10s):** user names Acme or asks for the menu → `show_menu` renders `MenuCart`.\n**Phase 2 — Build (10–40s):** natural-language adds/removes (`add_to_cart` / `remove_from_cart`) and/or widget steppers; the total updates live.\n**Phase 3 — Confirm (5–10s):** the app restates the cart and total in plain language; user says \"pay\".\n**Phase 4 — Hand off (2–5s):** `create_checkout` mints the signed link; ChatGPT opens it.\n**Phase 5 — Pay (off-app):** the diner enters their card on `pay.acme.example`; the app's job is done. Fulfilment is Acme's.\n\n---\n\n## 9. Handoff Architecture (Deep Dive)\n\n**What must be true of the handoff:**\n1. **Context survives the jump.** The cart token encodes every line (`stone_pizzax2-lemon_tartx1-sparklingx1`) plus the total, so Acme's checkout rehydrates the exact order without a second round-trip.\n2. **The link is signed and attributable.** Acme signs the checkout URL server-side and carries `src=chatgpt` for attribution. `handoff.allowedDomains: ['https://pay.acme.example', 'https://acme.example']` lets the compiler emit the redirect domain so the link opens cleanly.\n3. **State is re-validated past the boundary.** Acme recomputes pricing, checks inventory, and enforces the total at checkout — the widget's sum is display-only and never authoritative.\n4. **The link expires.** Checkout URLs carry an `expires_at`; a stale link lands on a \"cart expired — start again\" page rather than charging an out-of-date total.\n\n**URL pattern:** `https://pay.acme.example/checkout?cart={cartToken}&total={total}&src=chatgpt`\n\n**Why payment is the only handoff:** keeping card capture on Acme's PCI-scoped checkout means the MCP server never enters payment scope — no card data, no stored methods, no compliance burden added by the ChatGPT surface. The app is the storefront; Acme is the register.\n\n**Open questions for Acme engineering:**\n- Signing scheme + default expiry window (proposed: 15 minutes)?\n- Should the cart token be opaque (server-minted) instead of the human-readable `idxN-idxN` form, to prevent client-side total tampering before re-validation?\n- Post-payment visibility (webhook / polling) so a later chat turn can confirm \"your order is ready\" — out of scope for v1?\n\n---\n\n## 10. Demo Scope Recommendation\n\n**MVP (build in this order):**\n1. `show_menu` + `MenuCart` — menu renders, steppers work, total sums live.\n2. `add_to_cart` / `remove_from_cart` — natural-language and button edits both reflect in the cart.\n3. `create_checkout` — signed link opens Acme's checkout with the cart pre-loaded.\n\n**2-minute demo script:**\n```\nNARRATOR: \"A diner wants dinner from their neighbourhood spot,\nAcme Bistro, without leaving ChatGPT.\"\n\nUSER: \"Order two margheritas and a lemon tart from Acme Bistro.\"\n[show_menu renders MenuCart; add_to_cart ×2 fills the cart — $36]\n\nUSER: \"Add a sparkling water.\"\n[add_to_cart — total ticks to $40]\n\nUSER: \"What's my total?\"\n[MenuCart shows Total $40, four items]\n\nUSER: \"Check out and pay.\"\n[create_checkout mints the signed link; ChatGPT opens\n pay.acme.example — card entered there, never in chat]\n\nNARRATOR: \"Built and confirmed in one conversation; paid on Acme's\nown secure checkout. The app never saw a card number.\"\n```\n\n---\n\n## 11. Technical Architecture (High Level)\n\n```\n┌───────────────────────────────────────────────┐\n│ ChatGPT Client │\n│ MenuCart widget (Noodle Seed React view) │\n│ cascade-layer CSS · host theme tokens │\n└───────────────────────┬─────────────────────────┘\n │ tool calls\n ▼\n┌───────────────────────────────────────────────┐\n│ Acme Bistro MCP server (Noodle Seed) │\n│ show_menu · add_to_cart · remove_from_cart │\n│ create_checkout │\n│ branding tokens · handoff.allowedDomains │\n│ (static menu data; no per-user auth) │\n└───────────────────────┬─────────────────────────┘\n │ signed checkout link (no card data)\n ▼\n┌───────────────────────────────────────────────┐\n│ Acme Bistro checkout — pay.acme.example │\n│ PCI-scoped card capture · pricing/inventory │\n│ validation · order fulfilment │\n└───────────────────────────────────────────────┘\n```\n\nMenu data is static in v1 (authored in `server.ts`). Session cart state lives in the widget (React). No database, no per-user credentials, no card data in the MCP server — the smallest possible surface for a single-restaurant storefront.\n\n---\n\n## 12. Success Metrics\n\n| Metric | Target | Measurement |\n|--------|--------|-------------|\n| Menu render → first add | 55%+ of `show_menu` sessions add ≥1 item | `add_to_cart` call rate |\n| Cart with ≥1 item → `create_checkout` | 60%+ | Tool-call funnel |\n| Checkout link opened → paid (on Acme) | Acme-side; joined via `src=chatgpt` | Acme checkout analytics |\n| End-to-end (entry → paid order) | 15%+ | Funnel + Acme attribution |\n| Average order value | $30+ | Cart totals at `create_checkout` |\n| Time to checkout hand-off | Under 60s | Session duration |\n\n**Attribution mechanics:** every `create_checkout` link carries `src=chatgpt`, so Acme can attribute paid revenue to the ChatGPT storefront and compare it against their existing web channel.\n\n---\n\n## 13. Future Enhancements (Post-Launch)\n\n- **Item notes at scale** — surface the `notes` field in the widget for per-item requests (\"no basil\").\n- **Modifier groups** — sizes / add-ons if the menu grows beyond flat items (would introduce an item-detail widget).\n- **Live inventory** — mark sold-out items unavailable from Acme's kitchen system.\n- **Post-payment confirmation** — an Acme webhook so a later chat turn can confirm \"your order is ready for pickup.\"\n- **Returning-diner reorder** — opt-in, if Acme later adds per-user accounts (would move this app off the no-auth model deliberately).\n- **Scheduled pickup** — choose a pickup window before the checkout hand-off.\n- **Second location** — a lightweight location picker if Acme opens another kitchen (keeps single-menu simplicity per location).\n\n---\n\n### Appendix A — Funnel Boundary Cheat-Sheet\n\n| User request | Handled in the app? | Where it lands |\n|--------------|---------------------|----------------|\n| \"Show me the menu\" | ✅ In-chat | `show_menu` → `MenuCart` |\n| \"Add two margheritas\" | ✅ In-chat | `add_to_cart` |\n| \"Drop the salad\" | ✅ In-chat | `remove_from_cart` |\n| \"What's my total?\" | ✅ In-chat | Live widget total |\n| \"Check out / pay\" | ✅ In-chat → hand-off | `create_checkout` mints signed link |\n| Enter card & pay | ❌ OFF-APP | `pay.acme.example` (Acme PCI checkout) |\n| Pickup timing / order status | ❌ OFF-APP | Acme's side, post-payment |\n| Account / saved cards | ❌ Not in v1 | No per-user auth by design |\n\n---\n\n*This document is the master spec for the Acme Bistro ChatGPT App. Acme Bistro, its menu, and its domains are illustrative. All tool names, widget names, menu items, and prices match the runnable Noodle Seed app exactly; the checkout link shape and pricing/inventory validation are owned by Acme's backend past the funnel boundary.*\n" },
21
21
  { relPath: "examples/acme-bistro/design/api-contract.md", content: "# Acme Bistro — Recommended API Shapes\n\n**For Acme Bistro Engineering.** Concrete request/response JSON for each tool the ChatGPT App calls, so your backend can implement exactly what the app needs. These are a starting point for the contract, not a final spec — field names and envelopes can shift to match Acme's platform conventions, as long as the semantics below are preserved.\n\n> **The backend owns pricing, inventory, and payment.** The widget sums line items for *display only*; the amount that reaches checkout is recomputed and enforced by Acme at `pay.acme.example`. The MCP server never sees a card number, a CVV, or a stored payment method — payment is the single off-app step. Keep pricing, availability, and the signed checkout link server-side.\n\nThe app maps to four tools:\n\n| Tool | Kind | Job |\n|------|------|-----|\n| `show_menu` | `tool` (read-only) | Return the menu + render the `MenuCart` widget |\n| `add_to_cart` | `tool` (local write) | Reflect a natural-language addition into the visible cart |\n| `remove_from_cart` | `tool` (local write) | Remove one unit of an item |\n| `create_checkout` | model-visible `tool` (open-link) | Mint the signed, expiring payment link |\n\nMenu item IDs are the stable enum: `stone_pizza`, `roast_bowl`, `house_salad`, `lemon_tart`, `sparkling`.\n\n---\n\n## 1. `show_menu` — menu + widget\n\nThe one read. Returns the full menu (small enough to render without pagination) plus a status line the model can speak.\n\n**Request**\n```json\n{\n \"customer\": \"Guest\"\n}\n```\n\n**Response**\n```json\n{\n \"status\": \"Acme Bistro menu is ready for Guest. Build the order here; pay at checkout.\",\n \"customer\": \"Guest\",\n \"items\": [\n { \"id\": \"stone_pizza\", \"name\": \"Stone-baked Margherita\", \"price\": 14, \"kind\": \"Mains\" },\n { \"id\": \"roast_bowl\", \"name\": \"Harvest Roast Bowl\", \"price\": 13, \"kind\": \"Mains\" },\n { \"id\": \"house_salad\", \"name\": \"House Garden Salad\", \"price\": 11, \"kind\": \"Starters\" },\n { \"id\": \"lemon_tart\", \"name\": \"Lemon Tart\", \"price\": 8, \"kind\": \"Desserts\" },\n { \"id\": \"sparkling\", \"name\": \"Sparkling Water\", \"price\": 4, \"kind\": \"Drinks\" }\n ]\n}\n```\n\n**Notes.**\n- `price` is a whole-dollar USD number in v1. If Acme moves to cents or a currency field, keep one canonical numeric price per item so the widget's sum and the checkout total agree.\n- `items[]` is the authoritative menu — the model must not invent dishes or prices outside this list.\n- **Extensibility:** Acme may add fields (`description`, `available`, `dietary_tags`, `image_url`) without breaking the app, as long as `id`, `name`, `price`, and `kind` remain. If `available: false` is added, the widget should disable that row's `+` button.\n\n---\n\n## 2. `add_to_cart` — reflect a natural-language addition\n\nCalled when the diner says *\"add two margheritas\"* — the model fills `item` and `quantity` from language. The cart is session-local in the widget; this tool echoes the resolved selection so the model can speak it back.\n\n**Request**\n```json\n{\n \"customer\": \"Guest\",\n \"item\": \"stone_pizza\",\n \"quantity\": 2,\n \"notes\": \"\"\n}\n```\n\n**Response**\n```json\n{\n \"status\": \"Added 2 × stone_pizza for Guest.\",\n \"item\": \"stone_pizza\",\n \"quantity\": 2,\n \"notes\": \"\"\n}\n```\n\n**Notes.**\n- `quantity` is an integer ≥ 1 (defaults to 1). `item` must be one of the five menu IDs; reject unknown IDs.\n- `notes` is a free-text per-item request (\"no basil\"); optional, defaults to empty.\n- **If Acme makes this server-authoritative** (rather than widget-local), return the updated line and a running subtotal so the frontend can render without a second call — e.g. add `line_total` and `cart_subtotal`. For v1 the widget owns the running total, so the minimal echo above is sufficient.\n\n---\n\n## 3. `remove_from_cart` — remove one unit\n\nCalled by the widget's `−` button or by language (\"drop a margherita\"). Removes one unit of the item.\n\n**Request**\n```json\n{\n \"customer\": \"Guest\",\n \"item\": \"stone_pizza\"\n}\n```\n\n**Response**\n```json\n{\n \"status\": \"Removed stone_pizza for Guest.\",\n \"item\": \"stone_pizza\"\n}\n```\n\n**Notes.**\n- Removing decrements by one; the widget deletes the line when its quantity reaches zero.\n- No error if the item isn't in the cart — the operation is idempotent from the model's view (the widget guards the `−` button when quantity is 0).\n\n---\n\n## 4. `create_checkout` — mint the signed payment link\n\nThe one handoff. The widget computes the total (live React) and passes a url-safe cart token plus the numeric total; the tool returns a **signed, expiring** deep link to Acme's PCI-scoped checkout. **No card data is exchanged here** — the diner enters their card on `pay.acme.example`.\n\n**Request**\n```json\n{\n \"customer\": \"Guest\",\n \"cartToken\": \"stone_pizzax2-lemon_tartx1-sparklingx1\",\n \"total\": 40\n}\n```\n\n**Response**\n```json\n{\n \"status\": \"Ready to pay for Guest's order.\",\n \"summary\": \"Guest's Acme Bistro order · 40 USD\",\n \"checkoutUrl\": \"https://pay.acme.example/checkout?cart=stone_pizzax2-lemon_tartx1-sparklingx1&total=40&src=chatgpt\",\n \"expires_at\": \"2026-07-09T18:15:00-07:00\"\n}\n```\n\n**Notes.**\n- **`checkoutUrl` must be signed server-side.** The `cart` and `total` query params are a convenience for rehydration and display — Acme's checkout must **recompute pricing from the cart token and enforce its own total**, never trusting the client-supplied `total`. Treat the incoming `total` as a display hint to reconcile, not as the charge amount.\n- **`expires_at`** bounds the link (proposed 15-minute window). An expired link should land on a \"cart expired — start again\" page, not charge a stale total. The runnable app returns `status`, `summary`, and `checkoutUrl`; adding `expires_at` is the recommended production extension so the model can tell the diner how long the link is good for.\n- **`src=chatgpt`** is the attribution parameter — carry it through to Acme's order record so ChatGPT-sourced revenue is measurable against the web channel.\n- **Cart token format.** The app emits a human-readable `<id>x<qty>-<id>x<qty>` token. For production, consider an **opaque server-minted token** (the client passes a cart handle; Acme resolves it to the authoritative lines) to remove any incentive to tamper with the token or `total` before re-validation.\n- **`handoff.allowedDomains`** in the server (`https://pay.acme.example`, `https://acme.example`) is what lets the compiler derive the ChatGPT redirect domain, so the link opens without a safe-link warning. Any new payment domain must be added there.\n\n---\n\n## Validation & ownership summary\n\nThe backend must own and enforce:\n\n1. **Pricing** — the authoritative per-item price and the order total; the widget sum is display-only.\n2. **Inventory** — item availability at menu-read and at checkout; a sold-out item should not reach a paid order.\n3. **Payment** — all card capture on `pay.acme.example`, inside Acme's PCI scope. The MCP server is never in the payment path.\n4. **Link integrity** — server-side signing of `checkoutUrl`, an enforced `expires_at`, and recomputation of the total from the cart token before charging.\n\nEverything before payment — menu, cart, total, and minting the link — is the ChatGPT App's job. Everything at and after payment is Acme's.\n\n---\n\n## Open questions for Acme engineering\n\n1. **Cart token shape** — keep the readable `idxN-idxN` form, or move to an opaque server handle to prevent client-side tampering?\n2. **Signing scheme & expiry** — HMAC, JWT, or signed query params, and what default expiry window (proposed 15 min)?\n3. **Currency & precision** — stay whole-dollar USD, or introduce cents / a `currency` field? The widget and checkout total must agree.\n4. **Server-authoritative cart** — should `add_to_cart` / `remove_from_cart` become backend-owned (returning subtotals), or stay widget-local for v1?\n5. **Post-payment visibility** — expose a webhook or polling endpoint so a later chat turn can confirm order status? Out of scope for v1.\n" },
22
22
  { relPath: "examples/acme-bistro/design/wireframe.html", content: "<!DOCTYPE html>\n<html lang=\"en\">\n<head>\n<meta charset=\"UTF-8\">\n<meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\">\n<title>Acme Bistro × ChatGPT — End-to-End Wireframes</title>\n<style>\n @import url('https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700;800&family=JetBrains+Mono:wght@400;600&display=swap');\n * { margin: 0; padding: 0; box-sizing: border-box; }\n body { font-family: 'Inter', -apple-system, sans-serif; background: #f4f5f7; color: #1a1211; line-height: 1.55; }\n\n /* ── Acme Bistro brand tokens (from server branding) ── */\n :root {\n --acme-red: #B91C1C;\n --acme-red-deep: #991B1B;\n --acme-red-soft: #FEF3F2;\n --acme-red-border: #FBD5D2;\n --acme-dark: #1A1211;\n --green: #15803D; --green-soft: #F0FDF4; --green-border: #BBF7D0;\n --amber: #B45309; --amber-soft: #FFFBEB; --amber-border: #FDE68A;\n }\n\n /* ── Page Header ── */\n .page-header { background: #fff; border-bottom: 1px solid #e0dddb; padding: 30px 48px; position: sticky; top: 0; z-index: 100; }\n .page-header h1 { font-size: 22px; font-weight: 800; letter-spacing: -0.4px; }\n .page-header h1 .brand { color: var(--acme-red); }\n .page-header p { font-size: 13px; color: #8a8580; margin-top: 4px; }\n .page-header .scope { display: inline-block; margin-top: 10px; font-size: 11px; font-weight: 700; letter-spacing: 0.5px; padding: 5px 13px; background: var(--acme-dark); color: #fff; border-radius: 5px; }\n .page-header .scope b { color: var(--acme-red-border); }\n\n /* ── Section Nav ── */\n .section-nav { background: #fff; border-bottom: 1px solid #eee; padding: 11px 48px; display: flex; gap: 22px; font-size: 12px; font-weight: 600; position: sticky; top: 92px; z-index: 99; }\n .section-nav a { color: #8a8580; text-decoration: none; }\n .section-nav a:hover { color: var(--acme-red); }\n\n .container { max-width: 1440px; margin: 0 auto; padding: 36px 48px 80px; }\n\n /* ── Legend ── */\n .vocab { display: flex; gap: 16px; flex-wrap: wrap; margin: 0 0 20px; padding: 14px 18px; background: #fff; border: 1px solid #e6e3e0; border-radius: 12px; font-size: 12px; color: #555; }\n .vocab-item { display: flex; align-items: center; gap: 8px; }\n .vocab-sw { width: 16px; height: 16px; border-radius: 4px; border: 1px solid rgba(0,0,0,0.08); }\n .sw-red { background: var(--acme-red); } .sw-green { background: var(--green); }\n .sw-amber { background: var(--amber); } .sw-dark { background: var(--acme-dark); }\n .sw-grey { background: #cfcac5; } .sw-dash { background: repeating-linear-gradient(45deg,#fff,#fff 3px,#cfcac5 3px,#cfcac5 5px); }\n\n /* ── Section ── */\n .section { margin-bottom: 56px; }\n .section-label { font-size: 11px; font-weight: 700; letter-spacing: 1.5px; text-transform: uppercase; color: #a39d97; margin-bottom: 8px; display: block; }\n .section-title { font-size: 27px; font-weight: 800; letter-spacing: -0.5px; margin-bottom: 6px; }\n .section-subtitle { font-size: 14px; color: #6b655f; margin-bottom: 22px; max-width: 820px; }\n\n /* ── Rationale Block ── */\n .rationale { background: #fff; border: 1px solid #e6e3e0; border-left: 3px solid var(--acme-red); border-radius: 10px; padding: 16px 20px; margin-bottom: 22px; max-width: 960px; }\n .rationale h4 { font-size: 12px; font-weight: 700; text-transform: uppercase; letter-spacing: 0.8px; color: #a39d97; margin-bottom: 9px; }\n .rationale p { font-size: 13px; color: #46413c; line-height: 1.65; margin-bottom: 8px; }\n .rationale p:last-child { margin-bottom: 0; }\n .r-tag { display: inline-block; font-size: 10px; font-weight: 700; padding: 2px 8px; border-radius: 4px; margin-right: 4px; letter-spacing: 0.3px; }\n .r-tag.ux { background: #EEF2FF; color: #4338CA; }\n .r-tag.ui { background: #ECFEFF; color: #0E7490; }\n .r-tag.acme { background: var(--acme-red-soft); color: var(--acme-red-deep); }\n .r-tag.trust { background: var(--green-soft); color: var(--green); }\n code { background: #f1efec; padding: 1px 5px; border-radius: 3px; font-size: 11px; font-family: 'JetBrains Mono', monospace; }\n\n /* ── Phone Row ── */\n .phones-row { display: flex; gap: 24px; overflow-x: auto; padding-bottom: 12px; align-items: flex-start; }\n .phone-step { flex-shrink: 0; display: flex; flex-direction: column; align-items: center; }\n .step-label { font-size: 11px; font-weight: 700; color: #8a8580; text-transform: uppercase; letter-spacing: 0.8px; margin-bottom: 12px; text-align: center; max-width: 300px; }\n .step-label small { display: block; font-weight: 400; letter-spacing: 0; text-transform: none; color: #b0aaa4; margin-top: 3px; }\n .phone { width: 300px; min-height: 600px; background: #fff; border: 2px solid var(--acme-dark); border-radius: 30px; overflow: hidden; display: flex; flex-direction: column; }\n .phone.offapp { border: 2px dashed #b0aaa4; }\n .phone-notch { width: 90px; height: 22px; background: var(--acme-dark); border-radius: 0 0 12px 12px; margin: 0 auto; flex-shrink: 0; }\n .phone.offapp .phone-notch { background: #b0aaa4; }\n .phone-screen { padding: 14px; display: flex; flex-direction: column; gap: 10px; flex: 1; }\n .step-arrow { display: flex; align-items: center; justify-content: center; flex-shrink: 0; align-self: center; width: 32px; font-size: 22px; color: #cfcac5; padding-top: 260px; }\n\n /* ── Chrome ── */\n .chatgpt-header { display: flex; align-items: center; justify-content: space-between; padding: 6px 0 9px; border-bottom: 1px solid #eee; }\n .chatgpt-header .model-name { font-size: 13px; font-weight: 600; }\n .chatgpt-header .dots { font-size: 17px; color: #b0aaa4; letter-spacing: 2px; }\n .browser-header { display: flex; align-items: center; gap: 7px; padding: 7px 9px; background: #f1efec; border-radius: 8px; font-size: 10px; color: #6b655f; }\n .browser-header .lock { font-size: 10px; }\n .browser-header .url { font-family: 'JetBrains Mono', monospace; font-size: 9.5px; color: #46413c; overflow: hidden; text-overflow: ellipsis; white-space: nowrap; }\n\n /* ── Messages ── */\n .msg { max-width: 92%; font-size: 12.5px; line-height: 1.55; }\n .msg.user { align-self: flex-end; background: var(--acme-dark); color: #fff; padding: 9px 13px; border-radius: 16px 16px 4px 16px; margin-left: auto; }\n .msg.assistant { color: #1a1211; padding: 2px 0; }\n .msg.assistant strong { font-weight: 600; }\n\n /* ── Tool Call ── */\n .tool-call { display: flex; align-items: center; gap: 8px; padding: 7px 11px; background: #faf8f6; border: 1px solid #e6e3e0; border-radius: 9px; font-size: 10.5px; color: #6b655f; }\n .tool-call .icon { width: 19px; height: 19px; background: var(--acme-red); border-radius: 5px; display: flex; align-items: center; justify-content: center; flex-shrink: 0; }\n .tool-call .icon svg { width: 12px; height: 12px; stroke: #fff; fill: none; stroke-width: 2; }\n .tool-call .label { font-weight: 700; color: var(--acme-dark); font-family: 'JetBrains Mono', monospace; font-size: 10px; }\n .tool-call .mono-tool { font-family: 'JetBrains Mono', monospace; font-size: 9.5px; color: #8a8580; }\n\n /* ── MenuCart widget ── */\n .wcard { border: 1.5px solid var(--acme-red-border); border-radius: 14px; overflow: hidden; background: #fff; }\n .wcard-head { display: flex; align-items: center; gap: 9px; padding: 11px 13px; background: var(--acme-red-soft); border-bottom: 1px solid var(--acme-red-border); }\n .wcard-head .logo { width: 26px; height: 26px; border-radius: 7px; background: var(--acme-red); display: flex; align-items: center; justify-content: center; flex-shrink: 0; }\n .wcard-head .logo svg { width: 15px; height: 15px; stroke: #fff; fill: none; stroke-width: 1.7; }\n .wc-title { font-size: 13px; font-weight: 800; }\n .wc-status { font-size: 10px; color: #8a8580; margin-top: 1px; line-height: 1.35; }\n .wc-chip { margin-left: auto; font-size: 9.5px; font-weight: 700; padding: 3px 8px; background: #fff; border: 1px solid var(--acme-red-border); color: var(--acme-red-deep); border-radius: 20px; white-space: nowrap; }\n .menu-row { display: flex; align-items: center; gap: 8px; padding: 9px 13px; border-bottom: 1px solid #f4f2ef; }\n .mr-main { flex: 1; }\n .mr-name { font-size: 12px; font-weight: 600; }\n .mr-kind { font-size: 9.5px; color: #a39d97; text-transform: uppercase; letter-spacing: 0.4px; }\n .mr-price { font-size: 12px; font-weight: 700; color: #46413c; }\n .mr-qty { display: flex; align-items: center; gap: 7px; }\n .step-btn { width: 20px; height: 20px; border: 1px solid #d8d3ce; border-radius: 6px; display: flex; align-items: center; justify-content: center; font-size: 12px; color: #46413c; background: #fff; }\n .step-btn.on { border-color: var(--acme-red); color: var(--acme-red); }\n .step-btn.dis { opacity: 0.3; }\n .mr-count { font-size: 12px; font-weight: 700; min-width: 12px; text-align: center; }\n .wc-foot { display: flex; align-items: center; gap: 10px; padding: 12px 13px 8px; }\n .wc-total { font-size: 13px; color: #46413c; }\n .wc-total strong { font-size: 16px; font-weight: 800; color: var(--acme-dark); margin-left: 4px; }\n .wc-cta { margin-left: auto; display: inline-flex; align-items: center; gap: 6px; padding: 9px 15px; background: var(--acme-red); color: #fff; border: none; border-radius: 10px; font-size: 12px; font-weight: 700; cursor: pointer; }\n .wc-cta svg { width: 14px; height: 14px; stroke: #fff; fill: none; stroke-width: 2; }\n .wc-cta.dis { opacity: 0.4; }\n .wc-note { padding: 0 13px 12px; font-size: 9.5px; color: #a39d97; line-height: 1.45; }\n .wc-note b { color: var(--green); }\n\n /* ── Handoff card ── */\n .handoff-card { border: 1.5px solid var(--acme-red-border); border-radius: 14px; background: #fff; text-align: center; padding: 16px 15px 13px; }\n .handoff-card .glyph { width: 42px; height: 42px; margin: 0 auto 8px; border-radius: 11px; background: var(--acme-red-soft); display: flex; align-items: center; justify-content: center; }\n .handoff-card .glyph svg { width: 22px; height: 22px; stroke: var(--acme-red); fill: none; stroke-width: 1.6; }\n .handoff-card h4 { font-size: 13.5px; font-weight: 800; margin-bottom: 4px; }\n .handoff-card p { font-size: 11px; color: #6b655f; margin-bottom: 11px; line-height: 1.5; }\n .mini-sum { background: #faf8f6; border: 1px solid #eae7e3; border-radius: 9px; padding: 9px 11px; margin: 0 0 11px; text-align: left; }\n .mini-sum .row { display: flex; justify-content: space-between; font-size: 11px; color: #6b655f; padding: 2px 0; }\n .mini-sum .row.total { font-size: 12.5px; font-weight: 800; color: var(--acme-dark); border-top: 1px solid #eae7e3; margin-top: 4px; padding-top: 5px; }\n .pay-link { font-size: 9px; color: #a39d97; margin-top: 10px; line-height: 1.55; }\n .pay-link code { font-size: 8.5px; }\n .pay-link b { color: var(--acme-dark); }\n\n .cta-primary { display: inline-flex; align-items: center; justify-content: center; gap: 6px; width: 100%; padding: 10px; background: var(--acme-red); color: #fff; border: none; border-radius: 10px; font-size: 12.5px; font-weight: 700; cursor: pointer; margin-bottom: 6px; }\n .cta-ghost { display: block; width: 100%; padding: 9px; background: transparent; color: var(--acme-dark); border: 1.5px solid #d8d3ce; border-radius: 10px; font-size: 12px; font-weight: 600; cursor: pointer; }\n\n /* ── Off-app checkout body ── */\n .checkout-body { flex: 1; display: flex; flex-direction: column; gap: 9px; padding-top: 4px; }\n .co-brand { font-size: 14px; font-weight: 800; color: var(--acme-red); }\n .co-sub { font-size: 10px; color: #8a8580; }\n .co-field { border: 1px solid #e6e3e0; border-radius: 9px; padding: 9px 11px; }\n .co-field .lbl { font-size: 9px; color: #a39d97; text-transform: uppercase; letter-spacing: 0.5px; }\n .co-field .val { font-size: 12px; color: #46413c; margin-top: 3px; font-family: 'JetBrains Mono', monospace; }\n .co-field.card { background: var(--amber-soft); border-color: var(--amber-border); }\n .co-line { display: flex; justify-content: space-between; font-size: 11px; color: #6b655f; padding: 2px 0; }\n .co-line.total { font-weight: 800; color: var(--acme-dark); font-size: 13px; border-top: 1px solid #eee; padding-top: 5px; margin-top: 3px; }\n .co-pay { padding: 11px; background: var(--acme-red); color: #fff; border: none; border-radius: 10px; font-size: 13px; font-weight: 700; text-align: center; margin-top: auto; }\n .co-secure { font-size: 9.5px; color: #a39d97; text-align: center; margin-top: 7px; }\n\n /* ── Composer ── */\n .composer { margin-top: auto; padding: 9px 0 2px; border-top: 1px solid #eee; }\n .composer-bar { display: flex; align-items: center; background: #f1efec; border-radius: 20px; padding: 8px 12px; font-size: 11.5px; color: #a39d97; }\n .composer-bar .send { width: 24px; height: 24px; background: var(--acme-dark); border-radius: 50%; margin-left: auto; display: flex; align-items: center; justify-content: center; color: #fff; font-size: 12px; }\n\n /* ── Widget Gallery ── */\n .gallery { display: grid; grid-template-columns: repeat(auto-fill, minmax(300px,1fr)); gap: 22px; }\n .sf { }\n .sf-name { font-size: 12px; font-weight: 700; margin-bottom: 8px; color: #46413c; }\n .sf-name span { font-weight: 400; color: #a39d97; }\n\n /* ── API appendix ── */\n .api-panel { background: #fff; border: 1px solid #e6e3e0; border-radius: 12px; overflow: hidden; margin-bottom: 18px; }\n .api-panel-header { background: var(--acme-dark); color: #fff; padding: 12px 18px; font-size: 13px; font-weight: 700; }\n .api-step { padding: 14px 18px; border-bottom: 1px solid #f1efec; }\n .api-step:last-child { border-bottom: none; }\n .api-step-label { font-size: 10.5px; font-weight: 700; color: #a39d97; text-transform: uppercase; letter-spacing: 1px; margin-bottom: 7px; }\n .api-endpoint { background: #faf8f6; border: 1px solid #eae7e3; border-radius: 8px; padding: 9px 12px; margin-bottom: 7px; }\n .api-endpoint .kind { display: inline-block; font-size: 9px; font-weight: 700; padding: 2px 6px; border-radius: 3px; margin-right: 6px; letter-spacing: 0.4px; font-family: 'JetBrains Mono', monospace; }\n .kind.read { background: var(--green-soft); color: var(--green); }\n .kind.write { background: #ECFEFF; color: #0E7490; }\n .kind.link { background: var(--acme-red-soft); color: var(--acme-red-deep); }\n .api-endpoint .path { font-size: 12.5px; font-weight: 700; color: var(--acme-dark); font-family: 'JetBrains Mono', monospace; }\n .api-endpoint .desc { font-size: 11px; color: #8a8580; margin-top: 3px; }\n .api-note { font-size: 11px; color: #5f594f; background: var(--amber-soft); border-left: 3px solid var(--amber-border); padding: 8px 12px; border-radius: 0 6px 6px 0; margin-top: 6px; }\n .api-note strong { color: #46413c; }\n\n /* ── Audit table ── */\n .audit-table { width: 100%; border-collapse: collapse; font-size: 12px; margin-top: 14px; }\n .audit-table th { text-align: left; padding: 9px 13px; background: #faf8f6; font-weight: 700; font-size: 10.5px; text-transform: uppercase; letter-spacing: 0.5px; color: #a39d97; border-bottom: 1px solid #e6e3e0; }\n .audit-table td { padding: 9px 13px; border-bottom: 1px solid #f1efec; vertical-align: top; color: #46413c; }\n .audit-table td:first-child { font-weight: 600; color: #2d2825; }\n .audit-pass { color: var(--green); font-weight: 700; white-space: nowrap; }\n .audit-guard td:first-child { color: var(--acme-red-deep); }\n\n .page-divider { border: none; border-top: 2px solid #e6e3e0; margin: 48px 0; }\n .footer { text-align: center; font-size: 11px; color: #b0aaa4; padding: 24px 0 8px; }\n</style>\n</head>\n<body>\n\n<div class=\"page-header\">\n <h1><span class=\"brand\">Acme Bistro</span> × ChatGPT App — End-to-End Wireframes</h1>\n <p>Prepared by Noodle Seed · Browse → Build order → Confirm → Hand off to pay · Single-restaurant storefront</p>\n <span class=\"scope\">FUNNEL BOUNDARY: menu, order &amp; confirmation IN CHATGPT · <b>PAYMENT ONLY OFF-APP</b> (pay.acme.example) · no per-user auth</span>\n</div>\n\n<div class=\"section-nav\">\n <a href=\"#legend\">Legend</a>\n <a href=\"#flow\">End-to-End Flow</a>\n <a href=\"#build\">Build &amp; Total</a>\n <a href=\"#handoff\">Payment Handoff</a>\n <a href=\"#gallery\">Widget Gallery</a>\n <a href=\"#api\">MCP Tools</a>\n <a href=\"#compliance\">Compliance Audit</a>\n</div>\n\n<div class=\"container\">\n\n <!-- ── LEGEND ── -->\n <div class=\"section\" id=\"legend\">\n <div class=\"vocab\">\n <div class=\"vocab-item\"><div class=\"vocab-sw sw-red\"></div><strong>Acme Red</strong> — primary CTA + logo mark only</div>\n <div class=\"vocab-item\"><div class=\"vocab-sw sw-green\"></div><strong>Green</strong> — trust / \"card never in chat\"</div>\n <div class=\"vocab-item\"><div class=\"vocab-sw sw-amber\"></div><strong>Amber</strong> — off-app payment surface</div>\n <div class=\"vocab-item\"><div class=\"vocab-sw sw-dark\"></div><strong>Dark</strong> — text, user bubbles</div>\n <div class=\"vocab-item\"><div class=\"vocab-sw sw-grey\"></div><strong>Grey</strong> — neutral / host UI</div>\n <div class=\"vocab-item\"><div class=\"vocab-sw sw-dash\"></div><strong>Dashed frame</strong> — off-app destination</div>\n </div>\n <div class=\"rationale\">\n <h4>How to read these wireframes</h4>\n <p><span class=\"r-tag ui\">UI</span> <strong>Solid-border phones are the ChatGPT App</strong> (the Noodle Seed <code>MenuCart</code> widget rendered inline). <strong>Dashed-border phones are off-app</strong> — reached only after the payment hand-off, on Acme's own checkout. Every widget is preceded by its <code>tool-call</code> chip so you can see exactly which tool the model invoked.</p>\n <p><span class=\"r-tag trust\">TRUST</span> <strong>The app never guesses and never touches a card.</strong> Menu, prices, and totals are grounded in the <code>show_menu</code> data; the diner's card is entered only on the amber off-app checkout. This is the whole safety story of the app, and it is visible in the pixels.</p>\n </div>\n </div>\n\n <!-- ═══ SECTION 1: END-TO-END FLOW ═══ -->\n <div class=\"section\" id=\"flow\">\n <span class=\"section-label\">The whole journey</span>\n <div class=\"section-title\">One conversation, from craving to a paid-ready cart</div>\n <div class=\"section-subtitle\">A diner names Acme and their order in plain language; the model renders the menu, reflects the order into a live cart, confirms the total, and mints a signed payment link. Only the final step — entering a card — leaves ChatGPT.</div>\n\n <div class=\"phones-row\">\n\n <!-- Step 1: Menu -->\n <div class=\"phone-step\">\n <div class=\"step-label\">1 · Show the menu<small>show_menu → MenuCart</small></div>\n <div class=\"phone\"><div class=\"phone-notch\"></div><div class=\"phone-screen\">\n <div class=\"chatgpt-header\"><span class=\"model-name\">ChatGPT</span><span class=\"dots\">···</span></div>\n <div class=\"msg user\">Order me two margheritas and a lemon tart from Acme Bistro.</div>\n <div class=\"tool-call\"><span class=\"icon\"><svg viewBox=\"0 0 24 24\"><circle cx=\"12\" cy=\"12\" r=\"9\"/><circle cx=\"12\" cy=\"12\" r=\"4\"/></svg></span><span><span class=\"label\">show_menu</span> <span class=\"mono-tool\">{customer:\"Guest\"}</span></span></div>\n <div class=\"msg assistant\">Here's your Acme Bistro order — building it now:</div>\n <div class=\"wcard\">\n <div class=\"wcard-head\">\n <span class=\"logo\"><svg viewBox=\"0 0 24 24\"><circle cx=\"12\" cy=\"12\" r=\"9\"/><circle cx=\"12\" cy=\"12\" r=\"4\"/></svg></span>\n <div><div class=\"wc-title\">Acme Bistro</div><div class=\"wc-status\">Menu ready. Build the order here; pay at checkout.</div></div>\n <span class=\"wc-chip\">0 in cart</span>\n </div>\n <div class=\"menu-row\"><span class=\"mr-main\"><span class=\"mr-name\">Stone-baked Margherita</span> <span class=\"mr-kind\">Mains</span></span><span class=\"mr-price\">$14</span><span class=\"mr-qty\"><span class=\"step-btn dis\">−</span><span class=\"mr-count\">0</span><span class=\"step-btn\">+</span></span></div>\n <div class=\"menu-row\"><span class=\"mr-main\"><span class=\"mr-name\">Harvest Roast Bowl</span> <span class=\"mr-kind\">Mains</span></span><span class=\"mr-price\">$13</span><span class=\"mr-qty\"><span class=\"step-btn dis\">−</span><span class=\"mr-count\">0</span><span class=\"step-btn\">+</span></span></div>\n <div class=\"menu-row\"><span class=\"mr-main\"><span class=\"mr-name\">House Garden Salad</span> <span class=\"mr-kind\">Starters</span></span><span class=\"mr-price\">$11</span><span class=\"mr-qty\"><span class=\"step-btn dis\">−</span><span class=\"mr-count\">0</span><span class=\"step-btn\">+</span></span></div>\n <div class=\"menu-row\"><span class=\"mr-main\"><span class=\"mr-name\">Lemon Tart</span> <span class=\"mr-kind\">Desserts</span></span><span class=\"mr-price\">$8</span><span class=\"mr-qty\"><span class=\"step-btn dis\">−</span><span class=\"mr-count\">0</span><span class=\"step-btn\">+</span></span></div>\n <div class=\"menu-row\"><span class=\"mr-main\"><span class=\"mr-name\">Sparkling Water</span> <span class=\"mr-kind\">Drinks</span></span><span class=\"mr-price\">$4</span><span class=\"mr-qty\"><span class=\"step-btn dis\">−</span><span class=\"mr-count\">0</span><span class=\"step-btn\">+</span></span></div>\n <div class=\"wc-foot\"><span class=\"wc-total\">Total <strong>$0</strong></span><button class=\"wc-cta dis\"><svg viewBox=\"0 0 24 24\"><rect x=\"3\" y=\"5\" width=\"18\" height=\"14\" rx=\"2\"/><path d=\"M3 10h18\"/></svg>Check out &amp; pay</button></div>\n <div class=\"wc-note\">Payment happens on acme.example — <b>your card is never entered in chat.</b></div>\n </div>\n <div class=\"composer\"><div class=\"composer-bar\">Message<span class=\"send\">↑</span></div></div>\n </div></div>\n </div>\n <div class=\"step-arrow\">→</div>\n\n <!-- Step 2: NL order reflected -->\n <div class=\"phone-step\">\n <div class=\"step-label\">2 · Parse the order<small>add_to_cart ×2 from language</small></div>\n <div class=\"phone\"><div class=\"phone-notch\"></div><div class=\"phone-screen\">\n <div class=\"chatgpt-header\"><span class=\"model-name\">ChatGPT</span><span class=\"dots\">···</span></div>\n <div class=\"tool-call\"><span class=\"icon\"><svg viewBox=\"0 0 24 24\"><path d=\"M12 5v14M5 12h14\"/></svg></span><span><span class=\"label\">add_to_cart</span> <span class=\"mono-tool\">{item:\"stone_pizza\", quantity:2}</span></span></div>\n <div class=\"tool-call\"><span class=\"icon\"><svg viewBox=\"0 0 24 24\"><path d=\"M12 5v14M5 12h14\"/></svg></span><span><span class=\"label\">add_to_cart</span> <span class=\"mono-tool\">{item:\"lemon_tart\", quantity:1}</span></span></div>\n <div class=\"msg assistant\">Two Stone-baked Margheritas and a Lemon Tart — <strong>$36</strong> so far. Want a drink or a side, or shall I take you to checkout?</div>\n <div class=\"wcard\">\n <div class=\"wcard-head\">\n <span class=\"logo\"><svg viewBox=\"0 0 24 24\"><circle cx=\"12\" cy=\"12\" r=\"9\"/><circle cx=\"12\" cy=\"12\" r=\"4\"/></svg></span>\n <div><div class=\"wc-title\">Acme Bistro</div><div class=\"wc-status\">Added 2 × Stone-baked Margherita.</div></div>\n <span class=\"wc-chip\">3 in cart</span>\n </div>\n <div class=\"menu-row\"><span class=\"mr-main\"><span class=\"mr-name\">Stone-baked Margherita</span> <span class=\"mr-kind\">Mains</span></span><span class=\"mr-price\">$14</span><span class=\"mr-qty\"><span class=\"step-btn on\">−</span><span class=\"mr-count\">2</span><span class=\"step-btn\">+</span></span></div>\n <div class=\"menu-row\"><span class=\"mr-main\"><span class=\"mr-name\">Harvest Roast Bowl</span> <span class=\"mr-kind\">Mains</span></span><span class=\"mr-price\">$13</span><span class=\"mr-qty\"><span class=\"step-btn dis\">−</span><span class=\"mr-count\">0</span><span class=\"step-btn\">+</span></span></div>\n <div class=\"menu-row\"><span class=\"mr-main\"><span class=\"mr-name\">House Garden Salad</span> <span class=\"mr-kind\">Starters</span></span><span class=\"mr-price\">$11</span><span class=\"mr-qty\"><span class=\"step-btn dis\">−</span><span class=\"mr-count\">0</span><span class=\"step-btn\">+</span></span></div>\n <div class=\"menu-row\"><span class=\"mr-main\"><span class=\"mr-name\">Lemon Tart</span> <span class=\"mr-kind\">Desserts</span></span><span class=\"mr-price\">$8</span><span class=\"mr-qty\"><span class=\"step-btn on\">−</span><span class=\"mr-count\">1</span><span class=\"step-btn\">+</span></span></div>\n <div class=\"menu-row\"><span class=\"mr-main\"><span class=\"mr-name\">Sparkling Water</span> <span class=\"mr-kind\">Drinks</span></span><span class=\"mr-price\">$4</span><span class=\"mr-qty\"><span class=\"step-btn dis\">−</span><span class=\"mr-count\">0</span><span class=\"step-btn\">+</span></span></div>\n <div class=\"wc-foot\"><span class=\"wc-total\">Total <strong>$36</strong></span><button class=\"wc-cta\"><svg viewBox=\"0 0 24 24\"><rect x=\"3\" y=\"5\" width=\"18\" height=\"14\" rx=\"2\"/><path d=\"M3 10h18\"/></svg>Check out &amp; pay</button></div>\n <div class=\"wc-note\">Payment happens on acme.example — <b>your card is never entered in chat.</b></div>\n </div>\n <div class=\"composer\"><div class=\"composer-bar\">\"add a sparkling water\"<span class=\"send\">↑</span></div></div>\n </div></div>\n </div>\n <div class=\"step-arrow\">→</div>\n\n <!-- Step 3: Edit + confirm total -->\n <div class=\"phone-step\">\n <div class=\"step-label\">3 · Edit &amp; confirm total<small>add / remove · live sum</small></div>\n <div class=\"phone\"><div class=\"phone-notch\"></div><div class=\"phone-screen\">\n <div class=\"chatgpt-header\"><span class=\"model-name\">ChatGPT</span><span class=\"dots\">···</span></div>\n <div class=\"msg user\">Add a sparkling water too.</div>\n <div class=\"tool-call\"><span class=\"icon\"><svg viewBox=\"0 0 24 24\"><path d=\"M12 5v14M5 12h14\"/></svg></span><span><span class=\"label\">add_to_cart</span> <span class=\"mono-tool\">{item:\"sparkling\", quantity:1}</span></span></div>\n <div class=\"msg assistant\">Added a Sparkling Water — your total is <strong>$40</strong> for four items. Ready to pay whenever you are.</div>\n <div class=\"wcard\">\n <div class=\"wcard-head\">\n <span class=\"logo\"><svg viewBox=\"0 0 24 24\"><circle cx=\"12\" cy=\"12\" r=\"9\"/><circle cx=\"12\" cy=\"12\" r=\"4\"/></svg></span>\n <div><div class=\"wc-title\">Acme Bistro</div><div class=\"wc-status\">Added Sparkling Water.</div></div>\n <span class=\"wc-chip\">4 in cart</span>\n </div>\n <div class=\"menu-row\"><span class=\"mr-main\"><span class=\"mr-name\">Stone-baked Margherita</span> <span class=\"mr-kind\">Mains</span></span><span class=\"mr-price\">$14</span><span class=\"mr-qty\"><span class=\"step-btn on\">−</span><span class=\"mr-count\">2</span><span class=\"step-btn\">+</span></span></div>\n <div class=\"menu-row\"><span class=\"mr-main\"><span class=\"mr-name\">Lemon Tart</span> <span class=\"mr-kind\">Desserts</span></span><span class=\"mr-price\">$8</span><span class=\"mr-qty\"><span class=\"step-btn on\">−</span><span class=\"mr-count\">1</span><span class=\"step-btn\">+</span></span></div>\n <div class=\"menu-row\"><span class=\"mr-main\"><span class=\"mr-name\">Sparkling Water</span> <span class=\"mr-kind\">Drinks</span></span><span class=\"mr-price\">$4</span><span class=\"mr-qty\"><span class=\"step-btn on\">−</span><span class=\"mr-count\">1</span><span class=\"step-btn\">+</span></span></div>\n <div class=\"wc-foot\"><span class=\"wc-total\">Total <strong>$40</strong></span><button class=\"wc-cta\"><svg viewBox=\"0 0 24 24\"><rect x=\"3\" y=\"5\" width=\"18\" height=\"14\" rx=\"2\"/><path d=\"M3 10h18\"/></svg>Check out &amp; pay</button></div>\n <div class=\"wc-note\">Payment happens on acme.example — <b>your card is never entered in chat.</b></div>\n </div>\n <div class=\"composer\"><div class=\"composer-bar\">\"check out and pay\"<span class=\"send\">↑</span></div></div>\n </div></div>\n </div>\n <div class=\"step-arrow\">→</div>\n\n <!-- Step 4: Checkout handoff card -->\n <div class=\"phone-step\">\n <div class=\"step-label\">4 · Mint the payment link<small>create_checkout (in-chat)</small></div>\n <div class=\"phone\"><div class=\"phone-notch\"></div><div class=\"phone-screen\">\n <div class=\"chatgpt-header\"><span class=\"model-name\">ChatGPT</span><span class=\"dots\">···</span></div>\n <div class=\"msg user\">Check out and pay.</div>\n <div class=\"tool-call\"><span class=\"icon\"><svg viewBox=\"0 0 24 24\"><rect x=\"3\" y=\"5\" width=\"18\" height=\"14\" rx=\"2\"/><path d=\"M3 10h18\"/></svg></span><span><span class=\"label\">create_checkout</span> <span class=\"mono-tool\">{total:40, cartToken:\"…\"}</span></span></div>\n <div class=\"msg assistant\">Your order's ready — I've opened Acme's secure checkout to take payment:</div>\n <div class=\"handoff-card\">\n <div class=\"glyph\"><svg viewBox=\"0 0 24 24\"><rect x=\"3\" y=\"5\" width=\"18\" height=\"14\" rx=\"2\"/><path d=\"M3 10h18\"/></svg></div>\n <h4>Pay on Acme Bistro checkout</h4>\n <p>Your order is staged and ready. Enter your card on <strong>acme.example</strong> — it's never typed in chat.</p>\n <div class=\"mini-sum\">\n <div class=\"row\"><span>2 × Stone-baked Margherita</span><span>$28</span></div>\n <div class=\"row\"><span>1 × Lemon Tart</span><span>$8</span></div>\n <div class=\"row\"><span>1 × Sparkling Water</span><span>$4</span></div>\n <div class=\"row total\"><span>Total</span><span>$40</span></div>\n </div>\n <button class=\"cta-primary\"><svg viewBox=\"0 0 24 24\" style=\"width:14px;height:14px;stroke:#fff;fill:none;stroke-width:2\"><path d=\"M5 12h14M13 6l6 6-6 6\"/></svg>Pay $40 on acme.example ↗</button>\n <button class=\"cta-ghost\">Keep editing</button>\n <div class=\"pay-link\">Opens <code>pay.acme.example/checkout?cart=…&amp;total=40&amp;src=chatgpt</code><br>Signed link · expires in <b>15 min</b> · 🔒 payment handled by Acme</div>\n </div>\n <div class=\"composer\"><div class=\"composer-bar\">Message<span class=\"send\">↑</span></div></div>\n </div></div>\n </div>\n <div class=\"step-arrow\">→</div>\n\n <!-- Step 5: OFF-APP checkout -->\n <div class=\"phone-step\">\n <div class=\"step-label\">5 · Pay (OFF-APP)<small>pay.acme.example · Acme PCI checkout</small></div>\n <div class=\"phone offapp\"><div class=\"phone-notch\"></div><div class=\"phone-screen\">\n <div class=\"browser-header\"><span class=\"lock\">🔒</span><span class=\"url\">pay.acme.example/checkout?cart=…&amp;total=40&amp;src=chatgpt</span></div>\n <div class=\"checkout-body\">\n <div><div class=\"co-brand\">Acme Bistro</div><div class=\"co-sub\">Secure checkout · order from ChatGPT</div></div>\n <div class=\"co-field\"><div class=\"lbl\">Order</div><div class=\"val\" style=\"font-family:'Inter'\">2 Margherita · 1 Lemon Tart · 1 Sparkling</div></div>\n <div class=\"co-field card\"><div class=\"lbl\">Card number</div><div class=\"val\">•••• •••• •••• ____</div></div>\n <div class=\"co-field\"><div class=\"lbl\">Contact (optional)</div><div class=\"val\" style=\"font-family:'Inter'\">name@example.com</div></div>\n <div style=\"padding:2px 2px 0\">\n <div class=\"co-line\"><span>Subtotal</span><span>$40.00</span></div>\n <div class=\"co-line\"><span>Tax (recomputed by Acme)</span><span>$3.30</span></div>\n <div class=\"co-line total\"><span>Total</span><span>$43.30</span></div>\n </div>\n <button class=\"co-pay\">Pay $43.30</button>\n <div class=\"co-secure\">🔒 PCI-scoped · card stays on acme.example · the ChatGPT App never sees it</div>\n </div>\n </div></div>\n </div>\n\n </div>\n </div>\n\n <hr class=\"page-divider\">\n\n <!-- ═══ SECTION 2: BUILD & TOTAL (deep dive) ═══ -->\n <div class=\"section\" id=\"build\">\n <span class=\"section-label\">Capability · Order building</span>\n <div class=\"section-title\">Build the order in language, confirm it in pixels</div>\n <div class=\"section-subtitle\">The whole menu, the cart, the running total, and the pay button live in one inline widget. The diner drives it two ways — by talking to the model or by tapping the steppers — and both land in the same place.</div>\n\n <div class=\"rationale\">\n <h4>Why this approach</h4>\n <p><span class=\"r-tag acme\">ACME</span> <strong>One kitchen, one widget.</strong> A single restaurant with five items doesn't need discovery, carousels, or a fullscreen menu — it needs the fastest path from craving to a confirmed cart. <code>MenuCart</code> collapses menu, cart, and checkout into one card the diner never scrolls out of.</p>\n <p><span class=\"r-tag ux\">UX</span> <strong>Language is the input; the widget is the receipt.</strong> \"Two margheritas and a lemon tart\" parses into two <code>add_to_cart</code> calls — no tapping required — and the widget instantly shows the result so the diner can trust what the model heard. Editing works the same in both directions.</p>\n <p><span class=\"r-tag ui\">UI</span> <strong>Inline Card, brand accent on the CTA only.</strong> Acme red (<code>#B91C1C</code>) appears only on the header mark and the <strong>Check out &amp; pay</strong> button; everything else uses host theme tokens via cascade layers, so the widget is native in ChatGPT light or dark. No nested scroll — five rows fit.</p>\n <p><span class=\"r-tag trust\">TRUST</span> <strong>The total is honest and display-only.</strong> The widget sums line items live, but the amount that charges is recomputed by Acme at checkout. The reassurance line (\"your card is never entered in chat\") is present in every frame, not just the last one.</p>\n </div>\n </div>\n\n <hr class=\"page-divider\">\n\n <!-- ═══ SECTION 3: PAYMENT HANDOFF ═══ -->\n <div class=\"section\" id=\"handoff\">\n <span class=\"section-label\">Capability · The one handoff</span>\n <div class=\"section-title\">Payment is the only step that leaves ChatGPT</div>\n <div class=\"section-subtitle\">When the order is right, <code>create_checkout</code> mints a signed, expiring link carrying the cart token, the total, and an attribution tag. ChatGPT opens Acme's own PCI checkout. The MCP server is never in the payment path.</div>\n\n <div class=\"rationale\">\n <h4>Why this approach</h4>\n <p><span class=\"r-tag trust\">TRUST</span> <strong>The card never touches the app.</strong> No in-chat card field, no wallet, no stored payment method. Keeping capture on <code>pay.acme.example</code> means the ChatGPT surface adds zero PCI scope — the single most important safety property of the design.</p>\n <p><span class=\"r-tag acme\">ACME</span> <strong>The link is signed, expiring, and attributable.</strong> Acme signs the URL server-side, sets an <code>expires_at</code> (proposed 15 min), and carries <code>src=chatgpt</code> so ChatGPT-sourced revenue is measurable. <code>handoff.allowedDomains</code> lists <code>pay.acme.example</code> and <code>acme.example</code> so the compiler derives the redirect domain and the link opens without a safe-link warning.</p>\n <p><span class=\"r-tag ux\">UX</span> <strong>Context survives the jump.</strong> The cart token (<code>stone_pizzax2-lemon_tartx1-sparklingx1</code>) rehydrates the exact order on Acme's checkout — the diner never re-enters what they already told the model. State is re-validated past the boundary: Acme recomputes pricing and tax and enforces its own total.</p>\n </div>\n\n <div class=\"phones-row\">\n <div class=\"phone-step\">\n <div class=\"step-label\">In-chat: the hand-off card<small>CheckoutHandoff · create_checkout</small></div>\n <div class=\"phone\"><div class=\"phone-notch\"></div><div class=\"phone-screen\">\n <div class=\"chatgpt-header\"><span class=\"model-name\">ChatGPT</span><span class=\"dots\">···</span></div>\n <div class=\"msg assistant\">Your $40 order is staged. Tap to pay on Acme's checkout:</div>\n <div class=\"handoff-card\">\n <div class=\"glyph\"><svg viewBox=\"0 0 24 24\"><rect x=\"3\" y=\"5\" width=\"18\" height=\"14\" rx=\"2\"/><path d=\"M3 10h18\"/></svg></div>\n <h4>Pay on Acme Bistro checkout</h4>\n <p>Sign in (if you like) and pay with your card on <strong>acme.example</strong>.</p>\n <div class=\"mini-sum\">\n <div class=\"row\"><span>4 items</span><span>$40</span></div>\n <div class=\"row total\"><span>Pay on acme.example</span><span>$40+tax</span></div>\n </div>\n <button class=\"cta-primary\">Pay $40 on acme.example ↗</button>\n <div class=\"pay-link\">Signed · <b>expires 15 min</b> · <code>src=chatgpt</code></div>\n </div>\n <div class=\"composer\"><div class=\"composer-bar\">Message<span class=\"send\">↑</span></div></div>\n </div></div>\n </div>\n <div class=\"step-arrow\">→</div>\n <div class=\"phone-step\">\n <div class=\"step-label\">Off-app: Acme checkout<small>dashed = not our app</small></div>\n <div class=\"phone offapp\"><div class=\"phone-notch\"></div><div class=\"phone-screen\">\n <div class=\"browser-header\"><span class=\"lock\">🔒</span><span class=\"url\">pay.acme.example/checkout?cart=stone_pizzax2-lemon_tartx1-sparklingx1&amp;total=40&amp;src=chatgpt</span></div>\n <div class=\"checkout-body\">\n <div><div class=\"co-brand\">Acme Bistro</div><div class=\"co-sub\">Secure checkout</div></div>\n <div class=\"co-field\"><div class=\"lbl\">Order (rehydrated from token)</div><div class=\"val\" style=\"font-family:'Inter'\">2 Margherita · 1 Lemon Tart · 1 Sparkling</div></div>\n <div class=\"co-field card\"><div class=\"lbl\">Card number · PCI-scoped</div><div class=\"val\">•••• •••• •••• ____</div></div>\n <div style=\"padding:2px 2px 0\">\n <div class=\"co-line\"><span>Subtotal (re-validated)</span><span>$40.00</span></div>\n <div class=\"co-line\"><span>Tax</span><span>$3.30</span></div>\n <div class=\"co-line total\"><span>Total</span><span>$43.30</span></div>\n </div>\n <button class=\"co-pay\">Pay $43.30</button>\n <div class=\"co-secure\">🔒 card never leaves acme.example · app has no post-handoff visibility in v1</div>\n </div>\n </div></div>\n </div>\n </div>\n </div>\n\n <hr class=\"page-divider\">\n\n <!-- ═══ WIDGET GALLERY ═══ -->\n <div class=\"section\" id=\"gallery\">\n <span class=\"section-label\">Specimen grid</span>\n <div class=\"section-title\">Widget Gallery</div>\n <div class=\"section-subtitle\">Every widget state rendered once at rest. One widget ships: <code>MenuCart</code>. This is what engineers screenshot against the build.</div>\n\n <div class=\"gallery\">\n <div class=\"sf\">\n <div class=\"sf-name\">MenuCart <span>· empty (CTA disabled)</span></div>\n <div class=\"wcard\">\n <div class=\"wcard-head\"><span class=\"logo\"><svg viewBox=\"0 0 24 24\"><circle cx=\"12\" cy=\"12\" r=\"9\"/><circle cx=\"12\" cy=\"12\" r=\"4\"/></svg></span><div><div class=\"wc-title\">Acme Bistro</div><div class=\"wc-status\">Build your order, then check out to pay.</div></div><span class=\"wc-chip\">0 in cart</span></div>\n <div class=\"menu-row\"><span class=\"mr-main\"><span class=\"mr-name\">Stone-baked Margherita</span> <span class=\"mr-kind\">Mains</span></span><span class=\"mr-price\">$14</span><span class=\"mr-qty\"><span class=\"step-btn dis\">−</span><span class=\"mr-count\">0</span><span class=\"step-btn\">+</span></span></div>\n <div class=\"menu-row\"><span class=\"mr-main\"><span class=\"mr-name\">House Garden Salad</span> <span class=\"mr-kind\">Starters</span></span><span class=\"mr-price\">$11</span><span class=\"mr-qty\"><span class=\"step-btn dis\">−</span><span class=\"mr-count\">0</span><span class=\"step-btn\">+</span></span></div>\n <div class=\"wc-foot\"><span class=\"wc-total\">Total <strong>$0</strong></span><button class=\"wc-cta dis\"><svg viewBox=\"0 0 24 24\"><rect x=\"3\" y=\"5\" width=\"18\" height=\"14\" rx=\"2\"/><path d=\"M3 10h18\"/></svg>Check out &amp; pay</button></div>\n <div class=\"wc-note\">Payment happens on acme.example — <b>your card is never entered in chat.</b></div>\n </div>\n </div>\n\n <div class=\"sf\">\n <div class=\"sf-name\">MenuCart <span>· filled ($40, 4 items)</span></div>\n <div class=\"wcard\">\n <div class=\"wcard-head\"><span class=\"logo\"><svg viewBox=\"0 0 24 24\"><circle cx=\"12\" cy=\"12\" r=\"9\"/><circle cx=\"12\" cy=\"12\" r=\"4\"/></svg></span><div><div class=\"wc-title\">Acme Bistro</div><div class=\"wc-status\">Added Sparkling Water.</div></div><span class=\"wc-chip\">4 in cart</span></div>\n <div class=\"menu-row\"><span class=\"mr-main\"><span class=\"mr-name\">Stone-baked Margherita</span> <span class=\"mr-kind\">Mains</span></span><span class=\"mr-price\">$14</span><span class=\"mr-qty\"><span class=\"step-btn on\">−</span><span class=\"mr-count\">2</span><span class=\"step-btn\">+</span></span></div>\n <div class=\"menu-row\"><span class=\"mr-main\"><span class=\"mr-name\">Lemon Tart</span> <span class=\"mr-kind\">Desserts</span></span><span class=\"mr-price\">$8</span><span class=\"mr-qty\"><span class=\"step-btn on\">−</span><span class=\"mr-count\">1</span><span class=\"step-btn\">+</span></span></div>\n <div class=\"menu-row\"><span class=\"mr-main\"><span class=\"mr-name\">Sparkling Water</span> <span class=\"mr-kind\">Drinks</span></span><span class=\"mr-price\">$4</span><span class=\"mr-qty\"><span class=\"step-btn on\">−</span><span class=\"mr-count\">1</span><span class=\"step-btn\">+</span></span></div>\n <div class=\"wc-foot\"><span class=\"wc-total\">Total <strong>$40</strong></span><button class=\"wc-cta\"><svg viewBox=\"0 0 24 24\"><rect x=\"3\" y=\"5\" width=\"18\" height=\"14\" rx=\"2\"/><path d=\"M3 10h18\"/></svg>Check out &amp; pay</button></div>\n <div class=\"wc-note\">Payment happens on acme.example — <b>your card is never entered in chat.</b></div>\n </div>\n </div>\n\n <div class=\"sf\">\n <div class=\"sf-name\">CheckoutHandoff <span>· signed link (create_checkout)</span></div>\n <div class=\"handoff-card\">\n <div class=\"glyph\"><svg viewBox=\"0 0 24 24\"><rect x=\"3\" y=\"5\" width=\"18\" height=\"14\" rx=\"2\"/><path d=\"M3 10h18\"/></svg></div>\n <h4>Pay on Acme Bistro checkout</h4>\n <p>Your order is staged and ready. Card entered on <strong>acme.example</strong>, never in chat.</p>\n <div class=\"mini-sum\"><div class=\"row\"><span>4 items</span><span>$40</span></div><div class=\"row total\"><span>Total</span><span>$40+tax</span></div></div>\n <button class=\"cta-primary\">Pay $40 on acme.example ↗</button>\n <div class=\"pay-link\">Signed · expires 15 min · <code>src=chatgpt</code></div>\n </div>\n </div>\n </div>\n </div>\n\n <hr class=\"page-divider\">\n\n <!-- ═══ MCP TOOLS APPENDIX ═══ -->\n <div class=\"section\" id=\"api\">\n <span class=\"section-label\">Technical appendix</span>\n <div class=\"section-title\">MCP Tools &amp; Call Sequence</div>\n <div class=\"section-subtitle\">Tool mapping for each wireframe step. Four tools, served by the Noodle Seed–authored <code>acme_bistro</code> server. Concrete request/response JSON lives in <code>api-contract.md</code>.</div>\n\n <div class=\"api-panel\">\n <div class=\"api-panel-header\">Browse &amp; Build (Steps 1–3)</div>\n <div class=\"api-step\">\n <div class=\"api-step-label\">Step 1 — Show the menu</div>\n <div class=\"api-endpoint\"><span class=\"kind read\">READ</span><span class=\"path\">show_menu</span><span class=\"desc\">— tool + view. Returns the 5-item menu and renders MenuCart.</span></div>\n <div class=\"api-note\"><strong>Design intent:</strong> the menu is small and static, so it ships in one read — no pagination, no follow-up call. The <code>items[]</code> array is the model's only source of dish names and prices.</div>\n </div>\n <div class=\"api-step\">\n <div class=\"api-step-label\">Steps 2–3 — Build &amp; edit the cart</div>\n <div class=\"api-endpoint\"><span class=\"kind write\">WRITE</span><span class=\"path\">add_to_cart</span><span class=\"desc\">— tool + app visibility. Reflects a natural-language addition (item + quantity) into the visible cart.</span></div>\n <div class=\"api-endpoint\"><span class=\"kind write\">WRITE</span><span class=\"path\">remove_from_cart</span><span class=\"desc\">— tool + app visibility. Removes one unit; the widget's − button calls the same tool.</span></div>\n <div class=\"api-note\"><strong>Natural-language parsing:</strong> \"two margheritas and a lemon tart\" becomes <code>add_to_cart{item:\"stone_pizza\",quantity:2}</code> + <code>add_to_cart{item:\"lemon_tart\",quantity:1}</code> — the model fills the fields; no UI round-trip. The running total is summed live in the widget (React), not in a tool.</div>\n </div>\n </div>\n\n <div class=\"api-panel\">\n <div class=\"api-panel-header\">Confirm &amp; Hand off (Step 4 → off-app)</div>\n <div class=\"api-step\">\n <div class=\"api-step-label\">Step 4 — Mint the payment link</div>\n <div class=\"api-endpoint\"><span class=\"kind link\">OPEN-LINK</span><span class=\"path\">create_checkout</span><span class=\"desc\">— model-visible tool. Returns a signed deep link + summary; ChatGPT opens it.</span></div>\n <div class=\"api-note\"><strong>No payment in-chat.</strong> The widget passes a url-safe cart token and the numeric total; <code>create_checkout</code> returns <code>checkoutUrl = https://pay.acme.example/checkout?cart=…&amp;total=…&amp;src=chatgpt</code> (production adds a signed <code>expires_at</code>). The app never sees card data. Acme recomputes pricing/tax and enforces the total past the boundary. No <code>submit_order</code> tool exists by design — fulfilment is Acme's.</div>\n </div>\n </div>\n </div>\n\n <hr class=\"page-divider\">\n\n <!-- ═══ COMPLIANCE AUDIT ═══ -->\n <div class=\"section\" id=\"compliance\">\n <span class=\"section-label\">Compliance</span>\n <div class=\"section-title\">OpenAI Apps SDK Compliance Audit</div>\n <div class=\"section-subtitle\">How Acme Bistro maps to OpenAI's published ChatGPT Apps UX Principles and UI Guidelines. Verified in the build with <code>noodle check --target chatgpt</code>.</div>\n\n <div class=\"rationale\" style=\"max-width:100%\">\n <h4>Pre-publishing checklist</h4>\n <table class=\"audit-table\">\n <tr><th style=\"width:32%\">Requirement</th><th>How Acme Bistro addresses it</th><th style=\"width:70px\">Status</th></tr>\n <tr><td>Conversational value — relies on ChatGPT's strengths</td><td>Natural-language ordering (\"two margheritas and a lemon tart\") parses into <code>add_to_cart</code> calls with item + quantity — no tap-driven menu can do this. Editing by sentence (\"drop a margherita\") works the same way.</td><td class=\"audit-pass\">✓ Pass</td></tr>\n <tr><td>Beyond base ChatGPT — new knowledge/actions</td><td>Live single-restaurant menu, a running cart, and a signed checkout hand-off to Acme's real payment page. None available in base ChatGPT.</td><td class=\"audit-pass\">✓ Pass</td></tr>\n <tr><td>Atomic, model-friendly actions</td><td>Four tools with explicit Zod-typed input/output: <code>show_menu</code> (read), <code>add_to_cart</code>/<code>remove_from_cart</code> (local write), <code>create_checkout</code> (open-link). No ambiguity.</td><td class=\"audit-pass\">✓ Pass</td></tr>\n <tr><td>Helpful UI only — would plain text degrade UX?</td><td>Yes for the menu/cart — price rows and steppers are faster to scan than prose, and the running total needs a layout. <strong>No payment widget is built</strong> — card capture is off-platform, so a widget there would be wrong.</td><td class=\"audit-pass\">✓ Pass</td></tr>\n <tr><td>Meaningful task completion in-chat</td><td>The full order — browse, build, edit, confirm total — completes in ChatGPT. The one intentional hand-off is payment, on Acme's checkout.</td><td class=\"audit-pass\">✓ Pass</td></tr>\n <tr><td>Performance &amp; responsiveness</td><td>One read on entry; cart edits are local to the widget; one link mint at checkout. Static menu keeps <code>show_menu</code> well under target latency.</td><td class=\"audit-pass\">✓ Pass</td></tr>\n <tr><td>Discoverability</td><td>Broad natural triggers: \"show me the Acme Bistro menu\", \"order two margheritas from Acme\", \"what's my Acme total?\", \"check out and pay\".</td><td class=\"audit-pass\">✓ Pass</td></tr>\n <tr><td>Platform fit</td><td>Rich prompts (order + quantity in one sentence), multi-turn cart building, in-session memory of the cart. No per-user auth needed for the pre-payment surface.</td><td class=\"audit-pass\">✓ Pass</td></tr>\n </table>\n </div>\n\n <div class=\"rationale\" style=\"max-width:100%;margin-top:18px\">\n <h4>UI guidelines compliance</h4>\n <table class=\"audit-table\">\n <tr><th style=\"width:32%\">Guideline</th><th>Implementation</th><th style=\"width:70px\">Status</th></tr>\n <tr><td>Colour — system tokens; brand only on accents/CTA</td><td>Text, borders, and surfaces use host semantic tokens via cascade layers. Acme red <code>#B91C1C</code> appears only on the header mark and the primary <strong>Check out &amp; pay</strong> button.</td><td class=\"audit-pass\">✓ Pass</td></tr>\n <tr><td>Typography — inherit system fonts</td><td>System font stack; no custom Acme typeface inside the widget.</td><td class=\"audit-pass\">✓ Pass</td></tr>\n <tr><td>Inline Card — ≤2 actions, no nested scroll, no deep nav</td><td>MenuCart has one primary action (Check out &amp; pay) plus in-card steppers; five rows fit with no inner scroller and no drill-in.</td><td class=\"audit-pass\">✓ Pass</td></tr>\n <tr><td>Icons — monochromatic, outlined</td><td>Outlined plate mark and card glyph; no filled brand logo rendered in the response body.</td><td class=\"audit-pass\">✓ Pass</td></tr>\n <tr><td>Accessibility — WCAG AA, theme-aware</td><td>Acme red used only as a fill behind light text or as a 1px mark, never as body text on white. Widget adapts to host light/dark via <code>branding.surface</code> / <code>surfaceDark</code>.</td><td class=\"audit-pass\">✓ Pass</td></tr>\n <tr><td>Display mode — correct per intent</td><td>Inline Card only. No Carousel/Fullscreen/PiP — a flat 5-item menu doesn't warrant them.</td><td class=\"audit-pass\">✓ Pass</td></tr>\n </table>\n </div>\n\n <div class=\"rationale\" style=\"max-width:100%;margin-top:18px\">\n <h4>Domain guardrails (Acme-specific trust rows)</h4>\n <table class=\"audit-table\">\n <tr><th style=\"width:32%\">Guardrail</th><th>How Acme Bistro enforces it</th><th style=\"width:70px\">Status</th></tr>\n <tr class=\"audit-guard\"><td>No payment in chat</td><td>No card field, wallet, or stored method anywhere in the app. Card capture happens only on <code>pay.acme.example</code> after the hand-off. The MCP server never enters PCI scope. The \"your card is never entered in chat\" note is in every widget frame.</td><td class=\"audit-pass\">✓ Pass</td></tr>\n <tr class=\"audit-guard\"><td>Allergen / dietary honesty</td><td>The model states only what the menu data holds (name, course, price). Ingredient-level or cross-contact questions are deferred to Acme directly — never \"this is vegetarian/gluten-free\" without a menu flag.</td><td class=\"audit-pass\">✓ Pass</td></tr>\n <tr class=\"audit-guard\"><td>No invented items or prices</td><td>Grounded strictly in the <code>show_menu</code> <code>items[]</code> — only the five dishes, only their listed prices. The total is display-only; Acme recomputes the charge.</td><td class=\"audit-pass\">✓ Pass</td></tr>\n <tr class=\"audit-guard\"><td>Signed, expiring, attributable hand-off</td><td>Checkout link is signed server-side, carries <code>src=chatgpt</code>, and expires (proposed 15 min). <code>handoff.allowedDomains</code> whitelists the redirect domains so the link opens without a safe-link warning.</td><td class=\"audit-pass\">✓ Pass</td></tr>\n <tr class=\"audit-guard\"><td>No unseen fulfilment claims</td><td>The app builds and hands off the order; it makes no pickup-time or order-status promise it can't verify (no post-handoff visibility in v1).</td><td class=\"audit-pass\">✓ Pass</td></tr>\n </table>\n </div>\n </div>\n\n <div class=\"footer\">Acme Bistro (illustrative) · Prepared by Noodle Seed · End-to-end wireframes · matches the runnable <code>acme_bistro</code> server</div>\n\n</div>\n</body>\n</html>\n" },
23
23
  { relPath: "examples/acme-bistro/noodle.json", content: "{\n \"entrypoint\": \"src/server.ts\",\n \"name\": \"acme-bistro\",\n \"template\": \"widget\"\n}\n" },
24
24
  { relPath: "examples/acme-bistro/package.json", content: "{\n \"name\": \"acme-bistro\",\n \"version\": \"0.1.0\",\n \"private\": true,\n \"type\": \"module\",\n \"scripts\": {\n \"test\": \"vitest run\",\n \"validate\": \"noodle validate\",\n \"dev\": \"noodle dev\",\n \"deploy\": \"noodle deploy\"\n },\n \"devDependencies\": {\n \"@vitejs/plugin-react\": \"latest\",\n \"@noodleseed/one\": \"latest\",\n \"react\": \"latest\",\n \"react-dom\": \"latest\",\n \"vite\": \"latest\",\n \"vitest\": \"latest\"\n }\n}\n" },
25
25
  { relPath: "examples/acme-bistro/src/helpers.ts", content: "import type { ServerDefinition } from '@noodleseed/one';\nimport { generateHelpers } from '@noodleseed/one/react';\n\nexport type AppType = ServerDefinition;\n\nexport const { useBranding, useCallTool, useLayout, useOpenExternal, useToolInfo, useViewState } =\n generateHelpers<AppType>();\n" },
26
- { relPath: "examples/acme-bistro/src/server.ts", content: "import {\n annotations,\n managedCollection,\n noodlePlatform,\n server,\n tool,\n variable,\n z,\n} from '@noodleseed/one';\n\n// Fictional ordering app. Payment uses a checkout link; native guest requests require installation.\n\nconst menu = [\n { id: 'stone_pizza', name: 'Stone-baked Margherita', price: 14, kind: 'Mains' },\n { id: 'roast_bowl', name: 'Harvest Roast Bowl', price: 13, kind: 'Mains' },\n { id: 'house_salad', name: 'House Garden Salad', price: 11, kind: 'Starters' },\n { id: 'lemon_tart', name: 'Lemon Tart', price: 8, kind: 'Desserts' },\n { id: 'sparkling', name: 'Sparkling Water', price: 4, kind: 'Drinks' },\n] as const;\n\nconst itemId = z.enum(['stone_pizza', 'roast_bowl', 'house_salad', 'lemon_tart', 'sparkling']);\n\n// A business administrator may change this notice; the reusable application stays the same.\nconst serviceNotice = variable('SERVICE_NOTICE', {\n schema: z.string().max(500),\n default: 'Ask us about dietary requirements before placing your order.',\n portal: { label: 'Service notice', group: 'Guest experience' },\n requiredFor: ['show_menu'],\n});\n\nconst menuItemOutput = z.object({\n id: z.string(),\n name: z.string(),\n price: z.number(),\n kind: z.string(),\n});\n\nconst guestRequestRecord = z.object({\n locationReference: z.string().min(1).max(120),\n requestType: z.enum(['reservation_help', 'accessibility', 'dietary_question', 'other']),\n summary: z.string().min(1).max(1000),\n guestReference: z.string().max(120).optional(),\n progress: z.enum(['received', 'reviewing', 'handled']).default('received'),\n});\n\nconst guestRequests = managedCollection('guest_requests', {\n title: 'Guest requests',\n description: 'Guest service requests that restaurant staff can review and resolve.',\n schemaVersion: 1,\n // No source is declared, so Noodle is authoritative. Outside-owned records would name an exact\n // connector scan contract here; changes in that outside system would remain ordinary tools.\n record: guestRequestRecord,\n management: { notes: true },\n publicFields: ['locationReference', 'requestType', 'summary'],\n editableFields: ['locationReference', 'requestType', 'summary', 'guestReference', 'progress'],\n fields: { progress: { label: 'Progress' }, summary: { label: 'Guest request' } },\n summaryFields: ['requestType', 'summary', 'progress'],\n filterFields: ['progress'],\n sortFields: ['progress'],\n});\n\n// Tool annotations for host planners: the menu read is read-only; cart edits are local writes; checkout\n// opens an external (payment) link.\nconst readOnly = annotations.readOnly();\nconst localWrite = annotations.localAction({ destructive: false, confirm: false });\nconst openLink = annotations.openAction();\n\nexport default server(\n 'acme_bistro',\n {\n title: 'Acme Bistro',\n version: '1.0.0',\n branding: {\n name: 'Acme Bistro',\n accent: '#B91C1C',\n surface: '#FEF3F2',\n surfaceDark: '#1A1211',\n radius: 'lg',\n density: 'comfortable',\n },\n // Payment is the only off-app step; the compiler derives ChatGPT redirect_domains from this so the\n // signed checkout link opens without a safe-link warning. The card never reaches this app.\n handoff: {\n allowedDomains: ['https://pay.acme.example', 'https://acme.example'],\n },\n // Reusable business-record intent. Storage, lifecycle, access, and public intake bind separately.\n collections: [guestRequests],\n use: { records: noodlePlatform.records.v1 },\n variables: [serviceNotice],\n },\n [\n tool('submit_guest_request', {\n title: 'Submit a guest request',\n description: 'Record a guest request for staff review; this does not confirm a reservation.',\n annotations: annotations.localAction({ destructive: false, confirm: true }),\n input: guestRequestRecord.pick({ locationReference: true, requestType: true, summary: true }),\n output: z.object({ recordId: z.string() }),\n fulfil: ({ input, connectors }) => {\n const receipt = connectors.records.submitRecord({\n collection: 'guest_requests',\n payload: {\n locationReference: input.locationReference,\n requestType: input.requestType,\n summary: input.summary,\n },\n });\n return { recordId: receipt.recordId };\n },\n }),\n tool('show_menu', {\n title: 'Show the menu',\n description: 'Show the Acme Bistro menu and render the ordering widget.',\n annotations: readOnly,\n input: z.object({ customer: z.string().default('Guest') }),\n output: z.object({\n status: z.string(),\n customer: z.string(),\n serviceNotice: z.string().max(500),\n // Bounded list: the menu is a fixed catalog, so the ceiling is declared on the shape rather\n // than taken as a pagination input. `noodle check` reports `tool_design_output_bounds`.\n items: z.array(menuItemOutput).max(50),\n }),\n fulfil: ({ input }) => ({\n status: `Acme Bistro menu is ready for ${input.customer}. Build the order here; pay at checkout.`,\n customer: input.customer,\n serviceNotice,\n items: menu,\n }),\n viewTitle: 'Order at Acme Bistro',\n viewDescription: 'Browse the menu, build an order in chat, and hand off to pay.',\n invoking: 'Loading the menu…',\n invoked: 'Menu ready',\n domain: 'https://order.acme.example',\n view: {\n component: 'menu-cart',\n entry: './views/menu-cart.tsx',\n },\n csp: {\n connectDomains: ['https://acme.example'],\n resourceDomains: ['https://acme.example'],\n frameDomains: ['https://acme.example'],\n },\n }),\n // Widget-only cart edits — the model fills the item from natural language (\"add two margheritas\").\n tool('add_to_cart', {\n visibility: ['app'],\n description: 'Add a menu item to the Acme Bistro order from the widget.',\n annotations: localWrite,\n input: z.object({\n customer: z.string().default('Guest'),\n item: itemId.default('stone_pizza'),\n quantity: z.number().int().min(1).default(1),\n notes: z.string().default(''),\n }),\n output: z.object({\n status: z.string(),\n item: z.string(),\n quantity: z.number(),\n notes: z.string(),\n }),\n fulfil: ({ input }) => ({\n status: `Added ${input.quantity} × ${input.item} for ${input.customer}.`,\n item: input.item,\n quantity: input.quantity,\n notes: input.notes,\n }),\n }),\n tool('remove_from_cart', {\n visibility: ['app'],\n description: 'Remove a menu item from the Acme Bistro order.',\n annotations: localWrite,\n input: z.object({\n customer: z.string().default('Guest'),\n item: itemId.default('stone_pizza'),\n }),\n output: z.object({\n status: z.string(),\n item: z.string(),\n }),\n fulfil: ({ input }) => ({\n status: `Removed ${input.item} for ${input.customer}.`,\n item: input.item,\n }),\n }),\n // The only handoff: payment. The widget computes the total (live React) and passes a url-safe cart\n // token + total; the card is entered on Acme's PCI-scoped checkout, never in chat.\n tool('create_checkout', {\n title: 'Create checkout',\n description:\n 'Create the Acme Bistro payment checkout link for the current order. Pass a url-safe cart token ' +\n 'and the numeric total computed in the widget. Payment happens off-app; the card never reaches this app.',\n annotations: openLink,\n input: z.object({\n customer: z.string().default('Guest'),\n cartToken: z.string().default('cart'),\n total: z.number().min(0).default(0),\n }),\n output: z.object({\n status: z.string(),\n summary: z.string(),\n checkoutUrl: z.string(),\n }),\n // Do not place a literal `$` immediately before a token (`$${input.total}`) — it collides with the\n // `${…}` substitution syntax and leaves the token unresolved. Keep the amount token standalone.\n fulfil: ({ input }) => ({\n status: `Ready to pay for ${input.customer}'s order.`,\n summary: `${input.customer}'s Acme Bistro order · ${input.total} USD`,\n checkoutUrl: `https://pay.acme.example/checkout?cart=${input.cartToken}&total=${input.total}&src=chatgpt`,\n }),\n }),\n ],\n);\n" },
26
+ { relPath: "examples/acme-bistro/src/server.ts", content: "import {\n annotations,\n managedCollection,\n noodlePlatform,\n server,\n tool,\n variable,\n z,\n} from '@noodleseed/one';\n\n// Fictional ordering app. Payment uses a checkout link; native guest requests require installation.\n\nconst menu = [\n { id: 'stone_pizza', name: 'Stone-baked Margherita', price: 14, kind: 'Mains' },\n { id: 'roast_bowl', name: 'Harvest Roast Bowl', price: 13, kind: 'Mains' },\n { id: 'house_salad', name: 'House Garden Salad', price: 11, kind: 'Starters' },\n { id: 'lemon_tart', name: 'Lemon Tart', price: 8, kind: 'Desserts' },\n { id: 'sparkling', name: 'Sparkling Water', price: 4, kind: 'Drinks' },\n] as const;\n\nconst itemId = z.enum(['stone_pizza', 'roast_bowl', 'house_salad', 'lemon_tart', 'sparkling']);\n\n// Operators configure the notice without redeploying.\nconst guestExperience = variable('GUEST_EXPERIENCE', {\n schema: z.object({ notice: z.string().max(500) }),\n default: { notice: 'Ask us about dietary requirements before placing your order.' },\n portal: { label: 'Guest experience', group: 'Guest experience' },\n requiredFor: ['show_menu'],\n});\n\nconst menuItemOutput = z.object({\n id: z.string(),\n name: z.string(),\n price: z.number(),\n kind: z.string(),\n});\n\nconst guestRequestRecord = z.object({\n locationReference: z.string().min(1).max(120),\n requestType: z.enum(['reservation_help', 'accessibility', 'dietary_question', 'other']),\n summary: z.string().min(1).max(1000),\n guestReference: z.string().max(120).optional(),\n progress: z.enum(['received', 'reviewing', 'handled']).default('received'),\n});\n\nconst guestRequests = managedCollection('guest_requests', {\n title: 'Guest requests',\n description: 'Guest service requests that restaurant staff can review and resolve.',\n schemaVersion: 1,\n // No source is declared, so Noodle is authoritative. Outside-owned records would name an exact\n // connector scan contract here; changes in that outside system would remain ordinary tools.\n record: guestRequestRecord,\n management: { notes: true },\n publicFields: ['locationReference', 'requestType', 'summary'],\n editableFields: ['locationReference', 'requestType', 'summary', 'guestReference', 'progress'],\n fields: { progress: { label: 'Progress' }, summary: { label: 'Guest request' } },\n summaryFields: ['requestType', 'summary', 'progress'],\n filterFields: ['progress'],\n sortFields: ['progress'],\n});\n\n// Tool annotations for host planners: the menu read is read-only; cart edits are local writes; checkout\n// opens an external (payment) link.\nconst readOnly = annotations.readOnly();\nconst localWrite = annotations.localAction({ destructive: false, confirm: false });\nconst openLink = annotations.openAction();\n\nexport default server(\n 'acme_bistro',\n {\n title: 'Acme Bistro',\n version: '1.0.0',\n branding: {\n name: 'Acme Bistro',\n accent: '#B91C1C',\n surface: '#FEF3F2',\n surfaceDark: '#1A1211',\n radius: 'lg',\n density: 'comfortable',\n },\n // Payment is the only off-app step; the compiler derives ChatGPT redirect_domains from this so the\n // signed checkout link opens without a safe-link warning. The card never reaches this app.\n handoff: {\n allowedDomains: ['https://pay.acme.example', 'https://acme.example'],\n },\n // Reusable business-record intent. Storage, lifecycle, access, and public intake bind separately.\n collections: [guestRequests],\n use: { records: noodlePlatform.records.v1 },\n variables: [guestExperience],\n },\n [\n tool('submit_guest_request', {\n title: 'Submit a guest request',\n description: 'Record a guest request for staff review; this does not confirm a reservation.',\n annotations: annotations.localAction({ destructive: false, confirm: true }),\n input: guestRequestRecord.pick({ locationReference: true, requestType: true, summary: true }),\n output: z.object({ recordId: z.string() }),\n fulfil: ({ input, connectors }) => {\n const receipt = connectors.records.submitRecord({\n collection: 'guest_requests',\n payload: {\n locationReference: input.locationReference,\n requestType: input.requestType,\n summary: input.summary,\n },\n });\n return { recordId: receipt.recordId };\n },\n }),\n tool('show_menu', {\n title: 'Show the menu',\n description: 'Show the Acme Bistro menu and render the ordering widget.',\n annotations: readOnly,\n input: z.object({ customer: z.string().default('Guest') }),\n output: z.object({\n status: z.string(),\n customer: z.string(),\n serviceNotice: z.string().max(500),\n // Bounded list: the menu is a fixed catalog, so the ceiling is declared on the shape rather\n // than taken as a pagination input. `noodle check` reports `tool_design_output_bounds`.\n items: z.array(menuItemOutput).max(50),\n }),\n fulfil: ({ input }) => ({\n status: `Acme Bistro menu is ready for ${input.customer}. Build the order here; pay at checkout.`,\n customer: input.customer,\n serviceNotice: guestExperience.field('notice'),\n items: menu,\n }),\n viewTitle: 'Order at Acme Bistro',\n viewDescription: 'Browse the menu, build an order in chat, and hand off to pay.',\n invoking: 'Loading the menu…',\n invoked: 'Menu ready',\n domain: 'https://order.acme.example',\n view: {\n component: 'menu-cart',\n entry: './views/menu-cart.tsx',\n },\n csp: {\n connectDomains: ['https://acme.example'],\n resourceDomains: ['https://acme.example'],\n frameDomains: ['https://acme.example'],\n },\n }),\n // Widget-only cart edits — the model fills the item from natural language (\"add two margheritas\").\n tool('add_to_cart', {\n visibility: ['app'],\n description: 'Add a menu item to the Acme Bistro order from the widget.',\n annotations: localWrite,\n input: z.object({\n customer: z.string().default('Guest'),\n item: itemId.default('stone_pizza'),\n quantity: z.number().int().min(1).default(1),\n notes: z.string().default(''),\n }),\n output: z.object({\n status: z.string(),\n item: z.string(),\n quantity: z.number(),\n notes: z.string(),\n }),\n fulfil: ({ input }) => ({\n status: `Added ${input.quantity} × ${input.item} for ${input.customer}.`,\n item: input.item,\n quantity: input.quantity,\n notes: input.notes,\n }),\n }),\n tool('remove_from_cart', {\n visibility: ['app'],\n description: 'Remove a menu item from the Acme Bistro order.',\n annotations: localWrite,\n input: z.object({\n customer: z.string().default('Guest'),\n item: itemId.default('stone_pizza'),\n }),\n output: z.object({\n status: z.string(),\n item: z.string(),\n }),\n fulfil: ({ input }) => ({\n status: `Removed ${input.item} for ${input.customer}.`,\n item: input.item,\n }),\n }),\n // The only handoff: payment. The widget computes the total (live React) and passes a url-safe cart\n // token + total; the card is entered on Acme's PCI-scoped checkout, never in chat.\n tool('create_checkout', {\n title: 'Create checkout',\n description:\n 'Create the Acme Bistro payment checkout link for the current order. Pass a url-safe cart token ' +\n 'and the numeric total computed in the widget. Payment happens off-app; the card never reaches this app.',\n annotations: openLink,\n input: z.object({\n customer: z.string().default('Guest'),\n cartToken: z.string().default('cart'),\n total: z.number().min(0).default(0),\n }),\n output: z.object({\n status: z.string(),\n summary: z.string(),\n checkoutUrl: z.string(),\n }),\n // Do not place a literal `$` immediately before a token (`$${input.total}`) — it collides with the\n // `${…}` substitution syntax and leaves the token unresolved. Keep the amount token standalone.\n fulfil: ({ input }) => ({\n status: `Ready to pay for ${input.customer}'s order.`,\n summary: `${input.customer}'s Acme Bistro order · ${input.total} USD`,\n checkoutUrl: `https://pay.acme.example/checkout?cart=${input.cartToken}&total=${input.total}&src=chatgpt`,\n }),\n }),\n ],\n);\n" },
27
27
  { relPath: "examples/acme-bistro/src/views/menu-cart.tsx", content: "import { type CSSProperties, useMemo, useState } from 'react';\nimport {\n useBranding,\n useCallTool,\n useLayout,\n useOpenExternal,\n useToolInfo,\n useViewState,\n} from '../helpers.js';\nimport './widget-style.css';\n\ntype MenuItem = {\n readonly id: string;\n readonly name: string;\n readonly price: number;\n readonly kind: string;\n};\n\nfunction asMenu(value: unknown) {\n return value as\n | { readonly status?: string; readonly customer?: string; readonly items?: readonly MenuItem[] }\n | undefined;\n}\n\nexport default function MenuCart() {\n const { displayMode, theme } = useLayout();\n // Widget CSS is ours, so nothing applies `server.branding` for us. Map the one value this widget\n // cares about onto its own custom property; widget-style.css keeps a default for local dev.\n const branding = useBranding();\n const brandStyle = branding.accent\n ? ({ '--nw-accent': branding.accent } as CSSProperties)\n : undefined;\n const openExternal = useOpenExternal();\n const menuResult = asMenu(useToolInfo('show_menu').structuredContent);\n const addToCart = useCallTool('add_to_cart');\n const removeFromCart = useCallTool('remove_from_cart');\n const checkout = useCallTool('create_checkout');\n\n const items = menuResult?.items ?? [];\n const [customer] = useViewState('customer', menuResult?.customer ?? 'Guest');\n // Cart is session-local (id → quantity); the total is summed here in live React, not in a recorded fulfil.\n const [cart, setCart] = useState<Record<string, number>>({});\n const [status, setStatus] = useState(\n menuResult?.status ?? 'Build your order, then check out to pay.',\n );\n\n const total = useMemo(\n () => items.reduce((sum, item) => sum + item.price * (cart[item.id] ?? 0), 0),\n [items, cart],\n );\n const lineCount = Object.values(cart).reduce((n, q) => n + q, 0);\n\n async function add(item: MenuItem) {\n setCart((current) => ({ ...current, [item.id]: (current[item.id] ?? 0) + 1 }));\n const result = await addToCart.callTool({ customer, item: item.id, quantity: 1 });\n const structured = result.structuredContent as { readonly status?: string } | undefined;\n setStatus(structured?.status ?? `Added ${item.name}.`);\n }\n\n async function remove(item: MenuItem) {\n setCart((current) => {\n const next = { ...current };\n const q = (next[item.id] ?? 0) - 1;\n if (q <= 0) delete next[item.id];\n else next[item.id] = q;\n return next;\n });\n await removeFromCart.callTool({ customer, item: item.id });\n }\n\n async function payNow() {\n if (lineCount === 0) return;\n // The only handoff: payment. A url-safe cart token + the numeric total go to Acme's PCI checkout.\n const cartToken = items\n .filter((item) => cart[item.id])\n .map((item) => `${item.id}x${cart[item.id]}`)\n .join('-');\n const result = await checkout.callTool({ customer, cartToken, total });\n const structured = result.structuredContent as { readonly checkoutUrl?: string } | undefined;\n if (structured?.checkoutUrl) openExternal(structured.checkoutUrl);\n }\n\n return (\n <main\n className={`nw-shell${theme === 'dark' ? ' dark' : ''}`}\n style={brandStyle}\n data-llm={`Acme Bistro order for ${customer}: ${lineCount} item(s), total $${total}`}\n >\n <section className=\"nw-card\">\n <header className=\"nw-header\">\n <span className=\"nw-icon\" aria-hidden=\"true\">\n <PlateIcon />\n </span>\n <div className=\"nw-title-block\">\n <h1 className=\"nw-title\">Acme Bistro</h1>\n <p className=\"nw-subtitle\">{status}</p>\n </div>\n <span className=\"nw-chip\">\n {displayMode === 'fullscreen' ? 'Fullscreen' : `${lineCount} in cart`}\n </span>\n </header>\n\n <ul className=\"nw-menu\">\n {items.map((item) => (\n <li className=\"nw-row\" key={item.id}>\n <span className=\"nw-row-main\">\n <span className=\"nw-name\">{item.name}</span>\n <span className=\"nw-kind\">{item.kind}</span>\n </span>\n <span className=\"nw-price\">${item.price}</span>\n <span className=\"nw-qty\">\n <button\n aria-label={`Remove one ${item.name}`}\n className=\"nw-step\"\n type=\"button\"\n disabled={!cart[item.id]}\n onClick={() => remove(item)}\n >\n −\n </button>\n <span className=\"nw-count\">{cart[item.id] ?? 0}</span>\n <button\n aria-label={`Add one ${item.name}`}\n className=\"nw-step\"\n type=\"button\"\n onClick={() => add(item)}\n >\n +\n </button>\n </span>\n </li>\n ))}\n </ul>\n\n <footer className=\"nw-footer\">\n <span className=\"nw-total\">\n Total <strong>${total}</strong>\n </span>\n <button\n className=\"nw-button nw-button-primary\"\n type=\"button\"\n disabled={lineCount === 0 || checkout.isPending}\n onClick={payNow}\n >\n <CardIcon />\n {checkout.isPending ? 'Opening checkout…' : 'Check out & pay'}\n </button>\n </footer>\n <p className=\"nw-note\">\n Payment happens on acme.example — your card is never entered in chat.\n </p>\n </section>\n </main>\n );\n}\n\nfunction PlateIcon() {\n return (\n <svg viewBox=\"0 0 24 24\" aria-hidden=\"true\">\n <circle cx=\"12\" cy=\"12\" r=\"9\" />\n <circle cx=\"12\" cy=\"12\" r=\"4\" />\n </svg>\n );\n}\n\nfunction CardIcon() {\n return (\n <svg viewBox=\"0 0 24 24\" aria-hidden=\"true\">\n <rect x=\"3\" y=\"5\" width=\"18\" height=\"14\" rx=\"2\" />\n <path d=\"M3 10h18\" />\n </svg>\n );\n}\n" },
28
28
  { relPath: "examples/acme-bistro/src/views/widget-style.css", content: ":root {\n color-scheme: light dark;\n font-family:\n Inter, ui-sans-serif, system-ui, -apple-system, BlinkMacSystemFont, \"Segoe UI\", sans-serif;\n --nw-bg: #ffffff;\n --nw-surface: #fdf4f3;\n --nw-text: #1f1413;\n --nw-muted: #7a5f5c;\n --nw-border: #efd9d6;\n /* Local-dev default. At runtime menu-cart.tsx overrides this from server.branding.accent. */\n --nw-accent: #b91c1c;\n --nw-accent-strong: #991b1b;\n --nw-accent-soft: #fdeae8;\n --nw-radius: 10px;\n --nw-shadow: 0 18px 50px rgb(60 20 20 / 12%);\n}\n\n.dark,\n[data-theme=\"dark\"] {\n --nw-bg: #1a1211;\n --nw-surface: #241816;\n --nw-text: #f8ecea;\n --nw-muted: #c3a29e;\n --nw-border: #43302d;\n --nw-accent: #f87171;\n --nw-accent-strong: #ef4444;\n --nw-accent-soft: #3a1f1d;\n --nw-shadow: 0 18px 50px rgb(0 0 0 / 32%);\n}\n\n* {\n box-sizing: border-box;\n}\n\nbody {\n margin: 0;\n background: var(--nw-bg);\n color: var(--nw-text);\n}\n\nbutton {\n font: inherit;\n}\n\n.nw-shell {\n min-height: 100vh;\n padding: 14px;\n background: var(--nw-bg);\n color: var(--nw-text);\n}\n\n.nw-card {\n max-width: 560px;\n margin: 0 auto;\n background: var(--nw-surface);\n border: 1px solid var(--nw-border);\n border-radius: var(--nw-radius);\n box-shadow: var(--nw-shadow);\n overflow: hidden;\n}\n\n.nw-header {\n display: flex;\n align-items: center;\n gap: 12px;\n padding: 16px;\n border-bottom: 1px solid var(--nw-border);\n}\n\n.nw-icon svg {\n width: 24px;\n height: 24px;\n fill: none;\n stroke: var(--nw-accent);\n stroke-width: 1.7;\n stroke-linecap: round;\n stroke-linejoin: round;\n}\n\n.nw-title-block {\n flex: 1;\n min-width: 0;\n}\n\n.nw-title {\n margin: 0;\n font-size: 17px;\n font-weight: 700;\n}\n\n.nw-subtitle {\n margin: 2px 0 0;\n font-size: 13px;\n color: var(--nw-muted);\n}\n\n.nw-chip {\n padding: 4px 10px;\n border-radius: 999px;\n background: var(--nw-accent-soft);\n color: var(--nw-accent-strong);\n font-size: 12px;\n font-weight: 600;\n}\n\n.nw-menu {\n list-style: none;\n margin: 0;\n padding: 8px 16px;\n display: flex;\n flex-direction: column;\n gap: 4px;\n}\n\n.nw-row {\n display: flex;\n align-items: center;\n gap: 12px;\n padding: 10px 0;\n border-bottom: 1px dashed var(--nw-border);\n}\n\n.nw-row-main {\n flex: 1;\n min-width: 0;\n display: flex;\n flex-direction: column;\n}\n\n.nw-name {\n font-weight: 600;\n}\n\n.nw-kind {\n font-size: 12px;\n color: var(--nw-muted);\n}\n\n.nw-price {\n color: var(--nw-accent-strong);\n font-weight: 600;\n font-size: 13px;\n}\n\n.nw-qty {\n display: inline-flex;\n align-items: center;\n gap: 8px;\n}\n\n.nw-step {\n width: 26px;\n height: 26px;\n border: 1px solid var(--nw-border);\n border-radius: 8px;\n background: var(--nw-bg);\n color: var(--nw-text);\n cursor: pointer;\n}\n\n.nw-step:disabled {\n opacity: 0.4;\n cursor: default;\n}\n\n.nw-count {\n min-width: 16px;\n text-align: center;\n font-variant-numeric: tabular-nums;\n}\n\n.nw-footer {\n display: flex;\n align-items: center;\n justify-content: space-between;\n gap: 12px;\n padding: 12px 16px 4px;\n}\n\n.nw-total {\n font-size: 14px;\n color: var(--nw-muted);\n}\n\n.nw-total strong {\n color: var(--nw-text);\n font-size: 16px;\n}\n\n.nw-button {\n display: inline-flex;\n align-items: center;\n gap: 6px;\n padding: 9px 14px;\n border: 1px solid var(--nw-border);\n border-radius: 10px;\n background: var(--nw-bg);\n color: var(--nw-text);\n cursor: pointer;\n}\n\n.nw-button svg {\n width: 16px;\n height: 16px;\n fill: none;\n stroke: currentColor;\n stroke-width: 1.7;\n stroke-linecap: round;\n stroke-linejoin: round;\n}\n\n.nw-button-primary {\n background: var(--nw-accent);\n border-color: var(--nw-accent);\n color: #ffffff;\n font-weight: 600;\n}\n\n.nw-button-primary:disabled {\n opacity: 0.6;\n cursor: default;\n}\n\n.nw-note {\n margin: 0;\n padding: 8px 16px 16px;\n font-size: 12px;\n color: var(--nw-muted);\n}\n" },
29
29
  { relPath: "examples/acme-bistro/test/server.test.ts", content: "import { describe, expect, it } from 'vitest';\nimport app from '../src/server.js';\n\ndescribe('acme-bistro example', () => {\n it('exports a Noodle server definition', () => {\n expect(typeof app.toManifest).toBe('function');\n });\n\n it('declares the payment-only handoff domain', async () => {\n // End-to-end: the order completes in chat; only payment hands off to Acme's checkout.\n const text = JSON.stringify(await app.toManifest());\n expect(text).toContain('https://pay.acme.example');\n });\n\n it('exposes the menu widget, cart helpers, and checkout tool', async () => {\n const text = JSON.stringify(await app.toManifest());\n expect(text).toContain('show_menu');\n expect(text).toContain('add_to_cart');\n expect(text).toContain('create_checkout');\n });\n\n it('declares guest records and explicitly authors the native submission tool', async () => {\n const manifest = await app.toManifest();\n expect(manifest.server.collections).toEqual([\n expect.objectContaining({ name: 'guest_requests', schemaVersion: 1 }),\n ]);\n expect(\n manifest.tools.find((tool) => tool.name === 'submit_guest_request')?.fulfilment.steps,\n ).toMatchObject([{ use: 'records.submit_record' }]);\n });\n});\n" },
@@ -107,7 +107,7 @@ export const BUNDLED_EXAMPLE_FILES = [
107
107
  { relPath: "examples/weather/README.md", content: "# Weather Briefing\n\nTwo declarative tools that show the runtime's breadth working together, with **no auth and no API\nkeys**. The `weather_briefing` tool takes a city name and runs a **three-step flow**:\n\nCapability slots: HTTP connector authoring, ordered fulfilment flows, query/response mapping,\n**list-returning connector output** (a connector that returns a live, variable-length array), and\nsandboxed compute, including an explicit least-privilege per-operation response-size bound.\n\nFor a different API with an OpenAPI document, start with `noodle import openapi <file>` in a separate\ndirectory. It preserves supported typed JSON bodies and scalar parameters; unsupported input encodings\nstop import instead of dropping fields. Its offline test establishes the contract, not live behavior; follow the\n[connector guide](https://docs.noodleseed.dev/docs/guides/connectors) before replacing this curated flow.\n\n1. **`geo.search`** → geocode the city to coordinates (Open-Meteo Geocoding API)\n2. **`forecast.current`** → fetch current weather for those coordinates (Open-Meteo Forecast API)\n3. **`brief.summarize`** → derive a human-readable briefing in a **WASM/QuickJS compute sandbox**\n\nThe second tool, `search_places`, shows a connector returning a **live, variable-length list**: it binds\nthe whole Open-Meteo geocoding `results` array with `${response.results}`, then narrows each match to\n`{ id, label }` in a compute connector — the \"search → a list of options the model can pick from\"\npattern. Narrowing lives in compute because a `${...}` response mapping cannot iterate an array and a\ntool's Zod output does not strip fields at runtime.\n\nIt exercises, in one TypeScript-authored app:\n\n- **Server-level branding** with semantic tokens carried through the runtime artifact for any generated\n app surface.\n- **Ordered flow execution** with outputs threaded between steps (`${steps.geo.latitude}` → next step).\n- **Two HTTP connectors on two different hosts**, each with its own egress allowlist.\n- **Query parameters** (`query: [...]`) and a constant query baked into the path (`?current_weather=true`).\n- **Deep response mapping** with the `${...}` language — single-element indexing\n (`${response.results[0].latitude}`, `${response.current_weather.temperature}`) **and** whole-array\n binding (`${response.results}` returns the entire list verbatim).\n- **A list-returning connector + compute narrowing** — `geo.search_list` binds the whole `results`\n array; `places.narrow` reduces each element to `{ id, label }` and normalizes the no-results case\n to `[]`.\n- **A per-operation transport bound** — `search_list` sets\n `limits: { maxResponseBytes: 256 * 1024 }`, tightening this known-small endpoint below the 1 MiB default.\n The authoring ceiling is 6 MiB, but grant only the bytes representative evidence proves this operation\n needs.\n- **Sandboxed compute** (no network/fs/env/clock) turning raw numbers into conditions + advice.\n- **Typed input/output schemas** emitted as JSON Schema 2020-12.\n\n## APIs that require form-urlencoded search bodies\n\nThe live Open-Meteo calls above are GET requests. For APIs whose search endpoint is a POST expecting\n`application/x-www-form-urlencoded`, keep authoring a request object and select the encoding explicitly:\n\n```ts\nsearch_quotes: {\n type: 'read',\n method: 'POST',\n path: '/quotes/search',\n requestEncoding: 'form-urlencoded',\n input: z.object({\n fromAirportId: z.string(),\n categories: z.array(z.string()),\n }),\n request: {\n 'from airport id': '${args.fromAirportId}',\n 'aircraft[categories]': '${args.categories}',\n },\n // output and response mapping omitted\n},\n```\n\nNoodle builds a `URLSearchParams` body: spaces and punctuation in field names are encoded normally, while\neach array or nested object is JSON-stringified into its individual form field. Do not pre-encode the body\nor set `Content-Type` manually; the connector owns both.\n\n## Run it locally\n\nBefore an authorized hosted deployment, inspect this project's inputs with your project-local CLI:\n`noodle deploy preflight --org <org> --app weather --env staging --version 1 --json`.\nThis requires existing hosted access but does not publish or call the weather backend. Its readiness result\ndoes not replace the local and hosted representative-call checks below. Review independent missing bindings,\norigin and target-capability findings together before an authorized repair and recheck.\n\nFrom the repo root, with the workspace built (`pnpm build`):\n\n```bash\n: # 1. boot the local loopback dev server\nnode packages/cli/dist/cli.js dev examples/weather/src/server.ts --app weather\n\n: # 2. in another shell, call the printed local endpoint\nURL=http://127.0.0.1:<port>/o/local/weather/dev/mcp\ncurl -s \"$URL\" \\\n -H 'content-type: application/json' \\\n -H 'accept: application/json, text/event-stream' \\\n -H 'mcp-protocol-version: 2025-11-25' \\\n -d '{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"tools/call\",\"params\":{\"name\":\"weather_briefing\",\"arguments\":{\"city\":\"Paris\"}}}'\n```\n\nExample result (live data, abbreviated):\n\n```json\n{\n \"place\": \"Paris\", \"country\": \"France\",\n \"temperature_c\": 25.1, \"windspeed_kmh\": 8.3,\n \"conditions\": \"overcast\",\n \"headline\": \"Paris, France: 25°C, overcast.\",\n \"advice\": \"Comfortable conditions — no special prep needed.\"\n}\n```\n\nTry other cities (`Reykjavik`, `Singapore`, `Denver`) to see the conditions and advice change.\n\nCall `search_places` to see the **list-returning** tool — one query, many matches:\n\n```bash\ncurl -s \"$URL\" \\\n -H 'content-type: application/json' \\\n -H 'accept: application/json, text/event-stream' \\\n -H 'mcp-protocol-version: 2025-11-25' \\\n -d '{\"jsonrpc\":\"2.0\",\"id\":2,\"method\":\"tools/call\",\"params\":{\"name\":\"search_places\",\"arguments\":{\"query\":\"Springfield\"}}}'\n```\n\n```json\n{\n \"places\": [\n { \"id\": \"4951788\", \"label\": \"Springfield, Massachusetts, United States\" },\n { \"id\": \"4250542\", \"label\": \"Springfield, Illinois, United States\" },\n { \"id\": \"4508722\", \"label\": \"Springfield, Ohio, United States\" }\n ]\n}\n```\n" },
108
108
  { relPath: "examples/weather/noodle.json", content: "{\n \"entrypoint\": \"src/server.ts\",\n \"name\": \"weather\"\n}\n" },
109
109
  { relPath: "examples/weather/package.json", content: "{\n \"name\": \"weather\",\n \"version\": \"0.1.0\",\n \"private\": true,\n \"type\": \"module\",\n \"scripts\": {\n \"test\": \"vitest run\",\n \"validate\": \"noodle validate\",\n \"dev\": \"noodle dev\",\n \"deploy\": \"noodle deploy\"\n },\n \"devDependencies\": {\n \"@noodleseed/one\": \"latest\",\n \"vitest\": \"latest\"\n }\n}\n" },
110
- { relPath: "examples/weather/src/server.ts", content: "import { connector, server, tool, z } from '@noodleseed/one';\n\n// The same Weather Briefing server, authored in TypeScript with the Noodle authoring SDK.\n//\n// The SDK owns the *manifest*: the tool, its Zod-typed input/output schemas, and the flow — which you\n// write as ordinary code in `fulfil` and the SDK records symbolically into ordered steps.\n//\n// HTTP and compute connectors are authored here too, so the public developer entrypoint is one\n// self-contained server.ts. The SDK still compiles this to internal manifest/catalog data for the runtime.\n\nconst geocoding = connector('open_meteo_geocoding')\n .version('1.0.0')\n .http({\n baseUrl: 'https://geocoding-api.open-meteo.com',\n allowedOrigins: ['https://geocoding-api.open-meteo.com'],\n operations: {\n search: {\n type: 'read',\n method: 'GET',\n path: '/v1/search',\n query: ['name'],\n input: z.object({ name: z.string() }),\n output: z.object({\n latitude: z.number(),\n longitude: z.number(),\n place: z.string().optional(),\n country: z.string().optional(),\n }),\n response: {\n latitude: '${response.results[0].latitude}',\n longitude: '${response.results[0].longitude}',\n place: '${response.results[0].name}',\n country: '${response.results[0].country}',\n },\n },\n // A LIST-returning read. `${response.results}` binds the WHOLE array verbatim — a\n // variable-length list of place objects — with no pagination (Open-Meteo returns every match in\n // one page). Contrast the `search` op above, which indexes a single element (`results[0]`). To\n // reduce each element to a few fields, narrow it in the `geo_places` compute connector below: a\n // response mapping cannot iterate an array, and a tool's Zod output does not strip fields at\n // runtime.\n search_list: {\n type: 'read',\n method: 'GET',\n path: '/v1/search',\n query: ['name', 'count'],\n // This endpoint is intentionally small; tighten its allowance below the 1 MiB default.\n limits: { maxResponseBytes: 256 * 1024 },\n input: z.object({ name: z.string(), count: z.number().optional() }),\n output: z.object({ results: z.array(z.unknown()).optional() }),\n response: {\n results: '${response.results}',\n },\n },\n },\n });\n\nconst forecast = connector('open_meteo_forecast')\n .version('1.0.0')\n .http({\n baseUrl: 'https://api.open-meteo.com',\n allowedOrigins: ['https://api.open-meteo.com'],\n operations: {\n current: {\n type: 'read',\n method: 'GET',\n path: '/v1/forecast?current_weather=true',\n query: ['latitude', 'longitude'],\n input: z.object({ latitude: z.number(), longitude: z.number() }),\n output: z.object({\n temperature: z.number().optional(),\n windspeed: z.number().optional(),\n weathercode: z.number().optional(),\n }),\n response: {\n temperature: '${response.current_weather.temperature}',\n windspeed: '${response.current_weather.windspeed}',\n weathercode: '${response.current_weather.weathercode}',\n },\n },\n },\n });\n\nconst brief = connector('weather_brief')\n .version('1.0.0')\n .compute('summarize', {\n type: 'read',\n input: z.object({\n place: z.string(),\n country: z.string().optional(),\n temperature: z.number(),\n windspeed: z.number(),\n weathercode: z.number(),\n }),\n output: z.object({\n conditions: z.string(),\n headline: z.string(),\n advice: z.string(),\n }),\n // A real function — type-checked here, serialized to source and run in the sandbox. It must be\n // self-contained: no imports, no closure over outer variables, synchronous.\n run: (input) => {\n const codes: Record<number, string> = {\n 0: 'clear sky',\n 1: 'mainly clear',\n 2: 'partly cloudy',\n 3: 'overcast',\n 45: 'fog',\n 48: 'depositing rime fog',\n 51: 'light drizzle',\n 53: 'moderate drizzle',\n 55: 'dense drizzle',\n 61: 'slight rain',\n 63: 'moderate rain',\n 65: 'heavy rain',\n 71: 'slight snow',\n 73: 'moderate snow',\n 75: 'heavy snow',\n 77: 'snow grains',\n 80: 'slight rain showers',\n 81: 'moderate rain showers',\n 82: 'violent rain showers',\n 85: 'slight snow showers',\n 86: 'heavy snow showers',\n 95: 'thunderstorm',\n 96: 'thunderstorm with hail',\n 99: 'thunderstorm with heavy hail',\n };\n const code = Number(input.weathercode);\n const conditions = codes[code] || 'unknown conditions';\n const temp = Math.round(Number(input.temperature));\n const wind = Math.round(Number(input.windspeed));\n const where = input.country ? `${input.place}, ${input.country}` : input.place;\n const headline = `${where}: ${temp}°C, ${conditions}.`;\n const tips: string[] = [];\n if (temp <= 0) tips.push(\"bundle up, it's freezing\");\n else if (temp <= 10) tips.push('wear a warm coat');\n else if (temp >= 28) tips.push(\"stay hydrated, it's hot\");\n if (code >= 95) tips.push('thunderstorms expected — seek shelter');\n else if (code >= 71 && code <= 86 && code !== 80 && code !== 81 && code !== 82)\n tips.push('snow — dress warm and tread carefully');\n else if (code >= 51 && code <= 82) tips.push('bring an umbrella');\n if (wind >= 30) tips.push('expect strong winds');\n const advice = tips.length\n ? `${tips.join('; ')}.`\n : 'Comfortable conditions — no special prep needed.';\n return { conditions, headline, advice };\n },\n });\n\n// Narrowing a live list to `{ id, label }` summaries is the ONE reshape a response mapping cannot do\n// (the `${...}` language has no per-item iteration) and a tool's Zod output does not enforce at runtime\n// — so it happens here, in a sandboxed compute connector (a connector is HTTP or compute, not both).\n// This also normalizes the no-results case (Open-Meteo omits `results` when nothing matches) to `[]`.\nconst placeNarrow = connector('geo_places')\n .version('1.0.0')\n .compute('narrow', {\n type: 'read',\n input: z.object({ results: z.unknown().optional() }),\n output: z.object({ places: z.array(z.unknown()) }),\n // Self-contained: no imports, no closure over outer variables, synchronous.\n run: (input) => {\n const raw = input.results;\n const list = Array.isArray(raw) ? raw : [];\n const places = list.map((entry) => {\n const parts = [entry.name, entry.admin1, entry.country].filter(\n (part) => typeof part === 'string' && part.length > 0,\n );\n const id =\n entry.id !== undefined && entry.id !== null\n ? String(entry.id)\n : `${entry.latitude},${entry.longitude}`;\n return { id, label: parts.join(', ') };\n });\n return { places };\n },\n });\n\nexport default server(\n 'weather_briefing',\n {\n title: 'Weather Briefing',\n version: '1.0.0',\n use: { geo: geocoding, forecast, brief, places: placeNarrow },\n branding: {\n name: 'Weather Briefing',\n accent: '#0284C7',\n radius: 'md',\n density: 'comfortable',\n },\n },\n [\n tool('weather_briefing', {\n title: 'Weather briefing',\n description:\n 'Look up a city, fetch its current weather, and return a human-readable briefing. Runs a ' +\n 'three-step flow: geocode the city, fetch the forecast, then derive the briefing in a sandboxed compute step.',\n input: z.object({\n city: z.string(),\n }),\n output: z.object({\n place: z.string(),\n country: z.string(),\n temperature_c: z.number(),\n windspeed_kmh: z.number(),\n conditions: z.string(),\n headline: z.string(),\n advice: z.string(),\n }),\n fulfil: ({ input, connectors }) => {\n const located = connectors.geo.search({ name: input.city });\n const weather = connectors.forecast.current({\n latitude: located.latitude,\n longitude: located.longitude,\n });\n const briefing = connectors.brief.summarize({\n place: located.place,\n country: located.country,\n temperature: weather.temperature,\n windspeed: weather.windspeed,\n weathercode: weather.weathercode,\n });\n return {\n place: located.place,\n country: located.country,\n temperature_c: weather.temperature,\n windspeed_kmh: weather.windspeed,\n conditions: briefing.conditions,\n headline: briefing.headline,\n advice: briefing.advice,\n };\n },\n }),\n // A connector that returns a live, variable-length LIST: search a place name, get back the\n // matching locations as `{ id, label }` options the model can resolve against. The HTTP op binds\n // the whole array; the compute connector narrows each element to the two fields the model speaks\n // from. Append new tools AFTER existing ones so `tools[0]` stays stable for host harnesses.\n tool('search_places', {\n title: 'Search places',\n description:\n 'Search a place name and return the matching locations as a list of { id, label } options.',\n // Bound the list at the source: `limit` is capped in the schema and passed through to the\n // upstream `count` parameter, so the model can never pull an unbounded page into its context.\n // `noodle check` reports an unbounded array output as `tool_design_output_bounds`.\n input: z.object({\n query: z.string(),\n limit: z.number().int().min(1).max(10).default(5),\n }),\n output: z.object({\n places: z.array(z.object({ id: z.string(), label: z.string() })),\n }),\n fulfil: ({ input, connectors }) => {\n const found = connectors.geo.search_list({ name: input.query, count: input.limit });\n const narrowed = connectors.places.narrow({ results: found.results });\n return { places: narrowed.places };\n },\n }),\n ],\n);\n" },
110
+ { relPath: "examples/weather/src/server.ts", content: "import { connector, server, tool, z } from '@noodleseed/one';\n\n// The same Weather Briefing server, authored in TypeScript with the Noodle authoring SDK.\n//\n// The SDK owns the *manifest*: the tool, its Zod-typed input/output schemas, and the flow — which you\n// write as ordinary code in `fulfil` and the SDK records symbolically into ordered steps.\n//\n// HTTP and compute connectors are authored here too, so the public developer entrypoint is one\n// self-contained server.ts. The SDK still compiles this to internal manifest/catalog data for the runtime.\n\nconst geocoding = connector('open_meteo_geocoding')\n .version('1.0.0')\n .http({\n baseUrl: 'https://geocoding-api.open-meteo.com',\n allowedOrigins: ['https://geocoding-api.open-meteo.com'],\n operations: {\n search: {\n type: 'read',\n method: 'GET',\n path: '/v1/search',\n query: ['name'],\n input: z.object({ name: z.string() }),\n output: z.object({\n latitude: z.number(),\n longitude: z.number(),\n place: z.string().optional(),\n country: z.string().optional(),\n }),\n response: {\n latitude: '${response.results[0].latitude}',\n longitude: '${response.results[0].longitude}',\n place: '${response.results[0].name}',\n country: '${response.results[0].country}',\n },\n },\n // A LIST-returning read. `${response.results}` binds the WHOLE array verbatim — a\n // variable-length list of place objects — with no pagination (Open-Meteo returns every match in\n // one page). Contrast the `search` op above, which indexes a single element (`results[0]`). To\n // reduce each element to a few fields, narrow it in the `geo_places` compute connector below: a\n // response mapping cannot iterate an array, and a tool's Zod output does not strip fields at\n // runtime.\n search_list: {\n type: 'read',\n method: 'GET',\n path: '/v1/search',\n query: ['name', 'count'],\n // This endpoint is intentionally small; tighten its allowance below the 1 MiB default.\n limits: { maxResponseBytes: 256 * 1024 },\n input: z.object({ name: z.string(), count: z.number().optional() }),\n output: z.object({ results: z.array(z.unknown()).optional() }),\n response: {\n results: '${response.results}',\n },\n },\n },\n });\n\nconst forecast = connector('open_meteo_forecast')\n .version('1.0.0')\n .http({\n baseUrl: 'https://api.open-meteo.com',\n allowedOrigins: ['https://api.open-meteo.com'],\n operations: {\n current: {\n type: 'read',\n method: 'GET',\n path: '/v1/forecast?current_weather=true',\n query: ['latitude', 'longitude'],\n input: z.object({ latitude: z.number(), longitude: z.number() }),\n output: z.object({\n temperature: z.number().optional(),\n windspeed: z.number().optional(),\n weathercode: z.number().optional(),\n }),\n response: {\n temperature: '${response.current_weather.temperature}',\n windspeed: '${response.current_weather.windspeed}',\n weathercode: '${response.current_weather.weathercode}',\n },\n },\n },\n });\n\nconst brief = connector('weather_brief')\n .version('1.0.0')\n .compute('summarize', {\n type: 'read',\n input: z.object({\n place: z.string(),\n country: z.string().optional(),\n temperature: z.number(),\n windspeed: z.number(),\n weathercode: z.number(),\n }),\n output: z.object({\n conditions: z.string(),\n headline: z.string(),\n advice: z.string(),\n }),\n // A real function — type-checked here, serialized to source and run in the sandbox. It must be\n // self-contained: no imports, no closure over outer variables, synchronous.\n run: (input) => {\n const codes: Record<number, string> = {\n 0: 'clear sky',\n 1: 'mainly clear',\n 2: 'partly cloudy',\n 3: 'overcast',\n 45: 'fog',\n 48: 'depositing rime fog',\n 51: 'light drizzle',\n 53: 'moderate drizzle',\n 55: 'dense drizzle',\n 61: 'slight rain',\n 63: 'moderate rain',\n 65: 'heavy rain',\n 71: 'slight snow',\n 73: 'moderate snow',\n 75: 'heavy snow',\n 77: 'snow grains',\n 80: 'slight rain showers',\n 81: 'moderate rain showers',\n 82: 'violent rain showers',\n 85: 'slight snow showers',\n 86: 'heavy snow showers',\n 95: 'thunderstorm',\n 96: 'thunderstorm with hail',\n 99: 'thunderstorm with heavy hail',\n };\n const code = Number(input.weathercode);\n const conditions = codes[code] || 'unknown conditions';\n const temp = Math.round(Number(input.temperature));\n const wind = Math.round(Number(input.windspeed));\n const where = input.country ? `${input.place}, ${input.country}` : input.place;\n const headline = `${where}: ${temp}°C, ${conditions}.`;\n const tips: string[] = [];\n if (temp <= 0) tips.push(\"bundle up, it's freezing\");\n else if (temp <= 10) tips.push('wear a warm coat');\n else if (temp >= 28) tips.push(\"stay hydrated, it's hot\");\n if (code >= 95) tips.push('thunderstorms expected — seek shelter');\n else if (code >= 71 && code <= 86 && code !== 80 && code !== 81 && code !== 82)\n tips.push('snow — dress warm and tread carefully');\n else if (code >= 51 && code <= 82) tips.push('bring an umbrella');\n if (wind >= 30) tips.push('expect strong winds');\n const advice = tips.length\n ? `${tips.join('; ')}.`\n : 'Comfortable conditions — no special prep needed.';\n return { conditions, headline, advice };\n },\n });\n\n// Narrowing a live list to `{ id, label }` summaries is the ONE reshape a response mapping cannot do\n// (the `${...}` language has no per-item iteration) and a tool's Zod output does not enforce at runtime\n// — so it happens here, in a sandboxed compute connector (a connector is HTTP or compute, not both).\n// This also normalizes the no-results case (Open-Meteo omits `results` when nothing matches) to `[]`.\nconst placeNarrow = connector('geo_places')\n .version('1.0.0')\n .compute('narrow', {\n type: 'read',\n input: z.object({ results: z.unknown().optional() }),\n output: z.object({ places: z.array(z.unknown()) }),\n // Synchronous and self-contained.\n run: (input, host) => {\n const raw = input.results;\n const list = Array.isArray(raw) ? raw : [];\n const places = list.map((entry) => {\n const parts = [entry.name, entry.admin1, entry.country].filter(\n (part) => typeof part === 'string' && part.length > 0,\n );\n const id =\n entry.id !== undefined && entry.id !== null\n ? String(entry.id)\n : host.digest(`${entry.latitude},${entry.longitude}`);\n return { id, label: parts.join(', ') };\n });\n return { places };\n },\n });\n\nexport default server(\n 'weather_briefing',\n {\n title: 'Weather Briefing',\n version: '1.0.0',\n use: { geo: geocoding, forecast, brief, places: placeNarrow },\n branding: {\n name: 'Weather Briefing',\n accent: '#0284C7',\n radius: 'md',\n density: 'comfortable',\n },\n },\n [\n tool('weather_briefing', {\n title: 'Weather briefing',\n description:\n 'Look up a city, fetch its current weather, and return a human-readable briefing. Runs a ' +\n 'three-step flow: geocode the city, fetch the forecast, then derive the briefing in a sandboxed compute step.',\n input: z.object({\n city: z.string(),\n }),\n output: z.object({\n place: z.string(),\n country: z.string(),\n temperature_c: z.number(),\n windspeed_kmh: z.number(),\n conditions: z.string(),\n headline: z.string(),\n advice: z.string(),\n }),\n fulfil: ({ input, connectors }) => {\n const located = connectors.geo.search({ name: input.city });\n const weather = connectors.forecast.current({\n latitude: located.latitude,\n longitude: located.longitude,\n });\n const briefing = connectors.brief.summarize({\n place: located.place,\n country: located.country,\n temperature: weather.temperature,\n windspeed: weather.windspeed,\n weathercode: weather.weathercode,\n });\n return {\n place: located.place,\n country: located.country,\n temperature_c: weather.temperature,\n windspeed_kmh: weather.windspeed,\n conditions: briefing.conditions,\n headline: briefing.headline,\n advice: briefing.advice,\n };\n },\n }),\n // A connector that returns a live, variable-length LIST: search a place name, get back the\n // matching locations as `{ id, label }` options the model can resolve against. The HTTP op binds\n // the whole array; the compute connector narrows each element to the two fields the model speaks\n // from. Append new tools AFTER existing ones so `tools[0]` stays stable for host harnesses.\n tool('search_places', {\n title: 'Search places',\n description:\n 'Search a place name and return the matching locations as a list of { id, label } options.',\n // Bound the list at the source: `limit` is capped in the schema and passed through to the\n // upstream `count` parameter, so the model can never pull an unbounded page into its context.\n // `noodle check` reports an unbounded array output as `tool_design_output_bounds`.\n input: z.object({\n query: z.string(),\n limit: z.number().int().min(1).max(10).default(5),\n }),\n output: z.object({\n places: z.array(z.object({ id: z.string(), label: z.string() })),\n }),\n fulfil: ({ input, connectors }) => {\n const found = connectors.geo.search_list({ name: input.query, count: input.limit });\n const narrowed = connectors.places.narrow({ results: found.results });\n return { places: narrowed.places };\n },\n }),\n ],\n);\n" },
111
111
  { relPath: "examples/weather/test/server.test.ts", content: "import { describe, expect, it } from 'vitest';\nimport app from '../src/server.js';\n\ndescribe('weather example', () => {\n it('exports a Noodle server definition', () => {\n expect(typeof app.toManifest).toBe('function');\n });\n\n it('adds a list-returning search_places tool without disturbing tool order', async () => {\n const manifest = (await app.toManifest()) as {\n tools: ReadonlyArray<{ name: string }>;\n connectors?: Record<string, { id: string; version: string }>;\n };\n const toolNames = manifest.tools.map((t) => t.name);\n // The original briefing tool stays first — host harnesses (the online e2e) read `tools[0]`,\n // so new tools are appended, never prepended.\n expect(toolNames[0]).toBe('weather_briefing');\n expect(toolNames).toContain('search_places');\n expect(toolNames.indexOf('search_places')).toBeGreaterThan(\n toolNames.indexOf('weather_briefing'),\n );\n // The list is produced by a whole-array-bind HTTP op (`search_list`) narrowed to {id,label}\n // through a separate compute connector (`geo_places`).\n expect(manifest.connectors?.places).toEqual({ id: 'geo_places', version: '1.0.0' });\n const wire = JSON.stringify(manifest);\n expect(wire).toContain('search_list');\n expect(wire).toContain('narrow');\n });\n\n it('demonstrates an explicit least-privilege response-size bound', () => {\n const catalog = app.toConnectorCatalog();\n const geocoding = catalog?.connectors.find(\n (candidate) => candidate.id === 'open_meteo_geocoding',\n );\n\n expect(geocoding?.operations.search_list?.limits).toEqual({\n maxResponseBytes: 256 * 1024,\n });\n });\n});\n" },
112
112
  ];
113
113
  //# sourceMappingURL=example-files.js.map
@@ -159,6 +159,8 @@ export const COMPILE_ERROR_CODES = [
159
159
  'connector_not_in_catalog',
160
160
  'unknown_operation',
161
161
  'connector_binding_required',
162
+ 'ambiguous_nested_connector_binding',
163
+ 'invalid_connector_call_graph',
162
164
  'unsupported_credential_profile',
163
165
  'credential_scope_mismatch',
164
166
  'credential_audience_mismatch',
@@ -12,6 +12,7 @@ export * from './product-skill-ownership.js';
12
12
  export * from './product-skill-renderer.js';
13
13
  export * from './skill-registry.js';
14
14
  export { AGENT_KIT_VERSION } from './version.js';
15
+ export { NOODLE_WORDMARK } from './welcome-wordmark.js';
15
16
  export declare const MANAGED_BEGIN = "<!-- BEGIN NOODLE AGENT CONTEXT -->";
16
17
  export declare const MANAGED_END = "<!-- END NOODLE AGENT CONTEXT -->";
17
18
  export type AgentTargetSelection = AgentTarget | 'all' | 'none';
@@ -18,6 +18,7 @@ export * from './product-skill-ownership.js';
18
18
  export * from './product-skill-renderer.js';
19
19
  export * from './skill-registry.js';
20
20
  export { AGENT_KIT_VERSION } from './version.js';
21
+ export { NOODLE_WORDMARK } from './welcome-wordmark.js';
21
22
  export const MANAGED_BEGIN = '<!-- BEGIN NOODLE AGENT CONTEXT -->';
22
23
  export const MANAGED_END = '<!-- END NOODLE AGENT CONTEXT -->';
23
24
  const TARGETS = ['codex', 'claude-code'];
@@ -1,5 +1,6 @@
1
1
  import { contentHash } from './index.js';
2
2
  import { PLUGIN_WINDOWS_SUPPORT } from './plugin-platform-support.js';
3
+ import { NOODLE_WORDMARK } from './welcome-wordmark.js';
3
4
  /** The plugin identifier — matches the project-local skill used after bootstrap. */
4
5
  export const PLUGIN_NAME = 'noodle-seed';
5
6
  /** Cold-start discovery text shared by direct marketplace and official-directory projections. */
@@ -12,6 +13,15 @@ function bootstrapRouterBody() {
12
13
  '',
13
14
  'Noodle Seed turns one TypeScript file (`server.ts`) into a production MCP server or app: authored locally with the `noodle` CLI, validated and tested offline, and deployed to a governed hosted MCP endpoint reachable from supported AI clients and every MCP client. Use this skill whenever the user wants an MCP server or app, AI app or connector, or wants their product, API, or SaaS reachable by AI agents.',
14
15
  '',
16
+ '## First-use welcome',
17
+ '',
18
+ 'On first use of this plugin, show the following welcome to the user once per conversation, before project-local handoff or tool execution. Render the wordmark verbatim in a fenced text block in your conversational response, followed by the welcome sentence. Then continue the requested task immediately. Skip it if this conversation already contains the welcome, or the user requests machine-readable output or no branding. Never put the wordmark in command output or JSON, and never run an extra command just to display it. This is a first-use greeting, not evidence that installation, authentication, or setup succeeded.',
19
+ '',
20
+ '```text',
21
+ ...NOODLE_WORDMARK,
22
+ '```',
23
+ 'Welcome to Noodle Seed!',
24
+ '',
15
25
  '## Defer to the project-local skill',
16
26
  '',
17
27
  'Before cold-start work, check whether the active project already provides a project-local `noodle-seed` skill. When it exists, read it and follow it instead of this one. The project-local skill owns detailed commands, references, examples, and project defaults. Keep the execution transport rule below available when that route calls for a public `noodle` command.',
@@ -64,6 +64,9 @@ export function renderAuthoringWorkflowReference() {
64
64
  '- **HTTP**: `connector("id").version("1.0.0").http({ baseUrl, allowedOrigins, auth, operations })`; map request/response with `${args...}` / `${response...}`. Use `${execution.id}` for provider idempotency, never model input. Optional `evidence: { outcome: "${response.execution_outcome}", reference: "${response.id}" }` classifies completed/rejected/accepted/unknown; reference is a bounded opaque ID, never a bearer URL or payload. No automatic action retry.',
65
65
  '- **MCP**: `connector("id").version("1.0.0").mcp({ endpoint, allowedOrigins, auth?, operations })` where each operation freezes the separate upstream `tool` wire name plus input/output schema. Import with `noodle import mcp`; do not hand-copy a live surface or call `tools/list` at runtime.',
66
66
  '- **Compute**: `connector("id").version("1.0.0").compute(name, { input, output, calls?, run })` — a self-contained, sandboxed function (no imports/closure capture) that may call allowlisted operations via `callOperation`.',
67
+ '- **Explicit helpers**: `run: (input, host) => ...` can use `host.time.parse(iso)`, `host.time.format(epochMs)`, `host.time.parts(epochMs, timeZone)` and `host.digest(text, "hex")` (or `"base32hex"`). They convert bounded explicit data; there is no ambient clock. Pass trusted `context.temporal.instant` through fulfilment when current time is needed. `examples/weather` demonstrates a stable digest fallback for provider records without IDs.',
68
+ '- **Expected HTTP errors**: declare `responses: { "409": { response: { status: "conflict" }, evidence: { outcome: "rejected" } } }` alongside the ordinary success `response`. Explicit 4xx overrides exclude 401/403/429; validate against the same output schema. Undeclared errors still fail. Overrides never inherit successful completion evidence or introduce action retries.',
69
+ '- **Coordinated external actions**: a compute action may declare `coordination: { connectionId, namespace, key: "${args.resource}", reference: "${execution.id}" }` with a bounded execution deadline. It requires an installed application with a live bound connection and durable service coordination. Read `host.coordination.acquired` before writing; a blocked invocation may inspect `previous` through a declared read and call `host.resolveCoordination()` only after exact source proof, then require a fresh invocation/confirmation. The runtime permits at most one nested action when acquired and zero when blocked, even after recovery. Report explicit completed/rejected/unknown evidence with `host.reportOutcome(...)`; a successful return alone never unlocks uncertainty. Do not create an external-record collection for this.',
67
70
  '',
68
71
  'Tools record connector calls into a flow; recording is not execution. Do not branch on runtime outputs with native `if` — use declarative `when(...)` conditions.',
69
72
  '',
@@ -221,7 +224,7 @@ export function renderAuthoringWorkflowReference() {
221
224
  '',
222
225
  'Author managed config as `secret("NAME")` / `variable("NAME")` and operate it with `noodle secrets set` / `noodle variables set` (scoped org/app/env). Never inline secret values in `server.ts`, tests, or generated files.',
223
226
  '',
224
- 'For business-editable configuration, declare `const notice = variable("SERVICE_NOTICE", { schema: z.string().max(500), default: "Welcome", portal: { label: "Service notice", group: "Guest experience" }, requiredFor: ["show_menu"] })` and register it in `server(..., { variables: [notice], ... }, tools)`. Use the same ref in ordinary fulfilment/connector arguments. The default is reusable safe intent; each business supplies its own values without editing source. Only explicit `portal` metadata exposes a setting. Name-only references and declared variables without `portal` remain technical configuration; secrets remain credential slots. See the bundled `acme-bistro` source.',
227
+ 'For business-editable configuration, declare `const guestExperience = variable("GUEST_EXPERIENCE", { schema: z.object({ notice: z.string().max(500) }), default: { notice: "Welcome" }, portal: { label: "Guest experience" }, requiredFor: ["show_menu"] })` and register it in `server(..., { variables: [guestExperience], ... }, tools)`. Use the whole ref or `guestExperience.field("notice")` in ordinary fulfilment/connector arguments. `.field()` selects a schema-declared object property, can chain for nested objects, and retains the parent variable and full configuration snapshot; it never reads operator data at author time. Keep confirmed action arguments shallow enough for complete review; do not label ordinary settings sensitive to bypass the review. The default is reusable safe intent; each business supplies its own values without editing source. Only explicit `portal` metadata exposes a setting. Name-only references and declared variables without `portal` remain technical configuration; secrets remain credential slots. See the bundled `acme-bistro` source.',
225
228
  '',
226
229
  'Business schemas must be bounded: booleans, finite bounded numbers, bounded text, string enums, bounded arrays, and closed objects. Put defaults in the declaration, not inside Zod schema defaults; custom transforms/refinements and arbitrary schema code cannot run in the shared runtime. `requiredFor` names existing tools whose invocation needs the value; unresolved settings must leave only dependent capabilities unavailable. Publisher compilation does not require a future buyer’s values. Application code enforces business rules server-side; exposing a control or placing the rule in a prompt is insufficient.',
227
230
  '',
@@ -0,0 +1,3 @@
1
+ /** Original Noodle Seed block wordmark, shared by terminal and plugin onboarding. */
2
+ export declare const NOODLE_WORDMARK: readonly ["███╗ ██╗ ██████╗ ██████╗ ██████╗ ██╗ ███████╗ ███████╗███████╗███████╗██████╗", "████╗ ██║██╔═══██╗██╔═══██╗██╔══██╗██║ ██╔════╝ ██╔════╝██╔════╝██╔════╝██╔══██╗", "██╔██╗ ██║██║ ██║██║ ██║██║ ██║██║ █████╗ ███████╗█████╗ █████╗ ██║ ██║", "██║╚██╗██║██║ ██║██║ ██║██║ ██║██║ ██╔══╝ ╚════██║██╔══╝ ██╔══╝ ██║ ██║", "██║ ╚████║╚██████╔╝╚██████╔╝██████╔╝███████╗███████╗ ███████║███████╗███████╗██████╔╝", "╚═╝ ╚═══╝ ╚═════╝ ╚═════╝ ╚═════╝ ╚══════╝╚══════╝ ╚══════╝╚══════╝╚══════╝╚═════╝"];
3
+ //# sourceMappingURL=welcome-wordmark.d.ts.map
@@ -0,0 +1,10 @@
1
+ /** Original Noodle Seed block wordmark, shared by terminal and plugin onboarding. */
2
+ export const NOODLE_WORDMARK = [
3
+ '███╗ ██╗ ██████╗ ██████╗ ██████╗ ██╗ ███████╗ ███████╗███████╗███████╗██████╗',
4
+ '████╗ ██║██╔═══██╗██╔═══██╗██╔══██╗██║ ██╔════╝ ██╔════╝██╔════╝██╔════╝██╔══██╗',
5
+ '██╔██╗ ██║██║ ██║██║ ██║██║ ██║██║ █████╗ ███████╗█████╗ █████╗ ██║ ██║',
6
+ '██║╚██╗██║██║ ██║██║ ██║██║ ██║██║ ██╔══╝ ╚════██║██╔══╝ ██╔══╝ ██║ ██║',
7
+ '██║ ╚████║╚██████╔╝╚██████╔╝██████╔╝███████╗███████╗ ███████║███████╗███████╗██████╔╝',
8
+ '╚═╝ ╚═══╝ ╚═════╝ ╚═════╝ ╚═════╝ ╚══════╝╚══════╝ ╚══════╝╚══════╝╚══════╝╚═════╝',
9
+ ];
10
+ //# sourceMappingURL=welcome-wordmark.js.map
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@noodle-borg/agent-kit",
3
- "version": "0.100.0",
3
+ "version": "0.101.0",
4
4
  "license": "Apache-2.0",
5
5
  "type": "module",
6
6
  "engines": {
@@ -70,6 +70,8 @@ export interface PublicEmbedStore {
70
70
  readonly env: string;
71
71
  readonly surfaceMode: 'public' | 'mixed';
72
72
  readonly now: Date;
73
+ /** Installation recovery preserves revocation; explicit redeploy may replace it by default. */
74
+ readonly allowRevokedReplacement?: boolean;
73
75
  }): Promise<PublicEmbedRecord>;
74
76
  /** Resolve an id presented by a browser. Revoked ids resolve to undefined. */
75
77
  lookup(embedId: string): Promise<PublicEmbedRecord | undefined>;
@@ -82,6 +84,8 @@ export interface PublicEmbedStore {
82
84
  readonly org: string;
83
85
  readonly app: string;
84
86
  readonly env: string;
87
+ }, options?: {
88
+ readonly includeRevoked?: boolean;
85
89
  }): Promise<readonly PublicEmbedRecord[]>;
86
90
  revoke(embedId: string, now: Date): Promise<boolean>;
87
91
  }
@@ -15,6 +15,8 @@ export declare class InMemoryPublicEmbedStore implements PublicEmbedStore {
15
15
  readonly env: string;
16
16
  readonly surfaceMode: 'public' | 'mixed';
17
17
  readonly now: Date;
18
+ /** Installation recovery preserves revocation; explicit redeploy may replace it by default. */
19
+ readonly allowRevokedReplacement?: boolean;
18
20
  }): Promise<PublicEmbedRecord>;
19
21
  setBudget(embedId: string, budget: PublicEmbedBudget, _now: Date): Promise<PublicEmbedRecord | undefined>;
20
22
  lookup(embedId: string): Promise<PublicEmbedRecord | undefined>;
@@ -22,6 +24,8 @@ export declare class InMemoryPublicEmbedStore implements PublicEmbedStore {
22
24
  readonly org: string;
23
25
  readonly app: string;
24
26
  readonly env: string;
27
+ }, options?: {
28
+ readonly includeRevoked?: boolean;
25
29
  }): Promise<readonly PublicEmbedRecord[]>;
26
30
  revoke(embedId: string, now: Date): Promise<boolean>;
27
31
  }