ci: run pytest with -s -vv in the test jobs

Per-test lines and live (uncaptured) output: the pxiii_bec job sat
silent at 81 percent for hours, and file-level dots could not say which
test wedged. With -s -vv a hang names its test and streams the last
log lines before it.

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

.gitea/workflows/ci.yml

@@ -72,7 +72,11 @@ jobs:
           BEAMLINE: SIMULATED
         run: |
           source .venv/bin/activate
-          pytest  ./tests/unit
+          # -vv: one line per test, so a hung job shows the exact test it
+          # died in, not just a file of dots. -s: no output capture — prints
+          # and logs stream live instead of vanishing with a wedged worker
+          # (a pxiii_bec job once sat silent at 81% for hours).
+          pytest -s -vv ./tests/unit
 
   test-with-beamline-plugins:
     runs-on: ubuntu-latest
@@ -105,7 +109,9 @@ jobs:
           BEAMLINE: SIMULATED
         run: |
           source .venv/bin/activate
-          pytest ./tests/unit
+          # Same -s -vv rationale as the plain test job: live, per-test
+          # output so a plugin-variant hang is diagnosable from the log.
+          pytest -s -vv ./tests/unit
 
   test-with-coverage:
     runs-on: ubuntu-latest