[Sunrisepeak]

Summary

• The requirement moves to openkal-musl ^0.29.0 (released: 0.29.0: a program looked for by the system's conventions, link and linkat, the arrangement stated, openkal 0.25 openkal-musl#88, tag 0.29.0) on both target edges, and with it the OpenKal 0.25 implementations beneath: Linux 0.26, macOS 0.23, Windows 0.21, OpenSBI 0.9. Version 0.20.0; README updated.
• CI: okrun is built with mcpp 2026.11.9.1, the floor openkal-run states. Unpinned, the step received 2026.10.24.1 and was refused. MCPP_VERSION moves to 2026.11.9.1 for the tests.

Tests on the mtest library

tests/ is a package beside the runtime, as the examples are. The runtime's own build compiles libc++ with its own dialect flags, so a program that imports std is a consumer of what that build makes. Its tests are mtest UTest objects above this runtime, openkal-musl and the system's openkal implementation:

• cxx: examples/cxx's observations as one case (exceptions across frames, threads, filesystem names with volumes, links, random_device, thread_local destructors). The example stays the program the cross-builds carry.
• hard_link: std::filesystem::create_hard_link over openkal-musl's link. It checks that the two names are one file (equivalent), that a taken name is refused, and that the file remains when one name is removed. hard_link_count is not asserted: openkal's node information carries no count of names, so it answers 1.
• program_search (openkal-musl K11):
  • On Windows: hostname is found as hostname.exe through a ; PATH (an absent entry first) with PATHEXT set and with the default suffixes; hostname.exe given with its suffix is found as given; a name found nowhere is not started; a suffixless non-program file hostname in an earlier entry does not stop the search.
  • Elsewhere: true is found past an absent entry of a colon PATH.

CI runs the tests on Linux and natively on the Windows and macOS hosts. The mtest pin is in .github/versions.env, which the mtest action reads, so no workflow states it. Each job reports through .github/actions/test-report: the stores mcpp test kept are taken into one store of the job, written to the job's summary and kept as an artifact. The report job writes the workflow run's group (mtest ci report --group). tools/branch-graph.sh also makes the tests' package name the stack's working trees from its root: mcpplibs.os, reached through mtest, states the specification and the implementation by version, and the engine refused a path from inside the graph against those versions.

Test plan

• Existing suite at the functional change: CI run 42714691746 green at a6c82a7 (55fe36b plus the okrun pin).
• Tests on the mtest library: CI run 42719543679 green at 9a8d595.
  • The Windows host passes program_search, hard_link and cxx natively; Linux and macOS pass the same three.
  • The macOS image job's first attempt failed only on the L2 bench gate (index/symbol 1.16 against a limit of 1.15; it passed at a6c82a7), and passed on rerun.
• Review changes (versions.env, test-report action, ci report --group): CI run 42726797128 green at 3ef2471, all 11 checks.