[codex] Extend semantic E2E for Site Editor objects#316
Closed
adamziel wants to merge 1 commit into
Closed
Conversation
5204d23 to
c16bd65
Compare
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.
What it does
Extends the runtime WordPress semantic merge E2E slice with branch-local Site Editor objects:
wp_template_partwp_templatewp_global_stylesThe test now creates these through WordPress on both source and target branches, stores their IDs in the branch semantic option graph, merges source into target, and verifies both branches' Site Editor rows and option references survived the merge without ID rewriting.
Also updates
docs/merge-reliability.mdto point the release-gate evidence at the successfulv0.1.34publish run.Rationale
The fast PHP smoke suite already covers synthetic
wp_template_part,wp_template, andwp_global_stylesmerge cases. This adds the matching runtime coverage so real WordPress insertion, serialization, and branch merge behavior are covered by the semantic E2E path too.Implementation
The existing
forkpress-e2e-semantic.phpmu-plugin now inserts Site Editor rows during each branch mutation and includes them in theinspectresponse. The post-merge validator checks:This PR is stacked on #313 and should be retargeted to
trunkafter #313 merges.Testing instructions
Run:
Full runtime verification is:
Local full E2E was not run in this worktree because it does not have a built production
dist/x86_64-unknown-linux-gnuruntime bundle.