Correct as of the worker's wrangler.jsonc aliasing ./runtime/php-binary.js to
php-binary-85.ts. tests/target-runtime.spec.ts reads that alias out of the sibling checkout
and fails when the two drift, so this constant is checked against the artifact rather than
against itself.
It is a fallback rather than a fact, and the normal case. The only route that reports the
interpreter version is /php, which is diagnostic-gated -- so on a correctly configured
deployment drangler CANNOT read it, and x-cfw-v does not help: that is the header CONTRACT
version, bumped when a header is renamed, and it carries nothing about PHP.
The fallback, used when nothing could be read.
Correct as of the worker's
wrangler.jsoncaliasing./runtime/php-binary.jstophp-binary-85.ts.tests/target-runtime.spec.tsreads that alias out of the sibling checkout and fails when the two drift, so this constant is checked against the artifact rather than against itself.It is a fallback rather than a fact, and the normal case. The only route that reports the interpreter version is
/php, which is diagnostic-gated -- so on a correctly configured deployment drangler CANNOT read it, andx-cfw-vdoes not help: that is the header CONTRACT version, bumped when a header is renamed, and it carries nothing about PHP.