PIGS-864: Add render_pdf_page tool for inline page image rendering

CLAUDE.md

@@ -57,6 +57,7 @@ The codebase is **fully typed**. Treat any type error as a build failure.
 - **JSON-returning tools must use `outputTarget`** — any tool that produces JSON takes the shared `outputTargetSchema` param (`inline` | `file` | `both`, default `inline`) and returns via the `jsonResult` helper in `node-version/src/tools/jsonOutput.ts`.
   Inline returns parsed data under `data` so Claude can chain steps; `file`/`both` write to disk and return `outputFilename`.
   Default inline so transient flows don't litter the working folder. (Binary outputs like Excel/PDF remain file-only and are orthogonal to `outputTarget`.)
+- **Inline image tools** (e.g. `render_pdf_page`) return an MCP `image` content block (`type: 'image'`, base64 `data`, `mimeType`) and never write to disk — `outputTarget` does not apply.
 
 ## Sub-Agents
 

README.md

@@ -65,6 +65,11 @@ Split contract.pdf into two files: pages 1-5 and pages 6-10 using Nitro
 Add password protection to confidential.pdf in Desktop using Nitro
 ```
 
+**Render a PDF page as an image to verify content visually:**
+```
+Using Nitro, render page 1 of contract.pdf in Downloads at 150 DPI so I can see it
+```
+
 ## Data Handling
 
 When you invoke a Nitro PDF Services tool, the file you specify is uploaded to Nitro's hosted Platform API at `api.gonitro.com` for processing. Results are written back to your local disk. Your OAuth refresh token is stored only on your local device at `~/.nitro-mcp/session.json`; access tokens are kept in memory and never stored server-side.