CI measures with mcpp 2026.10.31.1, the floor openkal-platform states since 0.18.0

Co-authored-by: speak-agent <248744407+speak-agent@users.noreply.github.com>

Author: Sunrisepeak

.github/workflows/openkal-compat.yml

@@ -42,7 +42,7 @@ env:
   # run if this drifts from pins.toml. See the comment beside `mcpp` in
   # pins.toml for why this pin, not just validate.yml's, is gated by the
   # index floor.
-  MCPP_VERSION: "2026.10.27.1"
+  MCPP_VERSION: "2026.10.31.1"
   # CROSS-VALIDATION BEFORE A RELEASE, NOT AFTER IT.
   #
   # Empty in an ordinary run, so this measurement keeps using the RELEASED

.github/workflows/validate.yml

@@ -440,7 +440,10 @@ env:
   # ok-image rows take openkal-platform with no declaration, the
   # tests/examples/openkal-platform member's hosted arrangement -- and
   # packaging along three axes (SPEC-014); mcpp.plugins 0.20.0's floor.
-  MCPP_VERSION: "2026.10.27.1"
+  #
+  # 2026.10.31.1 (mcpp-community/mcpp#869): `features` in the machine output,
+  # and the floor openkal-platform states since 0.18.0 (2026.10.30.1).
+  MCPP_VERSION: "2026.10.31.1"
 
 jobs:
   lint:

.github/workflows/xpkgindex-update.yml

@@ -25,7 +25,7 @@ concurrency:
 
 env:
   PYTHONUTF8: '1'
-  MCPP_VERSION: '2026.10.27.1'
+  MCPP_VERSION: '2026.10.31.1'
   # CROSS-VALIDATION BEFORE A RELEASE: a candidate that needs an mcpp newer
   # than the pin (its package states the floor) is built with mcpp built from
   # this branch of mcpp-community/mcpp, as openkal-compat.yml measures with it.

CHANGELOG.md

@@ -9,6 +9,10 @@
 
 ### Added
 
+- **openkal-platform 0.19.0。** openkal 0.18 的版本组:openkal 0.18.0、openkal-linux 0.19.0、openkal-macos 0.16.0、
+  openkal-windows 0.14.0、openkal-musl 0.23.0、openkal-llvm-runtime 0.16.10、openkal-ld/run/tools 0.1.5。以 Windows
+  启动器打包(bundle-all、self-contained)需要 mcpp 2026.10.31.2。CI 的 mcpp 移到 2026.10.31.1(platform 0.18.0 起声明
+  `mcpp >= 2026.10.30.1`),客户端下限不变。GLOBAL 为 GitHub 标签归档,CN 为 GitCode `mcpp-res` 镜像,sha256 两处一致。
 - **openkal-musl 0.23.0、openkal-llvm-runtime 0.16.10。** openkal-musl 的文件 `mmap`、`munmap`、`msync` 经
   `openkal.map`(偏移按 `KAL_MAP_ALIGNMENT` 向下对齐,区域止于文件末尾);openkal-llvm-runtime 随之移动。测试成员
   `openkal-musl` 观察映射的文件,`openkal` 移到 0.16.10。GLOBAL 为 GitHub 标签归档,CN 为 GitCode `mcpp-res` 镜像,

tests/openkal/pins.toml

@@ -18,6 +18,8 @@ toolchain = "llvm@22.1.8"
 # index requires mcpp >= 2026.9.18.1 but this is mcpp 2026.9.17.3 [E0006]"
 # before a single line of the member's own source is read.
 #
+# 2026-10-30: measurement engine 2026.10.31.1, the workflow's (openkal-platform 0.18.0 and later
+# state mcpp >= 2026.10.30.1). The index client floor is unchanged.
 # 2026-10-28: measurement engine 2026.10.27.1, the workflow's (platforms, SPEC-013).
 # 2026-10-26: measurement engine 2026.10.26.1, the workflow's. 2026-10-24: measurement engine updated to 2026.10.24.1; runtime and
 # toolchain pins below remain unchanged. The index client floor is unchanged.
@@ -140,7 +142,7 @@ toolchain = "llvm@22.1.8"
 # openkal-musl 0.16.0 and openkal-llvm-runtime 0.12.0), because a pin that
 # moves onto an unreachable or divergent asset fails every member at once and
 # reports it as a compatibility result.
-mcpp      = "2026.10.27.1"
+mcpp      = "2026.10.31.1"
 
 # The Windows target is named for the C environment the graph presents there,
 # which is musl's (openkal-musl declares `[c-abi] presents = "posix"`), not