Pin the active Bifrost candidate to v0.10.6

adapters/candidates.json

@@ -5,9 +5,9 @@
       "id": "bifrost",
       "runner": "bifrost",
       "name": "Bifrost",
-      "requestedVersion": "v0.10.5",
+      "requestedVersion": "v0.10.6",
       "source": "https://github.com/BrokkAi/bifrost",
-      "revision": "d775e3b4656f418c7025c06577ce707e1556da91",
+      "revision": "6624e883dc8b8268dd4c454c06f8eebea173308e",
       "advertised": true,
       "referenceRunner": "bifrost",
       "runtimeNetworking": "disabled",

containers/reference/v1/manifest.json

@@ -30,9 +30,9 @@
       },
       "analyzer": {
         "name": "bifrost",
-        "requestedVersion": "v0.10.5",
+        "requestedVersion": "v0.10.6",
         "source": "https://github.com/BrokkAi/bifrost",
-        "revision": "d775e3b4656f418c7025c06577ce707e1556da91"
+        "revision": "6624e883dc8b8268dd4c454c06f8eebea173308e"
       },
       "toolchains": {
         "cargo": "cargo 1.96.0",

docs/src/content/docs/results/development-case-comparison.md

@@ -23,10 +23,11 @@ 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.
+to expect sigil-inclusive ranges (`$last`, `$sent`). No Bifrost version
+contemporary with this run satisfied them: both failed under v0.10.1, and
+`php-parity-static-property-access` still failed under v0.10.5, which corrected
+the declaration side but not the static usage side. Both pass from v0.10.6,
+which is later than anything this page could describe.
 
 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

docs/src/content/docs/results/evaluation-real-project-v1.md

@@ -13,8 +13,8 @@ v1 and v2 prospective slices, the separately reviewed legacy core, controls,
 overflow, and remaining development cases. This page remains the detailed
 historical v1 result; it does not become a proxy for the other strata.
 
-The active development candidate is public Bifrost v0.10.5 at immutable commit
-`d775e3b4656f418c7025c06577ce707e1556da91`. No result for that release is
+The active development candidate is public Bifrost v0.10.6 at immutable commit
+`6624e883dc8b8268dd4c454c06f8eebea173308e`. No result for that release is
 published on this page: the tables below remain historical v0.2.0 evidence
 produced with Bifrost v0.8.8, and any upgraded result must be published as a
 subsequent snapshot or release with its own provenance.

scripts/validate-reproduction-contract.sh

@@ -70,8 +70,8 @@ jq -e '
 jq -e '
   [.candidates[] | select(
     .id == "bifrost"
-    and .requestedVersion == "v0.10.5"
-    and .revision == "d775e3b4656f418c7025c06577ce707e1556da91"
+    and .requestedVersion == "v0.10.6"
+    and .revision == "6624e883dc8b8268dd4c454c06f8eebea173308e"
   )] | length == 1
 ' "$registry" >/dev/null
 

tests/test_freeze_shards.py

@@ -57,10 +57,10 @@ def test_v030_registry_uses_public_native_bifrost_identity(self):
         active_bifrost = next(item for item in active["candidates"] if item["id"] == "bifrost")
         frozen_bifrost = next(item for item in frozen["candidates"] if item["id"] == "bifrost")
         self.assertEqual(
-            active_bifrost["requestedVersion"], "v0.10.5"
+            active_bifrost["requestedVersion"], "v0.10.6"
         )
         self.assertEqual(
-            active_bifrost["revision"], "d775e3b4656f418c7025c06577ce707e1556da91"
+            active_bifrost["revision"], "6624e883dc8b8268dd4c454c06f8eebea173308e"
         )
         self.assertEqual(frozen_bifrost["requestedVersion"], "v0.10.2")
         self.assertEqual(