v0.1.0-beta
Current betaThe first Hewn beta: a theme family, component runtime, visual editor, Workspace, human-approved change sets, MCP, content bindings, quality tooling and rescue.
Added
- Hewn Blank, Hewn reference and Hewn Child themes.
- Component registry, JSON Schema contracts, PHP/TS validators and server renderer.
- Admin-only visual editor with structure tree, component library, bindings, viewports and iframe preview.
- Workspace with Ask/Build/Fix modes, plan and change-card flow.
- Draft → validated → planned → approved → applied change sets with preview, approval, apply and rollback.
- ACF field-group generation or native meta boxes when ACF is absent.
- MCP stdio bridge and WordPress MCP Adapter HTTP server with scoped tokens.
- Design Kernel tokens, Quality Engine and declarative generated components.
- AI media previews with provenance and explicit Media Library save.
- Rescue mu-plugin, safe mode, health probes, diagnostics and onboarding.
Improved
- Change-set recovery points, postconditions and production write gate.
- Workspace previews and selected-edit reliability.
- Release ZIPs, checksum manifest and release verifier.
- Admin design system and frontend asset delivery.
Security
- MCP off by default; write tools require an experimental flag and an explicit capability.
- Agent tokens are hashed at rest, site-bound, 24-hour, max 20 and revocable.
- Human approval is required; an agent session cannot hold propose and approve together.
- Production writes need HEWN_ALLOW_PRODUCTION_WRITES, hewn_production and approval.
- Audit entries use a site-salted HMAC chain with 90-day retention.
- 401 recursion fix, security headers and self-hosted fonts.
Fixed
- Parent theme folder resolution for Hewn Child.
- Unsaved-change guard for template switches.
- Workspace and visual editor issues from the hardening pass.
Release notes
- Only 0.1.0-beta exists; the 3 November hardening is listed as Unreleased in CHANGELOG.md but is present in the shipped beta artifacts.
- WordPress 7.0+ and PHP 8.2+ are required; the old 6.7 site claim is wrong.
- The visual editor is feature-flagged off outside the development channel.
- Distribution is manual ZIP + release.json; there is no self-hosted updater.