ConfigOps 0.4.0

Released 2026-08-19. This release makes WordPress Multisite a tested support contract instead of a storage foundation.

What shipped

• Network activation initializes and maintains isolated site ledgers, capabilities, schema state, and retention for existing and newly created sites.
• Network Options API changes made through authorized Network Admin, REST, and WP-CLI requests appear in a separate network-wide evidence ledger.
• Complete network option additions and updates can be undone one mutation at a time after current-value conflict checks, an atomic network lock, value-free auditing, post-write verification, and compensating recovery.
• Network deactivation, site deletion, retention, migration, and uninstall clean up the correct site or network-owned state without crossing scope boundaries.
• Automatic evidence delivery survives normal wp-admin navigation and uses one shared command path across wp-admin and REST.

Deliberate boundary

Network option deletes remain review-only because WordPress exposes the delete hook after the previous value is gone. Authority and plugin-lifecycle state, derived counters, named network sessions, and whole-network-change undo also remain unavailable. Site ledgers are not aggregated: ConfigOps does not provide cross-site bulk operations, remote apply, or fleet control.

Release evidence

• WordPress 7.0 and latest on PHP 8.2 through PHP 8.5.
• MySQL 8.4 and MariaDB 11.4 native integration lanes.
• 254 WordPress integration assertions, 132 Multisite assertions, and 51 exact adapter assertions.
• Real Chromium flows for site settings, WP Mail SMTP Free 4.9.0, Yoast SEO Free 28.2, and Network Admin at desktop and mobile widths.
• 76.43% tracked-production and 78.11% trust-boundary line coverage.

WordPress.org users upgrading from 0.3.0 also receive the navigation-safe evidence delivery and maintainability hardening developed in the unreleased 0.3.1 line.