connect

`/pad:connect` opts THIS session into Pad's live stream: it declares consent to receive `pad push` notifications (the security gate — no consent, no stream), wakes the session's push monitor, and on the FIRST connect of a session runs the workspace's boot ritual. Invoking this skill is also what starts the gated monitor process, so run it once per session you want connected. If the `pad` CLI is missing (command not found), say so and point at https://getpad.dev/install — don't retry or guess at alternate paths. If no `.pad.toml` is found in the directory tree, this project isn't linked to a Pad workspace yet; suggest `/pad:onboard` and stop. Do these in order: 1. **Arm the session.** Run `pad session arm`. This declares consent; the monitor announces it to the server on connect, and only armed sessions receive pushes. 2. **First-connect check + boot ritual.** Run `pad session first-connect --format json`. - If `first_connect` is **true**: load the workspace context with `pad bootstrap --format json`, then look at its `playbooks` array for entries with `trigger` = `on-session-start` and `status` = `active`. For each, load the body with `pad playbook show <invocation_slug> --format markdown` and follow it. This is the workspace's own operating ritual firing for whoever connects. (Many workspaces have none — that's fine; just skip.) - If `first_connect` is **false**: this is a reconnect. Do NOT re-run the boot ritual; just re-affirm the...