Who Changed It/Docs/Reference
Five commands under wp whochita for monitoring, deploy checks and scripted evidence exports. New in 1.0.0.
Version 1.0.0 adds five commands under wp whochita. They exist for the jobs a browser is bad at: checking the chain from a deploy script or a monitoring probe, pulling an evidence file on a schedule, and reading the latest events over SSH when wp-admin is the thing that is broken. The commands are loaded only when WP-CLI runs, so they add nothing to an ordinary page request.
Everything they do is the same code the settings screen uses: verify runs the full chain check behind Re-verify now, export writes the same signed file as the export buttons and is recorded in the log the same way, and purge goes through the audit chain like the button does. And because the request source is recorded since 1.0.0, anything the commands change shows up in the log marked via WP-CLI.
Verifies the audit chain from the first record to the last and prints each problem it finds with its chain position. It exits with status 1 when the chain is broken, which is what makes it useful outside an interactive shell: a deploy pipeline can refuse to continue, and a monitoring check can alert, without parsing any output.
wp whochita verify
wp whochita verify --format=json--format is table (default) or json. What the individual problems mean, and what a broken chain does and does not prove, is in integrity and evidence.
One screen describing the state of the log: plugin version, number of records, the oldest record, whether the chain is intact, the chain head's position and hash, how many authorised removals the chain has recorded, where the chain key is held (wp-config.php or the database), the default retention, the IP privacy mode, and when the next purge and the next digest will run.
wp whochita status
wp whochita status --format=json--format is table, json or yaml. The chain head hash is worth recording somewhere off the server now and then; the digest email does that for you if it is switched on.
The most recent events, newest first: chain position, time (UTC), severity, event type, object, user and IP.
wp whochita tail
wp whochita tail --limit=50 --severity=dangerous
wp whochita tail --format=csv--limit defaults to 20. --severity takes normal, strange or dangerous. --format is table, json, csv or yaml.
Writes a signed evidence export — the same format, manifest and signature as the export buttons — to a file or to standard output.
wp whochita export --format=json --file=evidence.json
wp whochita export --format=csv --severity=dangerous --from=2026-01-01 > flagged.csvThe manifest states the filters and time bounds used, so a filtered export is provably partial rather than silently incomplete. Every export is itself recorded as an event.
With no flags, runs the retention purge the daily cron runs: each event family loses the records past its own retention window, and the command reports how many went and how many remain. With --all it empties the log, after a confirmation prompt that --yes skips.
wp whochita purge
wp whochita purge --all --yesEither way the removal goes through the audit chain, which records what was taken out, so the chain still verifies afterwards. A full purge is recorded as log_purged, the first event of the empty log, and classified dangerous like the button — it alerts whoever receives dangerous events.
Gate a deploy on the chain. Run wp whochita verify as a step before the release; a non-zero exit stops the pipeline and the output names the positions that failed.
Nightly evidence file. A system cron line keeps a dated, signed export outside the web root:
15 2 * * * cd /var/www/example.com && wp whochita export --format=json \
--from=$(date -d yesterday +\%F) --to=$(date -d yesterday +\%F) \
--file=/srv/evidence/wci-$(date -d yesterday +\%F).jsonMonitoring. Point a check at wp whochita verify --format=json, or alert on new lines from wp whochita tail --severity=dangerous --format=json if you already collect output from WP-CLI.