Add the WordPress integration harness and the compatibility matrix

[Shubochandrosarker]

What this changes

Before: nothing in this repository loads WordPress. The unit suite stubs it — right for a fast suite, useless for anything that must exercise activation, a route, a capability or a cron event. Only two production files load under it. After: a real WordPress and a real database, across every supported version.

That gap is not theoretical. It is exactly how the init fatal fixed in #4 survived a green CI for the entire life of the 2.0.0 release.

Delivers P0-0, and the machinery P0-1 needs.

Type

• Release/CI plumbing
• Feature (test infrastructure)

Rules touched

• None of the above

No runtime code changed. Not one file under includes/, templates/ or assets/ is touched.

Current stable WordPress, determined at execution time

Per §9, not taken from documentation — read from the WordPress/wordpress-develop tag list:

Line	Latest
6.8	6.8.7
6.9	6.9.6
7.0	7.0.3 ← current stable

Matrix: WordPress 6.8 / 6.9 / 7.0.3 × PHP 8.2 / 8.3 / 8.4, plus a non-blocking trunk canary. A green canary is never support for an unreleased version.

What is here

File	Why
bin/install-wp-tests.sh	Installs WordPress + the core test library. No svn — GitHub runners don't ship it, and a missing binary is a confusing way to fail a compatibility matrix.
phpunit-integration.xml	Separate config, by necessity — see below
tests/integration/bootstrap.php	Loads WordPress, captures deprecations across load and activation
…/class-memberistic-integration-testcase.php, …-record-factory.php	Base case and fixtures
ActivationTest, FreshInstallTest, LoadDeprecationsTest	P0-0's own acceptance: schema, DB version, capabilities, roles, safe defaults
.github/workflows/integration.yml	The matrix + canary

Why two PHPUnit configs. Not preference — the WordPress core test library still calls PHPUnit\Util\Test::parseTestMethodAnnotations(), which PHPUnit 10 removed. Every integration test errors under 10.x, identically on 6.8, 6.9, 7.0 and trunk, so no newer WordPress resolves it. The integration job installs 9.6 over the top; the unit suite keeps 10.5 and never loads WordPress. Merge the configs if WordPress adopts PHPUnit 10+.

LoadDeprecationsTest is the load-bearing one. It finds version incompatibilities without anyone maintaining a per-release list of what got deprecated — a list that would be stale the day it was written. WordPress reports its own deprecations; the bootstrap captures them; the test asserts the set is empty. Its second test asserts the running WordPress matches the version the job installed — a matrix reporting green for a version it never exercised is precisely what Tested up to exists to prevent.

Scope

The harness and P0-0's acceptance tests only. RestAuthorizationTest, RestOwnershipTest, RestRouteInventoryTest and WebhookSecurityTest are P0-5/P0-6 and get their own PRs — the route-inventory artifact step was removed from the workflow so it doesn't reference a test that isn't here.

readme.txt Tested up to is deliberately unchanged. Per §13 and P0-1 it moves only after the matrix passes, and the matrix has never run.

What I ran

$ php -l on every ported file                    clean
$ vendor/bin/phpunit -c phpunit.xml              OK (51 tests, 847 assertions)
$ yaml.safe_load ci.yml release.yml integration.yml    all three valid
$ bash -n bin/install-wp-tests.sh                parses
$ bin/build-dist.sh && bin/assert-dist-clean.sh  distributable is clean
    correctly excluded: phpunit-integration.xml
    correctly excluded: tests
    correctly excluded: bin

⚠️ What I could NOT run — and why CI is the proof

I have not executed the integration suite. It cannot run in this environment:

Requirement	Status here
MySQL/MariaDB server	✗ not installed
Docker daemon (to run one)	✗ CLI present, no daemon — /var/run/docker.sock absent
api.wordpress.org	✗ gateway returns 403 — policy denial, confirmed via the proxy status endpoint
wordpress.org, downloads.wordpress.org	✗ unreachable
svn	✗ not installed
github.com (used to read the WP version)	✓ reachable

So GitHub Actions is the first place this code can execute, and this PR's CI run is its first real test rather than a confirmation. I expect to iterate on it. Treat a red integration job here as expected-and-being-fixed, not as a finished deliverable.

P0-0 and P0-1 stay open until that matrix is green. I have marked P0-0 in progress, not done.

Other gaps, stated plainly:

• The three integration tests have never asserted anything against a real WordPress. They are ported and lint-clean; that is all I can currently claim.
• bin/install-wp-tests.sh has never been executed — bash -n only.
• The trunk canary is untested like everything else here.

Also found

composer.lock is already out of date with composer.json on main, independent of this branch — git stash-free check against main reproduces it. composer install warns rather than fails, so CI is unaffected. Not fixed here: regenerating the lock needs packagist, which this environment cannot reach (curl error 28, SSL connection timeout).

Relatedly, yoast/phpunit-polyfills is not added to composer.json, though the reference implementation adds it. Adding it without being able to regenerate the lock would have made the mismatch worse and risked the unit-suite job. The integration workflow installs it explicitly at job time, so nothing needs it in the manifest.

Backlog

• P0-11 → done, with 4 of 5 boxes ticked (the fifth is the 2.0.1 release). Evidence is in-repo and CI was green on Fix the init-time fatal: require Booking_Adapter, and guard the whole manifest #4, which is the standard the provenance banner sets.
• P0-0 → in progress. No boxes ticked: nothing here has been proven green yet.

Risk and rollback

• Blast radius: none at runtime. No shipped file changes; the distributable is byte-identical apart from nothing at all — tests/, bin/ and phpunit-integration.xml are all excluded, asserted above. The new workflow only adds a CI job.
• Rollback: revert the commit; deletes a workflow and a test directory.
• Data migration to reverse? No.

---

Generated by Claude Code