orbit-fse-testlisted

# 🪐 orbit-fse-test — Full-Site-Editing compat WordPress 6.0+ ships block themes with the Site Editor. Plugins (and especially themes) must be FSE-aware or they break the editing experience. --- ## Quick start ```bash claude "/orbit-fse-test Audit ~/plugins/my-plugin for FSE compatibility." ``` --- ## What it checks ### 1. theme.json present + schema 3 ```json { "$schema": "https://schemas.wp.org/trunk/theme.json", "version": 3, "settings": { ... }, "styles": { ... }, "templateParts": [ ... ], "customTemplates": [ ... ] } ``` **Whitepaper intent:** `version: 3` (WP 6.6+) supports per-block typography fluid clamps + improved style engine. Older versions (1, 2) still parse but lock you out of new APIs. ### 2. Templates directory structure ``` my-theme/ ├── theme.json ├── style.css ├── templates/ │ ├── index.html │ ├── single.html │ ├── archive.html │ └── 404.html └── parts/ ├── header.html ├── footer.html └── sidebar.html ``` Plugins extending FSE → use `register_block_pattern()` (not raw template files). ### 3. Style variations ``` styles/ ├── pink.json ← variation ├── monochrome.json └── ... ``` Each style variation overrides theme.json values. Auditor checks variations stay valid against schema. ### 4. Block locking **Whitepaper intent:** Site Editor lets users break things. `templateLock: "all"` and `lock: { remove: true, move: true }` keep critical layout intact. ```html <!-- wp:group {"templateLock":"all"} --> <!-- wp:si