Carry document metadata in WordPress site plans - #640
Merged
Conversation
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
blocks-engine/wordpress-site-plan/v2with normalized per-document metadata and generic reporting summaries.Closes #639
Relates to #632
What changed
How to test
composer --working-dir=php-transformer validate --strict.php php-transformer/tests/contract/wordpress-site-plan.php; expectwordpress-site-plan contract passed.composer --working-dir=php-transformer test; expect all contracts, 244 parity fixtures, and package-install proof to pass.git diff --check origin/trunk...HEAD.The existing required WordPress 6.7.4/MySQL integration job remains enabled alongside the full Composer gate.
Compatibility
This is additive to WordPressSitePlan v2 from php-transformer v0.4.0. Existing v2 fields and resolver behavior remain unchanged. Consumers can ignore the new metadata/reporting fields; consumers needing stable import reports can now project them from resolved plan plus receipt without reading
TransformerResult,compiled_site,MaterializationView, raw HTML, source files, or private envelopes. Intended release: v0.4.1.AI assistance