docs(nav[prompts,resources]): lift to top level as peer MCP capabilities

Prompts and Resources are peer MCP concepts alongside Tools, not
subtypes — so tools/prompts.md and reference/api/resources.md both
read wrong by path. Move them to docs/prompts.md and docs/resources.md,
sitting beside tools/index in the "Use it" nav section. rediraffe
covers the old URLs.

Author: tony

docs/index.md

@@ -93,7 +93,8 @@ clients
 :caption: Use it
 
 tools/index
-tools/prompts
+prompts
+resources
 recipes
 configuration
 ```

docs/tools/prompts.md docs/prompts.mddocs/tools/prompts.md renamed to docs/prompts.md

@@ -6,7 +6,10 @@
 "api/tools" "reference/api/tools"
 "api/models" "reference/api/models"
 "api/middleware" "reference/api/middleware"
-"api/resources" "reference/api/resources"
+"api/resources" "resources"
+"reference/api/resources" "resources"
+"tools/prompts" "prompts"
+"tools/resources" "resources"
 "api/utils" "reference/api/utils"
 "architecture" "topics/architecture"
 "concepts" "topics/concepts"

docs/redirects.txt

@@ -29,12 +29,6 @@ Pydantic models for requests and responses.
 Safety-tier enforcement and request hooks.
 :::
 
-:::{grid-item-card} Resources
-:link: resources
-:link-type: doc
-MCP resource providers.
-:::
-
 :::{grid-item-card} Utils
 :link: utils
 :link-type: doc
@@ -50,6 +44,5 @@ server
 tools
 models
 middleware
-resources
 utils
 ```

docs/reference/api/index.md

@@ -58,7 +58,7 @@ All tools accept an optional `socket_name` parameter for multi-server support. I
 
 **Reaching for a workflow recipe?** The server also ships four
 short MCP prompts the client renders for the model — see
-{doc}`/tools/prompts`. They cover the most common patterns
+{doc}`/prompts`. They cover the most common patterns
 (run-and-wait, diagnose-failing-pane, build-dev-workspace,
 interrupt-gracefully) with embedded UUID-scoped wait channels and
 shell-agnostic guidance.

docs/reference/api/resources.md docs/resources.mddocs/reference/api/resources.md renamed to docs/resources.md

@@ -18,13 +18,13 @@ session picker popup when filling ``session_name=`` on
 
 ## What libtmux-mcp currently exposes
 
-- **Prompt arguments** — the four recipes ({doc}`/tools/prompts`)
+- **Prompt arguments** — the four recipes ({doc}`/prompts`)
   advertise their argument names and types. FastMCP derives a default
   completion shape from the Python signatures:
   ``str`` arguments accept free text, ``float`` arguments accept
   numeric strings, no enum / list suggestions.
 - **Resource template parameters** —
-  {doc}`/reference/api/resources` URIs carry ``{session_name}``,
+  {doc}`/resources` URIs carry ``{session_name}``,
   ``{window_index}``, ``{pane_id}``, and ``{?socket_name}``
   placeholders. Completion suggestions are again derived from the
   function signatures' types, not from live tmux state.
@@ -47,5 +47,5 @@ into the prompt's arguments.
 ## Further reading
 
 - [MCP completion spec](https://modelcontextprotocol.io/specification/2025-11-25/server/utilities/completion)
-- {doc}`/tools/prompts` — the prompt argument surface
-- {doc}`/reference/api/resources` — the resource-template parameter surface
+- {doc}`/prompts` — the prompt argument surface
+- {doc}`/resources` — the resource-template parameter surface