pb-setuplisted

<Purpose> pb-setup is the single entry point a new user runs right after installing the plugin. It takes someone from "just installed, nothing set up" to "first diagnosis + analysis report" in one guided flow: it resolves paths, checks dependencies, imports the runner's data, bootstraps their profile from that data, optionally captures a goal, and produces the first analysis report. Everything else (`/pb-today`, `/pb-log`, `/pb-report`, `/pb-plan`) becomes useful only after this runs once. </Purpose> <Use_When> - The runner just installed the plugin, or asks "how do I start / set up / get started / 시작" - `OMPB_HOME` has no `training-log.jsonl` yet (no data imported) - `runner-profile.json` is missing - Keyword triggers: "setup", "get started", "온보딩", "시작하기", "처음", "first run" </Use_When> <Do_Not_Use_When> - The runner is already set up (profile + log exist) and just wants a normal action — route to the specific command/skill instead. </Do_Not_Use_When> <Conventions> - **Scripts** live in the installed plugin and MUST be invoked by absolute path: `python3 "$CLAUDE_PLUGIN_ROOT/scripts/<name>.py" ...`. Never assume `scripts/` is in the cwd. - **Data** lives under `OMPB_HOME`, smart-resolved by the scripts: `$OMPB_HOME` → `~/.ompb` → `./.ompb` → default `~/.ompb`. Resolve it once at the start and tell the runner which dir is in use. </Conventions> <Steps> ## Step 0 — Resolve paths Confirm `$CLAUDE_PLUGIN_ROOT` is set (it is, inside an installed plugin). Determine the dat