fix(ci): run nested test dirs in CI (#340) (#355)

CI ran `node --test 'test/unit/*.test.js'` (top-level glob only) while the
canonical `npm test` runs both `test/unit/*.test.js` AND
`test/unit/**/*.test.js`. Six nested files in test/unit/runners/ and
test/unit/tools/ (runner clients, external-runner-detect, find/scrollintoview
orchestration) — 22 tests — were never executed in CI, so a regression in any
of them could reach main undetected.

Align the CI unit + integration globs with `npm test`. Verified locally:
top-level-only glob = 2341 tests, aligned glob = 2363 tests, all passing.
The integration glob gets the same nested coverage preemptively (no nested
integration files exist yet).

Closes #340

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

Author: Lykhoyda

.github/workflows/ci.yml

@@ -38,11 +38,11 @@ jobs:
         working-directory: scripts/cdp-bridge
 
       - name: Unit tests
-        run: node --test 'test/unit/*.test.js'
+        run: node --test 'test/unit/*.test.js' 'test/unit/**/*.test.js'
         working-directory: scripts/cdp-bridge
 
       - name: Integration tests
-        run: node --test 'test/integration/*.test.js'
+        run: node --test 'test/integration/*.test.js' 'test/integration/**/*.test.js'
         working-directory: scripts/cdp-bridge
 
       # Runs at repo root (no working-directory) — guards the changeset CI gate.