ConfigOps 0.7.0

Released 2026-08-25.

ConfigOps 0.7.0 expands the local lifecycle from observe → understand → undo to observe → understand → capture → reproduce → undo. A completed Change Session can now become a private Configuration Pack and reproduce its safe desired state on another WordPress website.

Shipped

• Save session as Pack with per-setting selection, name, description, and semantic Pack version.
• A strict configops-pack schema version 1 with stable identity, creation metadata, WordPress/plugin requirements, adapter/schema ownership, desired option states, and reserved empty extension points.
• .configops.json download with no old values, autoload metadata, table names, SQL, PHP, callbacks, or executable templates.
• Local file import and a complete Apply Preview covering compatible, already matching, changing, skipped, safety-excluded, incompatible, and conflicting settings.
• Explicit Apply under a one-use ten-minute plan, site boundary, operation mutex, baseline revalidation, per-setting verification, and compensating recovery.
• Pack application as a completed History session carrying Pack ID and version, followed by the same whole-session Undo contract as any other safe Change Session.

Deliberate boundary

Schema version 1 transports only complete, safe, adapter-backed site options. ConfigOps excludes a complete option when any protected or unsupported value prevents safe reconstruction. It warns about URLs, paths, emails, local references, and adapter-declared environment values but never guesses a replacement.

Packs are private files. This release has no cloud, account, marketplace, public trust model, signature verification, variable substitution, Pack stacking, Network Pack, fleet synchronization, or drift detection. The format reserves empty variables and extensions objects so those capabilities can receive explicit future schemas instead of being smuggled into version 1.

Read Configuration Packs for the operator workflow and full schema contract.