fix: Broken links in examples and extras (#1018)

Author: kabir

docs/content/1_0_0_Final/examples.md

@@ -142,7 +142,7 @@ mvn exec:java -Dopentelemetry=true
 
 The client expects an OpenTelemetry collector on port 5317. The easiest way is to run the Java server with `-Popentelemetry` (which starts the collector automatically), then run the client with `-Dopentelemetry=true` for end-to-end traces.
 
-For more information, see the [OpenTelemetry extras module](extra/opentelemetry).
+For more information, see the [OpenTelemetry extras module](../extra/opentelemetry).
 
 ## More Examples
 

docs/content/1_0_0_Final/extras.md

@@ -28,18 +28,18 @@ Import the extras BOM to manage versions:
 </dependencyManagement>
 ```
 
-## [HTTP Clients](extra/http-clients)
+## [HTTP Clients](../extra/http-clients)
 
 Alternative `A2AHttpClient` implementations. The **Vert.x HTTP Client** (`a2a-java-sdk-http-client-vertx`) replaces the default JDK HttpClient with a reactive, non-blocking Vert.x WebClient — recommended for Quarkus, reactive frameworks, and high-throughput scenarios. An **Android HTTP Client** (`a2a-java-sdk-http-client-android`) is also available for mobile applications.
 
-## [Storage & Persistence](extra/storage)
+## [Storage & Persistence](../extra/storage)
 
 JPA-backed replacements for the in-memory stores, providing database persistence for production and load-balanced deployments. Includes a **JPA Task Store** (`a2a-java-extras-task-store-database-jpa`) and a **JPA Push Notification Config Store** (`a2a-java-extras-push-notification-config-store-database-jpa`). Both use Jakarta Persistence API (JPA 3.0+) and share the same datasource configuration.
 
-## [Replicated Queue Manager](extra/replicated-queue-manager)
+## [Replicated Queue Manager](../extra/replicated-queue-manager)
 
 Replaces the default `InMemoryQueueManager` with event replication across multiple A2A server instances via message brokers. Required for multi-instance deployments. The core module (`a2a-java-queue-manager-replicated-core`) pairs with a MicroProfile Reactive Messaging strategy (`a2a-java-queue-manager-replication-mp-reactive`) supporting Apache Kafka, Pulsar, or AMQP. You can also write your own `ReplicationStrategy`.
 
-## [OpenTelemetry](extra/opentelemetry)
+## [OpenTelemetry](../extra/opentelemetry)
 
 Distributed tracing, metrics, and context propagation for A2A servers and clients using OpenTelemetry. The server module (`a2a-java-sdk-opentelemetry-server`) adds automatic span creation for all protocol methods with context propagation across async boundaries. Client modules (`a2a-java-sdk-opentelemetry-client`, `a2a-java-sdk-opentelemetry-client-propagation`) instrument A2A client operations.

docs/content/1_1_0_Final/examples.md

@@ -142,7 +142,7 @@ mvn exec:java -Dopentelemetry=true
 
 The client expects an OpenTelemetry collector on port 5317. The easiest way is to run the Java server with `-Popentelemetry` (which starts the collector automatically), then run the client with `-Dopentelemetry=true` for end-to-end traces.
 
-For more information, see the [OpenTelemetry extras module](extra/opentelemetry).
+For more information, see the [OpenTelemetry extras module](../extra/opentelemetry).
 
 ## More Examples
 

docs/content/1_1_0_Final/extras.md

@@ -28,18 +28,18 @@ Import the extras BOM to manage versions:
 </dependencyManagement>
 ```
 
-## [HTTP Clients](extra/http-clients)
+## [HTTP Clients](../extra/http-clients)
 
 Alternative `A2AHttpClient` implementations. The **Vert.x HTTP Client** (`a2a-java-sdk-http-client-vertx`) replaces the default JDK HttpClient with a reactive, non-blocking Vert.x WebClient — recommended for Quarkus, reactive frameworks, and high-throughput scenarios. An **Android HTTP Client** (`a2a-java-sdk-http-client-android`) is also available for mobile applications.
 
-## [Storage & Persistence](extra/storage)
+## [Storage & Persistence](../extra/storage)
 
 JPA-backed replacements for the in-memory stores, providing database persistence for production and load-balanced deployments. Includes a **JPA Task Store** (`a2a-java-extras-task-store-database-jpa`) and a **JPA Push Notification Config Store** (`a2a-java-extras-push-notification-config-store-database-jpa`). Both use Jakarta Persistence API (JPA 3.0+) and share the same datasource configuration.
 
-## [Replicated Queue Manager](extra/replicated-queue-manager)
+## [Replicated Queue Manager](../extra/replicated-queue-manager)
 
 Replaces the default `InMemoryQueueManager` with event replication across multiple A2A server instances via message brokers. Required for multi-instance deployments. The core module (`a2a-java-queue-manager-replicated-core`) pairs with a MicroProfile Reactive Messaging strategy (`a2a-java-queue-manager-replication-mp-reactive`) supporting Apache Kafka, Pulsar, or AMQP. You can also write your own `ReplicationStrategy`.
 
-## [OpenTelemetry](extra/opentelemetry)
+## [OpenTelemetry](../extra/opentelemetry)
 
 Distributed tracing, metrics, and context propagation for A2A servers and clients using OpenTelemetry. The server module (`a2a-java-sdk-opentelemetry-server`) adds automatic span creation for all protocol methods with context propagation across async boundaries. Client modules (`a2a-java-sdk-opentelemetry-client`, `a2a-java-sdk-opentelemetry-client-propagation`) instrument A2A client operations.

docs/content/dev/examples.md

@@ -142,7 +142,7 @@ mvn exec:java -Dopentelemetry=true
 
 The client expects an OpenTelemetry collector on port 5317. The easiest way is to run the Java server with `-Popentelemetry` (which starts the collector automatically), then run the client with `-Dopentelemetry=true` for end-to-end traces.
 
-For more information, see the [OpenTelemetry extras module](extra/opentelemetry).
+For more information, see the [OpenTelemetry extras module](../extra/opentelemetry).
 
 ## Stream Lifecycle Hook
 

docs/content/dev/extras.md

@@ -28,18 +28,18 @@ Import the extras BOM to manage versions:
 </dependencyManagement>
 ```
 
-## [HTTP Clients](extra/http-clients)
+## [HTTP Clients](../extra/http-clients)
 
 Alternative `A2AHttpClient` implementations. The **Vert.x HTTP Client** (`a2a-java-sdk-http-client-vertx`) replaces the default JDK HttpClient with a reactive, non-blocking Vert.x WebClient — recommended for Quarkus, reactive frameworks, and high-throughput scenarios. An **Android HTTP Client** (`a2a-java-sdk-http-client-android`) is also available for mobile applications.
 
-## [Storage & Persistence](extra/storage)
+## [Storage & Persistence](../extra/storage)
 
 JPA-backed replacements for the in-memory stores, providing database persistence for production and load-balanced deployments. Includes a **JPA Task Store** (`a2a-java-extras-task-store-database-jpa`) and a **JPA Push Notification Config Store** (`a2a-java-extras-push-notification-config-store-database-jpa`). Both use Jakarta Persistence API (JPA 3.0+) and share the same datasource configuration.
 
-## [Replicated Queue Manager](extra/replicated-queue-manager)
+## [Replicated Queue Manager](../extra/replicated-queue-manager)
 
 Replaces the default `InMemoryQueueManager` with event replication across multiple A2A server instances via message brokers. Required for multi-instance deployments. The core module (`a2a-java-queue-manager-replicated-core`) pairs with a MicroProfile Reactive Messaging strategy (`a2a-java-queue-manager-replication-mp-reactive`) supporting Apache Kafka, Pulsar, or AMQP. You can also write your own `ReplicationStrategy`.
 
-## [OpenTelemetry](extra/opentelemetry)
+## [OpenTelemetry](../extra/opentelemetry)
 
 Distributed tracing, metrics, and context propagation for A2A servers and clients using OpenTelemetry. The server module (`a2a-java-sdk-opentelemetry-server`) adds automatic span creation for all protocol methods with context propagation across async boundaries. Client modules (`a2a-java-sdk-opentelemetry-client`, `a2a-java-sdk-opentelemetry-client-propagation`) instrument A2A client operations.