@spardutti/claude-skills 2.28.0 → 2.30.0

package/lib/setup-hook.mjs

@@ -454,6 +454,18 @@ const GAUNTLET_SCRIPT = `#!/usr/bin/env bash
 # Setting either command switches the whole repo to explicit mode — auto-detection
 # is off, and only what you set runs.
 #
+# Per-project runners, for tests that cannot run on the host at all:
+#   <project>/.gauntlet-test        executable; run instead of the detected test
+#                                   command, with $FILES as its arguments
+#   <project>/.gauntlet-typecheck   executable; run instead of the detected
+#                                   typecheck command
+#
+# <project> is any directory holding a package.json or pyproject.toml, so one
+# half of a monorepo can run on the host while the other runs in a container.
+# Unlike GAUNTLET_TEST these do not disable detection anywhere else. Typically a
+# two-line \`docker compose run --rm -T api pytest "$@"\`. Same shape as
+# ship-gate's .mutmut-run.
+#
 # Every run records why it ended in /tmp/claude-gauntlet-<session>.why, so a green
 # run and a skipped one are told apart without re-running the hook.
 
@@ -551,6 +563,26 @@ add_dir_gates() {
   [ -n "$d" ] && [ -n "\${ROOT_TC:-}" ] && have_tc="skip"
   [ -n "$d" ] && [ -n "\${ROOT_TEST:-}" ] && have_test="skip"
 
+  # A project whose tests need a database, a queue, or any other service cannot
+  # run them on the host, and detection here finds the host runner every time.
+  # An executable runner in the project directory says where they DO run —
+  # usually \`docker compose run\` against the app container — and wins over
+  # everything detected below.
+  #
+  # Per project, not per repo: GAUNTLET_TEST switches the WHOLE repo to explicit
+  # mode, so a monorepo needing a container for one stack had to hand-write
+  # commands for all of them. These let one half run on the host and the other
+  # in a container. Same shape as ship-gate's .mutmut-run, deliberately.
+  RUNNER_EXT="($JS_EXT|py)"
+  if [ -z "$have_tc" ] && [ -x "$d\${d:+/}.gauntlet-typecheck" ]; then
+    add_gate typecheck "$pre$RUNNER_EXT\\$" "\${run}./.gauntlet-typecheck"
+    have_tc="skip"
+  fi
+  if [ -z "$have_test" ] && [ -x "$d\${d:+/}.gauntlet-test" ]; then
+    add_gate tests "$pre$RUNNER_EXT\\$" "\${run}./.gauntlet-test \\$FILES"
+    have_test="skip"
+  fi
+
   if [ -f "$d\${d:+/}package.json" ]; then
     pkg="$d\${d:+/}package.json"
     if [ -z "$have_tc" ]; then
@@ -946,6 +978,13 @@ fi
 py_mutmut() {
   d="$1"
   # Returned relative to the PROJECT, because the command runs from inside it.
+  # Tests that need a database, a queue, or any other service cannot run on the
+  # host: mutmut still generates every mutant and reports them all "not
+  # checked", which prints exactly like a clean run. An executable .mutmut-run
+  # in the project runs mutmut wherever those services are — typically
+  # \`docker compose run\` against the app container — and takes precedence over
+  # every host-local option below.
+  if [ -x "$d.mutmut-run" ]; then printf './.mutmut-run\\n'; return; fi
   if [ -x "$d.venv/bin/mutmut" ]; then printf './.venv/bin/mutmut\\n'; return; fi
   if [ -f "$d""uv.lock" ] && command -v uv >/dev/null 2>&1; then printf 'uv run mutmut\\n'; return; fi
   if [ -f "$d""poetry.lock" ] && command -v poetry >/dev/null 2>&1; then printf 'poetry run mutmut\\n'; return; fi
@@ -1121,6 +1160,32 @@ for owner in $OWNERS; do
     NOWF=$(mktemp)
     printf '%s\\n' "$OUT" \\
       | sed -n 's/^[[:space:]]*\\([^[:space:]]*\\): survived$/\\1/p' | sort -u > "$NOWF"
+
+    # When the tests need a service the run cannot reach — a database, a queue
+    # — mutmut still generates every mutant and records it "not checked". No
+    # survivors come out, so the gate printed "nothing survived" and, with no
+    # baseline yet, wrote an EMPTY one and told the user to commit it. That
+    # repo's Python gate could never fail again.
+    #
+    # Counting kills cannot catch it: \`mutmut results\` SKIPS killed mutants
+    # unless --all (mutmut/__main__.py results()), so a perfect suite and a
+    # suite that ran nothing both print nothing. The status string is what
+    # separates them — "not checked" is exit code None in status_by_exit_code,
+    # meaning the mutant was never executed at all.
+    NOTCHECKED=$(printf '%s\\n' "$OUT" | grep -c ': not checked$')
+    if [ "$NOTCHECKED" -gt 0 ]; then
+      echo "  $label mutmut — UNPROVEN: $NOTCHECKED mutant(s) were never run."
+      echo "      They are recorded \\"not checked\\", so the suite proved nothing"
+      echo "      about them. Usually the tests need a service this run cannot"
+      echo "      reach — a database, a queue. Put an executable .mutmut-run in"
+      echo "      \${base}that runs mutmut where those services are, typically"
+      echo "      docker compose run against the app container; the gate uses"
+      echo "      it ahead of every host-local option."
+      [ "$STATUS" = 0 ] && STATUS=2
+      rm -f "$NOWF"
+      continue
+    fi
+
     if [ "$MODE" = baseline ]; then
       cp "$NOWF" "$BL"
       NOTE="  $label mutmut — baseline set: $(wc -l < "$BL") survivor(s) accepted. Commit $BL."

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@spardutti/claude-skills",
-  "version": "2.28.0",
+  "version": "2.30.0",
   "description": "Guardrails for Claude Code — best-practice skills, planning commands, and delivery gates.",
   "type": "module",
   "repository": {