Changelog

On the 'renders every time' measure MDMA scores 94.4% on both Opus 5 and the open-weights Gemma-4-26B — a 0.0pp drop between tiers. OpenUI Lang drops 27.8pp over the same two models and json-render drops 44.4pp.

Every format was given its own published system prompt and scored with its own validator, on a byte-identical user message with no format hints. The report discloses where a format's own validator disagrees with the harness.

System-prompt size is part of the bill: OpenUI Lang 5172 tokens, MDMA 5910, json-render 8466, A2UI 19689. Mean output tokens and a renderable-per-1k-tokens efficiency figure are reported per model.

Forms, tables, charts, approval gates and the rest of the catalog as interactive Vue 3 components, with full state, bindings, actions, policy, audit and PII redaction from the same spec + runtime stack.

useComponentState, useBinding and useDocumentState return ComputedRefs, so reads stay reactive. MdmaProvider, MdmaThemeProvider, element overrides and custom variants are wired through provide/inject with exported InjectionKeys.

The Vue package ships the same --mdma-* driven styles.css as the React renderer, so a theme object moves between the two unchanged. Components are defineComponent + h() in plain .ts — no SFCs, no bundler.

type: custom carries a name that selects a host-registered variant, a props record for its inputs and an actions map for its events. A model cannot invent type: timer, but it can emit type: custom with name: timer once that variant is in the catalog the host passes to buildSystemPrompt.

One runtime call registers a variant's handler and its props schema together. The parser validates the envelope against the union, then the props against the matching entry in customSchemas, prefixing errors with props.*.

An unknown name passes the parse rather than failing it, so a document authored against a richer host still renders elsewhere; the renderer draws an inline notice instead of nothing.

Author, fixer and agent prompts document the envelope. Adds tuned variants for GPT-5.6 (sol / terra / luna), Claude Opus 4.8, Fable 5, Gemini 3.5 Flash and Grok 4.5.

A backend that would rather not interleave documents into visible prose can emit them on a CUSTOM event named mdma. Both channels feed one parse → store → render pipeline.

Tool calls, run steps and reasoning streams surface as an ordered feed via bridge.activity, each with a stable id, a kind, a label, a running/done status and streamed detail. Agent chatter and rendered components stay decoupled — render it as a timeline beside the documents, or ignore it.

Interrupts on RUN_FINISHED surface as bridge.interrupts, with resumeMode of auto, interrupt or user-turn. Returning false from onAction hands resumption to the caller.

Pass a preset, follow the OS preference with auto, or hand over a full MdmaTheme token object. Omit the prop and nothing changes — the default light look is unaffected.

The web stylesheet is driven by --mdma-* variables applied via data-theme or inline, so a theme can also be overridden directly in CSS. A document with no theme prop inherits from an ancestor MdmaThemeProvider.

Button hover and the input focus ring derive from the base tokens through color-mix, so a custom primary gets a coherent hover and focus instead of the built-in purple. A custom dark theme also selects the dark base, so headings and code backgrounds follow.

The React Native defaults were a blue-primary palette; they now match the web renderer's light and dark themes exactly. The native table and chart renderers, whose bodies had no themed background, now fill their container.

Renders the built-in component types plus inline Markdown as native UI. Only the view layer is reimplemented with RN primitives — spec and runtime are shared with the web renderer.

Ships MdmaDocument, per-component renderers, an MdmaThemeProvider with light and dark tokens, and customizations support.

The tasklist renderer emits ACTION_TRIGGERED on the transition into all-items-checked, and the webhook renderer gains a trigger button emitting INTEGRATION_CALLED. The bridge routes both back into the agent run alongside submit, button and approve/deny.

Hydrate component values at store creation — restoring a persisted conversation, for instance. It overlays AST defaults without emitting audit events or marking fields touched, and applies only to freshly created components so a streaming re-parse never clobbers in-flight edits.

A half-streamed type inside an unclosed fence is held as a pending block with a loading skeleton instead of rendering an unknown-type notice, and updateAst re-initialises a component when its type changes between parses.

A headless core, createMdmaAgentBridge, plus an optional React layer of useMdmaAgentStream and MdmaAgentView. Submit, approve and deny travel back into the run.

AG-UI coupling is isolated to a minimal structural agent interface, so any @ag-ui/client HttpAgent works. A conformance test type-checks that interface against the real packages without shipping them.

getAuthorPromptVariant('mobile-reality/mdma-il') returns the full authoring prompt — DSL input grammar, authoring rules and worked form, table and chart examples. The previous variant had none, which put the model out of distribution.