docs: document saved plan reveal

Author: elkaix

docs/configuration/data-locations.md

@@ -84,6 +84,8 @@ Inside each session directory:
 - **`tasks/`**: background task persistence — `tasks/<task_id>.json` stores status/pid/exit code; `tasks/<task_id>/output.log` stores output.
 - **`cron/`**: scheduled task persistence; reloaded into the scheduler when the session is resumed with `pythinker --session`. See [Scheduled tasks](../reference/tools.md#scheduled-tasks).
 
+Saved plan files can be outside the workspace. In the web interface, select **Reveal in file manager** next to a saved plan to select it in the operating system file manager.
+
 ## Built-in tool cache
 
 The first time the `Grep` tool needs ripgrep, the CLI can automatically download `rg` and cache it at `bin/rg` (`bin/rg.exe` on Windows). File-reference completion in the terminal UI uses `fd`; the CLI downloads and caches it at `bin/fd` (`bin/fd.exe` on Windows) in the background when needed. Subsequent runs reuse the cached binaries. `rg` prefers the system `PATH` before the cache, while `fd` checks the managed cache before falling back to system `fd` / `fdfind`. Deleting the `bin/` directory triggers a fresh download on the next use.

docs/reference/server-api.md

@@ -148,6 +148,7 @@ Endpoints are grouped by resource below. A `:{action}` suffix in a path is the a
 | `GET /api/v1/sessions/{session_id}/transcript/ops` | Op-batch catch-up (`since_seq`); `complete: false` means a full refresh is needed |
 | `GET /api/v1/sessions/{session_id}/transcript/user-messages` | Turn-opening user inputs, unpaginated |
 | `GET /api/v1/sessions/{session_id}/transcript/plan` | ExitPlanMode plan content, path, and review outcome |
+| `POST /api/v1/sessions/{session_id}/transcript/plan:reveal` | Reveal the saved plan identified by `agent_id` and `tool_call_id` in the gateway host file manager |
 
 ### Prompts