From 30992650b42a04d831bdef34c1b0b79d93b641cc Mon Sep 17 00:00:00 2001 From: David Baker Effendi Date: Fri, 21 Aug 2026 15:50:40 +0200 Subject: [PATCH] Flag that the development page's PHP row predates its audit The page reports PHP as ten shared cases with nine exact for both sides and none exact for the language server alone, which reads as Bifrost satisfying every PHP case in the 24 July run. That cannot describe the corpus as it stands. The PHP ground-truth audit landed on 22 July, two days before that run, and rewrote php-property-access and php-parity-static-property-access to expect sigil-inclusive ranges. Every Bifrost version measured since fails at least one of them: both under v0.10.1, and the static-property case alone under v0.10.5, which corrected the declaration side but not the static usage side. So the row describes a corpus from before the audit, or a shared denominator that dropped those two cases for a reason the page does not give. It is not evidence that Bifrost passed them. This is not hypothetical. Reading that row as current evidence produced a false regression hypothesis that took a source-level comparison across two Bifrost tags to disprove, and a round trip to another repository. A caution on the page is cheaper than the next person repeating it. The numbers are left untouched. The page is historical evidence and the point is that its provenance is unclear, not that the figures should be restated. Co-Authored-By: Claude Opus 5 --- .../results/development-case-comparison.md | 20 +++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/docs/src/content/docs/results/development-case-comparison.md b/docs/src/content/docs/results/development-case-comparison.md index 4b0f0bc..8c9a3ae 100644 --- a/docs/src/content/docs/results/development-case-comparison.md +++ b/docs/src/content/docs/results/development-case-comparison.md @@ -16,6 +16,26 @@ contract result, not an automatic defect verdict. Import, re-export, and export-metadata bindings are optional. They remain visible in reports but do not make an otherwise exact case non-exact. +:::caution[The PHP row predates the PHP ground-truth audit] +This page reports PHP as ten shared cases with nine exact for both sides and +none exact for the language server alone, which reads as Bifrost satisfying +every PHP case. That cannot describe the corpus as it stands. + +The PHP human ground-truth audit landed on 22 July 2026, two days before this +run, and rewrote `php-property-access` and `php-parity-static-property-access` +to expect sigil-inclusive ranges (`$last`, `$sent`). Every Bifrost version +measured since has failed at least one of them: both under v0.10.1, and +`php-parity-static-property-access` alone under v0.10.5, which fixed the +declaration side but not the static usage side. + +So this row reflects a corpus state from before that audit, or a shared +denominator that excluded those two cases for a reason this page does not +record. Either way it is not evidence that Bifrost passed them, and it should +not be used to date a regression — doing exactly that produced a false +regression hypothesis that took a source-level check across two Bifrost tags +to disprove. +::: + ## Shared-case overview | Language | Shared | Both exact | Bifrost only | LSP only | Neither |