Version Packages#41
Merged
Merged
Conversation
gitsad
approved these changes
Jul 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@mobile-reality/mdma-agui@0.2.0
Minor Changes
initialStateoption tocreateDocumentStorefor hydrating component values at storecreation — e.g. restoring a persisted conversation fetched from a backend. Keyed by component id →
its
valuesmap (symmetric withgetState()), it overlays AST defaults without emitting auditevents or marking fields
touched, and applies only to freshly-created components so a streamingre-parse never clobbers in-flight edits.
mdma-aguithreadsinitialStatethroughparseMdma,the bridge, and
MdmaAgentView/useMdmaAgentStream, so re-opened conversations renderpre-populated.
@mobile-reality/mdma-agui: a bridge that renders MDMA interactive documents streamed overthe AG-UI protocol and routes user actions (submit / approve / deny) back into the agent run.
Ships a headless core (
createMdmaAgentBridge) plus an optional React layer(
useMdmaAgentStream,MdmaAgentView). AG-UI coupling is isolated to a minimal structural agentinterface, so any
@ag-ui/clientHttpAgentworks without a hard dependency.emits
ACTION_TRIGGERED(itsonCompleteaction) on the transition into all-items-checked, andthe webhook renderer gains a trigger button that emits
INTEGRATION_CALLED. Themdma-aguibridge routes both back into the agent run — alongside form submit, button, and approve/deny — so
completing a checklist or firing a webhook resumes the AG-UI conversation.
Patch Changes
mdmafence isnot yet closed, a valid-YAML-but-unknown type (e.g. a half-streamed
approval-gatbeforeapproval-gatefinishes) is now left as a pending block (loading skeleton) instead of beingrendered as an unknown-type error. Once the fence closes, a genuinely unknown type still surfaces
the error as before. Known valid types continue to render live during streaming. The
mdma-aguiadapter now threads the source into
unified.run()so the parser can see the raw fences.@mobile-reality/mdma-renderer-react@0.4.0
Minor Changes
emits
ACTION_TRIGGERED(itsonCompleteaction) on the transition into all-items-checked, andthe webhook renderer gains a trigger button that emits
INTEGRATION_CALLED. Themdma-aguibridge routes both back into the agent run — alongside form submit, button, and approve/deny — so
completing a checklist or firing a webhook resumes the AG-UI conversation.
Patch Changes
@mobile-reality/mdma-runtime@0.3.0
Minor Changes
initialStateoption tocreateDocumentStorefor hydrating component values at storecreation — e.g. restoring a persisted conversation fetched from a backend. Keyed by component id →
its
valuesmap (symmetric withgetState()), it overlays AST defaults without emitting auditevents or marking fields
touched, and applies only to freshly-created components so a streamingre-parse never clobbers in-flight edits.
mdma-aguithreadsinitialStatethroughparseMdma,the bridge, and
MdmaAgentView/useMdmaAgentStream, so re-opened conversations renderpre-populated.
Patch Changes
DocumentStore.updateAstfreezing a component'stypefor the lifetime of its id. Duringstreaming, an early partial parse can produce a placeholder/truncated type (e.g.
approval-gatbefore
approval-gatefinishes streaming);updateAstnow re-initializes a component when itstype changes between parses, while still preserving in-flight state (values, touched) when the
type is unchanged.
@mobile-reality/mdma-attachables-core@0.2.4
Patch Changes
onActionmethods from the core attachable handlers (form, button, tasklist,table, callout, approval-gate, webhook). They were never invoked — renderers dispatch store actions
directly — so this is a dead-code cleanup with no behavioral change. Each handler's
definitionandinitializeare unchanged.@mobile-reality/mdma-cli@0.2.8
Patch Changes
@mobile-reality/mdma-parser@0.2.4
Patch Changes
mdmafence isnot yet closed, a valid-YAML-but-unknown type (e.g. a half-streamed
approval-gatbeforeapproval-gatefinishes) is now left as a pending block (loading skeleton) instead of beingrendered as an unknown-type error. Once the fence closes, a genuinely unknown type still surfaces
the error as before. Known valid types continue to render live during streaming. The
mdma-aguiadapter now threads the source into
unified.run()so the parser can see the raw fences.@mobile-reality/mdma-validator@0.3.1
Patch Changes
@mobile-reality/mdma-demo@0.0.12
Patch Changes