Skip to content

Extend semantic E2E with Site Editor objects#317

Merged
adamziel merged 1 commit into
trunkfrom
codex/wp-semantic-merge-e2e-next
May 18, 2026
Merged

Extend semantic E2E with Site Editor objects#317
adamziel merged 1 commit into
trunkfrom
codex/wp-semantic-merge-e2e-next

Conversation

@adamziel
Copy link
Copy Markdown
Contributor

What it does

Extends the runtime WordPress semantic merge E2E so branch-local Site Editor objects are part of the real merge graph.

The E2E now creates and validates wp_template_part, wp_template, and wp_global_styles rows on both source and target branches, alongside the existing pages/media/options/plugin-shaped graph.

Rationale

The fast PHP tests already cover many Site Editor invariants, but the runtime E2E should prove that real WordPress-created state survives a clean branch merge with zero conflicts.

Implementation

  • Adds Site Editor object creation to the semantic E2E mu-plugin.
  • Stores the branch-local Site Editor IDs in the existing semantic option graph.
  • Validates after merge that both branches' objects survived and that option JSON still points to the correct branch-local IDs.
  • Updates the merge reliability audit docs to point at the newer runtime evidence and v0.1.34 release gate.

Testing instructions

git diff --check origin/trunk...HEAD
bash -n tests/cow/e2e.sh
awk '/^cat > "\\$WORK\\/main\\/wp-content\\/mu-plugins\\/forkpress-e2e-semantic.php" <<\\x27PHP\\x27$/{in_block=1; next} in_block && /^PHP$/{exit} in_block{print}' tests/cow/e2e.sh | php -l

Full tests/cow/e2e.sh should run in CI because it needs a production runtime bundle.

@adamziel adamziel force-pushed the codex/wp-semantic-merge-e2e-next branch from 5d6f7f4 to 9563ccc Compare May 18, 2026 10:49
@adamziel adamziel marked this pull request as ready for review May 18, 2026 10:51
@adamziel adamziel merged commit 74c4de9 into trunk May 18, 2026
7 checks passed
@adamziel adamziel deleted the codex/wp-semantic-merge-e2e-next branch May 18, 2026 10:51
@adamziel adamziel mentioned this pull request May 18, 2026
adamziel added a commit that referenced this pull request May 18, 2026
## Release `v0.1.35`

Version bump and release metadata update for `v0.1.35`.

**Changelog draft:**
* Extend merge revalidation and WordPress semantic guards
([#313](#313))
* Add Events Calendar-shaped merge smoke coverage
([#318](#318))
* Extend semantic E2E with Site Editor objects
([#317](#317))
* Add thin SSH remote clone command
([#315](#315))
* Update release gate evidence for v0.1.34
([#319](#319))
* Guard plugin children behind logical identity collisions
([#320](#320))
* Hold case-insensitive upload path collisions
([#322](#322))
* Cover scoped crash recovery
([#323](#323))
* Hold malformed attachment metadata shapes
([#324](#324))
* Cover thin remote clone branch metadata
([#326](#326))
* Cover source-added trigger view dependencies
([#321](#321))
* Cover WooCommerce duplicate address semantics
([#325](#325))
* Cover Events Calendar organizer validator semantics
([#327](#327))
* Cover Elementor widget media validator semantics
([#328](#328))
* Reject duplicate attachment upload metadata rows
([#329](#329))
* Cover existing branch Git update crash recovery
([#330](#330))
* Mark WordPress media repairs review-only
([#331](#331))
* Cover backup attachment metadata drift
([#332](#332))
* Limit release verification for COW-only PRs
([#335](#335))
* Batch merge reliability roadmap coverage
([#336](#336))
* Cover WordPress upload MIME drift
([#333](#333))
* Add branch merge history commands
([#334](#334))
* Show restored stale-audit reviews
([#337](#337))
* Cover Yoast duplicate indexable permalinks
([#338](#338))
* Cover Yoast indexable hierarchy drift
([#339](#339))
* Cover revision parent semantic drift
([#340](#340))
* Expose merge history in branch switcher
([#341](#341))
* Cover ACF relationship validator drift
([#342](#342))
* Show merge history on branch admin page
([#343](#343))
* Drill into conflicts from branch admin history
([#344](#344))
* Expose branch tree on admin page
([#345](#345))
* Resolve conflicts from branch admin page
([#346](#346))
* Document conflict review workflow
([#347](#347))

**Full changelog:**
v0.1.34...release/v0.1.35

## Next steps

1. **Review** the changes in this pull request.
2. **Push** any additional edits to this branch (`release/v0.1.35`).
3. **Merge** this pull request to publish `v0.1.35`.

Merging will automatically build ForkPress binaries, create a GitHub
release, and update the Homebrew formula.

Co-authored-by: Codex <codex@openai.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants