chore: update tools list and enhance interactive terminal documentation

Signed-off-by: hortison <160366376+hortison@users.noreply.github.com>

Author: hortison

.github/agents/documentation.agent.md

@@ -1,7 +1,6 @@
 ---
 name: "Diátaxis Documentation Expert"
-agent: 'agent'
-tools: ['edit/editFiles', 'search', 'fetch']
+tools: ['search/changes', 'search/codebase', 'edit/editFiles', 'vscode/extensions', 'web/fetch', 'web/githubRepo', 'vscode/getProjectSetupInfo', 'vscode/installExtension', 'vscode/newWorkspace', 'vscode/runCommand', 'vscode/openSimpleBrowser', 'read/problems', 'execute/getTerminalOutput', 'execute/runInTerminal', 'read/terminalLastCommand', 'read/terminalSelection', 'execute/createAndRunTask', 'execute', 'execute/runTask', 'execute/runTests', 'search', 'search/searchResults', 'read/terminalLastCommand', 'read/terminalSelection', 'execute/testFailure', 'search/usages', 'vscode/vscodeAPI', 'github/*']
 description: 'Diátaxis Documentation Expert. An expert technical writer specializing in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework.'
 ---
 

content/en/kanvas/operator/_index.md

@@ -25,15 +25,4 @@ Using the search bar, you can search for specific resources and select them. The
 Operator supports connecting to Kubernetes pods via the following methods.
 
 - [Log Streaming](/kanvas/operator/log-streaming): Learn how to live-tail logs from your Kubernetes pods and containers directly within the visual topology.
-
-### Understanding Interactive Terminal
-
-The interactive terminal behaves in a fashion similar to similar to the behavior of the `kubectl exec` command, but web-based.
-
-{{< alert type="note" title="Distinct Capabilities" >}} Note that each component offers its own capabilities, and that these capabilities differ between Designer mode and Operator mode. For example, in operator mode, if you right-click (and hold) on a Kubernetes pod, you will see actions unique to the Pod component, which are to open either an interactive terminal to one or all of the containers in the pod or to start streaming logs from any/all of the containers in the pod. {{< /alert >}}
-
-While using using the interactive terminal, understand that you can only open one session per container. Each session's data is streamed via Meshery Broker (NATS) from MeshSync to Meshery Server / Kanvas. The GraphQL subscription between your web browser running Kanvas and Meshery Server provides isolation between other users who might be concurrently sharing an interactive terminal. Each connection established a unique session ID.
-
-<!-- {{< figure src="images/interactive-terminal-sequence-diagram.svg" link="images/interactive-terminal-sequence-diagram.svg"  width="100%" alt="interactive-terminal-sequence-diagram" >}} -->
-
-![interactive-terminal-sequence-diagram](images/interactive-terminal-sequence-diagram.svg)
+- [Interactive Terminal](/kanvas/operator/interactive-terminal): Learn how to establish an interactive shell session with your containers.

content/en/kanvas/operator/interactive-terminal.md

@@ -9,7 +9,7 @@ When operating cloud native infrastructure, deep diagnostics often require direc
 
 ## Overview
 
-The Kanvas Interactive Terminal allows operators to establish a secure, low-latency shell session with one or more pods simultaneously. This feature is essential for "last mile" debugging where metrics and logs alone are insufficient.
+The Kanvas Interactive Terminal allows operators to establish a secure, low-latency shell session with one or more pods simultaneously. This feature is essential for "last mile" debugging where metrics and logs alone are insufficient. The interactive terminal behaves in a fashion similar to the behavior of the `kubectl exec` command, but web-based.
 
 ### Key Features
 
@@ -20,7 +20,7 @@ The Kanvas Interactive Terminal allows operators to establish a secure, low-late
 
 ## How to Access the Terminal
 
-To use the Interactive Terminal, ensure you are in **Operator Mode** (Visualizer) and have a connected Kubernetes cluster.
+To use the Interactive Terminal, ensure you are in **Operator Mode** and have a connected Kubernetes cluster.
 
 1. **Navigate to Visualizer:** Open Kanvas and switch to **Operator** mode to view your active cluster resources.
 2. **Select a Workload:** Click on a **Pod** or **Deployment** node within your design.
@@ -65,6 +65,14 @@ The Interactive Terminal is built on an event-driven architecture designed for s
 3. **Data Transport:** Input and output data are streamed via **NATS** through the Meshery Broker. Shell output is preprocessed and transcribed before being delivered to the UI.
 4. **Session Isolation:** Each terminal session is mapped to a unique topic ID within the subscription, ensuring that data streams for multiple open terminals do not overlap.
 
+{{< alert type="note" title="Distinct Capabilities" >}} Note that each component offers its own capabilities, and that these capabilities differ between Designer mode and Operator mode. For example, in operator mode, if you right-click (and hold) on a Kubernetes pod, you will see actions unique to the Pod component, which are to open either an interactive terminal to one or all of the containers in the pod or to start streaming logs from any/all of the containers in the pod. {{< /alert >}}
+
+While using the interactive terminal, understand that you can only open one session per container. Each session's data is streamed via Meshery Broker (NATS) from MeshSync to Meshery Server / Kanvas. The GraphQL subscription between your web browser running Kanvas and Meshery Server provides isolation between other users who might be concurrently sharing an interactive terminal. Each connection establishes a unique session ID.
+
+<!-- {{< figure src="images/interactive-terminal-sequence-diagram.svg" link="images/interactive-terminal-sequence-diagram.svg"  width="100%" alt="interactive-terminal-sequence-diagram" >}} -->
+
+![interactive-terminal-sequence-diagram](images/interactive-terminal-sequence-diagram.svg)
+
 ***
 
 ### See Also