@aotter/mantle 0.1.5-alpha.1 → 0.2.0-alpha.1

package/docs/design-references/editorial-blog-2026-05-05.md

@@ -1,218 +0,0 @@
-# Editorial Blog Design Reference (2026-05-05)
-
-This document preserves the visual system from the retired
-`blog-editorial-2026-05-05` starter. The runnable starter was removed because
-it looked like a maintained template, but the design work is still useful as a
-reference for future themes.
-
-Use this as a design specimen, not as implementation guidance. Apply it through
-the version-matched `mantle:theme` workflow and the generated project's owned
-theme paths, such as `styles/globals.css`, `components/`, and `src/web/`.
-
-## Design Thesis
-
-The direction was a quiet literary journal: warm paper, dark ink, a narrow
-reading measure, editorial serif typography, and one vermilion accent. The UI
-avoided dashboard styling and treated the site chrome as magazine furniture:
-small caps, rules, careful spacing, and minimal controls.
-
-The design was intentionally opinionated. That is why it should be reused as a
-theme preset or design prompt, not shipped as the default blog starter.
-
-## Visual Tokens
-
-| Token | Light | Dark | Role |
-|---|---:|---:|---|
-| `paper` | `#f6f1e7` | `#1a1814` | Page background |
-| `ink` | `#1a1814` | `#f1ebdf` | Primary text |
-| `rule` | `#d4c8b3` | `#3d342a` | Hairlines, subtle borders |
-| `rule-strong` | `#3d342a` | `#5a4d40` | Form underlines, stronger separators |
-| `mute` | `#7a6d5e` | `#9a8d7e` | Metadata and secondary copy |
-| `accent` | `#a3331f` | `#e6594a` | Links, drop caps, error states, preview banner |
-| `accent-soft` | `#c9614a` | `#c9614a` | Secondary accent |
-| `selection` | `#f0d6a3` | `#4a3520` | Text selection background |
-
-Layout tokens:
-
-| Token | Value | Role |
-|---|---:|---|
-| `measure` | `38rem` | Main article measure |
-| `main max-width` | `48rem` | Single-column shell, slightly wider than the article |
-| `gutter` | `clamp(1.25rem, 4vw, 3rem)` | Responsive page padding |
-| `base font size` | `18px` | Reading-first default |
-| `line height` | `1.65` | Long-form prose rhythm |
-
-## Typography
-
-The type system used four families:
-
-| Use | Font stack |
-|---|---|
-| Display | `Fraunces`, `Noto Serif TC`, `Source Serif 4`, `Georgia`, `serif` |
-| Body | `Source Serif 4`, `Noto Serif TC`, `Georgia`, `serif` |
-| Mono/meta | `JetBrains Mono`, `ui-monospace`, `SF Mono`, `Menlo`, `monospace` |
-| CJK fallback | `Noto Serif TC` |
-
-Important behaviors:
-
-- Body text enables `kern`, `liga`, and `onum`.
-- Headings use Fraunces variable optical sizing with `opsz` and `SOFT`.
-- `h1` scales from `2.2rem` to `3.4rem`; hero `h1` scales up to `4rem`.
-- Metadata uses JetBrains Mono at `0.75rem`, uppercase, and `0.04em` tracking.
-- Paragraphs indent after the first paragraph with `p + p { text-indent: 1.5em; }`.
-- Post bodies reset the first paragraph indent and add a vermilion drop cap.
-
-## Page Chrome
-
-Header:
-
-- Sticky top header with a one-pixel rule.
-- Warm translucent paper background using `color-mix`, `saturate(140%)`, and
-  `blur(10px)`.
-- Wordmark uses display serif and inserts a vermilion middle dot between the
-  first word and the remaining brand words.
-- Navigation is centered, uppercase, display serif, and tracked at `0.18em`.
-- Current nav item is shown by a one-pixel underline in `ink`; hover uses
-  `accent`.
-
-Controls:
-
-- Language and theme are small popovers in the header.
-- Popover trigger typography follows mono/meta styling.
-- The language trigger shows a globe icon, full locale label, and chevron.
-- The theme trigger is icon-only and supports system, light, and dark.
-- Menu items use `menuitemradio` semantics and show a check icon for the active
-  value.
-- Popovers close on outside click and `Escape`.
-
-Footer:
-
-- One-pixel top rule.
-- Mono text at `0.75rem`.
-- Left side shows `site.brand` and `site.description`.
-- Right side links to `mantle`.
-
-## Templates
-
-Home:
-
-- Starts with a `hero` block: mono eyebrow, large display title, muted intro,
-  and markdown body.
-- Recent posts appear below the hero as an `entry-list`.
-
-Post:
-
-- Uses a narrow `article` measure.
-- Header contains optional publish date and title.
-- Optional cover image is bordered by `rule`.
-- Body markdown supports headings, blockquotes, inline code, code blocks, and
-  lists.
-- First body paragraph gets an editorial drop cap.
-
-Post list:
-
-- Reuses the hero grammar with an index eyebrow.
-- Entries render as a two-column grid: fixed `7rem` date rail plus flexible
-  title/excerpt column.
-- On narrow screens, entries collapse to one column.
-
-Page:
-
-- Same article shell as posts.
-- Uses page `intro` as muted mono metadata under the title.
-- `about` and `contact` slugs drive active nav hints.
-
-Contact:
-
-- Article intro and body are followed by a vertical form.
-- Field labels are uppercase mono.
-- Text inputs use underline-only styling; textarea uses a bordered box.
-- Submit button uses display serif, uppercase tracking, and an inverted
-  `ink`/`paper` fill.
-- Cloudflare Turnstile is mounted explicitly so it can re-render when the site
-  theme changes.
-
-404:
-
-- Centered block with a huge display-serif `404` glyph in `accent`.
-- Copy follows the same i18n bundle pattern as the rest of the chrome.
-
-## Interaction Model
-
-Theme preference is a three-way choice:
-
-- `system`: no stored value, follows `prefers-color-scheme`.
-- `light`: explicit localStorage override.
-- `dark`: explicit localStorage override.
-
-A bootstrap script runs in `<head>` before paint to avoid theme flash. Runtime
-theme changes dispatch a `mantle:theme` event. The contact page listens to that
-event and re-renders Turnstile with the resolved light/dark value.
-
-Language switching rewrites the leading locale segment in the current path. It
-does not translate content itself; it navigates to the equivalent route under
-the selected locale.
-
-## I18n Surface
-
-The archived design included two UI bundles:
-
-| Locale | Label |
-|---|---|
-| `en` | `English` |
-| `zh-TW` | `繁體中文` |
-
-The bundles covered:
-
-- Header labels: posts, about, contact.
-- Theme labels: auto, light, dark.
-- Language aria label.
-- Home and post-list eyebrows.
-- 404 title, body, and return link.
-- Contact labels, submit states, success message, and error prefix.
-
-Content translations were intentionally separate from UI chrome translations.
-Posts and pages came from CMS entries; nav and form labels came from the local
-i18n bundles.
-
-## Icons
-
-The icon system was deliberately tiny:
-
-- Inline SVG strings injected by templates.
-- Monochrome `currentColor` stroke.
-- Default size `16`.
-- Default stroke width `2`, with check icons at `2.5`.
-- No runtime icon dependency until the set grows beyond roughly 20 icons.
-
-The archived set included `sun`, `moon`, `monitor`, `globe`,
-`chevron-down`, `check`, `menu`, and `x`.
-
-## Reuse With The Current Theme Stack
-
-Map the design into the maintained starter layers instead of reviving the old
-runnable starter:
-
-| Current layer | What to reuse |
-|---|---|
-| L1 tokens | Colors, font stacks, measure, gutter, base rhythm |
-| L2 components | Popover styling, entry list, post body, drop cap, contact form |
-| L3 slots | Header, footer, language switcher, theme switcher |
-| L4 templates | Home, post, post list, page, contact, 404 composition |
-
-Do not copy the old package metadata, Wrangler config, fixtures, workspace
-dependencies, or smoke tests. Those belonged to the removed runnable starter and
-will drift from the maintained SDK packages.
-
-## If Reviving This Direction
-
-Revive it as one of these:
-
-- A documented visual preset selectable during agent seeding.
-- A project-owned theme preset applied through `mantle:theme`.
-- A generated design prompt that tells the provisioning agent how to style a
-  user's own brand.
-
-Do not bring it back as a runnable starter in this SDK repository. Agents treat
-runnable code as current product surface, so the preserved design belongs only
-in this reference.

package/docs/direct-authoring.md

@@ -1,5 +0,0 @@
-# Direct authoring
-
-This guide moved into the handbook: [`docs/handbook/start/project-and-cli.md`](handbook/start/project-and-cli.md).
-
-The handbook ships inside the `@aotter/mantle` package under `node_modules/@aotter/mantle/docs/handbook/` and describes the installed release.

package/docs/examples/builtin-commerce.md

@@ -1,269 +0,0 @@
----
-description: A product catalog and guest orders using only builtin create and update. No Durable Object, Queue, payment provider, or ref handlers.
----
-# Commerce catalog and orders
-
-**Handler class:** builtin · **Builder:** yes · [Examples hub](./README.md). Stock authority, Queue expiry, and a verified payment callback are [Commerce inventory](./cf-primitives-commerce-inventory.md).
-
-This example publishes products, lists them publicly, accepts guest orders with builtin `create`, and lets staff mark orders fulfilled or cancelled with builtin `update`. Every Procedure is `handler.kind: builtin`. It does not re-price lines, reserve stock, or talk to a payment provider.
-
-## Problem
-
-Staff publish products with a price. A guest places an order by sending customer fields, an order number, currency, a total, and line items. Staff see submitted orders and record fulfillment or cancellation. Mantle stores the catalog and the order rows. There is no inventory authority in this Manifest.
-
-## Manifest
-
-```yaml
-apiVersion: cms.mantle.aotter.net/v1
-kind: Schema
-metadata:
-  name: products
-spec:
-  title: Products
-  lifecycle: publishing
-  uniqueIndexes:
-    - [slug]
-  schema:
-    type: object
-    additionalProperties: false
-    required: [slug, title, priceMinor, currency]
-    properties:
-      slug: { type: string, pattern: "^[a-z0-9-]+$" }
-      title: { type: string, minLength: 1, maxLength: 160 }
-      summary: { type: string, maxLength: 500 }
-      priceMinor: { type: integer, minimum: 0, x-mcp-hint: money-minor }
-      currency: { type: string, pattern: "^[A-Z]{3}$" }
----
-apiVersion: cms.mantle.aotter.net/v1
-kind: Schema
-metadata:
-  name: orders
-spec:
-  title: Orders
-  description: Guest orders created and updated only by declared builtin Procedures.
-  lifecycle: operational
-  uniqueIndexes:
-    - [orderNumber]
-  indexes:
-    - [orderStatus]
-  searchableFields: [orderNumber, customerName, customerEmail]
-  schema:
-    type: object
-    additionalProperties: false
-    required: [orderNumber, orderStatus, currency, totalMinor, customerName, customerEmail, shippingAddress, items, placedAt]
-    properties:
-      orderNumber: { type: string, minLength: 1, maxLength: 40 }
-      orderStatus: { type: string, enum: [submitted, fulfilled, cancelled] }
-      currency: { type: string, pattern: "^[A-Z]{3}$" }
-      totalMinor: { type: integer, minimum: 0, x-mcp-hint: money-minor }
-      customerName: { type: string, minLength: 1, maxLength: 120 }
-      customerEmail: { type: string, format: email }
-      shippingAddress: { type: string, minLength: 1, maxLength: 500 }
-      items:
-        type: array
-        minItems: 1
-        maxItems: 20
-        items:
-          type: object
-          additionalProperties: false
-          required: [productSlug, title, quantity, unitPriceMinor, lineTotalMinor]
-          properties:
-            productSlug: { type: string, pattern: "^[a-z0-9-]+$" }
-            title: { type: string }
-            quantity: { type: integer, minimum: 1, maximum: 99 }
-            unitPriceMinor: { type: integer, minimum: 0 }
-            lineTotalMinor: { type: integer, minimum: 0 }
-      trackingNumber: { type: string, maxLength: 120 }
-      cancelReason: { type: string, maxLength: 500 }
-      placedAt: { type: number, x-mcp-hint: timestamp-ms, x-mantle-bind: now }
----
-apiVersion: cms.mantle.aotter.net/v1
-kind: View
-metadata:
-  name: public-products
-spec:
-  title: Public products
-  surface: public
-  from: products
-  fields: [id, slug, title, summary, priceMinor, currency, updatedAt]
-  filter:
-    eq: { field: status, value: published }
-  orderBy:
-    - { field: slug, direction: asc }
-  limit: 100
----
-apiVersion: cms.mantle.aotter.net/v1
-kind: View
-metadata:
-  name: submitted-orders
-spec:
-  title: Submitted orders
-  surface: staff
-  from: orders
-  fields: [id, version, orderNumber, orderStatus, customerName, customerEmail, shippingAddress, totalMinor, currency, placedAt]
-  filter:
-    eq: { field: orderStatus, value: submitted }
-  orderBy:
-    - { field: placedAt, direction: asc }
-  limit: 100
----
-apiVersion: cms.mantle.aotter.net/v1
-kind: Procedure
-metadata:
-  name: place-order
-spec:
-  title: Place order
-  input:
-    type: object
-    additionalProperties: false
-    required: [orderNumber, orderStatus, currency, totalMinor, customerName, customerEmail, shippingAddress, items]
-    properties:
-      orderNumber: { type: string, minLength: 1, maxLength: 40 }
-      orderStatus: { type: string, enum: [submitted] }
-      currency: { type: string, pattern: "^[A-Z]{3}$" }
-      totalMinor: { type: integer, minimum: 0, x-mcp-hint: money-minor }
-      customerName: { type: string, minLength: 1, maxLength: 120 }
-      customerEmail: { type: string, format: email }
-      shippingAddress: { type: string, minLength: 1, maxLength: 500 }
-      items:
-        type: array
-        minItems: 1
-        maxItems: 20
-        items:
-          type: object
-          additionalProperties: false
-          required: [productSlug, title, quantity, unitPriceMinor, lineTotalMinor]
-          properties:
-            productSlug: { type: string, pattern: "^[a-z0-9-]+$" }
-            title: { type: string }
-            quantity: { type: integer, minimum: 1, maximum: 99 }
-            unitPriceMinor: { type: integer, minimum: 0 }
-            lineTotalMinor: { type: integer, minimum: 0 }
-  output: { type: object }
-  handler: { kind: builtin, op: create, schema: orders }
----
-apiVersion: cms.mantle.aotter.net/v1
-kind: Procedure
-metadata:
-  name: review-order
-spec:
-  title: Review order
-  requires:
-    auth:
-      all:
-        - { "ctx.staff": [owner, editor] }
-  input:
-    type: object
-    additionalProperties: false
-    required: [id, expectedVersion, orderStatus]
-    properties:
-      id: { type: string }
-      expectedVersion: { type: number, minimum: 1 }
-      orderStatus: { type: string, enum: [fulfilled, cancelled] }
-      trackingNumber: { type: string, maxLength: 120 }
-      cancelReason: { type: string, maxLength: 500 }
-  output: { type: object }
-  handler: { kind: builtin, op: update, schema: orders }
----
-apiVersion: cms.mantle.aotter.net/v1
-kind: Trigger
-metadata:
-  name: place-order-http
-spec:
-  source: { kind: http, method: POST, path: /api/commerce/orders }
-  target: { procedure: place-order }
----
-apiVersion: cms.mantle.aotter.net/v1
-kind: Trigger
-metadata:
-  name: place-order-mcp
-spec:
-  source: { kind: mcp, surface: public }
-  target: { procedure: place-order }
----
-apiVersion: cms.mantle.aotter.net/v1
-kind: Trigger
-metadata:
-  name: review-order-mcp
-spec:
-  source: { kind: mcp, surface: staff }
-  target: { procedure: review-order }
-```
-
-Points worth noticing:
-
-- `products` is a publishing Schema. Staff draft and publish through Admin or Staff MCP generic lifecycle tools. The public View filters `status: published`.
-- `orders` is operational. `place-order` is builtin `create`; `review-order` is builtin `update` with `id` and `expectedVersion` required. `placedAt` is server-stamped.
-- `orderStatus` on create is narrowed to `submitted`, so this Procedure cannot insert a fulfilled row. Staff `review-order` can only move a row to `fulfilled` or `cancelled`.
-- Line titles, unit prices and `totalMinor` are caller-supplied. This Manifest does not re-price from `products` and does not reserve stock.
-- `review-order` does not set `x-mantle-ref` on `id`. Drive reviews from `submitted-orders` (which exposes `id` and `version`) through Staff MCP or Admin operations. A lone `[orderNumber]` unique index would otherwise make Admin prefill `id` with the order number; see [Procurement approvals](./builtin-procurement.md).
-
-## Worker and handlers
-
-None. Both Procedures are builtin:
-
-```ts
-import { createMantleWorker } from "@aotter/mantle/cloudflare";
-import { plan } from "../.mantle/generated/mantle.js";
-
-export default createMantleWorker({ plan });
-```
-
-Sign-in for staff review is the conventional Worker's Auth; see [Authentication](../handbook/cloudflare/authentication.md). The [local Admin OTP host](./host-local-admin-otp/README.md) is the opt-in Dev UI path.
-
-## Try it
-
-Public catalog:
-
-```sh
-curl -sS 'http://localhost:8787/api/views/public-products?show=20'
-```
-
-Place an order (the body is stored as sent; the server does not re-price):
-
-```sh
-curl -sS -X POST http://localhost:8787/api/commerce/orders \
-  -H 'content-type: application/json' \
-  -d '{"orderNumber":"MNT-20260919-1","orderStatus":"submitted","currency":"TWD","totalMinor":2400,"customerName":"Ada","customerEmail":"ada@example.test","shippingAddress":"1 Shell Lane","items":[{"productSlug":"notebook","title":"Notebook","quantity":2,"unitPriceMinor":1200,"lineTotalMinor":2400}]}'
-```
-
-The response is `{ ok: true, data: <EntryRow> }` with `collection: "orders"` and `status: "published"`. A duplicate `orderNumber` is HTTP 409 `CONFLICT`. `orderStatus` other than `submitted` is HTTP 400 `INPUT_VALIDATION_FAILED`.
-
-Staff, on `/mcp/staff`, read `query_view_submitted_orders` then:
-
-```json
-{
-  "jsonrpc": "2.0", "id": 2, "method": "tools/call",
-  "params": {
-    "name": "review_order",
-    "arguments": { "id": "ord_01j...", "expectedVersion": 1, "orderStatus": "fulfilled", "trackingNumber": "TEST-1" }
-  }
-}
-```
-
-A second reviewer replaying `expectedVersion: 1` receives `CONFLICT`. A contributor-role session is denied with `AUTH_DENIED`.
-
-| Surface | Tool | Origin |
-|---|---|---|
-| `/mcp` | `query_view_public_products` | public View |
-| `/mcp` | `place_order` | `place-order-mcp` Trigger |
-| `/mcp/staff` | `query_view_submitted_orders` | staff View |
-| `/mcp/staff` | `review_order` | staff MCP Trigger |
-| `/mcp/staff` | `create_draft_products`, `update_draft_products`, `request_publish`, ... | publishing Schema `products` |
-| `/mcp/staff` | `create_record_orders`, `update_record_orders` | operational Schema `orders` |
-
-## What this deliberately leaves out
-
-- **Stock authority.** There is no `inventory` Schema and no Durable Object. Two orders for the last unit both succeed. That story is [Commerce inventory](./cf-primitives-commerce-inventory.md).
-- **Re-pricing.** `totalMinor` and line totals are whatever the caller sent.
-- **Payments.** `submitted` is not `pending_payment`. There is no provider callback and no `pay-order` Procedure.
-- **Queue expiry and cron.** Unpaid reservation release does not apply; there is no reservation.
-- **Picking-list SQL View.** `submitted-orders` is a declared View over `orders`. The `json_each` picking list lives on the cf-primitives page.
-
-Related: [Publication](./builtin-publication.md) for localized product copy; [Procurement approvals](./builtin-procurement.md) for `ctx.user`-owned rows and OCC updates.
-
-## Source
-
-- [Commerce inventory](./cf-primitives-commerce-inventory.md) — DO stock, Queue expiry, payment callback
-- [Schema](../handbook/reference/schema.md), [Procedure](../handbook/reference/procedure.md), and [View](../handbook/reference/view.md) references — publishing vs operational, builtin `create`/`update`
-- [`host-local-admin-otp`](./host-local-admin-otp/README.md) — opt-in Admin host for publishing products

package/docs/examples/builtin-intake.md

@@ -1,143 +0,0 @@
----
-description: A public intake form that creates operational request rows with a builtin handler. No Turnstile or email ref hooks.
----
-# Intake form
-
-**Handler class:** builtin · **Builder:** yes · [Examples hub](./README.md). Turnstile verification and staff email are [Intake Turnstile and email hooks](./cf-primitives-intake-hooks.md).
-
-This example collects a public request and lists recent rows for staff. Every Procedure is `handler.kind: builtin`. Read it if you need any form that anonymous visitors submit and you are not wiring bot checks or mailers into the Manifest.
-
-## Problem
-
-Visitors submit a name, an email address and a message. Staff read recent submissions in Admin, over the staff View REST route, or through Staff MCP. Submissions are live records, not authored content, so the Schema is `operational`.
-
-## Manifest
-
-```yaml
-apiVersion: cms.mantle.aotter.net/v1
-kind: Schema
-metadata:
-  name: requests
-spec:
-  title: Requests
-  description: Requests submitted through the public intake flow.
-  lifecycle: operational
-  schema:
-    type: object
-    additionalProperties: false
-    required: [name, email, message]
-    properties:
-      name: { type: string, minLength: 1, maxLength: 120 }
-      email: { type: string, format: email }
-      message: { type: string, minLength: 1, maxLength: 2000 }
-      submittedAt: { type: number, x-mcp-hint: timestamp-ms, x-mantle-bind: now }
----
-apiVersion: cms.mantle.aotter.net/v1
-kind: View
-metadata:
-  name: recent-requests
-spec:
-  title: Recent requests
-  surface: staff
-  from: requests
-  fields: [id, name, email, message, submittedAt]
-  orderBy:
-    - { field: submittedAt, direction: desc }
-  limit: 50
----
-apiVersion: cms.mantle.aotter.net/v1
-kind: Procedure
-metadata:
-  name: submit-request
-spec:
-  title: Submit request
-  description: Create a new public request.
-  input:
-    type: object
-    additionalProperties: false
-    required: [name, email, message]
-    properties:
-      name: { type: string, minLength: 1, maxLength: 120 }
-      email: { type: string, format: email }
-      message: { type: string, minLength: 1, maxLength: 2000 }
-  output: { type: object }
-  handler: { kind: builtin, op: create, schema: requests }
----
-apiVersion: cms.mantle.aotter.net/v1
-kind: Trigger
-metadata:
-  name: submit-request-http
-spec:
-  source: { kind: http, method: POST, path: /api/requests }
-  target: { procedure: submit-request }
----
-apiVersion: cms.mantle.aotter.net/v1
-kind: Trigger
-metadata:
-  name: submit-request-mcp
-spec:
-  source: { kind: mcp, surface: public }
-  target: { procedure: submit-request }
-```
-
-`submittedAt` is stamped by the server (`x-mantle-bind: now`); a caller-supplied value is ignored. It lives in `data` next to the native `createdAt` column so the timestamp travels with the record through MCP output and exports; data properties may not reuse the native column names. The builtin `create` projects `input ∩ Schema.properties`.
-
-## Worker and handlers
-
-None are required. The Manifest above runs on the minimal Worker:
-
-```ts
-import { createMantleWorker } from "@aotter/mantle/cloudflare";
-import { plan } from "../.mantle/generated/mantle.js";
-
-export default createMantleWorker({ plan });
-```
-
-## Try it
-
-```sh
-curl -sS -X POST http://localhost:8787/api/requests \
-  -H 'content-type: application/json' \
-  -d '{"name":"Ada","email":"ada@example.test","message":"Please call me back."}'
-```
-
-```json
-{
-  "ok": true,
-  "data": {
-    "id": "req_01j...",
-    "collection": "requests",
-    "status": "published",
-    "version": 1,
-    "data": { "name": "Ada", "email": "ada@example.test", "message": "Please call me back.", "submittedAt": 1788879363492 },
-    "authorId": null,
-    "createdAt": 1788879363492,
-    "updatedAt": 1788879363492
-  }
-}
-```
-
-The builtin `create` returns the `EntryRow`; `status` is `published` immediately because the Schema is operational. A missing `name` is HTTP 400 `INPUT_VALIDATION_FAILED`.
-
-Staff read the queue at `GET /admin/api/views/recent-requests?page=1&show=50` with a staff session; the envelope is `{ ok, data: { rows, page, show, hasMore } }`.
-
-MCP tools:
-
-| Surface | Tool | Origin |
-|---|---|---|
-| `/mcp` | `submit_request` | `submit-request-mcp` Trigger |
-| `/mcp/staff` | `query_view_recent_requests` | `recent-requests` View |
-| `/mcp/staff` | `create_record_requests`, `update_record_requests` | operational Schema `requests` |
-
-## What this deliberately leaves out
-
-- **Bot check and notification.** Those are `ref` lifecycle hooks in [Intake Turnstile and email hooks](./cf-primitives-intake-hooks.md). They are not in this Manifest; Builder must not ingest that page.
-- **Deduplication.** Two identical submissions create two rows.
-- **Rate limiting.** The adapter applies its own request limits to Auth and Admin routes, not a per-form quota.
-
-Related: [Reservation requests](./builtin-reservation.md) uses the same builtin-create shape; [Procurement approvals](./builtin-procurement.md) adds member and staff roles.
-
-## Source
-
-- [Procedure reference](../handbook/reference/procedure.md) — builtin `create`
-- [Intake Turnstile and email hooks](./cf-primitives-intake-hooks.md) — Turnstile and email `ref` hooks on the same Schema