debug: run ladybug file ALONE under gdb (isolation diagnostic)

Tests whether the kuzu SIGSEGV reproduces with just tests/test_ladybug_queries.py on real x86 (no accumulated full-suite state). Result decides: accumulated-state trigger (→ process-isolation fix) vs kuzu-internal bug (→ upstream/upgrade).

Co-Authored-By: Claude <noreply@anthropic.com>

Author: HumanBean17

.github/workflows/debug-segfault.yml

@@ -33,7 +33,7 @@ jobs:
         run: |
           python -m pip install --upgrade pip
           pip install -e ".[dev]"
-      - name: Run suite under gdb (capture kuzu SIGSEGV backtrace)
+      - name: Run ladybug file ALONE under gdb (isolation test)
         continue-on-error: true
         env:
           JAVA_CODEBASE_RAG_RUN_HEAVY: "0"
@@ -48,7 +48,7 @@ jobs:
             -ex "run" \
             -ex "echo \n========== GDB: ALL THREADS BACKTRACE ==========\n" \
             -ex "thread apply all bt" \
-            --args python -m pytest tests -v 2>&1 | tee gdb-output.log
+            --args python -m pytest tests/test_ladybug_queries.py -v 2>&1 | tee gdb-output.log
           echo "gdb finished (inferior exit ${PIPESTATUS[0]}; 139 = SIGSEGV expected)"
       - name: Show crash location
         if: always()