From b38cfa33cf3b522588e7ba99340aa6b4db4da4d6 Mon Sep 17 00:00:00 2001
From: FORGE <78164141+LucaLin233@users.noreply.github.com>
Date: Sun, 25 Oct 2026 05:03:11 +0800
Subject: [PATCH] docs(run.sh): describe TEST_SEGMENT_SET in the segment
 comment

The comment above SEGMENTED_SUITES still said TEST_SEGMENTS sets how many processes share the work, which no longer matches the implementation or the README. State the segment count and point TEST_SEGMENT_SET at the per-job selection. Comments only; no behaviour change.
---
 tests/run.sh | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/tests/run.sh b/tests/run.sh
index a87bd4e..0653a01 100644
--- a/tests/run.sh
+++ b/tests/run.sh
@@ -68,8 +68,9 @@ for test_file in "$ROOT_DIR"/tests/test-*.sh; do
 done
 
 # Suites carrying CI segment guards, with the number of segments their source
-# defines.  TEST_SEGMENTS sets how many processes share the work; with
-# TEST_SEGMENTS=1 every suite runs in one process, all segments in order.
+# defines.  TEST_SEGMENTS is the number of segments a suite is cut into;
+# TEST_SEGMENT_SET picks which of them this job runs.  With TEST_SEGMENTS=1 a
+# suite runs once, all segments in order.
 declare -rA SEGMENTED_SUITES=(
     [test-motd.sh]=13
     [test-cloudflare-tunnel.sh]=12