Run Prettier

danilo-leal · danilo-leal · commit 1629123fb91e · 2025-08-24T12:30:14.000-03:00
diff --git a/docs/README.md b/docs/README.md
@@ -10,14 +10,19 @@ Run the following command to have the documentation live locally:
 ```bash
 npm run docs
 ```
+
 ## Preview changes locally
+
 To preview the changes locally, run the following command:
+
 ```bash
 mint dev
 ```
 
 ### Install the CLI
+
 Before running the site locally you need to install Mint's CLI:
+
 ```bash
 npm i -g mint
 ```
diff --git a/docs/community/contributing.mdx b/docs/community/contributing.mdx
@@ -3,8 +3,8 @@ title: "Contributing"
 description: "How to participate in the development of ACP"
 ---
 
-We welcome contributions from the community! 
+We welcome contributions from the community!
 
 All contributors must adhere to [Zed's Code of Conduct](https://zed.dev/code-of-conduct).
 
-For questions and discussions, please use GitHub Discussions.
+For questions and discussions, please use GitHub Discussions.
diff --git a/docs/libraries/rust.mdx b/docs/libraries/rust.mdx
@@ -1,4 +1,4 @@
 ---
 title: "Rust"
 description: "Rust library for the Agent Client Protocol"
----
+---
diff --git a/docs/protocol/agent-plan.mdx b/docs/protocol/agent-plan.mdx
@@ -3,4 +3,4 @@ title: "Agent Plan"
 description: "How Agents communicate their execution plans"
 ---
 
-*Documentation coming soon*
+_Documentation coming soon_
diff --git a/docs/protocol/content.mdx b/docs/protocol/content.mdx
@@ -3,4 +3,4 @@ title: "Content"
 description: "Content blocks and data types in the Agent Client Protocol"
 ---
 
-*Documentation coming soon*
+_Documentation coming soon_
diff --git a/docs/protocol/error.mdx b/docs/protocol/error.mdx
@@ -3,4 +3,4 @@ title: "Error"
 description: "Error handling in the Agent Client Protocol"
 ---
 
-*Documentation coming soon*
+_Documentation coming soon_
diff --git a/docs/protocol/initialization.mdx b/docs/protocol/initialization.mdx
@@ -5,15 +5,13 @@ description: "How all Agent Client Protocol connections begin"
 
 {/* todo! link to all concepts */}
 
-
 The Initialization phase allows [Clients](./overview#client) and [Agents](./overview#agent) to negotiate protocol versions, capabilities, and authentication methods.
 
 Before a Session can be created, Clients **MUST** initialize the connection by calling the `initialize` method with:
 
 - The latest [protocol version](#protocol-version) supported
 - The [capabilities](#client-capabilities) supported
 
-
 ```json
 {
   "jsonrpc": "2.0",
@@ -33,7 +31,6 @@ Before a Session can be created, Clients **MUST** initialize the connection by c
 
 The Agent **MUST** respond with the chosen [protocol version](#protocol-version) and the [capabilities](#agent-capabilities) it supports:
 
-
 ```json
 {
   "jsonrpc": "2.0",
@@ -69,7 +66,6 @@ If the Agent supports the requested version, it **MUST** respond with the same v
 
 If the Client does not support the version specified by the Agent in the `initialize` response, the Client **SHOULD** close the connection and inform the user about it.
 
-
 ## Capabilities
 
 Capabilities describe features supported by the Client and the Agent.
@@ -82,7 +78,6 @@ Capabilities are high-level and are not attached to a specific base protocol con
 
 Capabilities may specify the availability of protocol methods, notifications, or a subset of their parameters. They may also signal behaviors of the Agent or Client implementation.
 
-
 ### Client Capabilities
 
 The Client **SHOULD** specify whether it supports the following capability:
diff --git a/docs/protocol/prompt-turn.mdx b/docs/protocol/prompt-turn.mdx
@@ -238,9 +238,10 @@ After all ongoing operations have been successfully aborted and pending updates
 <Warning>
   API client libraries and tools often throw an exception when their operation is aborted, which may propagate as an error response to `session/prompt`.
 
-  Clients often display unrecognized errors from the Agent to the user, which would be undesirable for cancellations as they aren't considered errors.
+Clients often display unrecognized errors from the Agent to the user, which would be undesirable for cancellations as they aren't considered errors.
+
+Agents **MUST** catch these errors and return the semantically meaningful `cancelled` stop reason, so that Clients can reliably confirm the cancellation.
 
-  Agents **MUST** catch these errors and return the semantically meaningful `cancelled` stop reason, so that Clients can reliably confirm the cancellation.
 </Warning>
 
 The Agent **MAY** send `session/update` notifications with content or tool call updates after receiving the `session/cancel` notification, but it **MUST** ensure that it does so before responding to the `session/prompt` request.
diff --git a/docs/protocol/session-setup.mdx b/docs/protocol/session-setup.mdx
@@ -60,8 +60,8 @@ Before attempting to load a session, Clients **MUST** verify that the Agent supp
   "result": {
     "protocolVersion": 1,
     "agentCapabilities": {
-      "loadSession": true,
-    },
+      "loadSession": true
+    }
   }
 }
 ```
@@ -152,6 +152,7 @@ The Client can then continue sending prompts as if the session was never interru
 The session ID returned by `session/new` is a unique identifier for the conversation context.
 
 Clients use this ID to:
+
 - Send prompt requests via `session/prompt`
 - Cancel ongoing operations via `session/cancel`
 - Load previous sessions via `session/load` (if the Agent supports the `loadSession` capability)
diff --git a/docs/protocol/tool-calls.mdx b/docs/protocol/tool-calls.mdx
@@ -11,12 +11,12 @@ Tool Calls are the mechanism through which Agents interact with external tools a
 
 ## Structure
 
-*Documentation coming soon*
+_Documentation coming soon_
 
 ## Lifecycle
 
-*Documentation coming soon*
+_Documentation coming soon_
 
 ## Updates
 
-*Documentation coming soon*
+_Documentation coming soon_

-Original file line number
+Diff line change
@@ @@ -1,4 +1,4 @@ @@
 ---
 title: "Rust"
 description: "Rust library for the Agent Client Protocol"
 ----
 +---