Appearance
Skip to content
Know what changed.
Capture #1 · WP Mail SMTP 4.9.08 settings1 redacted7 safe undo targetsOpen full capture ↗
Documentation · 0.2.0
Configuration evidence for WordPress
Know what changed.
Undo only what is proven.
ConfigOps records one explicit settings task, separates decisions from technical side effects, removes probable credentials before storage, and refuses unsafe undo.
- Release
- 0.2.0 technical preview
- Runtime
- WordPress 7.0+ · PHP 8.2–8.5
- Storage
- Local database · no account
- Evidence
- 77.30% production · 79.02% trust boundaries
Actual product evidence · no mockup
One SMTP save, opened like a ledger.
The recorded request contains eight settings. The password is gone before persistence; seven supported values remain independently undoable.
Swipe to inspect the real capture · tap the image for full size
The operator path
Read the evidence in order.
- 01
Record one task
Name a bounded settings job, start recording, then use wp-admin normally.
Capture boundaries → - 02
Read what actually happened
Review intended settings separately from runtime noise, secrets, and unmanaged writes.
Review anatomy → - 03
Undo only matching state
ConfigOps checks current values, adapter versions, references, and capture integrity before writing.
Undo contract →
The line ConfigOps will not cross
A recorder is not a backup.
ConfigOps does not promise transactional rollback, copy media, deploy content, synchronize databases, or invent support for unknown custom tables. When evidence is incomplete or ownership is ambiguous, capability disappears instead of uncertainty being hidden.