[.github/workflows/ci.yml,sdk/nodejs/package.json] fix CI: macOS PyO3 linker + Windows node test glob

First CI run on this PR surfaced two environment-specific
issues that didn't repro on my macOS dev box:

1. `rust (macos-latest)` — `cargo build --workspace --all-targets`
   failed linking the test binary for `sqlrite-python` +
   `sqlrite-nodejs`. Those are PyO3 / napi-rs extension-module
   cdylibs; `extension-module` on PyO3 tells rustc not to link
   libpython, and napi-rs does the same for the Node symbols.
   On macOS the auto-generated `cargo test` binary for their
   rlib targets then fails at link time with unresolved Python
   symbols (`pyo3::err::panic_after_error` et al).

   Fix: exclude both crates from the rust-build-and-test + rust-
   lint jobs. Their test coverage lives in the per-SDK jobs
   (python-sdk + nodejs-sdk), which exercise them through
   maturin / napi-rs — the native tooling knows how to handle
   the extension-module link. Added an explanatory comment at
   the exclude block so the next person doesn't accidentally
   re-include them.

2. `nodejs-sdk (windows-latest)` — `npm test` failed with
   "Could not find 'D:\…\sdk\nodejs\test\*.mjs'". Git Bash on
   Windows doesn't glob-expand `*.mjs` the way bash on
   Linux/macOS does; the literal string is passed through to
   node's `--test` runner, which then can't find a file named
   `*.mjs`.

   Fix: hardcode the one test file path in `scripts.test`:
   `node --test test/test.mjs`. Works identically on all three
   OSes. If/when we add a second test file, we'll switch to a
   glob-expansion helper (maybe `find test -name '*.mjs' -exec
   node --test {} +`) or native Node.js directory discovery.

Verified locally with the corrected commands:

- `cargo build --workspace --exclude sqlrite-desktop --exclude
  sqlrite-python --exclude sqlrite-nodejs --all-targets` ✓
- `cargo test` with same exclusions ✓ (183 pass)
- `cargo clippy` with same exclusions ✓
- `cargo doc` with same exclusions ✓
- `cd sdk/nodejs && npm ci && npm run build && npm test` ✓
  (11 pass)

The other two Rust SDKs (ffi + wasm) still get built +
tested via their own workspace memberships — only extension-
module crates need the exclusion. Desktop stays excluded for
the existing frontend-build reason (no change there).

No functional code changes — CI config + one package.json
script tweak.

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

Author: joaoh82

.github/workflows/ci.yml

@@ -71,11 +71,33 @@ jobs:
           # doesn't steal macOS's target dir and vice versa.
           shared-key: rust-build-and-test
 
-      - name: cargo build --workspace --exclude sqlrite-desktop
-        run: cargo build --workspace --exclude sqlrite-desktop --all-targets
+      # Exclusions explained:
+      #
+      # - `sqlrite-desktop` needs the Svelte frontend built first
+      #   (handled in the `desktop-build` job).
+      #
+      # - `sqlrite-python` + `sqlrite-nodejs` are PyO3/napi-rs
+      #   extension-module cdylibs. Their `extension-module` feature
+      #   tells the Rust toolchain not to link libpython / libnode at
+      #   compile time, so `--all-targets` fails on macOS when it
+      #   tries to build the auto-generated test binary for their
+      #   rlib targets (unresolved Python/Node symbols). The per-SDK
+      #   `python-sdk` + `nodejs-sdk` jobs below exercise these
+      #   crates through their native tooling (maturin / napi-rs).
+      - name: cargo build
+        run: |
+          cargo build --workspace \
+            --exclude sqlrite-desktop \
+            --exclude sqlrite-python \
+            --exclude sqlrite-nodejs \
+            --all-targets
 
-      - name: cargo test --workspace --exclude sqlrite-desktop
-        run: cargo test --workspace --exclude sqlrite-desktop
+      - name: cargo test
+        run: |
+          cargo test --workspace \
+            --exclude sqlrite-desktop \
+            --exclude sqlrite-python \
+            --exclude sqlrite-nodejs
 
   # ---------------------------------------------------------------------------
   # Rust: lint — fmt + clippy + doc. One cell (ubuntu) because these
@@ -103,12 +125,25 @@ jobs:
         # No `-D warnings` for now — see the top-level env comment.
         # Deny-by-default lints (the ones that surface real bugs,
         # e.g. `approx_constant`) still fail without the flag.
-        run: cargo clippy --workspace --exclude sqlrite-desktop --all-targets
+        # Exclude the extension-module SDK cdylibs for the same
+        # reason as `rust-build-and-test` — their test binaries
+        # can't link standalone.
+        run: |
+          cargo clippy --workspace \
+            --exclude sqlrite-desktop \
+            --exclude sqlrite-python \
+            --exclude sqlrite-nodejs \
+            --all-targets
 
       - name: cargo doc
         # `--no-deps` skips deps docs (they build on docs.rs, not here).
         # Not warnings-as-errors yet — same rationale as clippy above.
-        run: cargo doc --workspace --exclude sqlrite-desktop --no-deps
+        run: |
+          cargo doc --workspace \
+            --exclude sqlrite-desktop \
+            --exclude sqlrite-python \
+            --exclude sqlrite-nodejs \
+            --no-deps
 
   # ---------------------------------------------------------------------------
   # Python SDK: build the PyO3 extension, install into a venv, run pytest.

sdk/nodejs/package.json

@@ -32,7 +32,7 @@
   "scripts": {
     "build": "napi build --platform --release",
     "build:debug": "napi build --platform",
-    "test": "node --test test/*.mjs"
+    "test": "node --test test/test.mjs"
   },
   "devDependencies": {
     "@napi-rs/cli": "^2.18.4"