Repository navigation
feat: migrate WP Starter configuration and finalize compatibility - #6
Merged
Merged
Conversation
brianvarskonst
changed the base branch from
phase-5-kernel-integration
to
main
September 30, 2026 10:05
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.
Existing WP Starter configurations can now migrate to native Runtime configuration while retaining compatibility profiles, legacy step aliases, extension services and callback behavior. The compatibility layer reports deprecations without contaminating HTTP responses. Migration preserves source files and supports dry-run, explicit force and repeatable no-op runs.
Standalone setup also repairs standard WordPress package placement and Composer metadata after
composer install --no-plugins. This covers core, plugins, MU plugins, themes and dropins, including real WPackagist packages. Regular Composer installers remain supported. Offline recovery deliberately refuses root/overlapping layouts and unknown destination conflicts; correctly installed root/nested layouts remain usable. ADR 0019 documents these limits and rollback behavior.Review corrected two defects: preparation rejected already-correct root/nested layouts, and URL dropins ignored forced replacement of existing symlinks. Regression tests verify unchanged files on failed recovery/download and replacement of only the intended link.
Validation after the corrections:
docs/acceptance.md.QA #3 and Runtime phases 1–5 are merged. Final Phase 6 CI is checked before merging. Consumer migrations remain separate in starter #29 and demo #49; they still need CI read access to this private repository and a final dependency update to Runtime main. No credentials or repository access were changed during this review. Final full drop-in acceptance remains open as documented.