wp-health-checklisted

# WP Health Check Lightweight sanity probe. Cheap (<5s), idempotent, no writes. Answers "is this target workable for the next operation?" — NOT "what is wrong with this site overall" (that is `wp-diagnose`). ## Iron Rule <EXTREMELY-IMPORTANT> 1. NEVER substitute `wp-health-check` for `wp-diagnose` — health-check is a sub-5s ping; deep probes (slow queries, plugin conflicts, php errors) belong to diagnose. 2. NEVER skip health-check after `wp-pair-setup` or `wp-migrate` apply — the pair/migrate's own success response does not prove the next-request side of the contract holds. 3. ALWAYS report the warnings array verbatim — warnings frequently identify the EXACT host config that breaks downstream tools (permalinks, exec disabled, mod_security stripping headers). </EXTREMELY-IMPORTANT> ## When to use - After `wp-pair-setup` or `wp-connect`. - Before `wp-migrate` apply (verify destination reachable). - After installing/activating a plugin. - User asks any of: "is it up", "is it healthy", "what version", "is the companion working". Skip when: - User wants a full audit → `wp-diagnose`. - User wants raw runtime state (hooks/transients/options) → `wp-introspect`. ## Boundary Owns: - Single call to `rolepod_wp_health_check { target_id }`. - Surfacing the structured output (versions, *_ok flags, warnings). - Sub-5s budget per call. Does not own: - Multi-probe diagnostic sweep (plugin conflicts, slow queries, php errors) → `wp-diagnose`. - Runtime state snapshot → `wp-introspect