v0.2.0

WPGuard's first public release adds persistent correction checks to supported WordPress edits.

Save a requirement for one site and field, then check future option, post-meta, or post-content updates against it. Failed or unknown applicable checks refuse the write. Historical requests can be imported privately and retrieved for an exact client; imported narratives do not become executable rules automatically.

Also includes site context, edit previews, change packets, and prior-value snapshots for supported mutations. Coverage varies by tool. Read SECURITY.md before connecting a site: current token scopes and the companion key are for trusted operators.

Install: use the attached companion ZIP (WordPress 5.6+, PHP 8.0+), or run ghcr.io/cgallic/wpguard-mcp:0.2.0 on Linux amd64 or arm64. The server and companion are separate components. See the installation guide.

The attached .sha256 file verifies the companion ZIP. No customer histories or real correction examples are bundled.

What's Changed

• Safety-core + docs batch: close 17 backlog issues by @cgallic in #27
• Connect wpguard core to WP MCP Cloud by @cgallic in #28
• Bind approvals to exact WordPress changes by @cgallic in #29

New Contributors

• @cgallic made their first contribution in #27

Full Changelog: https://github.com/cgallic/wpguard-mcp/commits/v0.2.0