[DavidBakerEffendi]

Implements BrokkAi/bifrost-dev#3130 option B1. The owner decided on 2026-10-29 to land it into the v0.9.2 refresh. Tracking issue for the owed rerun: #297.

What changed

• New adapter file: adapters/bifrost/dependency-evidence/scala/pom.xml, declaring org.scala-lang:scala-library:2.13.16. The Bifrost Scala kernel copies it into every case workspace as pom.xml, so Bifrost activates the Scala standard-library model from exact local evidence. Only the Scala kernel run materializes it (bifrost_dependency_evidence_for).
• Configuration hash: the pom is hashed into the run's configuration_hash, through both the run loop and bifrost_policy_paths.
• Version scope: the pom.xml is part of the configuration from the v0.9.2 Bifrost pin (bifrost 0.14.0) on. A report from an earlier pin hashes without it, as CodeQL's version-scoped closures do, so the committed bifrost 0.11.4 Scala report and the released tag still validate. Re-run the v0.9.2 Bifrost Scala kernel with scala-library dependency evidence #297 tracks the owed v0.9.2 Scala group rerun.
• docs/scala-kernel.md: documents the evidence and the host prerequisite. scala-library-2.13.16.jar and -sources.jar must be in ~/.m2; the runner never downloads them.
• docs/v0.9.2-release-contract.md: amendment. One group's configuration changes and that group reruns under a fresh attempt namespace. Earlier Scala attempts stay retained but unpublished. No case, fixture, policy or other analyzer changes.

Why

Bifrost activates a library model only from build evidence, and a case workspace containing only the .scala fixture yields none. The Scala map-iteration pair, for example, was analyzed against no scala.collection.mutable.Map model at all.

Validation

• cargo test: 308/308, including the new scala_kernel_materializes_and_hashes_its_dependency_evidence.
• cargo run -- validate, cargo run -- validate-reports (92 reports, at the first commit), and cargo fmt --check all pass.
• All 70 Scala fixture files compile in isolation, offline, with Scala 2.13.18. The 2.13.16 compiler is not cached on this host, so the docs state 2.13.18.
• I ran a Bifrost dev build carrying bifrost-dev#8010 and #8030 against the map-iteration pair, with the pom and the real 2.13.16 jars in a scratch ~/.m2. The scala-library pack activates, and the blocker moves from unsupported (assignments) to unsupported (deferred_execution). That is the comprehension's callback execution, which stays open in bifrost-dev#4295.

The version-scope fix (second commit) was validated by cargo build only. Restoring the evidence to rerun validate-reports and the tests locally needs about 6 GB, and this host is low on disk, so CI runs them.

Not done here

The Scala kernel group has not been rerun inside the v0.9.2 execution framework. That needs the pinned Bifrost release and the refresh's ≥125 GiB disk precondition; this host has 99 GiB free. It is tracked by #297.

🤖 Generated with Claude Code