FN-7371: clarify CI mode regression guard

Clarifies the test-infrastructure regression guard for CI mode selection.\n\n- Update the FNXC rationale for the CI=true --print-mode subprocess test.\n- Document that full-suite mode remains an explicit opt-in via --full or FUSION_TEST_FULL.\n\nFiles changed:\n scripts/__tests__/test-changed.test.mjs | 4 ++--\n 1 file changed, 2 insertions(+), 2 deletions(-)

Fusion-Task-Id: FN-7371

Fusion-Task-Lineage: b7482ef1-4db7-4003-85f7-3466470d3dff

Co-authored-by: Fusion (runfusion.ai) <noreply@runfusion.ai>
This commit is contained in:
gsxdsm
2026-07-01 10:04:55 -07:00
parent 6d1507aa8f
commit 627c5fb0bd

View File

@@ -1586,8 +1586,8 @@ const packageHashSnippet = (pkgName) => `(mod) => {
}`;
/*
FNXC:TestInfrastructure 2026-06-27-03:46:
CI no longer routes through scripts/test-changed.mjs for the merge gate, so CI=true must not force mode=full. Keep paired full-trigger assertions here so this regression guard proves the --print-mode harness can still observe legitimate full-suite opt-ins.
FNXC:TestInfrastructure 2026-07-01-00:00:
CI no longer routes through scripts/test-changed.mjs as an implicit full-suite trigger, so CI=true must not force mode=full. Keep paired full-trigger assertions here so this --print-mode subprocess guard proves full-suite mode remains explicit opt-in only.
*/
test("integration: CI=true does not force the full suite (only --full / FUSION_TEST_FULL do)", () => {
const dir = mkdtempSync(path.join(tmpdir(), "tc-print-mode-"));