[vishxrad]

Description

Adds thesysdev/openui (@openuidev/a2ui) to the Related Projects table in docs/public/ecosystem/renderers.md.

@openuidev/a2ui is an experimental A2UI v1.0 or later profile from the OpenUI project. It keeps the v1.0 or later lifecycle and envelopes intact (createSurface, updateDataModel, deleteSurface, actions, renderer/agent functions, errors, capabilities, data-model metadata) but represents updateComponents.components as an array of OpenUI Lang statements instead of component JSON objects. The core client is framework-agnostic (it depends on @openuidev/lang-core, not React) and validates incoming messages with exported Zod schemas, so Vue, Svelte, Angular, native or server-side hosts can drive it and supply their own rendering adapter. A React adapter (@openuidev/a2ui/react) ships with the package and renders surfaces through @openuidev/react-lang. MIT licensed.

Because the component representation differs from the Basic Catalog JSON shape, standard A2UI agents are not compatible with it out of the box, so it is listed under Related Projects rather than in the Community Renderers table, and the description says so.

• Source: https://github.com/thesysdev/openui/tree/main/packages/a2ui
• npm: https://www.npmjs.com/package/@openuidev/a2ui
• Docs: https://www.openui.com/docs/api-reference/a2ui

Documentation-only change; no code or CHANGELOG affected.

Pre-launch Checklist

One time:

• I signed the CLA.
• I read the Contributors Guide.
• I read the Style Guide.
• I have built and run at least one sample. (Not applicable: docs-only listing.)

For this PR:

• I have updated the relevant CHANGELOG.md file. (Not applicable: ecosystem docs listing.)
• I updated/added relevant documentation.
• My code changes (if any) have tests. (No code changes.)
• If my branch is on a fork, I have verified that scripts/e2e_test.sh passes. (Not applicable: docs-only change.)

If you need help, consider asking for advice on the discussion board.

[gemini-code-assist]

Code Review

This pull request adds the thesysdev/openui (@openuidev/a2ui) renderer to the ecosystem documentation. The feedback suggests moving this entry from the main 'Community Renderers' table to 'Related Projects' or 'Notable Mentions' because it uses OpenUI Lang statements instead of standard A2UI component JSON objects, which prevents out-of-the-box compatibility with standard A2UI agents.

[gemini-code-assist]

Since @openuidev/a2ui uses OpenUI Lang statements instead of the standard A2UI component JSON objects (Basic Catalog), standard A2UI agents will not be compatible with it out of the box. Marking it as a fully compliant v1.0 or later renderer in the main table with a ✅ could be misleading to users who expect plug-and-play compatibility.

As you noted in the PR description, it would be more appropriate to list this under Related Projects or Notable Mentions rather than the main Community Renderers table, clearly highlighting that it is an experimental profile with a different component representation.

References

1. When documenting protocol or specification versions, use 'version or later' (e.g., 'v1.0 or later') to ensure forward compatibility when describing feature availability or state.

[Varun-S10]

Hi @vishxrad, Thank you for moving the entry to Related Projects. Could you please also update the version wording to v1.0 or later as noted in the bot comment reference?

[vishxrad]

Thanks @Varun-S10! Updated the wording to 'v1.0 or later' in d949d53.