@@ -896,6 +896,7 @@ S1 与 S2 之间不插入新能力。S3 之后的每个新系统是对架构的
 | "e2e 1069 在 xcode-27 上的失败是本分支引入的回归"（已发布的引擎单独运行通过之后的结论） | 那次对照没有并行条件，不可比。快速路径在运行环境的描述文件比图文件新时拒绝，这是设计内的；描述文件属于家目录，旁边任何一个 mcpp 装包都会改写它。当天索引里新进了多个包，套件并行的脚本首次安装时，1069 的两次运行之间描述文件被改写。本地在两次运行之间改写该文件，得到同样的现象与同样的拒绝原因 | 1069 声明 `# resources: machine`；它断言的性质只在旁边无人改动家目录时成立 |
 | 平台组升到 openkal-windows 0.22.1（本轮所做） | openkal-run 写的是 `^0.21.0`，mcpplibs.os 的上界是 `<0.22.0`；组里一个包只有一个版本，引擎拒绝 | 修正回移到 0.21 线（0.21.1）；openkal-musl 0.29.4 写 `^0.21.1`；0.22.1 留作 0.22 线的头 |
 | PR 上的 e2e 即全量 | PR 运行按改动选择（`E2E_SET=pr`），一次推送可能只选中几个脚本 | 合入前对分支手动触发一次全量运行；它查出了 `mcpp why platform` 的一处回归（合并陈述时丢了平台自己的行与提供者），已修 |
+| "全量运行的覆盖检查失败是 macOS 作业被取消的后果"（本轮所做的判断） | 覆盖检查的输出列出六个脚本没有在任何 runner 上运行过：13、28、31 的探测写死了 runner 已不安装的载荷版本或位置（30 的 A 模式同因被略过），650、653、657 需要 emsdk 载荷而分片没有。此前自行跳过的脚本以 0 退出、记为通过，所以检查看不见；改为 77 之后才显现，而 PR 运行按改动选择，也看不见 | 13、28、30、31 从家目录读取载荷版本（`_toolchain_env.sh`）；650、653、657 与 981、1079 一起在安装 emsdk 的作业里运行；合入前再做一次全量运行 |
 
 ### 15.3 尚未实施
 
 
@@ -379,24 +379,24 @@ jobs:
             exit 1
           fi
           echo "ok: wasm32-emscripten ran through the payload's runner; the decoy node was never run"
-          # #851 (e2e 981) needs the emsdk payload this step has just installed;
-          # the shards have none and skip it, so it runs here, in that home.
-          MCPP="$MCPP_UNDER_TEST" bash tests/e2e/981_a_web_link_has_the_profiles_level_and_the_wasm_exception_model.sh 2>&1 \
-            | tee "$RUNNER_TEMP/981.log"
-          if grep -q '^SKIP' "$RUNNER_TEMP/981.log" || ! grep -qx 'PASS: 981' "$RUNNER_TEMP/981.log"; then
-            echo "::error::e2e 981 did not run to its PASS line over the installed emsdk"
-            exit 1
-          fi
-          # e2e 1079 (the `longjmp` member of `abi`) needs the same payload and a
-          # node of the image; the shards have no emsdk and it skips itself there.
-          # A script that does not apply exits 77, so the status says it ran.
-          MCPP="$MCPP_UNDER_TEST" bash tests/e2e/1079_an_emscripten_rows_longjmp_model_round_trips.sh 2>&1 \
-            | tee "$RUNNER_TEMP/1079.log"
-          rc=${PIPESTATUS[0]}
-          if [ "$rc" -ne 0 ]; then
-            echo "::error::e2e 1079 ended with $rc over the installed emsdk (77: it skipped itself)"
-            exit 1
-          fi
+          # THE WEB-ROW SCRIPTS RUN HERE, OVER THE PAYLOAD THIS STEP HAS JUST
+          # INSTALLED. The shards have no emsdk, and each of these leaves there
+          # with 77 after its `SKIP:` line; until 2026-11-12 that exit was 0, the
+          # shards reported them as passes, and 650, 653 and 657 ran on no
+          # runner. A status other than 0 fails the step, 77 included.
+          for t in 650_wasm_row_names_its_launcher.sh \
+                   653_exceptions_is_the_second_abi_member.sh \
+                   657_a_build_program_under_the_web_row_uses_the_host_compiler.sh \
+                   981_a_web_link_has_the_profiles_level_and_the_wasm_exception_model.sh \
+                   1079_an_emscripten_rows_longjmp_model_round_trips.sh; do
+            echo "::group::e2e $t"
+            MCPP="$MCPP_UNDER_TEST" bash "tests/e2e/$t" && rc=0 || rc=$?
+            echo "::endgroup::"
+            if [ "$rc" -ne 0 ]; then
+              echo "::error::e2e $t ended with $rc over the installed emsdk (77: it skipped itself)"
+              exit 1
+            fi
+          done
 
   coverage:
     # THE DENOMINATOR. Every check above is per host, and no per-host check
 
@@ -118,6 +118,14 @@
   its merged fields in this version's first form).
 - An e2e part whose only script does not apply on the machine is a run that
   reported a case, not an empty run.
+- Six e2e scripts run on a runner again. A script that does not apply on a
+  machine leaves with 77 and is reported as a skip; it left with 0 and was
+  reported as a pass, and the coverage check of the first full run named six
+  scripts no runner had run. The probes of 13, 28 and 31 named a payload
+  release or a store the runners no longer have, and read the release from
+  the home now (`_toolchain_env.sh`), as does Mode A of 30, which was left out
+  for the same reason. 650, 653 and 657 need the emsdk payload and run in the
+  job that installs it, beside 981 and 1079.
 
 ## [2026.11.10.2] - 2026-11-10
 
 
@@ -9,6 +9,7 @@
 # (that would require glibc/sysroot env activation, which is xlings'
 # subos shim concern, not mcpp's toolchain-resolve feature).
 set -e
+source "$(dirname "$0")/_toolchain_env.sh"
 
 TMP=$(mktemp -d)
 trap "rm -rf $TMP" EXIT
@@ -21,11 +22,21 @@ mkdir -p "$SANDBOX_HOME/registry/data/xpkgs"
 # predicate (physical location must resolve inside cfg.registryDir), so the
 # seed is deliberately KEPT: it doubles as a live canary — if the fence ever
 # regresses, the machine's gcc breaks loudly and immediately.
-if [[ -d "$HOME/.xlings/data/xpkgs/xim-x-gcc/16.1.0" ]]; then
-    ln -s "$HOME/.xlings/data/xpkgs/xim-x-gcc" \
-          "$SANDBOX_HOME/registry/data/xpkgs/xim-x-gcc"
+# The payload is the one this machine has: in the home mcpp installs into
+# (`mcpp toolchain install gcc <version>`, which is where CI's runners have it)
+# or in the system xlings. The probe named the system xlings and 16.1.0 alone
+# until 2026-11-12, and the script skipped itself on every runner.
+GCC_SEED=""
+for store in "$(dirname "$MCPP_E2E_GCC_ROOT")" "$HOME/.xlings/data/xpkgs/xim-x-gcc"; do
+    if [[ -d "$store/$GCC_VERSION" ]]; then
+        GCC_SEED="$store"
+        break
+    fi
+done
+if [[ -n "$GCC_SEED" ]]; then
+    ln -s "$GCC_SEED" "$SANDBOX_HOME/registry/data/xpkgs/xim-x-gcc"
 else
-    echo "SKIP: system xlings has no gcc 16.1.0"
+    echo "SKIP: neither mcpp's home nor the system xlings has gcc $GCC_VERSION"
     echo "OK"
     exit 77
 fi
@@ -36,7 +47,7 @@ cd "$TMP"
 "$MCPP" new myapp > /dev/null
 cd myapp
 
-cat > mcpp.toml <<'EOF'
+cat > mcpp.toml <<EOF
 [package]
 name        = "myapp"
 version     = "0.1.0"
@@ -45,7 +56,7 @@ standard   = "c++23"
 modules    = true
 import_std = true
 [toolchain]
-linux = "gcc@16.1.0"
+linux = "gcc@${GCC_VERSION}"
 [modules]
 sources = ["src/**/*.cppm", "src/**/*.cpp"]
 [targets.myapp]
@@ -66,9 +77,9 @@ echo "$out" | grep -q 'toolchain'  || { echo "missing toolchain: $out"; exit 1;
 #    render as `@mcpp/...` — so we match the shortened form
 #    rather than the absolute one. The trailing path components are
 #    what actually prove the toolchain came from mcpp's sandbox.
-echo "$out" | grep -q 'Resolved.*gcc@16.1.0' || {
-    echo "missing Resolved gcc@16.1.0: $out"; exit 1; }
-echo "$out" | grep -q '@mcpp/registry/data/xpkgs/xim-x-gcc/16.1.0/bin/g++' || {
+echo "$out" | grep -q "Resolved.*gcc@${GCC_VERSION}" || {
+    echo "missing Resolved gcc@${GCC_VERSION}: $out"; exit 1; }
+echo "$out" | grep -q "@mcpp/registry/data/xpkgs/xim-x-gcc/${GCC_VERSION}/bin/g++" || {
     echo "Resolved path doesn't reference the mcpp sandbox xpkg: $out"; exit 1; }
 
 echo "OK"
@@ -9,14 +9,13 @@
 # it in this test (would be a 200 MB download per CI run).
 set -e
 
-# musl-gcc lives in the workspace toolchain (.xlings.json) once
-# `xlings install -y` is run. CI does this; locally the developer has it
-# from the `.xlings.json` workspace install too.
-if ! command -v x86_64-linux-musl-g++ >/dev/null 2>&1 \
-   && ! [ -x "$HOME/.xlings/data/xpkgs/xim-x-musl-gcc/15.1.0/bin/x86_64-linux-musl-g++" ] \
-   && ! [ -x "$HOME/.mcpp/registry/data/xpkgs/xim-x-musl-gcc/15.1.0/bin/x86_64-linux-musl-g++" ]
-then
-    echo "SKIP: no musl-gcc 15.1.0 available — not testing --target=*-linux-musl"
+# The musl toolchain is the one this home has (`mcpp toolchain install gcc
+# <version>-musl`; CI's shards install it), whichever release that is. The probe
+# named 15.1.0 until 2026-11-12, the runners installed a later one, and the
+# script skipped itself on every runner.
+source "$(dirname "$0")/_toolchain_env.sh"
+if ! [ -x "$MUSL_GCC_ROOT/bin/x86_64-linux-musl-g++" ]; then
+    echo "SKIP: no musl-gcc payload in this home: not testing --target=*-linux-musl"
     echo "OK"
     exit 77
 fi
@@ -47,14 +46,14 @@ cat >> mcpp.toml <<EOF
 linux = "gcc@${GNU_GCC_VER}"
 
 [target.x86_64-linux-musl]
-toolchain = "gcc@15.1.0-musl"
+toolchain = "gcc@${MUSL_GCC_VERSION}-musl"
 linkage   = "static"
 EOF
 else
-cat >> mcpp.toml <<'EOF'
+cat >> mcpp.toml <<EOF
 
 [target.x86_64-linux-musl]
-toolchain = "gcc@15.1.0-musl"
+toolchain = "gcc@${MUSL_GCC_VERSION}-musl"
 linkage   = "static"
 EOF
 fi
 
@@ -5,13 +5,16 @@
 # Verifies the contract of each mode by extracting the produced tarball
 # and inspecting the resulting binary + (for non-static) bundled libs.
 #
-# Skipped when musl-gcc isn't installed (Mode A needs it). The default
-# Mode C path runs unconditionally.
+# Mode A needs a musl-gcc payload and is left out where the home has none; the
+# payload is whichever release the home has (_toolchain_env.sh). Its probe named
+# 15.1.0 until 2026-11-12, the runners installed a later one, and Mode A ran on
+# no runner. The default Mode C path runs unconditionally.
 set -e
 
 TMP=$(mktemp -d)
 trap "rm -rf $TMP" EXIT
 export MCPP_HOME=$HOME/.mcpp
+source "$(dirname "$0")/_toolchain_env.sh"
 
 cd "$TMP"
 "$MCPP" new myapp > /dev/null
@@ -71,7 +74,7 @@ grep -q 'Hello' "$TMP/c-name.log" || {
     cat "$TMP/c-name.log"; echo "Mode C: top-level entry output missing"; exit 1; }
 
 # ─── Mode A (static, musl) ─────────────────────────────────────────────
-musl_gcc="$HOME/.mcpp/registry/data/xpkgs/xim-x-musl-gcc/15.1.0/bin/x86_64-linux-musl-g++"
+musl_gcc="$MUSL_GCC_ROOT/bin/x86_64-linux-musl-g++"
 if [[ -x "$musl_gcc" ]]; then
     "$MCPP" pack --mode static > "$TMP/pack-a.log" 2>&1 || {
         cat "$TMP/pack-a.log"; echo "Mode A pack failed"; exit 1; }
 
@@ -14,7 +14,11 @@ trap "rm -rf $TMP" EXIT
 export MCPP_HOME="$TMP/mcpp-home"
 MCPP_INHERIT_CONFIG=0 MCPP_INHERIT_SUBOS=0 source "$(dirname "$0")/_inherit_toolchain.sh"
 
-MUSL_PAYLOAD="$MCPP_HOME/registry/data/xpkgs/xim-x-musl-gcc/15.1.0/bin/x86_64-linux-musl-g++"
+# The musl payload is the one linked from the developer's home, whichever
+# release that is. The probe named 15.1.0 until 2026-11-12, the runners
+# installed a later one, and the script skipped itself on every runner.
+source "$(dirname "$0")/_toolchain_env.sh"
+MUSL_PAYLOAD="$MUSL_GCC_ROOT/bin/x86_64-linux-musl-g++"
 if [[ ! -x "$MUSL_PAYLOAD" ]]; then
     echo "SKIP: no reusable musl-gcc xpkg payload"
     echo "OK"