wp-diagnoselisted

# WP Diagnose Heavyweight probe + audit. Multi-second, ranks findings by severity, writes a markdown / JSON artifact. Subsumes audit_security + audit_many + cron/cache/mail/user_session inspection. The "what is wrong here" entry point — `wp-health-check` answers "is it up", this answers "is it healthy at depth". ## Iron Rule <EXTREMELY-IMPORTANT> 1. NEVER use `wp-diagnose` as a pre-flight check before every tool call — it is multi-second and writes artifacts; for cheap pre-flight use `wp-health-check`. 2. NEVER skip the artifact write — the per-run report at `./.rolepod-wplab/artifacts/<run_id>/diagnose-report.md` is the canonical handoff to the user / to ticket systems / to `wp-migrate`. 3. ALWAYS surface CRITICAL findings before INFO findings — a 6-month-outdated WordPress core with known CVEs hidden under 80 lines of "autoload is 60 KB" wastes the user's first read. </EXTREMELY-IMPORTANT> ## When to use - "Audit this site for security issues." - "Why is this site slow?" - "Are any plugins out of date?" - "Check for plugin conflicts." - "Show me PHP errors." - "Run a full diagnostic before I migrate." - "Audit these 20 sites" → `audit_many` orchestrator. Skip when: - "Is it up?" → `wp-health-check`. - "What's in `wp_options` for plugin X?" → `wp-introspect`. ## Boundary Owns: - `rolepod_wp_diagnose` (5 scopes: plugin_conflict_probe / slow_queries / large_options / broken_images / php_errors). - `rolepod_wp_audit_security` (core/plugin/theme outdated + weak admins +