btms-prv-sizinglisted

# btms-prv-sizing — Battery Pack PRV Sizing ## Overview Two execution paths share the same backend API: - **Browser Path** — local relay serves an HTML GUI; user clicks ▶ Run; results auto-stream back to chat. Claude Code only (needs `bash`/`PowerShell` and a writeable filesystem). Best for exploring, charting, and exporting reports. - **MCP Path** — Claude calls `prv_solve` directly via HTTP MCP; results land in chat with no relay or browser. Works in any environment with the MCP connector configured. Best for "I already know my parameters" and parameter sweeps. Setup, installation, `.mcp.json` configuration, and end-user troubleshooting live in [README.md](README.md). Detailed step-by-step commands for each path live in [references/playbook.md](references/playbook.md). Common runtime gotchas live in [references/troubleshooting.md](references/troubleshooting.md). This file is the **runtime playbook router** — follow it from top to bottom every time the skill is invoked. --- ## Step 0 — Environment detection (run once per session) Before the Route Decision, determine which runtime profile this session is in. The signal is whether a shell tool is available. 1. Scan the active tool list / system reminder for a `Bash` or `PowerShell` tool whose description mentions executing shell commands. If present → set `runtime = "code"`. 2. Otherwise → set `runtime = "headless"` (Claude Desktop / claude.ai — no relay, no filesystem, no browser). **Only MCP Path i