Prove the Studio-to-Spacefast WP Docs workflow#18
Open
chubes4 wants to merge 5 commits into
Open
Conversation
This was referenced Jul 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Make Git Markdown canonical while proving an optional reversible WordPress Studio and MDI authoring loop, a Blume static build, and approval-gated Spacefast publication.
What changed
How to test
bash -n tests/*.sh; expect All repository shell gates parse successfully..bash tests/verify-studio-spacefast.sh; expect The 403-record corpus, Blume build, representative routes, and mocked Spacefast publication contract pass..WP_DOCS_STUDIO_SITE_DIR=/path/to/site bash tests/verify-studio-mdi.sh --mutate; expect Primary-mode counts, split state, both authoring directions, exact fixture restoration, and Git cleanliness pass for a compatible configured Studio site..Compatibility
No WordPress runtime API, plugin extension path, or persisted content schema changes. Git Markdown remains canonical; Studio is optional, MDI runtime state stays outside the corpus, and Spacefast publication remains approval-gated.
Evidence
AI assistance
Source relationships