fix(docs): correct quickstart errors and API examples across integrations

- Agent-spec: remove invalid CLI `-f agent-spec` option, link to manual setup
- A2A: fix env var (GEMINI_API_KEY) and port (10002) to match starter template
- AWS Strands: fix useRenderTool to use Zod schema and correct render props
- LangGraph: add auth guide cross-reference in configurable docs

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: tylerslaton

docs/content/docs/integrations/a2a/quickstart.mdx

@@ -60,7 +60,7 @@ Before you begin, you'll need the following:
         Create a `.env` file in your agent directory and add your Google API key:
 
         ```plaintext title="agent/.env"
-        GOOGLE_API_KEY=your_google_api_key
+        GEMINI_API_KEY=your_gemini_api_key
         ```
 
         <Callout type="info" title="What about other models?">
@@ -107,7 +107,7 @@ Before you begin, you'll need the following:
         <Accordions className="mb-4">
             <Accordion title="Troubleshooting">
                 - If you're having connection issues, try using `0.0.0.0` or `127.0.0.1` instead of `localhost`
-                - Make sure your agent is running on port 8000
+                - Make sure your agent is running on port 10002
                 - Check that your Google API key is correctly set
             </Accordion>
         </Accordions>

docs/content/docs/integrations/aws-strands/generative-ui/tool-rendering.mdx

@@ -105,35 +105,34 @@ Now we'll use the `useRenderTool` hook to render the tool call in the UI with a
 
 import { useRenderTool } from "@copilotkit/react-core/v2"; // [!code highlight]
 import { CopilotSidebar } from "@copilotkit/react-core/v2";
+import { z } from "zod"; // [!code highlight]
 
 export default function Page() {
   // [!code highlight:41]
+  const weatherParams = z.object({
+    location: z.string().describe("The location to get weather for"),
+  });
+
   useRenderTool({
     name: "get_weather",
-    parameters: [
-      {
-        name: "location",
-        description: "The location to get weather for",
-        required: true,
-      },
-    ],
-    render: ({ status, args, result }) => {
+    parameters: weatherParams,
+    render: ({ status, parameters, result }) => {
       if (status === "executing") {
         return (
           <div className="p-4 bg-blue-50 rounded-lg">
             <p className="text-sm text-blue-600">
-              Getting weather for {args.location}...
+              Getting weather for {parameters.location}...
             </p>
           </div>
         );
       }
 
       if (status === "complete" && result) {
-        const weather = result;
+        const weather = JSON.parse(result);
         return (
           <div className="p-4 bg-white border rounded-lg shadow-sm">
             <h3 className="font-semibold text-lg mb-2">
-              Weather in {args.location}
+              Weather in {parameters.location}
             </h3>
             <div className="space-y-1 text-sm">
               <p>🌡️ Temperature: {weather.temperature}°F</p>
@@ -178,26 +177,24 @@ You should see the custom UI component render with the weather information beaut
 You can access the tool arguments even while the tool is still executing:
 
 ```tsx
+const weatherParams = z.object({
+  location: z.string().describe("The location to get weather for"),
+});
+
 useRenderTool({
   name: "get_weather",
-  parameters: [
-    {
-      name: "location",
-      description: "The location to get weather for",
-      required: true,
-    },
-  ],
-  render: ({ status, args, result }) => {
-    // args is available immediately, even when status is "executing"
-    const location = args.location;
+  parameters: weatherParams,
+  render: ({ status, parameters, result }) => {
+    // parameters is available immediately, even when status is "executing"
+    const location = parameters.location;
 
     return (
       <div className="p-4 bg-blue-50 rounded-lg">
         {status === "executing" && (
           <p>Fetching weather for {location}...</p>
         )}
         {status === "complete" && result && (
-          <p>Weather in {location}: {result.temperature}°F</p>
+          <p>Weather in {location}: {JSON.parse(result).temperature}°F</p>
         )}
       </div>
     );

docs/content/docs/integrations/langgraph/configurable.mdx

@@ -14,6 +14,10 @@ If you wish to read further, you can refer to [the configuration guide by LangGr
 
 This is useful when you want to send execution-time configuration information (such as different tokens or metadata for a given session) that should not be part of the agent state.
 
+<Callout type="info" title="Looking for authentication?">
+  If you need to pass authentication tokens specifically, see the dedicated [Authentication guide](/langgraph/auth) which covers LangGraph Platform and self-hosted authentication patterns in detail.
+</Callout>
+
 ## Implementation
 
 By default, LangGraph agents are invoked with a `config` argument. This config has a `configurable` property which can be accessed and filled with your data.

docs/snippets/integrations/agent-spec/run-and-connect.mdx

@@ -2,17 +2,4 @@ import { Accordions, Accordion } from "fumadocs-ui/components/accordion";
 
 You'll need to run your agent and connect it to CopilotKit before proceeding.
 
-If you don't already have CopilotKit and your agent connected, choose one of the following options:
-
-<Accordions>
-  <Accordion title="I already have an agent">
-    You can follow the instructions in the [quickstart](/agent-spec/quickstart) guide.
-  </Accordion>
-  <Accordion title="I want to start from scratch">
-    Run the following command to create a brand new project with a pre-configured agent:
-
-    ```bash
-    npx copilotkit@latest create -f agent-spec
-    ```
-  </Accordion>
-</Accordions>
+If you don't already have CopilotKit and your agent connected, follow the [quickstart](/agent-spec/quickstart) guide to set up your project manually.