Merge branch 'upstream/main' into angular-explorer-08-support

Author: josemontespg

.github/workflows/docs.yml

@@ -76,7 +76,7 @@ jobs:
         run: |
           cp -R specification/* docs/specification/
           # Flatten JSON files to version roots to support clean URLs without redirects
-          for version in v0_8 v0_9; do
+          for version in v0_8 v0_9 v0_10; do
             if [ -d "docs/specification/$version/json" ]; then
               cp docs/specification/$version/json/*.json docs/specification/$version/
             fi

.prettierrc

@@ -19,6 +19,13 @@
       "options": {
         "singleQuote": false
       }
+    },
+    {
+      "files": "docs/**/*.md",
+      "options": {
+        "embeddedLanguageFormatting": "off",
+        "tabWidth": 4
+      }
     }
   ]
 }

agent_sdks/python/src/a2ui/basic_catalog/constants.py

@@ -21,5 +21,5 @@
     VERSION_0_8: {
         CATALOG_SCHEMA_KEY: "specification/v0_8/json/standard_catalog_definition.json"
     },
-    VERSION_0_9: {CATALOG_SCHEMA_KEY: "specification/v0_9/json/basic_catalog.json"},
+    VERSION_0_9: {CATALOG_SCHEMA_KEY: "specification/v0_9/catalogs/basic/catalog.json"},
 }

agent_sdks/python/src/a2ui/schema/catalog.py

@@ -280,7 +280,7 @@ def _with_pruned_common_types(self) -> "A2uiCatalog":
 
     root_common_types = []
     for ref in external_refs:
-      if ref.startswith("common_types.json#/$defs/"):
+      if "common_types.json#/$defs/" in ref:
         root_common_types.append(ref.split("#/$defs/")[-1])
 
     new_common_types_schema = copy.deepcopy(self.common_types_schema)

docs/concepts/actions.md

@@ -237,7 +237,7 @@ Renderers include an `a2uiClientCapabilities` object in the **metadata** of thei
 {
   "v0.9": {
     "supportedCatalogIds": [
-      "https://a2ui.org/specification/v0_9/basic_catalog.json",
+      "https://a2ui.org/specification/v0_9/catalogs/basic/catalog.json",
       "https://my-company.com/catalogs/v1/custom.json"
     ],
     "inlineCatalogs": []

docs/concepts/catalogs.md

@@ -57,15 +57,15 @@ Whether you are building a simple prototype or a complex production application,
 
 ### The Basic Catalog
 
-To help developers get started quickly, the A2UI team maintains the [Basic Catalog](../../specification/v0_9/json/basic_catalog.json).
+To help developers get started quickly, the A2UI team maintains the [Basic Catalog](../../specification/v0_9/catalogs/basic/catalog.json).
 
 This is a pre-defined catalog file that contains a basic set of general-purpose components (Buttons, Inputs, Cards) and functions. It is not a special "type" of catalog; it is simply a version of a catalog that we have already written and have open source renderers for.
 
 The basic catalog allows you to bootstrap an application or validate A2UI concepts without needing to write your own schema from scratch. It is intentionally sparse to remain easily implementable by different renderers.
 
 Since A2UI is designed for LLMs to generate the UI at either design time or runtime, we do not think portability requires a standardized catalog across multiple clients; the LLM can interpret the catalog for each individual frontend.
 
-[See the A2UI v0.9 basic catalog](../../specification/v0_9/json/basic_catalog.json)
+[See the A2UI v0.9 basic catalog](../../specification/v0_9/catalogs/basic/catalog.json)
 
 ### Defining Your Own Catalog
 
@@ -163,7 +163,7 @@ where:
 - `--version`: The A2UI specification version to use for official catalog
   fallbacks. Choices are `0.9` or `0.10`. Defaults to `0.9`.
 - `--extend-basic-catalog`: If passed, automatically includes the entirety of
-  `basic_catalog.json` in the root output regardless of whether the input
+  `catalogs/basic/catalog.json` in the root output regardless of whether the input
   catalogs explicitly reference it.
 - `--out-dir`, `-o`: The directory where the assembled catalog will be saved. Defaults to `dist`.
 - `--verbose`, `-v`: If passed, enables verbose debug logging to help diagnose issues.
@@ -211,7 +211,7 @@ This catalog imports only `Text` from the Basic Catalog to build a simple Popup
   "$id": "https://github.com/.../hello_world_with_some_basic/v1/catalog.json",
   "components": {
     "allOf": [
-      {"$ref": "basic_catalog.json#/components/Text"},
+      {"$ref": "catalogs/basic/catalog.json#/components/Text"},
       {
         "Popup": {
           "type": "object",
@@ -297,7 +297,7 @@ Example of an A2A AgentCard advertising that the agent supports the basic and ri
         "description": "Provides agent driven UI using the A2UI JSON format.",
         "params": {
           "supportedCatalogIds": [
-            "https://a2ui.org/specification/v0_9/basic_catalog.json",
+            "https://a2ui.org/specification/v0_9/catalogs/basic/catalog.json",
             "https://github.com/.../rizzcharts_catalog_definition.json"
           ]
         }
@@ -323,7 +323,7 @@ Example of A2A message containing the supportedCatalogIds in metadata
   "metadata": {
     "a2uiClientCapabilities": {
       "supportedCatalogIds": [
-        "https://a2ui.org/specification/v0_9/basic_catalog.json",
+        "https://a2ui.org/specification/v0_9/catalogs/basic/catalog.json",
         "https://github.com/.../rizzcharts_catalog_definition.json"
       ]
     }
@@ -341,7 +341,7 @@ Example A2UI Message from the agent defining the catalog_id used in a surface
 {
   "createSurface": {
     "surfaceId": "salesDashboard",
-    "catalogId": "https://a2ui.org/specification/v0_9/basic_catalog.json"
+    "catalogId": "https://a2ui.org/specification/v0_9/catalogs/basic/catalog.json"
   }
 }
 ```
@@ -366,18 +366,18 @@ While standard JSON parsers ignore unknown fields, dropping a component in a Ser
 
 - **Breaking Changes (Major Version Bump Required)**  
   Any change that alters structure in a way that cannot be safely ignored by older clients incrementing the **Major** version in the `catalogId` URI (e.g., `v1` to `v2`).
-  - **Adding a container component:** e.g., adding a `Grid` or `Accordion` component. If an older client ignores a container, it will drop all of its children, breaking the UI tree.
-  - **Removing a container component:** e.g., removing a `Grid` or `Accordion` component. If an older agent uses the container it would be ignored by the client, and the client would drop all of its children, breaking the UI tree.
-  - **Changing field types:** e.g., changing a property from a `string` to an `object`. This will fail JSON Schema validation on older clients.
-  - **Adding a required property:** without a default value, as older agents won't know to send it.
+    - **Adding a container component:** e.g., adding a `Grid` or `Accordion` component. If an older client ignores a container, it will drop all of its children, breaking the UI tree.
+    - **Removing a container component:** e.g., removing a `Grid` or `Accordion` component. If an older agent uses the container it would be ignored by the client, and the client would drop all of its children, breaking the UI tree.
+    - **Changing field types:** e.g., changing a property from a `string` to an `object`. This will fail JSON Schema validation on older clients.
+    - **Adding a required property:** without a default value, as older agents won't know to send it.
 
 - **Non-Breaking Changes (Allowable under Major Version)**  
   Changes that can be safely ignored or degrade gracefully without breaking the layout or data model can stay at the current version.
-  - **Adding a leaf component (non-container):** e.g., adding `Badge` or `Tooltip`. If ignored, the layout remains intact.
-  - **Adding an optional property:** e.g., adding `subtitle` to a Card.
-  - **Removing a property:** Safe for the client to ignore if the agent stops sending it.
-  - **Adding new functions or styles:** These can generally be ignored without changing the semantic meaning of the component.
-  - **Metadata Changes:** Updating `description` fields or fixing typos in docs requires no version bump and has no impact on runtime.
+    - **Adding a leaf component (non-container):** e.g., adding `Badge` or `Tooltip`. If ignored, the layout remains intact.
+    - **Adding an optional property:** e.g., adding `subtitle` to a Card.
+    - **Removing a property:** Safe for the client to ignore if the agent stops sending it.
+    - **Adding new functions or styles:** These can generally be ignored without changing the semantic meaning of the component.
+    - **Metadata Changes:** Updating `description` fields or fixing typos in docs requires no version bump and has no impact on runtime.
 
 ### Graceful Degradation
 
@@ -388,14 +388,14 @@ While standard JSON parsers ignore unknown fields, dropping a component in a Ser
 Here is how catalog version mismatches are handled in practice:
 
 - **An old iOS client is using an older catalog than the agent**
-  - The agent sends a new component `Badge` that the old iOS client doesn't know about. The client renders a generic textbox placeholder or safe text description for it, keeping the rest of the interface functional.
-  - The agent sends a new property `badge` on a `Button` that an old client doesn't know about. The client safely ignores it and renders the basic button.
-  - The agent no longer sends the `Facepile` component that was removed in a later catalog version. This causes no issues for the client.
+    - The agent sends a new component `Badge` that the old iOS client doesn't know about. The client renders a generic textbox placeholder or safe text description for it, keeping the rest of the interface functional.
+    - The agent sends a new property `badge` on a `Button` that an old client doesn't know about. The client safely ignores it and renders the standard button.
+    - The agent no longer sends the `Facepile` component that was removed in a later catalog version. This causes no issues for the client.
 
 - **A web client rolls out a new catalog version ahead of the agent**
-  - The web client supports the new `Badge` component, but the agent doesn't know about it yet.
-  - The web client removed the `badge` property on `Button`, so it ignores it if the agent sends it.
-  - The web client added new styles for `Button` that the agent doesn't know about. Again this causes no issues as the agent doesn't use them.
+    - The web client supports the new `Badge` component, but the agent doesn't know about it yet.
+    - The web client removed the `badge` property on `Button`, so it ignores it if the agent sends it.
+    - The web client added new styles for `Button` that the agent doesn't know about. Again this causes no issues as the agent doesn't use them.
 
 ### Versioning with CatalogId
 
@@ -423,11 +423,11 @@ To ensure a stable user experience, A2UI employs a two-phase validation strategy
 ### Two-Phase Validation
 
 1. **Agent-Side (Pre-Send):** Before transmitting any UI payload, the agent runtime validates the generated JSON against the catalog definition.
-   - Purpose: To catch hallucinated properties or malformed structures at the source.
-   - Outcome: If validation fails, the agent can attempt to fix or regenerate the A2UI JSON, or it can do graceful degradation such as falling back to text in a conversational app.
+    - Purpose: To catch hallucinated properties or malformed structures at the source.
+    - Outcome: If validation fails, the agent can attempt to fix or regenerate the A2UI JSON, or it can do graceful degradation such as falling back to text in a conversational app.
 2. **Client-Side:** Upon receiving the payload, the client library validates the JSON against its local definition of the catalog.
-   - Purpose: Security and stability. This ensures that the code executing on the user's device strictly conforms to the expected contract, protecting against version mismatches or compromised agent outputs.
-   - Outcome: Failures here are reported back to the agent using the “error” client message
+    - Purpose: Security and stability. This ensures that the code executing on the user's device strictly conforms to the expected contract, protecting against version mismatches or compromised agent outputs.
+    - Outcome: Failures here are reported back to the agent using the “error” client message
 
 ### Graceful Degradation
 

docs/concepts/components.md

@@ -171,7 +171,7 @@ Every component has:
 
 ## The Basic Catalog
 
-To help developers get started quickly, the A2UI team maintains the [Basic Catalog](../../specification/v0_9/json/basic_catalog.json).
+To help developers get started quickly, the A2UI team maintains the [Basic Catalog](../../specification/v0_9/catalogs/basic/catalog.json).
 
 This is a pre-defined catalog file that contains a basic set of general-purpose components (Buttons, Inputs, Cards). It is not a special "type" of catalog; it is simply a version of a catalog that has open source renderers available.
 

docs/concepts/data-binding.md

@@ -174,32 +174,33 @@ Adding/removing items automatically updates the rendered components.
 
 Interactive components update the data model bidirectionally:
 
-| Component          | Example                                     | User Action      | Data Update              |
-| ------------------ | ------------------------------------------- | ---------------- | ------------------------ |
-| **TextField**      | `{"text": {"path": "/form/name"}}`          | Types "Alice"    | `/form/name` = "Alice"   |
-| **CheckBox**       | `{"value": {"path": "/form/agreed"}}`       | Checks box       | `/form/agreed` = true    |
-| **MultipleChoice** | `{"selections": {"path": "/form/country"}}` | Selects "Canada" | `/form/country` = ["ca"] |
+| Component          | Example                                     | User Action      | Data Update                |
+| ------------------ | ------------------------------------------- | ---------------- | -------------------------- |
+| **TextField**      | `{"text": {"path": "/form/name"}}`          | Types "Alice"    | `/form/name` = `"Alice"`   |
+| **CheckBox**       | `{"value": {"path": "/form/agreed"}}`       | Checks box       | `/form/agreed` = `true`    |
+| **MultipleChoice** | `{"selections": {"path": "/form/country"}}` | Selects "Canada" | `/form/country` = `["ca"]` |
 
 ## Best Practices
 
 - **Use granular updates**: Update only changed paths.
 
-  ```json
-  {
-    "dataModelUpdate": {
-      "path": "/user",
-      "contents": [{"key": "name", "valueString": "Alice"}]
+    ```json
+    {
+      "dataModelUpdate": {
+        "path": "/user",
+        "contents": [{"key": "name", "valueString": "Alice"}]
+      }
     }
-  }
-  ```
+    ```
 
 - **Organize by domain**: Group related data.
 
-  ```json
-  {"user": {...}, "cart": {...}, "ui": {...}}
-  ```
+    ```json
+    {"user": {...}, "cart": {...}, "ui": {...}}
+    ```
 
 - **Pre-compute display values**: Formats data (currency, dates) on the agent before sending.
-  ```json
-  {"price": "$19.99"} // Not: {"price": 19.99}
-  ```
+
+    ```json
+    {"price": "$19.99"} // Not: {"price": 19.99}
+    ```

docs/concepts/data-flow.md

@@ -53,7 +53,7 @@ A2UI defines a sequence of JSON messages that describe the UI. When streamed, th
       "version": "v0.9",
       "createSurface": {
         "surfaceId": "main",
-        "catalogId": "https://a2ui.org/specification/v0_9/basic_catalog.json"
+        "catalogId": "https://a2ui.org/specification/v0_9/catalogs/basic/catalog.json"
       }
     }
     {
@@ -197,7 +197,7 @@ A sequence of self-contained JSON objects is streaming-friendly, easy for LLMs t
       "version": "v0.9",
       "createSurface": {
         "surfaceId": "booking",
-        "catalogId": "https://a2ui.org/specification/v0_9/basic_catalog.json"
+        "catalogId": "https://a2ui.org/specification/v0_9/catalogs/basic/catalog.json"
       }
     }
     ```

docs/ecosystem/a2ui-in-the-world.md

@@ -166,19 +166,19 @@ The A2UI community is building exciting projects:
 ### Open Source Examples
 
 - **Restaurant Finder** ([samples/agent/adk/restaurant_finder](https://github.com/google/A2UI/tree/main/samples/agent/adk/restaurant_finder))
-  - Table reservation with dynamic forms
-  - Gemini-powered agent
-  - Full source code available
+    - Table reservation with dynamic forms
+    - Gemini-powered agent
+    - Full source code available
 
 - **Contact Lookup** ([samples/agent/adk/contact_lookup](https://github.com/google/A2UI/tree/main/samples/agent/adk/contact_lookup))
-  - Search interface with results list
-  - A2A agent example
-  - Demonstrates data binding
+    - Search interface with results list
+    - A2A agent example
+    - Demonstrates data binding
 
 - **Component Gallery** ([samples/client/angular - gallery mode](https://github.com/google/A2UI/tree/main/samples/client/angular))
-  - Interactive showcase of all components
-  - Live examples with code
-  - Great for learning
+    - Interactive showcase of all components
+    - Live examples with code
+    - Great for learning
 
 ### Third-Party Integrations