OpenUI Lang profile for A2UI v1.0 - feedback on an experimental a2ui adapter

[vishxrad]

We’ve implemented an experimental A2UI v1.0 integration in OpenUI:

thesysdev/openui#854

The proposed @openuidev/a2ui package preserves the A2UI v1.0 surface lifecycle and bidirectional message envelopes, including data-model updates, actions, function calls, responses, errors, capabilities, and renderer
metadata.

The deliberate difference is the component representation:
createSurface.components and updateComponents.components contain OpenUI Lang statements instead of A2UI catalog component JSON.

The package includes:

• A framework-neutral protocol client
• Incremental surface and data-model updates
• Current A2UI v1.0 candidate RPC envelopes
• An optional React adapter using @openuidev/react-lang
• Runtime Zod schemas, documentation, and 32 tests

Before publishing @openuidev/a2ui, we’d appreciate feedback from the A2UI maintainers and community:

1. Does this look useful as an ecosystem integration or experimental profile?
2. Is the package naming sufficiently clear about the component-format difference?
3. What interoperability or compliance expectations should we meet before publishing?
4. Once published, would this fit under Related Projects or Notable Mentions in the A2UI ecosystem documentation?

The package is not published yet. We’d like to validate interest and positioning with the A2UI community first.