ci: pin 2026.8.24.4, which is the release that survives the bare-metal step

把 pin 移到 24.3 让裸机那一步第一次真正到达 OpenSBI,而**它之后的那一步**
随即失败:`mcpp run --target X` 一直把 X 的构建记在宿主的缓存槽里,
于是下一条裸的 `mcpp run` 直接 exec 了交叉产物。

那个缺陷早于本包,只因为一个自称测裸机的步骤开始真的测裸机才现形。
mcpp-community/mcpp#498 修复,随 2026.8.24.4 发布。

Author: Sunrisepeak

.github/workflows/ci.yml

@@ -17,7 +17,7 @@ on:
   workflow_dispatch:
 
 env:
-  MCPP_VERSION: 2026.8.24.3
+  MCPP_VERSION: 2026.8.24.4
   XLINGS_VERSION: v2026.8.17.2
   XLINGS_NON_INTERACTIVE: '1'
 

mcpp.toml

@@ -47,8 +47,13 @@ provides = [
 # AT 2026.8.24.3. That tool predates the layer vocabulary and ignores the whole
 # array, so it neither refuses the declaration nor reads it. A CI pinned there
 # would report green over a manifest whose central claim was never examined,
-# which is why this package's `MCPP_VERSION` moves to 2026.8.24.3 in the same
-# change that adds the line.
+# which is why this package's `MCPP_VERSION` moves in the same change that adds
+# the line. It moves to 2026.8.24.4 rather than .3: raising the pin made the
+# bare-metal step below reach OpenSBI for the first time, and the step AFTER it
+# then failed — `mcpp run --target X` had been recording X's build under the
+# host's cache key, so the next bare `mcpp run` exec'd the cross artefact. The
+# defect predates this package and was found only because a step that claimed to
+# test bare metal started doing so. Fixed in mcpp-community/mcpp#498.
 #
 # The window that REFUSES is 2026.8.24.1 alone — between the release that began
 # validating the `mcpp:` prefix and the one that learned this layer. Publishing