wp-introspectlisted

# WP Introspect Read-only runtime visibility into WordPress. Covers four scopes via the companion `/introspect` endpoint plus `hook_state` for callback enumeration. Pure read — never writes, never evaluates code (that is `wp-execute-php`). ## Iron Rule <EXTREMELY-IMPORTANT> 1. NEVER set `include_values: true` on production-matched siteurl — option/transient values may contain API keys, third-party tokens, or PII; the production guard fires server-side but client should self-gate first. 2. NEVER call `introspect` repeatedly in a tight loop — every call is a full PHP request; for repeated polling use `request-observer` instead (see `references/introspect-scopes.md`). 3. ALWAYS pair the right scope to the question — `hooks` answers "who is listening", `options_full` answers "what is stored", `transients` answers "what is cached", `request_state` answers "what's the current request"; using `options_full` for a hook question wastes context. </EXTREMELY-IMPORTANT> ## When to use - "Why is filter X not firing?" → `hooks` scope + `hook_state` on that hook. - "Why is the transient cache cold?" → `transients` scope. - "What option does plugin X store?" → `options_full` (names only, then targeted lookup). - "What's the current request lifecycle state?" → `request_state`. Skip when: - The question needs PHP-level mutation (run a function, set a variable) → `wp-execute-php`. - The question is a multi-probe diagnostic (slow queries + plugin conflicts + PHP errors) → `wp-diagnose`. -