Fix content-only static artifact boundary - #862
Merged
Conversation
AI: OpenAI GPT-5.6 Sol via OpenCode implemented the content-only intake and companion-plugin boundary with adversarial regression coverage.
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
1 participant
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.
Fixes #853
Summary
Tests
npm test(51 passed; WordPress-runtime, browser-WP-Codebox, and operator-only suites skipped by manifest without their configured runtime env)npm run test:companion-plugincomposer validate --no-check-publishMigration / Compatibility
Existing compiler payloads using PHP render templates, PHP companion assets, or schema-less companion payloads now fail closed. Migrate server-side behavior to native blocks/data bindings or client-side JavaScript; static markup remains supported in generated dynamic blocks.
AI Assistance
OpenAI GPT-5.6 Sol via OpenCode implemented the content-only intake and companion-plugin boundary, updated tests and documentation, and ran the listed verification. Chris Huber remains responsible for every line.