ConfigOps 0.5.0

Released 2026-08-24. This release expands conflict-checked site-setting undo beyond the plugins for which ConfigOps ships a dedicated adapter.

Verified key undo beyond adapters

• A site administrator can explicitly enable Verified key undo for plugin arrays under ConfigOps → Support contracts.
• For an unclaimed associative wp_options update, ConfigOps verifies every addition, removal, and replacement against the captured before and after snapshots.
• Before writing, it rechecks current adapter ownership, current parent structure, every target value, and the option's autoload mode.
• Unrelated keys added or changed later are preserved. One conflicting target refuses the complete patch.
• A failed or synchronously rewritten write is compensated back to the complete current state and audited distinctly.

Network operations

• Network Admin now supports named Network Change Sessions for planned work spanning several requests.
• The active-session pointer is network-owned and atomic, and start, stop, authorization, finalization, and cleanup follow the same fail-closed ownership rules as site sessions.
• Named sessions group Network Options evidence without enabling whole-network-change undo. Complete additions and updates remain mutation-level only.

Deliberate boundary

Verified key undo is structural, not semantic, and remains opt-in. It does not restore custom tables, direct SQL, secrets, roots, list indexes, integer-keyed parents, truncated evidence, adapter-owned options, or a target that changed again. ConfigOps is still a compensating settings-undo layer, not a database snapshot or transactional rollback engine.

Release evidence

• 903 unit and deterministic fuzz assertions, 46 adversarial assertions, 272 real WordPress integration assertions, 154 Multisite assertions, and 51 exact real-plugin adapter assertions.
• Real Chromium error, persistence, review, undo, Network Admin, desktop, and mobile flows.
• PHP 8.2–8.5 compatibility, WordPress 7.0–7.1, native MySQL 8.4 and MariaDB 11.4, deterministic packaging, documentation integrity, UI budgets, dependency audits, and WordPress Plugin Check.
• 77.39% tracked-production and 80.27% trust-boundary line coverage.