docs: update installation paths

Author: JakubWorek

README.md

@@ -20,18 +20,18 @@ over the protocol) and A2A **clients** (applications discovering and driving
 those agents) — one package, three wire transports (JSON-RPC,
 HTTP+JSON/REST, gRPC), and an opt-in compatibility layer for v0.3 peers.
 
-- 🚀 **v1.0 beta release** tracking [A2A Protocol Specification v1.0](https://a2a-protocol.org/v1.0.0/specification/).
+- 🚀 **v1.0 stable release** implementing [A2A Protocol Specification v1.0](https://a2a-protocol.org/v1.0.0/specification/).
 - 🔌 **Three transports** — JSON-RPC, HTTP+JSON/REST, and gRPC (Node-only),
   all backed by a single `DefaultRequestHandler`.
 - 🔄 **v0.3 backward compatibility** as an opt-in layer so v1.0 deployments
   can interoperate with peers still on v0.3 during a staged migration.
 
 ## Installation
 
-You can install the A2A SDK using `npm`. The v1.0 beta release is now available:
+You can install the A2A SDK using `npm`:
 
 ```bash
-npm install @a2a-js/sdk@next
+npm install @a2a-js/sdk
 ```
 
 ### For Server Usage

docs/migration-guide.md

@@ -14,7 +14,7 @@ model changes (renamed fields, restructured types, new operations), see:
 - Install the v1.0 SDK:
 
   ```bash
-  npm install @a2a-js/sdk@next
+  npm install @a2a-js/sdk
   ```
 
 > Migrating all v0.3 clients to v1.0 during upgrade is not required: the v1.0 SDK