While checking v0.9.1 compatibility in @a2ui/react@0.10.1, I noticed a gap between the v0.9.1 spec and the current published runtime/types.

The v0.9.1 evolution guide says v0.9.1 is compatible with v0.9 payloads, and that schemas accept both "v0.9" and "v0.9.1".

However, in the current published packages:

• @a2ui/react@0.10.1 exposes @a2ui/react/v0_9, but no v0_9_1 renderer export.
• @a2ui/web_core@0.10.1 exposes @a2ui/web_core/v0_9, but no v0_9_1 runtime export.
• The v0_9 server-to-client TypeScript types still narrow message version to "v0.9" only.
• MessageProcessor resolves createSurface.catalogId by exact catalog ID match.
• @a2ui/react@0.10.1 uses the v0.9 Basic catalog ID:
  https://a2ui.org/specification/v0_9/catalogs/basic/catalog.json
  but does not appear to also register the v0.9.1 Basic catalog ID:
  https://a2ui.org/specification/v0_9_1/catalogs/basic/catalog.json.

As a result, it is unclear whether clients are expected to pass v0.9.1 payloads through the existing v0_9 runtime, or whether there should be official v0.9.1-compatible exports/types/catalog IDs.

Could the expected support path for v0.9.1 payloads in @a2ui/react be clarified?