onboardlisted

Set this project up with Pad. If `pad` is not on PATH, give the install one-liner from https://getpad.dev/install and stop. If no `.pad.toml` exists, first run `pad auth whoami` (fast and safe: in non-interactive use — which is where you run — it returns immediately rather than waiting on input, and it works regardless of workspace-link state) to check whether this machine is already configured and authenticated: - If it reports a real user, it's safe to self-heal: run `pad workspace init` (a name/`--template` are optional) to link and create the workspace non-interactively. - If it reports "not configured," "session expired," or anything other than a real user, this machine hasn't finished setup yet. Do **not** run `pad init` or `pad workspace init` yourself — `pad workspace init` now fails fast, non-interactively, with an actionable error instead of hanging (BUG-2538/BUG-2577): "not been initialized yet" pointing at `pad auth setup`, or "not authenticated" pointing at `pad auth login`. That error still means only a human at an interactive terminal can finish it, so running it yourself just spends a tool call confirming what `pad auth whoami` already told you. (With both stdin AND stdout attached to a real terminal it instead drops into the browser auth flow, now bounded at 20 minutes wall-clock — not a state your tool call is ever in.) `pad init` is not a safer probe either: verified live, it fails fast when stdin/stdout aren't terminals in both