two things verifying 2026.8.26.2 turned up

[Sunrisepeak]

Follow-up to #512, discovered while verifying it.

examples/06-openkal-cross teaches the short target spellings. It listed three; the fourth — --target aarch64-linux — is precisely the one 2026.8.26.2 made writable. Verified at the artifact:

$ mcpp build --target aarch64-linux
$ file target/aarch64-linux-musl/*/bin/portable-report
  ELF 64-bit LSB executable, ARM aarch64, statically linked

[toolchain] default = "llvm@22.1.8" is removed. openkal-llvm-runtime declares requires = ["mcpp:compiler=llvm"], and mcpp now reads it — so the manifest was restating what the graph already says. Measured with a gcc global default, all four targets:

Resolved llvm@22.1.8 → aarch64-linux-musl → …/xim-x-llvm/22.1.8/bin/clang++
         required by openkal-llvm-runtime@0.1.3
         (`requires = ["mcpp:compiler=llvm"]`), not your gcc@16.1.0 — this project only

and ~/.mcpp/config.toml byte-identical afterwards.

⚠️ The dependency floor had gone stale at 0.1.1, whose compiler-rt builtins do not compile for aarch64 — that is what the aarch64 leg actually died on. Nothing in CI builds this example, so a pin expiring here has nothing that would say so. I nearly recorded this as an mcpp/openkal aarch64 defect and a CI coverage gap; both were wrong. tests/e2e/287 does build aarch64-linux-musl over openkal and passes.

All four targets built locally before and after.

---

And the matrix's compiler axis was following the cache

⚠️ Same commit: the PR's scan (windows-x86_64) was green, and the same job on main was red. That run's restored cache carried an extra gcc@16.1.0, so the scan produced 24 cells where expected.tsv declares 16 for that host — and all eight extras were reported as cells the table does not mention.

What a runner happens to have installed is not what this repository declares, and the criterion has to be the second. scan.sh's compiler axis now comes from expected.tsv's own column via MATRIX_COMPILERS, computed by the workflow from the same column the install step reads — so "install these" and "scan these" cannot disagree.

⭐ Installed versions outside the declaration are named on stderr rather than silently dropped: a measurement that did not run and one that passed are indistinguishable from an exit code.

Verified locally — linux-x86_64 payload mode, 24 cells matched, three undeclared installed versions reported by name.