Commit5fd554ddRecorded4 Sep 2026Repositorysigil-websocket

Wire the native integration harnesses into CI

Message

sigil test globs test-*.sgl, so it finds the 28 unit tests and none of the four native WebSocket integration harnesses. Until now nothing ran them in CI: the pipeline was deps install -> build -> sigil test. A gate that never runs cannot fail, which is indistinguishable from a gate that always passes -- so the regression added earlier in this branch had no protective value on the pipeline at all.

Scoped to wiring: one step appended, nothing else in the pipeline touched (4 insertions, 0 deletions). The glob deliberately matches test-native-websocket-*.sh only and excludes the wasm harness, which has different prerequisites (binaryen, a wasm runtime).

The runner script keeps two outcomes apart that must never be confused:

  • SETUP-FAILED when node is absent, saying in as many words that the tests did not execute and this is not a pass. No estate ci.sgv invokes node today, so whether the CI image has it is UNVERIFIED -- if it does not, this step must say why rather than emit a confusing red.
  • A floor as well as a cap: a glob that matches nothing exits 0 and reads exactly like a clean run, so the script refuses to report success unless it actually ran at least four harnesses.

Verified in four states by running the exact command the CI step runs, because a CI change nobody has seen fail is the thing this branch spent its day proving worthless:

  clean source     -> exit 0, "integration harnesses run: 4, status: 0"
  guard sabotaged  -> exit 1, names the harness AND the reason ("went deaf")
  node removed     -> exit 1, SETUP-FAILED, distinct from a red test
  one harness gone -> exit 1, "matched 3 ... expected at least 4"

Not verified: an actual CI run. That needs a push, which I do not have approval for. What is verified is the step's command in the four states above.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AbXvyDXoTUyqV1tb1fkeFa

Changed
 .kiln/ci.sgv                     |  4 ++++
 scripts/run-integration-tests.sh | 50 ++++++++++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 54 insertions(+)
Diff
.kiln/ci.sgvmodified
@@ -6,4 +6,8 @@
6
(shell name: deps "sigil deps install")
7
(shell name: build "sigil build")
8
(shell name: test "sigil test")
+9
;; `sigil test` globs test-*.sgl and finds only the unit tests, so the
+10
;; native WebSocket integration harnesses ran nowhere until this step
+11
;; existed. The script reports SETUP-FAILED distinctly from a red test.
+12
(shell name: integration "scripts/run-integration-tests.sh")
13
]))
scripts/run-integration-tests.shadded
@@ -0,0 +1,50 @@
+1
#!/usr/bin/env bash
+2
#
+3
# Run the native WebSocket integration harnesses.
+4
#
+5
# These are NOT discovered by `sigil test`, which globs test-*.sgl and so finds
+6
# only the unit tests. Until this script was wired into .kiln/ci.sgv the
+7
# integration suite never ran in CI at all -- and a gate that never runs cannot
+8
# fail, which is indistinguishable from a gate that always passes.
+9
#
+10
# Deliberately globs test-native-websocket-*.sh only. The wasm harness has
+11
# different prerequisites (binaryen, a wasm runtime) and is not wired here.
+12
set -u
+13
+14
cd "$(dirname "$0")/.." || exit 1
+15
+16
# SETUP-FAILED is a distinct outcome from a red test, and must not be reported
+17
# as one. These harnesses drive their servers from Node; if it is absent the
+18
# tests did not fail, they never ran, and saying so is the difference between
+19
# "the code is broken" and "this runner cannot answer the question".
+20
if ! command -v node > /dev/null 2>&1; then
+21
echo "SETUP-FAILED: node is not on PATH, so the integration harnesses cannot run."
+22
echo " These tests did NOT fail -- they did not execute. Do not read this as a pass."
+23
exit 1
+24
fi
+25
echo "node: $(node --version)"
+26
+27
status=0
+28
ran=0
+29
for t in test/integration/test-native-websocket-*.sh; do
+30
[ -f "$t" ] || continue
+31
ran=$((ran + 1))
+32
echo "== $t"
+33
if sh "$t"; then
+34
echo " ok"
+35
else
+36
echo " FAILED: $t"
+37
status=1
+38
fi
+39
done
+40
+41
# A floor as well as a cap: a glob that matches nothing exits 0 and reads
+42
# exactly like a clean run. Four harnesses exist; expect to have run them.
+43
if [ "$ran" -lt 4 ]; then
+44
echo "SETUP-FAILED: matched $ran integration harnesses, expected at least 4."
+45
echo " An empty or partial glob passes for free; refusing to report success."
+46
exit 1
+47
fi
+48
+49
echo "integration harnesses run: $ran, status: $status"
+50
exit "$status"