### Python platform (enabled)
- **Use for**: Python runtime-debug scenarios (debugpy/DAP probes / logs / outbound HTTP capture).
- Scenario **scripts** call python debug tools via `callTool('<bare-tool>', {...})` — discover the
  available `pdt_*` tool names (debug connect / probes / snapshots / logs / http capture …) from your
  connected MCP schemas; don't guess.

**What to test & how — capture the SAME evidence the verifier would** (a scenario runs FOR
verification, so its script must collect what the python cycle collects). In the script:
1. **Connect** — `pdt_debug_connect` (one of `host`+`debugpyPort` / `pid` / `processName` /
   `containerName`). The target needs `debugpy` installed in its environment.
2. Pick an **evidence path** for the changed code path:
   - **Probe path** (proves the code path executed) — set a probe at the changed location
     (`pdt_debug_put-tracepoint` / `pdt_debug_put-logpoint` / `pdt_debug_put-exceptionpoint`),
     **exercise the path** (drive it via a request / CLI / another platform's call — without this the
     probe never fires), then read `pdt_debug_get-probe-snapshots`; at least one probe must come back
     `triggered: true`.
   - **Log path** (proves no errors during execution) — exercise the path, then `pdt_debug_get-logs`
     filtered to the error level (no ERROR-level entries = pass).
   - **Network path** (proves the expected outbound call happened) — `pdt_o11y_get-http-requests`
     once to install the capture agent (forward-looking), exercise the path, then read it again and
     assert the expected request(s) / status.
   - **Thread-dump path** (for deadlock / GIL-contention / hang fixes) — `pdt_debug_dump-threads`
     snapshots every thread's stack at once (momentarily pauses, then resumes); assert the expected
     thread states (e.g. the previously-deadlocked thread is no longer blocked).

`return` the probe snapshots / logs / captured flows (read them with `returnOutput: true` so their
data reaches the script's `return`) **plus explicit pass/fail assertions** so a later verify run can
judge them. **The python platform (`pdt_*`) is
Python ONLY** — never author `pdt_*` scenarios for Node.js / Java / Go / Rust / Ruby / .NET / PHP
backends; use the **node** platform for Node.js and the **backend** platform for the rest.