stillmade-sdk 0.1.8 → 0.1.10

package/.stillmade/sdk-baseline.json

@@ -9,7 +9,7 @@
   "examples/clean-text.stillmade.json": "1d0ab95c652b201540fec45918651cdcffa7a70ea7909a17f8c1ad80345797e2",
   "examples/comfy-invert.stillmade.json": "126bd3a8a88e14c08ae11c62a441ed099d83e16830e2062f936e14e56cb297eb",
   "examples/comfy-text-to-image.stillmade.json": "957a616887115984c1888cf9c0eee2fe771dcbf041166ad112fb6c3feb7ad4dd",
-  "examples/custom-interface.stillmade.json": "e824f14f61b21d747a668faae55ad4f8afca9c2942a48436baefaa6925eb5a1b",
+  "examples/custom-interface.stillmade.json": "6177c63be4d47739461d9657defef6cc701fc90556905de79d65d187840a01d7",
   "examples/describe-image.stillmade.json": "1cf5985eaf7c27150815887c2f4550b3c5c716e9f2badda22ace606c082ac7cd",
   "examples/docs-only-campfire-narrator.stillmade.json": "87c6a3b643b1ee007487e162aeced6f6302648f4c4a58b015e7df2ab9f2959be",
   "examples/docs-only-custom-ui.stillmade.json": "4602fd6b9576d364e16b79d2f08b196a251a8e98cf3149576686a96680a5dfe6",

package/AGENTS.md

@@ -6,7 +6,7 @@ This folder is the StillMade Block SDK. Read this file before writing code; it i
 
 Do not tell the user a Block is ready, done or working until `node packages/block-cli/cli.js gate .` passes after your last edit, and report the exact status it prints. In this folder Claude Code (`.claude/settings.json`) and Cursor (`.cursor/hooks.json`) run the gate when you finish a turn and send any failures back to you, but only in a session started in this folder: if you downloaded the SDK during the current session, run the gate yourself. Other agents must also run it themselves. If you cannot fix a failure, say plainly that the Block is not ready and list the failing checks.
 
-Contract `stillmade.block-builder@1.3.0`. Humans, coding agents, imported source, GitHub repositories and generated code all adapt to the Block platform; anything that becomes a StillMade Block obeys this contract.
+Contract `stillmade.block-builder@1.5.1`. Humans, coding agents, imported source, GitHub repositories and generated code all adapt to the Block platform; anything that becomes a StillMade Block obeys this contract.
 
 ## Source of truth
 
@@ -24,6 +24,8 @@ A Step is one job: the work between two moments where a person or the outside wo
 2. **Finding new things turns into handling each one**: the trigger (a schedule or an app event), the app read, its filter and "only new" are the first job; what is done with each item is the next job. A trigger is a setting of the first job, never a Step of its own.
 3. **The result leaves StillMade**: it is sent, posted, published, paid or written into another app. Consecutive writes to the same app, with the glue that shapes data for them, are one job.
 
+In a production the Steps are the workspaces a person opens: work feeding the next workspace is its part, else it joins the one before; neighbouring workspaces with one main result type are one Step unless another part feeds the second. A video ends in the Editor (1.0), which has captions and export built in, so Export video is never a Step beside it.
+
 A part that only runs in the desktop app cannot share a Step with cloud parts. Before adding a Step, name which of the three reasons makes it separate; if none applies, make it a part of a neighbor. A Step nobody would ever open must not exist on its own. Prefer an app task's own filter (a Gmail query such as `has:attachment filename:png`) to an AI check, and use AI decide only for judgement.
 
 Inside one job, each capability stays its own part: a capability Block performs exactly one hosted operation and a connector one app task, so every part keeps its own permission, approval and credit rules, and StillMade groups the parts of one job into one Step (`groups` in the Project Type). Never invent a combined runtime. When one Block can do the whole job with documented primitives (a JavaScript Block doing several local transforms, a workspace owning its whole document), build it as one Block.
@@ -52,7 +54,7 @@ Give the Block a short, plain name of 40 characters or fewer that says what it d
 
 ## Interface
 
-If the capability needs UI, use the Block UI SDK: generated `manifest.ui` controls first; a sandboxed custom view (`view.html`/`view.css`/`view.js`) only when the core interaction genuinely needs one. Expose the capability, not the implementation: meaningful controls, sensible defaults, preview, direct manipulation, progress, clear errors and visible outputs. Do not show raw JSON, internal IDs, filesystem details, provider terminology or developer settings unless the Block is itself a developer tool. When a person chooses among options they need to hear or see (voices, music, sounds, fonts, looks, colors, templates or images), let them preview each option before choosing: a sample to play or a thumbnail, from the Block's own files or the host's free samples, never a paid generation. Leave previews out only when the builder states there is nothing to preview. Choices StillMade owns, such as voices and models in the run review, already show their samples. Follow the host appearance (Light, Dark and White) and the mobile layout contract: one interface for every screen size that fits a 320 CSS-pixel phone without horizontal scrolling.
+If the capability needs UI, use the Block UI SDK: generated `manifest.ui` controls first; a sandboxed custom view (`view.html`/`view.css`/`view.js`) only when the core interaction genuinely needs one. Build custom views from the Block kit the host injects (`block-kit.css`): the result in `sm-stage`, picks as pictures in `sm-choices`, one `sm-primary` naming the action (Write, Generate; never "Run") and no price (StillMade's run button adds it), extras in a closed `sm-more`; a look the person names wins. Fit one laptop screen without scrolling: label beside control, status in a few words, files as tiles, rare tools as icons. Drop words nobody needs; put helpful ones in a closed `sm-hint`. Expose the capability, not the implementation: meaningful controls, sensible defaults, preview, direct manipulation, progress, clear errors and visible outputs. Do not show raw JSON, internal IDs, filesystem details, provider terminology or developer settings unless the Block is itself a developer tool. When a person chooses among options they need to hear or see (voices, music, sounds, fonts, looks, colors, templates or images), let them preview each option before choosing: a sample to play or a thumbnail, from the Block's own files or the host's free samples, never a paid generation. Leave previews out only when the builder states there is nothing to preview. Choices StillMade owns, such as voices and models in the run review, already show their samples. Follow the host appearance (Light, Dark and White) and the mobile layout contract: one interface for every screen size that fits a 320 CSS-pixel phone without horizontal scrolling.
 
 ## Shared editing
 
@@ -78,6 +80,10 @@ A successful run means more than a returned value. Validate inputs before work;
 
 Errors must say what failed, why it likely failed, whether a retry makes sense and what the user can do, so the native project chat and controller can troubleshoot. In JavaScript, throw an `Error` with that message: the host reports it as a `JAVASCRIPT` run failure carrying your message (guest code cannot set its own error code). Reject invalid or oversized input up front with a message naming the input and the limit. Never reduce a failure to "Something went wrong".
 
+## Only supplied facts
+
+A text Block that writes from supplied facts must not let its prompt template outrank its own "never invent" rule. Every section that needs a specific fact (phone, website, address, price, inspection, certification, warranty, features) is written only when the input supplies that fact; otherwise the section is left out or replaced by a generic line that asserts nothing (for example "Call us today to schedule your test drive."). Never default to "inspected", "certified", invented features or placeholder contact details such as 555 numbers or example websites. Prefer extract-then-generate: first list the facts the input actually contains, then write using only that list. Add a check after generation that rejects or removes sentences naming a claim, number or address not present in the input. Include fixtures with the facts omitted and with them supplied.
+
 ## Adapt to the platform
 
 Do not modify StillMade core because a request does not fit immediately. First implement the capability entirely through documented SDK and platform primitives. If that is impossible, classify why: A Block implementation problem (fix it), B missing SDK exposure of an existing host capability, C missing generic platform primitive, D security or permission restriction, E runtime or language incompatibility, F fundamentally incompatible capability. For B or C, name the smallest general primitive that would serve this Block and a meaningful class of future Blocks (shaped like `files.watch()` or `media.transform()`, never `supportThisSpecificBlock()`). Return `{"unsupported":"exact reason","gapClass":"B|C|D|E|F","primitive":"..."}` instead of a package that pretends to work.

package/DESKTOP_CAPABILITIES.md

@@ -72,7 +72,7 @@ stop.addEventListener('click', async () => {
 });
 ```
 
-`record.stop` returns `{asset,cursor,displays,coordinates}`. `asset` is a canonical media reference with `assetId`, `versionId`, `kind`, `mime`, and a device-local `sm-media:` URL. Cursor samples contain `{x,y,time}`: global device-independent screen coordinates and milliseconds relative to recording start. Multiple monitors can have negative coordinates. These are not automatically converted into cropped-window video coordinates. Share/upload media through the existing host media flow before teammates on other devices can use it.
+`record.stop` returns `{asset,cursor,displays,coordinates}`. `asset` is a canonical media reference with `assetId`, `versionId`, `kind`, `mime`, and a device-local `sm-media:` URL. Cursor samples contain `{x,y,time}`: global device-independent screen coordinates and milliseconds relative to recording start. Multiple monitors can have negative coordinates. These are not automatically converted into cropped-window video coordinates. Share/upload media through the existing host media flow before teammates on other devices can use it. By default that flow uploads a 1080p working copy of large video (the account's media setting); the original stays in the desktop media library.
 
 `record.cancel` discards an active capture. `session.close` revokes all access and cancels capture. StillMade also renders a host-owned cancel/revoke control outside the Block iframe. Screen source selection happens for every recording. No preview can bypass consent or access the native bridge directly.
 

package/INTERFACE_DESIGN.md

@@ -1,85 +1,169 @@
 # Block interface design
 
-Simplicity first: show the work and the next useful action. The app owns project navigation; a Block owns its production surface. Neither needs a second shell.
-
-## Mandatory authoring rules — for LLMs and creators
-
-These are requirements, not optional conventions. Authors must follow them;
-they are not all machine-enforced. Explicit user requests may authorize the
-named exception, but do not authorize unrelated technical UI.
-
-- Do not add Technical result, Result details, JSON dumps, source editors,
-  manifests, debug consoles, or diagnostic panels to a production workspace
-  unless the user explicitly requests that surface or the stated task is
-  source/debug inspection. A collapsed disclosure is still an added surface.
-- Do not nest decorative cards, bordered panels, or modal shells around the
-  same work area. Use one workspace with spacing and labels. Nested containers
-  needed for layout are fine; repeated visible framing is not.
-- Do not duplicate the host's step navigation, counters, or workspace identity.
-- Do not append a generic Workflow tools menu to production Blocks. Batch,
-  loop, schedule, memory, migration, and diagnostic tools are not default
-  workspace chrome; add a specific surface only when explicitly requested.
-- Show the useful output itself, not a technical representation of the output.
-- Keep required approvals, errors, progress, and stale-input warnings visible.
-  These are operational feedback, not optional diagnostic panels.
-- Do not lock page scrolling or introduce sticky headers unless the task
-  explicitly needs them. A production page must keep all controls reachable.
-  The host owns page scrolling; embedded workspaces may scroll their own
-  content, but must not trap scrolling or clip controls below the viewport.
-- Do not keep media galleries, asset inputs, or control strips sticky by default.
-  They belong to the same scrolling task surface. A fixed timeline/inspector is
-  appropriate only when the actual editing task requires that layout, with all
-  controls still reachable; it is not a default for every Block.
-- Do not add an ambiguous settings gear for task actions. Show the immediate
-  action directly; label secondary task controls by purpose. Do not disguise
-  source, wiring, or debug controls as ordinary production settings.
-
-For an existing Block, apply the [SDK update procedure](/block-sdk/PASTE_TO_LLM.md#updating-existing-blocks-through-the-sdk)
-to the actual owned source and a new release/remix. These requirements do not
-authorize rewriting published packages or silently repinning saved projects.
-
-## Rules — implemented enforcement
-
-These are implementation facts, not aesthetic suggestions.
-
-- The host supplies the Project Type step bar. Production workspaces do not add another step counter or Back/Next bar.
-- For custom views the host omits its duplicate title and outer frame border. Sandbox isolation remains enabled.
-- The host does not append a generic Technical result disclosure to custom workspaces. Stored outputs and required approval actions are preserved.
-- Shared form containment wraps adjacent labeled controls and keeps checkboxes compact.
-- Admission rejects a primary textarea with 12 or more rows when no task presentation is detected. This is a narrow heuristic, not proof of a usable visual workspace: `StillMade.render` can render text cards.
-- HTML, JavaScript, permission, and appearance validation remain separate checks. Simplicity never bypasses safety or approval.
-
-The SDK exports `INTERFACE_DESIGN_RULES` separately from `INTERFACE_DESIGN_CONVENTIONS`. The older `INTERFACE_DESIGN_PRINCIPLES` export is a compatibility alias for conventions, not enforced guarantees.
-
-## Conventions — design guidance
-
-Static review warns about more than eight visible controls, ungrouped large option sets, and multiple primary headings. Warnings are not hard failures. The following guidance requires design review; it is not automatically enforced.
-
-### Do not
-
-- Repeat the Block name, step number, or workflow navigation in nested panels.
-- Place a workspace in a card inside another card merely to create hierarchy.
-- Use dialogs as permanent page layout or put a dialog inside another dialog.
-- Give every section a border. Use spacing and short labels.
-- Put twenty controls in the initial view, even if they wrap.
-- Show camera, timing, patch, variant, and export settings before they are needed.
-- Make users read a technical plan to reach the actual work.
-- Call text scene descriptions a visual storyboard, frame review, or motion preview.
-- Present placeholder imagery as the actual approved assets.
-- Lead with JSON, manifests, MCP, transport details, or diagnostics.
-- Add decorative circles around icons, emoji controls, or unlabeled icon buttons.
-- Claim approval, rendering, or successful testing without the actual result.
-- Hide spending approvals, failures, or stale-source warnings for neatness.
-- Discard drafts or selections when collapsing controls or changing layout.
-
-### Prefer
-
-One obvious primary action, strong defaults, and the controls needed for the current decision. Group advanced adjustments behind labeled disclosures. Use recognizable line icons with accessible names, tooltips, keyboard focus, and generous hit areas; keep text when an icon is ambiguous.
-
-Use StillMade theme tokens, typography, and spacing. Give the preview, timeline, images, or other task object the main surface. Only include source or diagnostic surfaces when authorized under the mandatory authoring rules above; do not add them automatically, even collapsed.
-
-Motion workflows distinguish planning notes from actual frame approval. Frame Review should display the exact images being approved before Motion Designer uses them. Motion preview should display the composition, not just its layer descriptions. These are product acceptance requirements to verify, not guarantees established by static admission.
-
-## Known coverage gap
-
-Existing pinned Blocks can still contain excessive nested panels and text-only plans. Host containment does not redesign their interfaces. Correct those through new versioned Block releases and explicit upgrades; do not rewrite immutable releases or silently change a saved workflow's pins.
+A Block page should work at a glance: the thing being made is the biggest
+thing on the page, there is one obvious next action, choices are pictures, and
+words appear only when someone needs them. The app owns project navigation;
+a Block owns its production surface. Neither needs a second shell.
+
+Most Blocks need no custom view: generated `manifest.ui` controls already
+follow these rules. Write a custom view only when the core interaction needs
+one, and start it from the Block kit.
+
+## 1. Start from the Block kit
+
+StillMade adds the Block kit stylesheet (`packages/design-system/block-kit.css`)
+to every Block view, standard and frame. Use its classes and ship little or no
+CSS of your own. Every kit rule has zero specificity, so your own CSS always
+wins. Open `packages/design-system/block-kit.html` in a browser to see every
+piece in Light, Dark and White.
+
+```html
+<main class="sm-block" data-layout="split">
+  <section class="sm-stage" id="stage" data-ratio="16:9" aria-live="polite">
+    <div class="sm-empty" id="empty">
+      <span class="sm-glyph" data-glyph="video" aria-hidden="true"></span>
+      <p>Drop a clip</p>
+    </div>
+  </section>
+
+  <fieldset class="sm-choices" id="look" data-stillmade-share="look" data-ratio="16:9">
+    <legend>Look</legend>
+    <label><input type="radio" name="look" value="warm" checked><img src="data:..." alt=""><span>Warm</span></label>
+    <label><input type="radio" name="look" value="cool"><img src="data:..." alt=""><span>Cool</span></label>
+  </fieldset>
+
+  <div class="sm-field">
+    <div class="sm-label">
+      <label for="caption">Caption</label>
+      <details class="sm-hint"><summary aria-label="About captions" title="About captions"></summary><p>Shown over the first two seconds.</p></details>
+    </div>
+    <input id="caption" data-stillmade-input="caption" placeholder="Optional">
+  </div>
+
+  <div class="sm-actions">
+    <button type="button" class="sm-primary" id="run" data-stillmade-action="run">Make it</button>
+    <p class="sm-status" id="status" role="status"></p>
+  </div>
+
+  <details class="sm-more">
+    <summary>More</summary>
+    <div class="sm-fields"><!-- secondary settings --></div>
+  </details>
+</main>
+```
+
+| Class | Use it for |
+| --- | --- |
+| `sm-block` | The one workspace. `data-layout="split"` puts the stage beside the controls on wide screens. |
+| `sm-stage` | The thing being made: preview, media or result. `data-ratio="16:9"`, `"9:16"` or `"1:1"`. |
+| `sm-empty` | An empty stage: a glyph, at most five words, one action. |
+| `sm-choices` | Picks shown as pictures (`img`, `.sm-swatch`, `.sm-glyph`) and one or two words. `data-compact` for short text chips. Give the `fieldset` an `id` and `data-stillmade-share` so teammates see the same pick. |
+| `sm-field`, `sm-fields` | A short label above one control; a responsive group of them. |
+| `sm-actions` | One `sm-primary`, then `sm-quiet` buttons and `sm-icon` buttons (each with `aria-label` and `title`). |
+| `sm-status` | Live state beside the action: `data-state="loading"`, `"success"`, `"waiting"` or `"error"`. |
+| `sm-more` | A closed `<details>` for secondary settings. |
+| `sm-hint` | A closed `<details>` info toggle for an explanation that might help. |
+| `sm-gallery` | A grid of results or media. |
+| `sm-glyph` | A small icon in `currentColor`: `play`, `pause`, `plus`, `close`, `check`, `chevron`, `upload`, `image`, `video`, `audio`, `text`, `spark`, `info`, `warning`, `spinner`. Works in standard views, which cannot use SVG. |
+
+**Function first.** When the person building a Block does not ask for a look,
+use the kit as is: they want it to work and be easy to use. When they name a
+design direction, follow it; the kit is the default, not a ceiling. Original
+designs keep `appearance: "original"`.
+
+## 2. Decide every sentence
+
+| If the words… | Then |
+| --- | --- |
+| aren't needed to finish the task (an intro, "how it works", the Block name again, a description of what is already visible) | Drop them. |
+| say what a glyph, thumbnail, swatch or sample can show | Show the picture. Keep one or two words under it. |
+| might help some people (what a setting does, a format limit) | Put them in a closed `sm-hint`, or secondary settings in a closed `sm-more`. |
+| report an error, a spending approval, a stale input or a destructive step | Keep them visible, in few words. Say what to do next. |
+
+Buttons say the action in one to three words ("Make it", "Export"). Status says
+the state in one to four words ("Making", "Ready", "Needs approval").
+
+The button that makes something names what it makes ("Write", "Generate image",
+"Make video"), never "Run", "Run step", "Submit" or "Review cost", and says the
+progress word while it works ("Writing…").
+
+Credit prices come from StillMade, never from the Block. On a Step, StillMade's
+run button carries the price beside the verb ("Write · 1 credit"), with a chip
+before it when the model, quality or count can change; each choice there shows
+its own price. When a custom view starts paid work, StillMade's run review shows
+the same single priced button. Pressing a priced button runs at that price; a
+confirmation appears only when the server's price is higher than the one shown.
+Do not write credit numbers in the Block.
+
+## 3. Rules
+
+These are requirements for every author, person or model. Not all are checked
+automatically. An explicit request from the person can authorize a named
+exception, never unrelated technical UI.
+
+1. Show the thing being made, not a technical representation of it. No JSON
+   dumps, source editors, manifests, debug consoles or "Technical result"
+   panels unless the task is about source. A collapsed disclosure is still an
+   added surface.
+2. One obvious next action. Seven or fewer choices in view; strong defaults.
+3. Choices people see or hear (voices, music, sounds, fonts, looks, colors,
+   templates, images) show a preview of each option: a thumbnail or a sample
+   to play, never a paid generation.
+4. One workspace. No cards inside cards, no dialogs as page layout, no second
+   title, step counter, Back/Next bar or generic "Workflow tools" menu.
+5. Keep the page in normal scroll flow. No sticky media, headers or control
+   strips unless the editing task needs a fixed timeline or inspector.
+6. Name secondary controls by purpose; no ambiguous settings gear.
+7. Icons come from the kit glyphs or your own files, with an accessible name
+   and tooltip. Never emoji, never a circle around an icon.
+8. Never hide spending approvals, failures or stale-source warnings for
+   neatness, and never discard drafts when collapsing controls.
+9. Text scene descriptions are planning notes, never a storyboard, frame review
+   or motion preview. Frame Review shows the exact images being approved.
+10. Compact: the whole Block fits one laptop screen (about 720 px tall)
+    without scrolling, and a 320 px phone without sideways scrolling. If it
+    does not fit, fold, shrink or move something; never add a section below.
+11. A short setting is one row, its label beside the control (the kit's
+    `sm-field` does this on any view wider than a phone). No card around a
+    single control.
+12. Status is a dot or a few words ("No narration yet"), never a paragraph.
+    The reason sits behind an `sm-hint`.
+13. Files are tiles: a saved file is a thumbnail or chip, and adding one is a
+    + tile (a `label` around a hidden file input). Never the browser's bare
+    "Choose File / No file chosen" picker, and no size limits in view until
+    a file is too big.
+14. Rare tools (update, schedule, history, reload) are named icon buttons
+    beside the action, never sections under the work.
+
+## 4. What StillMade checks
+
+- Admission rejects a primary textarea of 12 or more rows when no task
+  presentation (stage, media, list or `StillMade.render`) is detected
+  (`INTERFACE_DESIGN_RULES`).
+- Admission warns about more than eight visible controls, more than seven
+  ungrouped options, more than one `h1`, a visible paragraph over twenty words,
+  a word dropdown for something people see or hear, a bare browser file
+  picker, and a size limit printed in view.
+- Admission also warns, and `stillmade-block ready` fails the "UI works" check
+  (DOD-15), when a button says "Run", "Run step" or "Submit", when the
+  interface shows a credit price, or when it has a page heading
+  (`blockKitProblems`; the failing rules are `BLOCK_KIT_READINESS_RULES`). StillMade's own Block builder also sends back a custom
+  view that is not built from `sm-block`, unless the person asked for their
+  own look (`appearance: "original"`).
+- The host supplies the Project Type step bar and omits its own title and frame
+  around custom views, and does not add a "Technical result" disclosure.
+- HTML, JavaScript, permission and appearance validation are separate checks.
+  Simplicity never bypasses safety or approval.
+
+The SDK exports the ordered principles as `BLOCK_INTERFACE_PRINCIPLES` and the
+kit vocabulary as `BLOCK_KIT_CLASSES`. `INTERFACE_DESIGN_CONVENTIONS`,
+`INTERFACE_DESIGN_PRINCIPLES` and `INTERFACE_AUTHORING_RULES` remain as
+compatibility names for the same list.
+
+## Existing Blocks
+
+Pinned Blocks can still contain nested panels and text-only plans; the kit does
+not redesign them. Move a Block to the kit through a new versioned release and
+an explicit upgrade, following the
+[SDK update procedure](/block-sdk/PASTE_TO_LLM.md#updating-existing-blocks-through-the-sdk).
+Never rewrite immutable releases or silently change a saved workflow's pins.

package/MODULES.md

@@ -49,7 +49,7 @@ against the manifest's port types.
 | `progress(value, label)` | Reports progress from 0 to 1 with a short label. Each report extends the run limit. |
 | `log(...values)` | Adds a line to the run log (up to 500 lines). |
 | `asset(path)` | A copy of one of the module's own files, such as a `.wasm` build, as an `ArrayBuffer`. |
-| `files.read(ref)` | The bytes of a saved image, video, audio or asset the Block received as input, or that StillMade made in this run: files it wrote, transform results and generated media. Other files cannot be read, and transforms, hosted calls and actions accept only these references too. |
+| `files.read(ref)` | The bytes of a saved image, video, audio or asset the Block received as input, or that StillMade made in this run: files it wrote, transform results and generated media. Media the person kept on their device (a `sm-media://device/...` address in a project Step) reads the same way, without leaving the device. Other files cannot be read, and transforms, hosted calls and actions accept only these references too; a hosted call or action gets a cloud copy of device media, made once per version. |
 | `files.write(data, {mediaType, name})` | Saves PNG, JPEG, WebP, GIF, MP4, WebM, MP3, WAV, M4A or OGG to the runner's library and returns a reference you can return as an output. At most 64 files per run. |
 | `media.transform(request)` | On-device media work done by StillMade: decode audio to samples, extract or loudness-normalise audio, cut, join or re-encode video, and take thumbnails. Results are saved like `files.write`. See [Media processing](#media-processing). |
 | `actions.run(action)` | Runs a declared portable action. `media.generate` asks the person to approve one StillMade credit maximum for the batch; `stock.search` runs directly. |

package/NATIVE_MCP.md

@@ -208,7 +208,7 @@ expose the former live-tab control bridge. The remote MCP adapter remains availa
 for the catalog, creation, saved-project, and run-inspection tools listed above,
 but it cannot control an open StillMade tab.
 
-Supported saved-project workflow edits: `begin_project_block_remix` starts a private Create draft from the exact pinned Block source. After `get_creation` / `save_creation` edits, `preview_project_workflow_edit` and `apply_project_workflow_edit` add, replace, move or remove a Block in the Project Type. Add/replace require a complete saved Block creation draft and `creations:read`; the Block passes static SDK admission and a remix must identify the exact current parent. Apply requires `projects:read`, `projects:write`, the three preview digests and a unique request ID. It commits the Type and Canvas together, pins the exact package, and archives affected results. The call does not run a Block. `prepare_project_type_draft` copies the current exact project workflow and embedded Block code to Create for listing review; only the project owner can do this, with `projects:read` and `creations:write`. It returns whether the project stayed current during the handoff. It does not publish.
+Supported saved-project workflow edits: `begin_project_block_remix` starts a private Create draft from the exact pinned Block source. After `get_creation` / `save_creation` edits, `preview_project_workflow_edit` and `apply_project_workflow_edit` add, replace, move or remove a Block in the Project Type. Add/replace require a complete saved Block creation draft and `creations:read`; the Block passes static SDK admission and a remix must identify the exact current parent. Apply requires `projects:read`, `projects:write`, the three preview digests and a unique request ID. It commits the Type and Canvas together, pins the exact package, and archives affected results. The call does not run a Block. `prepare_project_type_draft` copies the current exact project workflow and embedded Block code to Create for listing review; only the project owner can do this, with `projects:read` and `creations:write`. It returns whether the project stayed current during the handoff. When the account already has a Project Type with the same name and no `entityId` is given, it saves nothing and names that Project Type (`AGENT_CONFLICT`): ask the person, then pass its `entityId` and revision to update it, or `separateCopy: true` for a new copy. It does not publish.
 
 Local verification on September 27, 2026: focused PGlite workflow mutation and MCP capability tests covered exact Block draft replacement, move replay, remix ancestry, and listing draft source/version handoff; project workflow and Create-draft tests passed; the client production build completed. These checks do not establish a live account or production deployment acceptance.