docs: Revise doc guides for 0.6.x release

src/app/docs/kagent/concepts/agents/page.mdx

@@ -56,9 +56,13 @@ Here's how you could reference an existing agent (`promql-agent`) as a tool:
 ```yaml
 ...
     # Referencing existing tools
+    tools:
     - type: McpServer
       mcpServer:
-        toolServer: kagent-tool-server
+        name: kagent-tool-server
+        # Or a Kubernetes Service with "appProtocol: mcp", labels, and annotations for MCP
+        # Or an MCPServer
+        kind: RemoteMCPServer
         toolNames:
         - k8s_get_resources
         - k8s_get_available_api_resources

src/app/docs/kagent/concepts/architecture/page.mdx

@@ -4,6 +4,8 @@ pageOrder: 1
 description: "Explore the high-level architecture of kagent, including its core components like the Controller, App/Engine, CLI, and Dashboard."
 ---
 
+import { Tabs, Tab } from '@/components/mdx/tabs';
+
 export const metadata = {
   title: "kagent architecture",
   description: "Explore the high-level architecture of kagent, including its core components like the Controller, App/Engine, CLI, and Dashboard.",
@@ -47,6 +49,29 @@ The CLI offers a way to interact with the engine for those who prefer a CLI inte
 
 Kagent dashboard provides a web interface for managing and working with AI agents. Is it the simplest way to get started with kagent.
 
+<Tabs tabs={[
+  { id: 'kagent', label: 'kagent dashboard' },
+  { id: 'kubectl', label: 'kubectl port-forward' }
+]} />
+
+<div id="kagent-tab">
+  ```shell
+  kagent dashboard
+  ```
+</div>
+
+<div id="kubectl-tab">
+1. Enable port-forwarding on the `kagent` service.
+
+   ```shell
+   kubectl -n kagent port-forward svc/kagent 8001:80
+   ```
+
+2. Open your browser to [http://localhost:8001](http://localhost:8001).
+</div>
+
+![kagent dashboard](/images/kagent-landing.png "kagent landing page")
+
 ## Next Steps
 
 - Try [building your own agent](/docs/kagent/getting-started/first-agent)

src/app/docs/kagent/concepts/memory/page.mdx → src/app/docs/kagent/concepts/memory/page.txt

@@ -31,15 +31,15 @@ kubectl create secret generic pinecone-credentials -n kagent --from-literal PINE
 Once the API key is in place, you can use the Memory CRD to configure the memory for your agent. For example:
 
 ```yaml
-apiVersion: kagent.dev/v1alpha1
+apiVersion: kagent.dev/v1alpha2
 kind: Memory
 metadata:
   name: my-pinecone-memory
   namespace: kagent
 spec:
   provider: Pinecone
   # The secret containing the API key for the vector database
-  apiKeySecretRef: pinecone-credentials
+  apiKeySecret: pinecone-credentials
   # The key in the secret containing the API key
   apiKeySecretKey: PINECONE_API_KEY
   pinecone:
@@ -62,7 +62,7 @@ You can use Kubernetes CLI to create the memory.
 To attach memory to an agent, you can use the `memory` field in the agent spec. Note that the field is an array, so you can attach multiple memories to an agent:
 
 ```yaml
-apiVersion: kagent.dev/v1alpha1
+apiVersion: kagent.dev/v1alpha2
 kind: Agent
 metadata:
   name: memoryagent

src/app/docs/kagent/concepts/tools/page.mdx

@@ -35,16 +35,3 @@ MCP stands for [Model Context Protocol](https://modelcontextprotocol.io/introduc
 ## HTTP Tools
 
 HTTP tools are another way to bring external tools into kagent. Simply put, given a URL and a schema, kagent will send the user query to the URL and return the response. Kagent has the ability to discovery HTTP tools from services running in the cluster, assuming they are OpenAPI Compliant.
-
-## Tool Discovery
-
-Tool Discovery is one of the most powerful features of kagent. It allows you to discover tools from the cluster and make them available to your agents automatically. 
-
-Simply annotate a service with the following annotation:
-
-```yaml
-annotations:
-  kagent.dev/tool.type: "openapi" | "mcp"
-```
-
-Once annotated, kagent will automatically discover all tools from the service and make them available to your agents.