linting fixes

Author: maeste

docs/specification.md

@@ -983,7 +983,7 @@ Retrieves the current push notification configuration for a specified task. Requ
 
 </div>
 
-**Response `error` type (on failure)**: [`JSONRPCError`](#612-jsonrpcerror-object) (e.g., [`PushNotificationNotSupportedError`](#82-a2a-specific-errors), [`TaskNotFoundError`](#82-a2a-specific-errors)).
+**Response `error` type (on failure)**: [`JSONRPCError`](#612-jsonrpcerror-object) (e.g., [`PushNotificationNotSupportedError`](#822-a2a-specific-json-rpc-errors), [`TaskNotFoundError`](#822-a2a-specific-json-rpc-errors)).
 
 #### 7.6.1. `GetTaskPushNotificationConfigParams` Object (`tasks/pushNotificationConfig/get`)
 
@@ -1039,7 +1039,7 @@ Deletes an associated push notification configuration for a task. Requires the s
 
 - **Request `params` type**: [`DeleteTaskPushNotificationConfigParams`](#781-deletetaskpushnotificationconfigparams-object-taskspushnotificationconfigdelete)
 - **Response `result` type (on success)**: [`null`]
-- **Response `error` type (on failure)**: [`JSONRPCError`](#612-jsonrpcerror-object) (e.g., [`PushNotificationNotSupportedError`](#82-a2a-specific-errors), [`TaskNotFoundError`](#82-a2a-specific-errors)).
+- **Response `error` type (on failure)**: [`JSONRPCError`](#612-jsonrpcerror-object) (e.g., [`PushNotificationNotSupportedError`](#822-a2a-specific-json-rpc-errors), [`TaskNotFoundError`](#822-a2a-specific-json-rpc-errors)).
 
 #### 7.8.1. `DeleteTaskPushNotificationConfigParams` Object (`tasks/pushNotificationConfig/delete`)
 
@@ -1235,6 +1235,7 @@ google.rpc.Status {
 ```
 
 Error details **SHOULD** include:
+
 - `google.rpc.ErrorInfo` with A2A-specific reason codes
 - `google.rpc.RequestInfo` with request identification
 - `google.rpc.ResourceInfo` for resource-related errors (e.g., task not found)
@@ -1284,27 +1285,33 @@ HTTP+JSON/REST implementations **MUST** return error responses with `Content-Typ
   "error": {
     "code": "A2A_ERROR_CODE",
     "message": "Human-readable error description",
-    "details": {
-      "type": "ERROR_TYPE",
-      "reason": "SPECIFIC_REASON_CODE",
-      "domain": "a2a.protocol",
-      "metadata": {
-        "key": "value"
+    "details": [
+      {
+        "@type": "type.googleapis.com/google.rpc.ErrorInfo",
+        "reason": "SPECIFIC_REASON_CODE",
+        "domain": "a2a.protocol",
+        "metadata": {
+          "key": "value"
+        }
+      },
+      {
+        "@type": "type.googleapis.com/google.rpc.RequestInfo",
+        "requestId": "client-request-id"
       }
-    }
+    ]
   },
-  "request_id": "client-request-id",
   "timestamp": "2024-03-15T10:30:00Z"
 }
 ```
 
 **Required fields:**
+
 - `error.code`: A2A-specific error identifier (e.g., "TASK_NOT_FOUND")
 - `error.message`: Human-readable error description
 
 **Optional fields:**
-- `error.details`: Additional structured error information
-- `request_id`: Client-provided request identifier for tracing
+
+- `error.details`: An array of objects containing additional structured error information.
 - `timestamp`: ISO 8601 timestamp when the error occurred
 
 #### 8.4.4. HTTP Error Headers
@@ -2156,7 +2163,7 @@ For a client to be considered **A2A-compliant**, it **MUST**:
 #### 11.2.2. Protocol Implementation
 
 - **Core method usage**: **MUST** properly construct requests for at least `message/send` and `tasks/get` methods.
-- **Error handling**: **MUST** properly handle all A2A error codes defined in [Section 8.2](#82-a2a-specific-errors).
+- **Error handling**: **MUST** properly handle all A2A error codes defined in [Section 8.2](#822-a2a-specific-json-rpc-errors).
 - **Authentication**: **MUST** support at least one authentication method when interacting with agents that require authentication.
 
 #### 11.2.3. Optional Client Features