Revert accidental changes to catalogs.md

Author: wrenj

docs/catalogs.md

@@ -59,15 +59,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/standard_catalog.json).
+To help developers get started quickly, the A2UI team maintains the [Basic Catalog](../specification/v0_9/json/basic_catalog.json).
 
 This is a pre-defined catalog file that contains a standard 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/standard_catalog.json)
+[See the A2UI v0.9 basic catalog](../specification/v0_9/json/basic_catalog.json)
 
 ### Defining Your Own Catalog
 
@@ -172,7 +172,7 @@ This catalog imports all elements from the Basic Catalog and adds a new `Suggest
   "$id": "https://github.com/.../hello_world_with_all_basic/v1/catalog.json",
   "components": {
     "allOf": [
-      { "$ref": "standard_catalog_definition.json#/components" },
+      { "$ref": "basic_catalog_definition.json#/components" },
       {
         "SuggestionChips": {
           "type": "object",
@@ -195,22 +195,24 @@ This catalog imports all elements from the Basic Catalog and adds a new `Suggest
 
 #### Example: Cherry-picking Components
 
-This catalog imports only `Text` from the Basic Catalog to build a simple Popup surface.
+This catalog imports only `Text` and `Icon` from the Basic Catalog to build a simple Popup surface.
 
 ```json
 {
   "$id": "https://github.com/.../hello_world_with_some_basic/v1/catalog.json",
   "components": {
     "allOf": [
-      { "$ref": "standard_catalog_definition.json#/components/Text" },
+      { "$ref": "basic_catalog_definition.json#/components/Text" },
+      { "$ref": "basic_catalog_definition.json#/components/Icon" },
       {
         "Popup": { 
           "type": "object",
           "description": "A modal overlay that displays an icon and text.",
           "properties": {
-            "text": { "$ref": "common_types.json#/$defs/ComponentId" }
+            "text": { "$ref": "common_types.json#/$defs/ComponentId" },
+            "icon": { "$ref": "common_types.json#/$defs/ComponentId" }
           },
-          "required": [ "text" ]
+          "required": [ "text", "icon" ]
         }
       }
     ]
@@ -224,7 +226,7 @@ This catalog imports only `Text` from the Basic Catalog to build a simple Popup
 
 Client renderers implement the catalog by mapping the schema definition to actual code.
 
-[Example typescript renderer for the hello world catalog]
+[Example Rizzcharts typescript renderer for the hello world catalog](../samples/client/angular/projects/rizzcharts/src/a2ui-catalog/catalog.ts).
 
 ```typescript
 import { Catalog, DEFAULT_CATALOG } from '@a2ui/angular'; 
@@ -235,35 +237,13 @@ export const RIZZ_CHARTS_CATALOG = {
   HelloWorldBanner: {     
     type: () => import('./hello_world_banner').then((r) => r.HelloWorldBanner),     
     bindings: ({ properties }) => [       
-      inputBinding('message', () => ('message' in properties && properties['message']) || undefined)
+      inputBinding('message', () => ('message' in properties && properties['message']) || undefined),       
+      inputBinding('backgroundColor', () => ('backgroundColor' in properties && properties['backgroundColor']) || undefined),       
     ],   
   }, 
 } as Catalog;
 ```
 
-and the hello_world_banner implementation
-
-```json
-import { DynamicComponent } from '@a2ui/angular';
-import { Component, Input } from '@angular/core';
-
-@Component({
-  selector: 'hello-world-banner',
-  imports: [], 
-  template: `
-    <div>
-      <h2>Hello World Banner</h2>
-      <p>{{ message }}</p>
-    </div>
-  `,
-})
-export class HelloWorldBanner extends DynamicComponent {
-  @Input() message?: string;
-}
-```
-
-You can see a working example of a client renderer in the [Rizzcharts demo](../samples/client/angular/projects/rizzcharts/src/a2ui-catalog/catalog.ts).
-
 ## A2UI Catalog Negotiation
 
 Because clients and agents can support multiple catalogs, they must agree on which catalog to use through a catalog negotiation handshake.
@@ -285,7 +265,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/standard_catalog.json",
+            "https://a2ui.org/specification/v0_9/basic_catalog.json",
             "https://github.com/.../rizzcharts_catalog_definition.json"
           ]
         }
@@ -311,7 +291,7 @@ Example of A2A message containing the supportedCatalogIds in metadata
   "metadata": {
     "a2uiClientCapabilities": {
       "supportedCatalogIds": [
-        "https://a2ui.org/specification/v0_9/standard_catalog.json",
+        "https://a2ui.org/specification/v0_9/basic_catalog.json",
         "https://github.com/.../rizzcharts_catalog_definition.json"
       ]
     }
@@ -329,7 +309,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/standard_catalog.json"
+    "catalogId": "https://a2ui.org/specification/v0_9/basic_catalog.json"
   }
 }
 ```