wp-connectlisted

# WP Connect Re-open a previously paired site, or open a new connection over local/SSH/Docker. Picks the right `connect_*` tool by what the user has and what they need to do. ## Iron Rule <EXTREMELY-IMPORTANT> 1. NEVER pick a connection kind without knowing what the user will DO — REST works for 58 of 62 tools but Local/SSH/Docker are needed for the wp-cli-via-companion-shortcut bypass (rare) and direct filesystem ops outside ABSPATH. 2. NEVER store the chosen kind silently — surface "I'm opening this as a `<kind>` target because <reason>" so the user can correct mid-flow. 3. ALWAYS close the previous target with `rolepod_wp_disconnect` before opening the same site under a different kind — registry collisions cause confusing tool failures later. </EXTREMELY-IMPORTANT> ## When to use - "เชื่อม walnutztudio.com" + creds are already in vault (skip pair). - User wants to work against a local WordPress at `/path/to/wp/`. - User has SSH access to the server and wants direct shell. - User runs WP-in-Docker locally. Skip when: - No creds in vault AND user pasted a pair prompt → `wp-pair-setup`. - User already has an active target_id → no need to reconnect. ## Boundary Owns: - Picking the kind (local / rest / ssh / docker). - Calling the right `rolepod_wp_connect_<kind>` tool. - Surfacing the resulting `target_id` + companion status. Does not own: - Pairing (first-time companion redeem) → `wp-pair-setup`. - Post-connect health probe — that is `wp-health-check`. - Any actual W