By 17 July 2026, phpr's WordPress gate covers ten selected core groups: option, media, post, user, query, REST API, taxonomy, comment, XML-RPC and multisite. Each group is compared by test name against a fresh PHP-oracle baseline.
What parity means here
Parity does not always mean an empty error count. The REST API group contains one oEmbed error that is also present in the current upstream WordPress trunk under the reference interpreter; taxonomy carries the same warning on both runtimes. The requirement is the same named outcomes as the oracle.
| option · media | 413 · 762 tests |
| post · user · query | 906 · 1,341 · 1,889 tests |
| REST API | 3,514 tests · 1 shared upstream error |
| taxonomy · comment · XML-RPC · multisite | 878 · 582 · 316 · 32 tests |
The runtime surface expanded with the workload
The WordPress sessions added a real phpr -S server SAPI, native MySQLi over the Rust mysql crate, GD through the system libgd, EXIF, native fileinfo, HTML parsing and serialization, SAX-style XML, broader mbstring behavior, DNS reverse lookup, DOM canonicalization and many engine-level semantic fixes.
The same gate still keeps Symfony HttpKernel at 1,665 tests, 0 errors and 0 failures, Doctrine ORM at 3 errors / 13 failures, and the Rust test suite green.
Coverage numbers and development status
At the time of this milestone, the latest complete global measurement was dated 14 July 2026: 2,493 passing Zend tests, 522 / 654 core functions and 785 / 2,143 internal functions. Those figures are retained here as the historical snapshot rather than silently replacing them with later results.
Historical follow-up
This grouped milestone was subsequently surpassed: both complete WordPress suites reached effective oracle parity, global coverage rose to 1,017 internal functions, and the Axum worker-server phase began. See the 31 July full-suite and Axum update.