wp-changeslisted

# WP Changes The rollback skill. Every write the MCP issued through companion v2.3+ is captured in the Change Ledger (categorized, before+after state, applied flag). This skill queries that ledger, toggles individual rows, runs git-bisect-style binary narrowing, and panic-disables every change in a time window when the site is on fire. ## Iron Rule <EXTREMELY-IMPORTANT> 1. NEVER panic-revert without first running `wp-health-check` to confirm the site is actually broken — panic disables real production changes; using it as a "I'm curious" tool causes user-visible regressions. 2. NEVER toggle a row with `reversible: 0` and expect the side effect to undo — execute_php side effects and wp-cli destructive ops are flagged irreversible at record time; the toggle flips the flag but cannot replay the inverse. Surface this verbatim. 3. ALWAYS surface `target_descriptor` + `source_tool` when listing changes — user needs to recognize what each row IS, not just an opaque ID. </EXTREMELY-IMPORTANT> ## When to use - "เว็บพังหลัง AI แก้ของ" — panic + bisect flow. - "What did AI do in the last hour?" — query with `since_minutes: 60`. - "Undo only the last theme.json change, keep the rest" — single toggle. - "Re-enable the changes I disabled earlier" — bulk toggle. - Pre-migration: query ledger to know what changed before you snapshot. Skip when: - The site is up + user has no complaint → no need to touch ledger. - Plain "is it up" → `wp-health-check`. - Multi-probe diagnosis → `wp-diagn