claudeup 6.5.1 → 6.7.1

package/src/__tests__/shell-script-callers.test.ts

@@ -66,18 +66,18 @@ describe("only the toolchain bootstrap goes through a shell", () => {
 		expect(await callersOf(/\brunShellScript\(/)).toEqual(ALLOWED);
 	});
 
-	test("nothing spawns with `shell: true` outside utils/run.ts", async () => {
+	test("nothing spawns with a shell outside utils/run.ts", async () => {
 		// Catches someone reaching for `spawn`/`exec` directly rather than
 		// through the seam — a second shell path that never names
 		// `runShellScript`.
 		//
-		// Scope, stated honestly: this checks `shell: true` only. Several
-		// version-DETECTION helpers in CliToolsScreen still pass
-		// `shell: "/bin/bash"` to run pipelines like `which -a x 2>/dev/null`.
-		// Those interpolate a catalogue `name`, not an installer command, and
-		// were out of scope here — so this assertion would be false if it
-		// claimed no shell exists anywhere.
-		expect(await callersOf(/shell:\s*true/)).toEqual([]);
+		// Both spellings: `shell: true` and a named shell (`shell: "/bin/bash"`).
+		// The CLI Tools screen used the second for its version probe (`which -a`
+		// pipelines, a string-form `exec` of each check command); that probe now
+		// lives in services/tool-probe.ts and runs argv only. `shell: false` and
+		// the alias writer's `shell: ShellKind` values are not spawn options and
+		// do not match.
+		expect(await callersOf(/shell:\s*(true|["'`])/)).toEqual([]);
 	});
 
 	test("the scan can actually fail", async () => {