wp-pair-setuplisted

# WP Pair Setup Onboarding skill. The companion-issued pair_token is a single-use, 60-min, single-bind credential bridge. This skill redeems it once, persists the resulting App Password, opens a RestTarget, and confirms readiness — so the user can move into build/debug work without the manual App Password dance. ## Iron Rule <EXTREMELY-IMPORTANT> 1. NEVER call `rolepod_wp_pair` twice with the same `pair_token` — it is single-use; the second call returns 410 and burns the user's chance. 2. NEVER fall back to manual App Password entry without first checking `wp_health_check` after the pair — a half-paired target reads `companion: null` and silently breaks every companion-gated tool. 3. ALWAYS run `rolepod_wp_health_check` on the returned `target_id` before reporting "ready" — a 200 from `/pair/redeem` only proves the token redeemed, not that the site is workable. </EXTREMELY-IMPORTANT> ## When to use - User pasted a prompt that begins `=== rolepod-wplab one-click pair ===`. - A token in the form `rolepod_wp_pair_<48 hex>` appears in chat. - "เชื่อม walnutztudio.com" / "connect my WordPress" with no prior credentials in vault. Skip when: - Credentials for the site are already in the vault — use `wp-connect` instead. - The user wants manual App Password entry — use `wp-connect` Path B. ## Boundary Owns: - Single-use redemption of a `rolepod_wp_pair_<hex>` token. - Persisting the minted credential into the local vault. - First-connect handshake + health probe. Does not ow