ci: SPIR-V magic 的断言不能只点名 .h —— 规则会选编译器,两个编译器把声明拆得不一样

macOS 与 Windows 上图形示例的**构建都成功了**:规则供给了 `xim:shaderc@2026.3`、两个
着色器阶段都编译了、Vulkan 那一半也链接上了 loader 包。红的是我写的那条断言。

glslang 写出完整的 `const uint32_t ...[] = {...}`(magic 在 `.h` 里),glslc 写出初始
化列表、由规则在外面补声明(magic 在 `.inc` 里)。**一条只点名 `.h` 的断言,是一条
关于某一个编译器的断言** —— 正是这个 job 存在的理由所要抓的那种形状,只不过这次它抓到
的是自己。

顺带一个陷阱:改成 `grep -qs '<pat>' a.h a.inc` 是错的。**GNU grep 在被点名的文件不
存在时返回 2,即使它在前一个文件里匹配到了,也即使加了 `-s`** —— `-s` 压的是消息不是
状态。于是这条判据在「只产出 header」的那条路上永远失败,而失败原因与被测性质无关。
逐个文件测。

两条腿都实测过:glslang 路(只有 .h)通过;把 magic 改掉当场变红。

Author: speak-agent

.agents/docs/2026-09-07-heterogeneous-cross-platform-ecosystem.md

@@ -357,6 +357,23 @@ install/config 形状,而那套形状是按 Linux 写的:
 顺带一条读数:两条腿的中心像素**逐字节相同**(`(124, 70, 62, 255)`),所以 CI 的反向
 腿从「CPU 腿跑起来了」加强成「两条腿报出同一个像素、不同的设备名」。
 
+### 10.4c 图形示例在三个平台上都构建通过,而先红的是判据自己
+
+macOS 与 Windows 上的构建都成功了 —— 规则供给了 `xim:shaderc@2026.3`,两个着色器阶段
+都编译了,Vulkan 那一半也链接上了 loader 包。**红的是我写的那条断言**:
+
+    target/.build-mcpp/out/spirv/triangle_vert.h carries no SPIR-V magic
+
+因为规则会**选**编译器,而两个编译器把声明拆得不一样:glslang 写出完整的
+`const uint32_t ...[] = {...}`(magic 在 `.h` 里),glslc 写出初始化列表、由规则在外面
+补声明(magic 在 `.inc` 里)。**一条只点名 `.h` 的断言,是一条关于某一个编译器的断言**
+—— 正是这个 job 存在的理由所要抓的那种形状,只不过这次它抓到的是自己。
+
+顺带一个可迁移的小陷阱:改成 `grep -qs '<pat>' a.h a.inc` 是错的。**GNU grep 在被
+点名的文件不存在时返回 2,即使它在前一个文件里匹配到了,也即使加了 `-s`** —— `-s` 压的
+是消息不是状态。于是这条判据在「只产出 header」的那条路上永远失败,而失败的原因与被测
+的性质无关。正确写法是逐个文件测。
+
 ### 10.5 一条留下的不一致,以及它什么时候消失
 
 `mcpp:plugins` 0.2.5 里 `xim:shaderc` 在 macOS 与 Windows 上是**精确版本**,而

.github/workflows/ci-linux.yml

@@ -294,9 +294,23 @@ jobs:
           # compiled only the first source would leave the second header absent
           # and everything after this would still pass.
           for f in triangle_vert triangle_frag; do
-            h="target/.build-mcpp/out/spirv/$f.h"
-            test -f "$h" || { echo "missing $h"; exit 1; }
-            grep -q '0x07230203' "$h" || { echo "$h carries no SPIR-V magic"; exit 1; }
+            d="target/.build-mcpp/out/spirv"
+            test -f "$d/$f.h" || { echo "missing $d/$f.h"; exit 1; }
+            # Either file: which of the two carries the words is a property of
+            # the shader compiler the rule chose, not of the shader. See the
+            # cross-platform jobs, where that choice differs.
+            # ONE FILE AT A TIME, because `grep -qs a b` exits 2 when `b`
+            # does not exist -- even on a match in `a`, and even with `-s`,
+            # which suppresses the message and not the status. Written as one
+            # grep over both names, this criterion fails whenever the route
+            # that produces only a header is taken, which is a failure about
+            # the criterion and not about the shader.
+            found=""
+            for g in "$d/$f.h" "$d/$f.inc"; do
+              [ -f "$g" ] && grep -q '0x07230203' "$g" && found=1
+            done
+            [ -n "$found" ] \
+              || { echo "$f carries no SPIR-V magic in either $f.h or $f.inc"; exit 1; }
           done
           icd=$(find "${MCPP_HOME:-$HOME/.mcpp}/registry/data/xpkgs/xim-x-mesa-lavapipe" \
                      "$HOME/.xlings/data/xpkgs/xim-x-mesa-lavapipe" \

.github/workflows/ci-macos.yml

@@ -336,9 +336,28 @@ jobs:
           # depend on step order, which is not a property anybody reads.
           "/tmp/mcpp-fresh" build --toolchain "llvm@${MCPP_LLVM_VER}"
           for f in triangle_vert triangle_frag; do
-            h="target/.build-mcpp/out/spirv/$f.h"
-            test -f "$h" || { echo "missing $h"; exit 1; }
-            grep -q '0x07230203' "$h" || { echo "$h carries no SPIR-V magic"; exit 1; }
+            d="target/.build-mcpp/out/spirv"
+            test -f "$d/$f.h" || { echo "missing $d/$f.h"; exit 1; }
+            # THE MAGIC IS NOT ALWAYS IN THE HEADER, AND THAT IS THE POINT OF
+            # THIS JOB. The rule chooses the shader compiler this platform
+            # publishes -- glslang on Linux, glslc here -- and the two split
+            # the declaration differently: glslang writes a complete `const
+            # uint32_t ...[] = {...}`, glslc an initialiser list the rule
+            # declares around, so the words land in `<stem>.inc`. An assertion
+            # naming only the header is an assertion about ONE compiler, which
+            # is exactly the shape this step exists to catch.
+            # ONE FILE AT A TIME, because `grep -qs a b` exits 2 when `b`
+            # does not exist -- even on a match in `a`, and even with `-s`,
+            # which suppresses the message and not the status. Written as one
+            # grep over both names, this criterion fails whenever the route
+            # that produces only a header is taken, which is a failure about
+            # the criterion and not about the shader.
+            found=""
+            for g in "$d/$f.h" "$d/$f.inc"; do
+              [ -f "$g" ] && grep -q '0x07230203' "$g" && found=1
+            done
+            [ -n "$found" ] \
+              || { echo "$f carries no SPIR-V magic in either $f.h or $f.inc"; exit 1; }
           done
           echo "ok: both shader stages compiled and the Vulkan half linked"
 

.github/workflows/ci-windows.yml

@@ -431,9 +431,28 @@ jobs:
           # depend on step order, which is not a property anybody reads.
           "$MCPP_SELF" build --toolchain "llvm@20.1.7"
           for f in triangle_vert triangle_frag; do
-            h="target/.build-mcpp/out/spirv/$f.h"
-            test -f "$h" || { echo "missing $h"; exit 1; }
-            grep -q '0x07230203' "$h" || { echo "$h carries no SPIR-V magic"; exit 1; }
+            d="target/.build-mcpp/out/spirv"
+            test -f "$d/$f.h" || { echo "missing $d/$f.h"; exit 1; }
+            # THE MAGIC IS NOT ALWAYS IN THE HEADER, AND THAT IS THE POINT OF
+            # THIS JOB. The rule chooses the shader compiler this platform
+            # publishes -- glslang on Linux, glslc here -- and the two split
+            # the declaration differently: glslang writes a complete `const
+            # uint32_t ...[] = {...}`, glslc an initialiser list the rule
+            # declares around, so the words land in `<stem>.inc`. An assertion
+            # naming only the header is an assertion about ONE compiler, which
+            # is exactly the shape this step exists to catch.
+            # ONE FILE AT A TIME, because `grep -qs a b` exits 2 when `b`
+            # does not exist -- even on a match in `a`, and even with `-s`,
+            # which suppresses the message and not the status. Written as one
+            # grep over both names, this criterion fails whenever the route
+            # that produces only a header is taken, which is a failure about
+            # the criterion and not about the shader.
+            found=""
+            for g in "$d/$f.h" "$d/$f.inc"; do
+              [ -f "$g" ] && grep -q '0x07230203' "$g" && found=1
+            done
+            [ -n "$found" ] \
+              || { echo "$f carries no SPIR-V magic in either $f.h or $f.inc"; exit 1; }
           done
           echo "ok: both shader stages compiled and the Vulkan half linked"