@terreno/mcp 57.11.0 → 57.13.0

package/dist/docs/versioned/next/how-to/github-actions-ci.md

@@ -7,24 +7,23 @@ describes how they behaved if one is ever re-enabled.
 
 ## Docs site (`docs-deploy.yml`)
 
-`Build docs site` is often the longest PR job because Docusaurus compiles every
-versioned tree under `website/versioned_docs/` and TypeDoc regenerates API
-pages.
+`Build docs site` is often the longest PR job because TypeDoc regenerates API
+pages. The site builds only the current docs tree; `website/versioned_docs/` is
+markdown for the MCP server.
 
 PR builds set `DOCS_PREVIEW=true` and pass `--no-minify`. Both PR and
 `master` use Docusaurus Faster (Rspack/SWC via `@docusaurus/faster`).
 
 | Behavior | PR preview | `master` production |
 | --- | --- | --- |
-| Versioned docs (`57.1.0`, `0.30.0`, …) | Omitted (`disableVersioning`) | Built |
+| Versioned docs (`57.1.0`, `0.30.0`, …) | Omitted | Prebuilt archives unpacked under `/<version>/` |
 | JS minify | Off | On |
 | Local search index | Skipped | Built |
 | Generated API + component MDX | Restored from cache when `api`/`rtk`/`ui` hashes match | Same cache, then full generate on miss |
 | TypeDoc workspace `tsc` | Once per generate (api+rtk deps share a process) | Same |
 | Rspack cache (`node_modules/.cache/rspack`) | Restored per `pull_request` vs `push` | Separate production key |
 
-Production still builds every version. Do not rely on `/57.1.0/…` URLs in a
-PR deploy preview.
+Do not rely on `/57.1.0/…` URLs in a PR deploy preview.
 
 ## Other high-cost jobs
 

package/dist/docs/versioned/next/how-to/preview-demo.md

@@ -1,10 +1,10 @@
 # Preview a component demo
 
-Open a component demo and change the shareable query. The preview controls sit in the
-navigation header on demo and dev component routes: dropdowns for theme, viewport, and
+Open a demo or dev route and change the shareable query. The preview controls sit in the
+navigation header on every demo and dev screen, including the catalogs: dropdowns for theme, viewport, and
 background, plus a settings button (sliders icon) that opens a modal for right-to-left,
 reduced motion, locale, and the share query. In windows narrower than 768px every
-preview control moves into that modal; the Dev/Demo mode link stays in the header. `?embed=1` applies the same query and hides
+preview control moves into that modal; the Dev/Demo mode link stays in the header. The header chrome uses the same `theme` query. `?embed=1` applies the same query and hides
 the controls.
 
 ```text
@@ -13,11 +13,11 @@ the controls.
 
 | Query | Values |
 | --- | --- |
-| `theme` | `light` (default) or `dark` (canonical dark role remap) |
+| `theme` | `light` (default), `dark`, or `system` (follow the device color scheme) |
 | `viewport` | `full` (default), `320`, `375`, `1024`, `1280` |
 | `background` | `default`, `inverse`, `transparent` |
 | `locale` | Passed to components that already read a locale, such as consent |
 | `rtl` | `1` sets document direction to `rtl` on web |
 | `reducedMotion` | `1` sets `data-reduced-motion="1"` on the document element |
 
-Reload keeps the query. The settings modal shows the current query when any value is not the default. Choosing a control's default removes that key from the URL. Leaving the component route restores the app theme and, on web, document direction and reduced motion. Custom palettes stay on `/palette`.
+Reload keeps the query. The settings modal shows the current query when any value is not the default. Choosing a control's default removes that key from the URL. Opening a component from the catalog keeps the current preview query. Leaving a component route restores document direction and reduced motion on web. Custom palettes stay on `/palette`.

package/dist/docs/versioned/next/how-to/rate-limiting.md

@@ -52,6 +52,23 @@ Pass `{store: "mongo"}`. Hits live in `rateLimitHits` on the same mongoose conne
 
 Unauthenticated keys use `req.ip`. Express `trust proxy` defaults to **off** so a client cannot rotate `X-Forwarded-For` to bypass the auth bucket. On Cloud Run (one hop via GFE), pass `trustProxy: 1`. Extra proxies: hop count or a subnet list. `trustProxy: false` is the same as the default.
 
+## Limit one route
+
+Use `createRouteRateLimitMiddleware` for a stricter limit on one expensive route. It works with or without the global limiter.
+
+```typescript
+import {createRouteRateLimitMiddleware} from "@terreno/api";
+
+const uploadLimit = createRouteRateLimitMiddleware({
+  name: "uploads",
+  max: 1,
+  windowMs: 60_000,
+  store: "mongo",
+});
+```
+
+`DocumentStorageApp` takes the same options as `uploadRateLimit`. The example backend allows one upload per IP per minute and sets `trust proxy` to `1` on Cloud Run so the key is the real client IP.
+
 ## Auth vs API buckets
 
 | Path | Bucket |

package/dist/docs/versioned/next/how-to/test-ui-accessibility.md

@@ -0,0 +1,35 @@
+# Test UI accessibility
+
+Run the WCAG scanner against every changed rendered state:
+
+```bash
+bun run accessibility:scan \
+  "http://localhost:8085/dev/Theme?story=ThemeComponent&theme=light" \
+  "http://localhost:8085/dev/Theme?story=ThemeComponent&theme=dark"
+```
+
+The scanner applies axe rules tagged WCAG 2.0 A/AA, WCAG 2.1 A/AA, and WCAG
+2.2 AA. It writes a JSON report and full-page screenshots under
+`/opt/cursor/artifacts/accessibility/` and exits nonzero when any violation is
+found.
+
+## Verify what automation cannot
+
+1. Use only the keyboard to reach and operate each changed control.
+2. Confirm focus order and the visible focus indicator match the visual order.
+3. Inspect each control's accessible name, role, state, and error relationship.
+4. Check light and dark modes, plus loading, empty, disabled, and error states
+   affected by the change.
+5. At 200% browser zoom, confirm content remains usable without clipping or
+   losing actions.
+
+Automated scans do not prove keyboard behavior, announcement quality, reading
+order, or whether alternative text conveys the intended meaning. Record those
+manual checks with the automated report in the pull request Verification table.
+
+## Fixing findings
+
+Fix violations in the changed feature before submission. If a finding is
+pre-existing and outside the changed path, capture a baseline on an unaffected
+route and name both routes in the pull request. Do not suppress an axe rule
+without a linked issue and a documented reason.

package/dist/docs/versioned/next/implementationPlans/agent-ui-rich-replies.md

@@ -0,0 +1,359 @@
+# Agent UI Rich Replies: steppers, checklists, galleries, and copy
+
+**Status:** approved 2026-10-07
+**Task list:** [`docs/tasks/agent-ui-rich-replies.md`](../tasks/agent-ui-rich-replies.md)
+**Supporting skills:** `terreno-ui`, `terreno-backend-api`, `ai-prompt-governance`, `update-docs`, `verify-ui-changes`, `backend-test-env`
+**Source:** OpenAI, "GPT-6 and Intelligent UI for everyone", the "Planning a Sunday roast" GPT-5.6 vs GPT-6 Instant comparison (fetched 2026-10-07).
+
+Terreno agents can already reply with whole-reply YAML block documents: headings, markdown,
+metrics, cards, charts, dataset tables, images, callouts, and buttons that reply, open,
+select, or call a host callback. OpenAI's GPT-6 launch shows a meal-plan reply that goes
+further: a summary card at the top, a three-photo collage, a photo menu list, a guest-count
+stepper that recalculates the shopping list, a "Copy shopping list" button, and a timed
+cooking checklist with a "1 of 8" counter. The GPT-5.6 version beside it uses a markdown
+"How much lamb?" table. This plan adds the missing pieces, so a Terreno agent can
+return both replies. The new blocks are on by default (D6); a host whose shipped clients cannot render them yet sets `uiBlocks.richBlocks: false`.
+
+## The idea
+
+Six additions to the closed block catalog in `@terreno/blocks`, each rendered by
+`BlocksView` with `@terreno/ui` components:
+
+| Demo element | Terreno block | Interaction |
+| --- | --- | --- |
+| "Your dinner plan" summary with a small label above the title | `card.eyebrow` (new optional field) | none |
+| Three grouped hero photos | `gallery` (2–6 images, optional captions) | none |
+| Menu items: photo, bold title, description | `list` (items with optional image) | none |
+| Guest count − / + with recalculated quantities | `stepper` | **host callback round trip** |
+| "Copy shopping list" | `copy` action kind on a button | on the device (clipboard) |
+| Cooking checklist with times and "n of m" | `checklist` | **host callback per tick** (local when the host has no checklist action) |
+| "How much lamb?" guests table | `table` renders typed columns; markdown tables in `text` get theme styling | none |
+
+The stepper follows the decision made in chat: **− and + are callback buttons like the
+existing ones.** A tap sends `POST /gpt/actions` with the stepper's callback name and
+`{...callback.payload, value: <next>}`. The host action returns
+`{replace: "block", blocks: {v: 1, blocks: [<new stepper>]}}`, and `GPTChat` swaps the block by
+id through `overrides`, as it does today. `@terreno/ai` ships an opt-in host action,
+`scaleStepperHostAction`. It reads the stepper the agent wrote from the stored history, not
+from the tap request, and scales every item linearly from it. Scaling from the agent's
+original keeps rounding from drifting tap after tap. The owner of a history can still edit
+its stored prompts through `PATCH /gpt/histories/:id`, so an app whose numbers matter
+(prices, stock) must compute them from its own data, not from the stored block.
+
+```yaml
+- type: card
+  eyebrow: How much should you buy?
+  children:
+    - type: stepper
+      id: guests
+      label: Number of people
+      unit: People
+      value: 5
+      min: 1
+      max: 20
+      callback: {name: scaleStepper}
+      items:
+        - {label: Bone-in leg of lamb, amount: 2, unit: kg, decimals: 1}
+        - {label: Carrots, amount: 8, round: up}
+      note: Generous portions, with a little extra.
+    - type: actions
+      id: copy_list
+      elements:
+        - {type: button, id: copy, text: Copy shopping list, action: {kind: copy, target: guests}}
+```
+
+The checklist works the same way (D2). Each tick sends a callback with the full set of ticks,
+and `toggleChecklistHostAction` returns the checklist with those ticks. Photos (D3) come from
+a library of images generated once with the Vertex image model and stored through
+`FileStorageService`. The agent picks from it with a `findPhotos` tool and writes `file:` ids.
+
+Rejected: a shared document `state` with `{{formula}}` bindings computed on the device.
+It needs an expression language, and the human chose a server round trip.
+
+## The plan
+
+| # | Task | Depends on | Lands in | Proves it |
+| --- | --- | --- | --- | --- |
+| T1 | Stepper block round trips through a host callback (tracer) | none | blocks, ui, ai | fixture, renderer, handler, and route tests |
+| T2 | Prompt offers the new blocks only when the host opts in | T1 | blocks, ai | prompt + chat-turn tests |
+| T3 | Table block renders typed columns | T1 | ui | `DataTable` + `BlocksView` tests |
+| T4 | Markdown tables in `text` get theme styling | T3 | ui | `MarkdownView` test |
+| T5 | `checklist` contract | T2 | blocks | fixtures |
+| T6 | `gallery` contract | T5 | blocks | fixtures + image-host lint |
+| T7 | `list` contract | T6 | blocks | fixtures + image-host lint |
+| T8 | `card.eyebrow` contract | T7 | blocks | fixtures |
+| T9 | `copy` action contract + `blockPlainText` | T8 | blocks | fixtures + serializer tests |
+| T10 | Checklist renders and toggles | T3, T4, T5 | ui | `BlocksView` test |
+| T11 | Gallery renders | T6, T10 | ui | `BlocksView` test |
+| T12 | List renders | T7, T11 | ui | `BlocksView` test |
+| T13 | Card eyebrow renders | T8, T12 | ui | `BlocksView` test |
+| T14 | Copy action writes the clipboard | T9, T13 | ui | `BlocksView` test |
+| T15 | Sunday roast golden document + playground story | T14 | blocks, demo | fixture + story screenshot |
+| T16 | Example app: the roast reply against the real callback routes | T15, T20, T21 | example-backend, example-frontend | Playwright + recording |
+| T17 | Model smoke: a real model writes the roast reply | T15, T20 | example-backend | smoke script output |
+| T18 | Docs sweep, changelog, rules | T15, T20, T21 | docs, rules | `website:build`, `rules:check` |
+| T19 | Generated photo library: generate images once and store them | none | example-backend | model + script tests |
+| T20 | `findPhotos` tool and photo URLs in the example app | T19 | example-backend, example-frontend | tool + action tests |
+| T21 | Checklist ticks round trip through a host callback | T10 | ai | handler + route tests |
+
+Tracer: T1, from the agent's YAML through `validateBlocks`, `BlocksView`, the callback
+event, `POST /gpt/actions`, and `scaleStepperHostAction`, back to a replaced block.
+Out of scope: formulas or shared state, scripted html, persisting overrides, maps, tabs,
+interactive diagrams, generated tools (see Expansions).
+Open risks:
+- Each tap is one round trip. `pendingElementIds` disables both buttons until the reply
+  lands, so fast taps are dropped, not queued (Q4).
+- `scaleStepperHostAction` finds the agent's block by `messageId`, which is `msg-<index>`
+  when the host sets no message id. When that misses, it uses the only assistant prompt that
+  holds a stepper with that `blockId`. If more than one does, it returns 409 rather than
+  guess.
+- Stored history prompts are writable by their owner, so the stored stepper is not a trust
+  boundary (see the idea above; the how-to says so).
+
+## Contracts
+
+Field names are the contract. Limits go in `BLOCK_LIMITS` and are printed in the prompt
+from there. Lint paths use the existing `blocks[0].images[2].src` form.
+
+### `stepper` (T1)
+
+| Field | Required | Rule |
+| --- | --- | --- |
+| `id` | yes | block id pattern, at most 54 characters (room for the `_increase` suffix) |
+| `label` | yes | 1–80 |
+| `value`, `min`, `max` | yes | numbers; `min` < `max`; `min` ≤ `value` ≤ `max` (`OUT_OF_RANGE`) |
+| `step` | no | > 0, default 1 |
+| `unit` | no | 1–40, shown under the value ("People") |
+| `callback` | yes | `{name, payload?}`; `name` is checked by `UNKNOWN_HOST_ACTION` when `hostActions` is passed |
+| `itemsTitle` | no | 1–80, a small heading above the items ("Your shopping quantities") |
+| `items` | no | 0–12 of `{label (1–80), amount (number), unit? (1–20), decimals? (0–3, default 0), round?: nearest \| up (default nearest)}` |
+| `note` | no | 1–280, muted under the items |
+
+The renderer reserves the element ids `<id>_decrease` and `<id>_increase`. Lint reports
+`DUPLICATE_ID` when any other block or element uses them.
+
+Rendering: the label as an eyebrow, `IconButton` − and +, then the value with its unit,
+`itemsTitle`, the items as a two-column label / amount grid formatted with `decimals` ("2.0 kg"), then the
+note. − is disabled when one more step would go below `min`, + when it would go above `max`.
+Both are disabled while either element is pending,
+and when `callback.name` is not in `hostActions`. Accessible labels: "Decrease <label>",
+"Increase <label>".
+
+Callback event: `blockId: <id>`, `elementId: <id>_increase` or `<id>_decrease`, action
+`{kind: "callback", name, payload: {...payload, value: value ± step}}`.
+
+`scaleStepperHostAction` (in `@terreno/ai`) is `{handler, payload, handles: "stepper", logResponse: false}`. Its `payload` schema is `z.object({value: z.number()}).passthrough()`, and the handler reads only `value`.
+
+1. Loads the stepper the agent wrote with `findAgentBlock({history, messageId, blockId, type})`,
+   a shared helper (`ai/src/service/agentBlocks.ts`). It reads `history.prompts[n]` when
+   `messageId` is `msg-<n>` (stored prompts have no ids), parses it with `parseBlocks`, and
+   finds the block of that type whose id is `blockId`. When that misses, it uses the only
+   assistant prompt holding such a block. With more than one, it returns 409. With none, 404.
+2. Checks that `value` is a number within `[min, max]` on the `step` grid. Anything else
+   returns 400.
+3. Returns `{replace: "block", blocks: {v: 1, blocks: [stepper]}}`. The returned stepper has
+   the new `value`, and each item's `amount` is `original amount × value / original value`,
+   rounded by that item's `decimals` and `round`.
+
+`logResponse: false` is a new optional host-action field. With it, the `AIRequest` row for
+`POST /gpt/actions` keeps today's ids-only prompt, adds the numeric `value`, and leaves out
+the returned block. Every other host action keeps logging the full response, as today.
+
+### Default on, with an opt-out (T2)
+
+| Option | Effect |
+| --- | --- |
+| `uiBlocks.richBlocks` (default `true`) | The prompt offers `checklist`, `gallery`, `list`, `card.eyebrow`, and `copy`. `false` removes them. |
+| `richBlocks` on **and** a host action with `handles: "stepper"` | The prompt offers `stepper` and names those actions as its callbacks. Without a stepper action, the prompt never mentions `stepper`, because its buttons would be dead. |
+| `richBlocks` on **and** a host action with `handles: "checklist"` | The checklist prompt line tells the model to set `callback` to that action. Without one, it says to leave `callback` out (ticks stay local). |
+
+`blocksPromptSection` gains `richBlocks` (default `true`, matching the server), `stepperActions`, and `checklistActions`.
+`validateBlocks` gains the same two lists: a stepper or checklist whose `callback.name` is not
+in its list fails `UNKNOWN_HOST_ACTION`. `chatTurn` derives both lists from the host actions'
+`handles` field. The server always accepts the new blocks when it validates. The
+opt-out only stops the model from writing them for clients that cannot render them yet.
+
+Upgrading changes behaviour: every host with `uiBlocks` on gets the new blocks in its prompt
+after the bump. The changelog entry says so under a "Behaviour change" heading and names
+`richBlocks: false` as the opt-out.
+
+### `checklist` (T5)
+
+`{type: checklist, id (at most 31 characters), title? (1–120), callback?: {name, payload?}, items: 1–30 of {id (at most 32 characters), text (1–120), detail? (1–280), meta? (1–40), checked?: boolean}}`.
+Item ids are unique. The element id of a tick is `<id>_<item id>`, reserved like the stepper's
+(`DUPLICATE_ID`). Rendering: the title on the left and "n of m" on the right, then one
+`CheckBox` row per item: the bold `text` first, then `meta` (the time, small and muted), then a muted
+`detail` (D7).
+
+With a `callback`, an `onAction` handler, and either no `hostActions` list or one that names the
+callback (matching the stepper), a tick sends
+`{kind: "callback", name, payload: {...payload, itemId, checked, state: {<item id>: boolean, ...}}}`
+with `blockId: <id>` and `elementId: <id>_<item id>`. `state` is the full set of ticks after
+this one, because overrides live only in the client (D4). The whole checklist is disabled until
+the reply lands, so a second tick cannot send a `state` that misses the first, and the checklist
+then shows the returned block. Ticks are not applied ahead of
+the reply. Without a `callback`, without `onAction`, or when a `hostActions` list leaves the name
+out, ticks are local.
+
+`toggleChecklistHostAction` (in `@terreno/ai`, T21) is `{handler, payload, handles: "checklist", logResponse: false}`
+with payload `z.object({itemId: z.string(), checked: z.boolean(), state: z.record(z.string(), z.boolean())}).passthrough()`.
+It loads the agent's checklist with `findAgentBlock`, rejects item ids the checklist does not
+have (400), and returns `{replace: "block", blocks: {v: 1, blocks: [checklist]}}` with
+`checked` set from `state`. Apps that record progress register their own `handles: "checklist"`
+action.
+
+### `gallery` (T6)
+
+`{type: gallery, id?, images: 2–6 of {src, alt (1–200), caption? (1–120)}}`. Each `src` follows
+the `image` rules, including `IMAGE_HOST_NOT_ALLOWED`. Rendering: up to 3 images sit in one
+row of equal 4:3 tiles; more than 3 wrap into a 3-column grid. Narrow screens scroll the row
+sideways (Q5).
+
+### `list` (T7)
+
+`{type: list, id?, items: 1–12 of {title (1–120), text? (1–500, plain text), meta? (1–40), image?: {src, alt}}}`.
+Image sources follow the `image` rules. Rendering: a 3:4 portrait thumbnail on the left,
+then the bold title and muted text.
+
+### `card.eyebrow` (T8)
+
+Optional `eyebrow` (1–60) on `card`, rendered small and muted above `title`.
+
+### Generated photo library (T19, T20)
+
+The agent cannot make photos on the fly, and `https` images need an allowlist. So the example
+app generates a library once and stores it.
+
+| Piece | Contract |
+| --- | --- |
+| `PhotoLibraryEntry` model (example-backend) | `{fileAttachmentId, gcsKey, alt (1–200), tags: string[] (1–12), prompt}`, every field with a `description`; `createdUpdatedPlugin`, `isDeletedPlugin`; `prompt` is unique. A soft-deleted entry still holds its prompt, and `--force` leaves the old stored object and its `FileAttachment` behind |
+| `bun run photos:generate` (example-backend script) | Reads `src/scripts/photoPrompts.ts` (about 12 entries: roast lamb, crispy potatoes, honey carrots and parsnips, lemony greens, apple crumble, a laid table, and so on). It runs each through AI SDK `generateImage` with the Vertex image model (`imagen-4.0-fast-generate-001` unless `PHOTO_IMAGE_MODEL` is set), uploads it with `FileStorageService.upload` as a system user, and upserts a `PhotoLibraryEntry` by `prompt`. Re-runs skip prompts that already exist unless `--force` is passed. Requires `GOOGLE_VERTEX_PROJECT`, Application Default Credentials for Vertex, and `GCS_BUCKET`, validated up front; `GOOGLE_VERTEX_LOCATION` (default `us-central1`) picks a regional endpoint for Imagen. Uploads are owned by a find-or-create system user `photo-library@system.invalid`. A failed prompt is logged, the run continues, and the exit code is 1 if any failed |
+| `findPhotos({query, count})` tool | Matches `query` words against `tags` and `alt`, and returns up to `count` (1–6) `{src: "file:<entry id>", alt}` |
+| `photoLibrary` `modelRouter` with an instance action `url` | `GET /photoLibrary/:id/url` returns `{url}` (a `FileStorageService.getSignedUrl`) to any authenticated user. The library is shared, so the per-user `GET /files/*` route does not fit. List and read are `IsAuthenticated`; create, update, and delete are disabled |
+| example-frontend `resolveImage` | Resolves `file:<id>` through the generated SDK hook for `url` |
+
+The library holds only generated food photos, no user data.
+
+### `copy` action (T9)
+
+A new `action.kind`: `{kind: copy, text?, target?}`. Lint requires exactly one of the two,
+reporting `MISSING_REQUIRED` as it does for `open`. `target` must name a `stepper`,
+`checklist`, `list`, `table`, or `text` block (`COPY_TARGET_INVALID`). `text` holds at most
+4,000 characters (`copyTextMaxLength`); `target` is a block id.
+`blockPlainText(block, {datasets?, checked?})` in `@terreno/blocks` turns a block into the
+copied text:
+
+| Block | Text |
+| --- | --- |
+| `stepper` | `<label>: <value> <unit>`, then one `<item label>: <amount> <unit>` line per item |
+| `checklist` | one `[x] text` or `[ ] text` line per item, using the current toggles |
+| `list` | one `- title: text` line per item |
+| `table` | a header row, then the rows, tab-separated |
+| `text` | the markdown as written |
+
+`BlocksView` copies the text from the **current** block, with the override and toggles applied,
+using `expo-clipboard`. It then shows "Copied" in a polite live region next to the button for
+2 s. It does not call `onAction` or the server.
+
+### Tables (T3, T4)
+
+T3: `DataTable` gets real `number` and `date` cells. `number` is right-aligned. `date` is
+formatted with Luxon (`DateTime.fromISO(...).toLocaleString(DateTime.DATE_MED)`). The
+`table` block renderer stops forcing every column to `text` and `width: 120`. It maps the
+dataset's column types to these cells. It measures the container with `onLayout` and splits
+the width evenly, at least 96 per column, scrolling sideways past that. Number headers
+right-align to match their cells. Headers show column names with underscores as spaces, and the
+copied header row does the same. The table sits in a frame sized to its header plus rows (54
+each, up to 10 rows), so it never spills over the next block; longer tables scroll inside it.
+
+T4: `react-native-markdown-display` already lays GFM tables out as views. T4 adds theme
+styling: `border.default` cell borders, a bold header row on `surface.secondaryLight`, and
+horizontal scroll when the table is wider than its container. Its test fails on `master`
+first.
+
+## Acceptance criteria
+
+| ID | Criterion | Verification |
+| --- | --- | --- |
+| AC1 | Each new block and the `copy` action has at least one valid and one invalid fixture, and `jsonSchema.test.ts` agrees with Zod on all of them | `bun test blocks/` |
+| AC2 | Every new error code (`OUT_OF_RANGE`, `COPY_TARGET_INVALID`) appears in `docs/reference/blocks.md` | `blocksDocParity.test.ts` |
+| AC3 | With `richBlocks: false`, `blocksPromptSection` output is byte-identical to `master`, even when a stepper action is registered. With `richBlocks` unset, `addGptRoutes` and `blocksPromptSection` both behave as `true`. On, the prompt has one line per new block (added as each contract lands; the full snapshot is taken in T9), limits come from `BLOCK_LIMITS`, and the stepper line names the stepper actions | prompt snapshot tests |
+| AC4 | Tapping + on a 5-person stepper emits a callback with `payload.value: 6`. An item `{amount: 2, unit: kg, decimals: 1}` renders "2.0 kg". Rendering an override with `value: 6` shows 6 and the new amounts | `ui/src/blocks/BlocksView.test.tsx` |
+| AC5 | Through `POST /gpt/actions`, with a stored stepper (5 people; lamb `2` kg / 1 dp; parsnips `7` / up; broccoli `625` g / nearest) and `value: 6`: the result is `{replace: "block", blocks: {v: 1, blocks: [stepper]}}` with lamb 2.4, parsnips 9 (nearest would give 8), and broccoli 750. An extra agent `callback.payload` key is accepted. `value: 21` (max 20) returns 400. An unknown `blockId` returns 404. Two stored prompts with the same stepper id and a missed `msg-<n>` return 409. The `AIRequest` row has the ids and `value`, and no `response` | `ai/src/service/scaleStepper.test.ts`, `ai/src/routes/gptActions.test.ts` |
+| AC6 | Without a callback, toggling an item changes "1 of 8" to "2 of 8" on the device. With a callback in `hostActions`, the tick emits `payload: {itemId, checked: true, state}` with all 8 items, disables the whole checklist while the tick is pending, and the counter shows "2 of 8" only after the override arrives | `BlocksView.test.tsx` |
+| AC6b | Through `POST /gpt/actions`, `toggleChecklistHostAction` returns the stored checklist with `checked` from `state`. An unknown item id returns 400. The `AIRequest` row has no `response` | `ai/src/service/toggleChecklist.test.ts`, `ai/src/routes/gptActions.test.ts` |
+| AC7 | Gallery, list, and eyebrow render with `@terreno/ui` components only, with `alt` as the accessible label | `BlocksView.test.tsx` |
+| AC8 | Pressing a copy button whose target is a stepper at value 6 writes the scaled list to the clipboard (mocked `expo-clipboard`) and shows "Copied" | `BlocksView.test.tsx` |
+| AC9 | A `number` column renders right-aligned and a `date` column renders Luxon `DATE_MED`. A GFM table in `text` has themed borders, a bold header, and scrolls sideways when wide. Both tests fail on `master` | `DataTable.test.tsx`, `BlocksView.test.tsx`, `MarkdownView.test.tsx` |
+| AC10 | `blocks/src/fixtures/golden/sunday-roast.yaml` reproduces the GPT-6 demo reply (title, gallery, summary card, menu list, stepper + copy card with `itemsTitle`, checklist, note, tips, follow-up buttons) plus the GPT-5.6 "How much lamb?" table. It validates with `hostActions: ["scaleStepper", "toggleChecklist"]`, `stepperActions: ["scaleStepper"]`, `checklistActions: ["toggleChecklist"]`, and `imageHosts: ["images.example.com"]` in its own test, outside the option-less `valid/` loop | `bun test blocks/` |
+| AC11 | In example-frontend, the roast reply is stored in a real `GptHistory` and streamed by the mocked model. Pressing + changes 5 to 6 through the real `POST /gpt/actions` on example-backend. Copy writes the list. A checklist tick goes through `POST /gpt/actions` and updates the counter. Gallery and list images load through `GET /photoLibrary/:id/url`, with only the storage download stubbed (`page.route` on the signed-URL host serves a fixture image) | `bun run frontend:e2e` (`e2e/ai-chat.spec.ts`), with screenshots and a recording attached to the PR (`/opt/cursor/artifacts/` is read-only in this sandbox) |
+| AC12 | With a model key set, a generated photo library in the database, and the `findPhotos` tool registered, `bun run blocks:smoke` sends "Give me a plan for a sunday lamb roast, I'm having friends over still figuring out numbers tbh" through `AIService` with the opted-in prompt. It asserts that the reply validates and contains `gallery`, `list`, `stepper`, `checklist`, and a `copy` action, and that every image `src` is a `file:` id that `findPhotos` returned. Without a key it exits 0 and says it skipped | script exit code; output saved to `--out`. **Partly met:** the checks are unit-tested with a mock model, but no real model has run it (no key in the build sandbox) |
+| AC14 | `photos:generate` with a fake image model and a fake storage service creates one entry per prompt, and a second run creates none. `findPhotos({query: "roast lamb", count: 3})` returns 3 `file:` ids. `GET /photoLibrary/:id/url` returns a URL to a non-admin user, and create returns 405 | `example-backend` tests |
+| AC13 | Docs: reference rows, a how-to "Add a stepper callback", the explanation catalog fixed (it lacks `callout`, `image`, `details`, and `html` today), and a changelog entry | `bun run website:build`, `bun run rules:check` |
+
+## Assumptions
+
+- "Serving layout" means the stepper card: the label, − value +, the unit, the quantities grid,
+  and the note (Q6).
+- "Summary in an outline at the top" means the summary card: an eyebrow, a title, and a
+  bold-label bullet list written in markdown inside `text`. No new outline block.
+- Generating the library is an operator step run once per environment (`bun run photos:generate`). Tests use a fake image model and fake storage, so CI never calls Vertex.
+- "The tables" means the GPT-5.6 "How much lamb?" guests table, plus tables in general (Q7).
+- Copy feedback is inline "Copied" text in a live region, as in the demo, not a toast.
+- iOS and Android render through the same `BlocksView`. Builds already shipped do not know
+  the new blocks and would show an error banner, with the raw YAML collapsed, for the whole reply
+  that uses them. With the default on
+  (D6), a host with such builds must set `richBlocks: false` until they update. X10 (a
+  client-declared catalog version) would remove that manual step.
+- The `copy` action never reaches the server, so `hostActions` lint does not apply to it.
+  Local checklist ticks (no callback) don't either.
+- Image tiles reuse `useResolvedImages` for `file:` ids.
+- Storage: no new collection. Each stepper tap adds one `AIRequest` row. Like every host
+  action today, its prompt holds only ids; this adds the numeric `value`. Unlike other host
+  actions, the returned block is left out (`logResponse: false`), because an agent can put
+  anything in a stepper label.
+- Fixtures under `fixtures/valid/` use `data:image` or `file:` sources, because that loop
+  validates without `imageHosts`. Invalid cases that need options go in `lint.test.ts`.
+
+## Open questions (recommendation assumed)
+
+| ID | Question | Recommendation | Why | If answered differently | Tasks affected |
+| --- | --- | --- | --- | --- | --- |
+| Q3 | Should `@terreno/ai` ship `scaleStepperHostAction`, or should each app write its own handler? | Ship it, opt-in, exported from `@terreno/ai` | Any app gets the roast reply in one line; apps with real logic (prices, stock) register their own `handles: "stepper"` action | Drop the export; example-backend owns the handler | T1, T16 |
+| Q4 | Should + / − send one callback per tap, or batch taps (300 ms debounce, then one call)? | One per tap, with the buttons disabled while pending | Matches the existing callback buttons; simplest to prove | Add a debounce and send the final value | T1 |
+| Q5 | Should `gallery` take a `layout` (`collage`, `grid`, `carousel`)? | No: one adaptive layout | Fewer choices for the model; the demo uses one row | Add the enum and two more renderer branches | T6, T11 |
+| Q6 | Does "serving layout" mean the stepper card (− 5 +, People, quantities grid)? | Yes | It sits between the stepper and the copy button in the demo | Name what it is; likely one more block or field | T1 |
+| Q7 | Does "the tables" mean the GPT-5.6 "How much lamb?" table (guests → lamb, potatoes)? | Yes: as a `table` block with typed columns, plus themed markdown tables | It is the only table in the post; the GPT-6 reply shows quantities as a grid | Name the table and what it should do (sort, scale with the stepper) | T3, T4, T15 |
+
+## Expansions (follow up later)
+
+| ID | Idea | Why it came up | Rough size | Depends on |
+| --- | --- | --- | --- | --- |
+| X1 | Generated tools in chat (savings calculator, bill splitter, game) | The post's "Create interactive experiences" section | L | a state + formulas design, or more host callbacks |
+| X2 | Interactive diagrams ("change an input to see what happens") | The post's central limit theorem example | L | X1 |
+| X3 | `map` block with stops and notes | The post's road-trip example | M | none |
+| X4 | Full eval that the model picks these blocks for planning questions (beyond the T17 smoke) | The post trains the model's design judgment | M | T17 |
+| X5 | Copy button on markdown code fences | A common chat copy target; not in the demo | S | T14 |
+| X6 | Sortable table columns | `DataTable` supports `sortable` already | S | T3 |
+| X7 | Write `blocks.json` to `blocks/schemas/` for native clients | `blocksJsonSchema` exists but is not published there | S | T9 |
+| X8 | Streaming inside a block (partial lists) | The post's progressive compiler | M | none |
+| X9 | Persist overrides (if Q2 stays no) | A reload resets the stepper | M | Q2 |
+| X11 | Generate images per reply (a `generatePhoto` tool) | D3 picked a stored library instead | M | T19 |
+| X10 | A client-declared catalog version, so the server picks blocks per client | Shipped native builds lag behind the server; more pressing now that D6 turns the blocks on by default | M | T2 |
+
+## Decisions
+
+| ID | Question asked | Answer | What it changes |
+| --- | --- | --- | --- |
+| D1 | How should the agent express the +/− servings interaction: fixed block types computed on the device, shared state with formulas, or scripted html? | "When they press the button it should round trip to the server for it to process the function callback. That's a callback button like the others we have." | `stepper` − / + are host callbacks through `POST /gpt/actions`; the server returns the replaced block. No formulas, no scripted html. |
+| D2 | Q1: Should checklist ticks also round-trip to the server, like the stepper? | "Callback per tick" | `checklist.callback`, `toggleChecklistHostAction`, and T21. Ticks wait for the server; without a registered checklist action they stay local. |
+| D3 | Q8: Where should a real agent get photos for the gallery and menu list? | First "Generated images", then: "change q8 to generate some images and store them" | A library generated once with the Vertex image model and stored through `FileStorageService` (T19). The agent picks with `findPhotos` and writes `file:` ids, resolved by `GET /photoLibrary/:id/url` (T20). No per-reply generation and no `imageHosts`. |
+| D4 | Q2: Should stepper and checklist changes survive a page reload? | "No (Recommended)" | Overrides stay in client memory. X9 stays parked. |
+| D5 | Approve the plan? | "Approve (Recommended)", given with D2–D4 | Status set to approved with these answers applied. |
+| D6 | (unprompted) | "enable rich blocks by default" | `uiBlocks.richBlocks` and `blocksPromptSection` default to `true`; `false` opts out. AC3 now pins the `false` case to `master` and checks the default. The changelog flags the behaviour change. The stepper still needs a `handles: "stepper"` action. |
+| D7 | (review of the built PR) | "in blocks playground, ensure every kind of block is available. also the serving callback doesn't work. if it cant work, wire up toasts or something. flip the checkboxes to be bold title, then time, then description. none of the images render." | The playground offers a preset per block type and an "All blocks" preset. The stepper and checklist callbacks run locally there through pure `scaleStepperBlock` / `applyChecklistState` helpers moved into `@terreno/blocks` (the host actions call the same helpers); other actions show a toast. Checklist rows read bold title, time, description. Demo stories and presets use bundled public-domain food photos through `file:` ids instead of colour swatches. Tasks T22–T25. |
+
+## Sign-off
+
+Status: approved 2026-10-07 (chat; answers in D2–D6). Built 2026-10-08; AC12 partly met (see AC table).
+Cut: 2 rounds, 23 findings: 21 fixed, 2 moved to questions or expansions (round 1 F4 → Q7, round 2 F2 → Q8, since answered as D3), 0 rebutted. Sign-off answers changed T5, T10, T16–T21; no cut re-run, since less than half the tasks changed and the tracer did not move

package/dist/docs/versioned/next/reference/README.md

@@ -10,7 +10,7 @@ Technical reference for Terreno packages and APIs. Information-oriented, precise
 - [@terreno/ai](ai.md) — AI service, GPT routes, Langfuse integration
 - [@terreno/ai/harness](ai-harness.md) — Durable multi-phase tasks with transactional checkpoints and audit spans
 - [Agent UI Asks](agent-ui-asks.md) — `@terreno/blocks` ask schemas, simple cards, the compact surface, limits, error codes, SSE events, the headless `pendingAsks` and `turn` endpoints, and JSON Schemas for native clients
-- [UI blocks](blocks.md) — whole-reply YAML for leaf and layout blocks: grammar, limits, and error codes
+- [UI blocks](blocks.md) — whole-reply YAML for leaf, layout, and interactive blocks (stepper, checklist, gallery, list, copy): grammar, limits, and error codes
 - [@terreno/admin-backend](admin-backend.md) — Auto-generated admin CRUD endpoints
 - [@terreno/admin-frontend](admin-frontend.md) — Admin panel UI components
 - [@terreno/admin-spa](admin-spa.md) — Standalone admin SPA + Express serve plugin

package/dist/docs/versioned/next/reference/admin-backend.md

@@ -259,6 +259,32 @@ status. `AuditEvent` itself is never audited.
 
 **Important:** Only expose models that should be editable via admin panel. Avoid sensitive internal models.
 
+## Document storage
+
+`DocumentStorageApp` mounts a GCS file browser at `basePath` (default `/documents`): list, upload, download, create folder, and delete.
+
+| Option | Default | Notes |
+| --- | --- | --- |
+| `bucketName` | `GCS_BUCKET` | 503 `Storage not configured` when neither is set |
+| `folderPrefix` | `""` | Root inside the bucket. A non-empty value without a trailing `/` gets one, so `pr-5` and `pr-5/` both scope to `pr-5/` |
+| `access` | `"admin"` | `"authenticated"` also admits signed-in non-admins, confined to `{folderPrefix}users/<userId>/`. Admins always see the whole `folderPrefix` |
+| `uploadRateLimit` | off | `{max, windowMs, store?, keyBy?}` on `POST basePath/` only. Keys by IP by default. See [Rate limiting](../how-to/rate-limiting.md#limit-one-route) |
+| `allowedMimeTypes`, `maxFileSize` | images, PDF, text, Office; 10 MB | Upload filter |
+| `fileUploadsEnabled` | `true` | `false` or `(req) => boolean` rejects uploads; list, download, delete stay on |
+
+```typescript
+new DocumentStorageApp({
+  access: "authenticated",
+  basePath: "/documents",
+  bucketName: process.env.GCS_BUCKET ?? "",
+  uploadRateLimit: {max: 1, store: "mongo", windowMs: 60_000},
+});
+```
+
+Pair it with `DocumentStorageBrowser` from `@terreno/admin-frontend`. Pass `backButton={false}` when the browser is embedded outside admin. Upload failures (including 429) show inline.
+
+Example-backend deploys set `GCS_BUCKET` to the example documents bucket. PR previews also set `GCS_FOLDER_PREFIX` to `pr-<number>/`. Unset `GCS_BUCKET` is the only path that returns 503 `Storage not configured`. A bucket GCS reports as missing lists as an empty folder.
+
 ## Best Practices
 
 - Add `description` to all model fields — flows through to admin UI

package/dist/docs/versioned/next/reference/admin-frontend.md

@@ -240,6 +240,21 @@ const syncConflicts = useConflicts();
 
 ### AdminRolesList
 
+Role cards and the **Available permissions** list split permissions into two groups:
+
+1. **Custom permissions**: actions an app or plugin declared, such as `admin:runScripts` or
+   `user:impersonate`.
+2. **Model permissions**: the actions `modelRouter` and admin model access check: `create`,
+   `list`, `read`, `update`, `delete`, `write`, and `writeOwned`.
+
+A resource with both kinds of action appears in both groups. Each group shows one row per
+resource, with that resource's actions as badges. Badge color shows the kind of access:
+
+- Green: read-only actions (`read`, `list`, `access`, `view*`)
+- Red: destructive actions (`delete`, `destroy`, `remove`)
+- Amber: every other action. Custom actions (such as screen gates like `adminScreen:syncLab`)
+  fall here because the screen cannot tell from the name whether they only read data
+
 Role editing starts with a dedicated **Admin page** toggle for `admin:access`. That is the only
 permission that opens the admin panel. Grant it first; model and tool permissions do nothing until
 the role can enter.