@biffo/cli 0.176.0 → 0.176.2

package/_skeletons/plugin-template/scripts/verify.sh

@@ -89,6 +89,13 @@ SKIPPED=""
 # break-even at one catch per 336 pushes, against an observed rate of roughly
 # one per 165.
 #
+# The command is plain `pytest -q`, matching CI. `--no-cov` looked like a free
+# speed-up and is a **pytest-cov flag**: repos without that plugin -- e.g.
+# biffo-plugin-ideation, whose CI runs `uv run pytest -q` -- reject it outright
+# with `unrecognized arguments`. That is the gate failing where CI passes, which
+# H5 pre-registered as a condition that refutes it, and it was caught during
+# rollout rather than by review.
+#
 # BIFFO_VERIFY_PYTEST overrides in BOTH directions: 1 forces it in, 0 forces it
 # out. An override that only forces on would leave no way to escape a suite that
 # has quietly grown past the threshold.
@@ -103,14 +110,28 @@ pytest_is_fast() {
   _cache="$_d/.pytest-duration"
   if [ -f "$_cache" ]; then
     _secs=$(cat "$_cache" 2>/dev/null)
+  elif [ -n "$LIST" ]; then
+    # --list must not run a test suite to answer a question about the repo, so
+    # with no cached measurement it has to guess -- and the direction of the
+    # guess is the whole decision.
+    #
+    # Guessing "fast" makes --list CLAIM a check the gate may not run, which is
+    # the fail-open direction and exactly what this tooling exists to eliminate.
+    # Guessing "slow" makes it under-report a check the gate does run: visible,
+    # conservative, and self-correcting, because the first real run writes the
+    # measurement and every --list after that is exact.
+    #
+    # Both directions were tried. Under-reporting is the one that cannot lie
+    # about coverage.
+    _secs=99999
   else
     # First run in a repo: time it once, then decide from then on. A timeout
     # means "too slow", which is the correct verdict rather than a hang.
     _start=$(date +%s)
     if [ "$_d" = "." ]; then
-      timeout "$((PYTEST_BUDGET_SECONDS * 4))" uv run pytest -q --no-cov >/dev/null 2>&1 || true
+      timeout "$((PYTEST_BUDGET_SECONDS * 4))" uv run pytest -q >/dev/null 2>&1 || true
     else
-      timeout "$((PYTEST_BUDGET_SECONDS * 4))" uv run --directory "$_d" pytest -q --no-cov >/dev/null 2>&1 || true
+      timeout "$((PYTEST_BUDGET_SECONDS * 4))" uv run --directory "$_d" pytest -q >/dev/null 2>&1 || true
     fi
     _secs=$(($(date +%s) - _start))
     echo "$_secs" > "$_cache" 2>/dev/null || true
@@ -283,8 +304,8 @@ if [ -n "$PY_DIRS" ]; then
         [ -n "$bandit_paths" ] && ci_has "bandit" && run_check "bandit$suffix" uv run bandit -r $bandit_paths -ll -q
         if [ "$PYTEST" = "0" ]; then
           skip "pytest$suffix" "excluded by BIFFO_VERIFY_PYTEST=0"
-        elif [ -n "$PYTEST" ] || { [ -z "$LIST" ] && pytest_is_fast "."; }; then
-          ci_has "pytest" && run_check "pytest$suffix" uv run pytest -q --no-cov
+        elif [ -n "$PYTEST" ] || pytest_is_fast "."; then
+          ci_has "pytest" && run_check "pytest$suffix" uv run pytest -q
         else
           skip "pytest$suffix" "suite is slower than ${PYTEST_BUDGET_SECONDS}s - CI keeps it"
         fi
@@ -295,8 +316,8 @@ if [ -n "$PY_DIRS" ]; then
         ci_has "bandit" && run_check "bandit$suffix" uv run --directory "$d" bandit -r src -ll -q
         if [ "$PYTEST" = "0" ]; then
           skip "pytest$suffix" "excluded by BIFFO_VERIFY_PYTEST=0"
-        elif [ -n "$PYTEST" ] || { [ -z "$LIST" ] && pytest_is_fast "$d"; }; then
-          ci_has "pytest" && run_check "pytest$suffix" uv run --directory "$d" pytest -q --no-cov
+        elif [ -n "$PYTEST" ] || pytest_is_fast "$d"; then
+          ci_has "pytest" && run_check "pytest$suffix" uv run --directory "$d" pytest -q
         else
           skip "pytest$suffix" "suite is slower than ${PYTEST_BUDGET_SECONDS}s - CI keeps it"
         fi

package/_skeletons/sibling-template/scripts/verify.sh

@@ -89,6 +89,13 @@ SKIPPED=""
 # break-even at one catch per 336 pushes, against an observed rate of roughly
 # one per 165.
 #
+# The command is plain `pytest -q`, matching CI. `--no-cov` looked like a free
+# speed-up and is a **pytest-cov flag**: repos without that plugin -- e.g.
+# biffo-plugin-ideation, whose CI runs `uv run pytest -q` -- reject it outright
+# with `unrecognized arguments`. That is the gate failing where CI passes, which
+# H5 pre-registered as a condition that refutes it, and it was caught during
+# rollout rather than by review.
+#
 # BIFFO_VERIFY_PYTEST overrides in BOTH directions: 1 forces it in, 0 forces it
 # out. An override that only forces on would leave no way to escape a suite that
 # has quietly grown past the threshold.
@@ -103,14 +110,28 @@ pytest_is_fast() {
   _cache="$_d/.pytest-duration"
   if [ -f "$_cache" ]; then
     _secs=$(cat "$_cache" 2>/dev/null)
+  elif [ -n "$LIST" ]; then
+    # --list must not run a test suite to answer a question about the repo, so
+    # with no cached measurement it has to guess -- and the direction of the
+    # guess is the whole decision.
+    #
+    # Guessing "fast" makes --list CLAIM a check the gate may not run, which is
+    # the fail-open direction and exactly what this tooling exists to eliminate.
+    # Guessing "slow" makes it under-report a check the gate does run: visible,
+    # conservative, and self-correcting, because the first real run writes the
+    # measurement and every --list after that is exact.
+    #
+    # Both directions were tried. Under-reporting is the one that cannot lie
+    # about coverage.
+    _secs=99999
   else
     # First run in a repo: time it once, then decide from then on. A timeout
     # means "too slow", which is the correct verdict rather than a hang.
     _start=$(date +%s)
     if [ "$_d" = "." ]; then
-      timeout "$((PYTEST_BUDGET_SECONDS * 4))" uv run pytest -q --no-cov >/dev/null 2>&1 || true
+      timeout "$((PYTEST_BUDGET_SECONDS * 4))" uv run pytest -q >/dev/null 2>&1 || true
     else
-      timeout "$((PYTEST_BUDGET_SECONDS * 4))" uv run --directory "$_d" pytest -q --no-cov >/dev/null 2>&1 || true
+      timeout "$((PYTEST_BUDGET_SECONDS * 4))" uv run --directory "$_d" pytest -q >/dev/null 2>&1 || true
     fi
     _secs=$(($(date +%s) - _start))
     echo "$_secs" > "$_cache" 2>/dev/null || true
@@ -283,8 +304,8 @@ if [ -n "$PY_DIRS" ]; then
         [ -n "$bandit_paths" ] && ci_has "bandit" && run_check "bandit$suffix" uv run bandit -r $bandit_paths -ll -q
         if [ "$PYTEST" = "0" ]; then
           skip "pytest$suffix" "excluded by BIFFO_VERIFY_PYTEST=0"
-        elif [ -n "$PYTEST" ] || { [ -z "$LIST" ] && pytest_is_fast "."; }; then
-          ci_has "pytest" && run_check "pytest$suffix" uv run pytest -q --no-cov
+        elif [ -n "$PYTEST" ] || pytest_is_fast "."; then
+          ci_has "pytest" && run_check "pytest$suffix" uv run pytest -q
         else
           skip "pytest$suffix" "suite is slower than ${PYTEST_BUDGET_SECONDS}s - CI keeps it"
         fi
@@ -295,8 +316,8 @@ if [ -n "$PY_DIRS" ]; then
         ci_has "bandit" && run_check "bandit$suffix" uv run --directory "$d" bandit -r src -ll -q
         if [ "$PYTEST" = "0" ]; then
           skip "pytest$suffix" "excluded by BIFFO_VERIFY_PYTEST=0"
-        elif [ -n "$PYTEST" ] || { [ -z "$LIST" ] && pytest_is_fast "$d"; }; then
-          ci_has "pytest" && run_check "pytest$suffix" uv run --directory "$d" pytest -q --no-cov
+        elif [ -n "$PYTEST" ] || pytest_is_fast "$d"; then
+          ci_has "pytest" && run_check "pytest$suffix" uv run --directory "$d" pytest -q
         else
           skip "pytest$suffix" "suite is slower than ${PYTEST_BUDGET_SECONDS}s - CI keeps it"
         fi

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@biffo/cli",
-  "version": "0.176.0",
+  "version": "0.176.2",
   "description": "Biffo project scaffolding CLI",
   "license": "MIT",
   "type": "module",