Skip to content

feat: migrate WP Starter configuration and finalize compatibility - #6

Merged
brianvarskonst merged 16 commits into
mainfrom
phase-6-compatibility-migration
Sep 30, 2026
Merged

brianvarskonst merged 16 commits into
mainfrom
phase-6-compatibility-migration

Conversation

@brianvarskonst

@brianvarskonst brianvarskonst commented Sep 29, 2026 •

Copy link
Copy Markdown
Member

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:

  • Complete local QA: 1,043 tests / 7,298 assertions, no skips, coding standards and PHPStan max passed.
  • All 407 inventory rows have executed passing behavioral evidence; the evidence checker's four tests passed.
  • All 249 isolated differential cases against pinned WP Starter release/development baselines passed.
  • Real WPackagist installation passed in CI. Previous fresh starter/demo browser, database, kernel and global no-plugins replay evidence is recorded in 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.

@brianvarskonst
brianvarskonst changed the base branch from phase-5-kernel-integration to main September 30, 2026 10:05
@brianvarskonst
brianvarskonst marked this pull request as ready for review September 30, 2026 10:08
@brianvarskonst
brianvarskonst merged commit b1c1662 into main Sep 30, 2026
5 checks passed
@brianvarskonst
brianvarskonst deleted the phase-6-compatibility-migration branch September 30, 2026 19:45
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.

1 participant