fix: use file redirect instead of tee for Bun crash resilience

The previous approach using `tee` failed because when Bun segfaults,
the pipe breaks and tee doesn't flush output to the file. The grep
then finds no summary and reports "crashed before producing results"
even though all tests passed.

Fix: redirect bun output to file directly (`> file 2>&1 || true`),
then `cat` it for CI log visibility. Use portable `awk` instead of
`grep -oP` for summary extraction.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: anandgupta42

.github/workflows/ci.yml

@@ -94,35 +94,36 @@ jobs:
         # Bun 1.3.x has a known segfault during process cleanup after all tests
         # pass (exit code 143/SIGTERM or 134/SIGABRT). We capture test output and
         # check for real failures vs Bun crashes to avoid false CI failures.
+        shell: bash
         run: |
-          set +e
-          bun test --timeout 30000 2>&1 | tee /tmp/test-output.txt
-          TEST_EXIT=$?
-          set -e
-
-          # Extract pass/fail counts from Bun test summary
-          PASS_COUNT=$(grep -E '^\s+\d+ pass' /tmp/test-output.txt | awk '{print $1}' || echo "")
-          FAIL_COUNT=$(grep -E '^\s+\d+ fail' /tmp/test-output.txt | awk '{print $1}' || echo "")
-
-          # If no summary at all, Bun crashed before running tests — real failure
-          if [ -z "$PASS_COUNT" ] && [ -z "$FAIL_COUNT" ]; then
-            echo "::error::Bun crashed before producing test results (exit code $TEST_EXIT)"
-            exit 1
-          fi
+          # Redirect bun output to file, then cat it for CI visibility.
+          # This avoids tee/pipe issues where SIGTERM kills tee before flush.
+          bun test --timeout 30000 > /tmp/test-output.txt 2>&1 || true
+          cat /tmp/test-output.txt
+
+          # Extract pass/fail counts from Bun test summary (e.g., " 5362 pass")
+          PASS_COUNT=$(awk '/^ *[0-9]+ pass$/{print $1}' /tmp/test-output.txt || true)
+          FAIL_COUNT=$(awk '/^ *[0-9]+ fail$/{print $1}' /tmp/test-output.txt || true)
 
-          # Real test failures
-          if [ "$FAIL_COUNT" != "" ] && [ "$FAIL_COUNT" != "0" ]; then
+          echo ""
+          echo "--- Test Summary ---"
+          echo "pass=${PASS_COUNT:-none} fail=${FAIL_COUNT:-none}"
+
+          # Real test failures — always fail CI
+          if [ -n "$FAIL_COUNT" ] && [ "$FAIL_COUNT" != "0" ]; then
             echo "::error::$FAIL_COUNT test(s) failed"
             exit 1
           fi
 
-          echo "Tests passed: $PASS_COUNT pass, $FAIL_COUNT fail"
-
-          # If bun exited non-zero but all tests passed, it's a Bun crash during cleanup
-          if [ "$TEST_EXIT" -ne 0 ]; then
-            echo "::warning::Bun exited with code $TEST_EXIT after all tests passed (known Bun 1.3.x segfault during cleanup — not a test failure)"
+          # Tests passed (we have a pass count and zero/no failures)
+          if [ -n "$PASS_COUNT" ] && [ "$PASS_COUNT" -gt 0 ] 2>/dev/null; then
+            exit 0
           fi
 
+          # No test summary at all — Bun crashed before running tests
+          echo "::error::No test results found in output — Bun may have crashed before running tests"
+          exit 1
+
   # ---------------------------------------------------------------------------
   # Driver E2E tests — only when driver code changes.
   # Uses GitHub Actions services (no Docker-in-Docker).