test(nodejs): use in-memory SQLite databases in e2e tests

[rekmarks]

• Switch from file-based SQLite databases to :memory: databases in e2e tests
• Prevents test pollution from persisted database files between test runs
• Affects bip39-identity-recovery.test.ts and remote-comms.test.ts
  • I observed failures in the BIP-39 tests on repeated local runs, probably due to db file reuse.

---

Note

Low Risk
Low risk: changes are confined to NodeJS e2e test setup/fixtures and only affect how test databases are created, with no production logic impact. Main risk is subtle differences in SQLite :memory: lifecycle causing unexpected test behavior if any test relied on persistence across connections.

Overview
E2E test isolation improvement: updates NodeJS e2e tests to create SQLite databases with dbFilename: ':memory:' instead of writing per-test .db files.

This applies to the BIP39 identity recovery and remote comms suites, reducing cross-run pollution/flakiness by ensuring each kernel/test uses ephemeral storage.

^{Written by Cursor Bugbot for commit 539e189. This will update automatically on new commits. Configure here.}

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	88.41% 🟰 ±0%	5883 / 6654
🔵	Statements	88.3% 🟰 ±0%	5980 / 6772
🔵	Functions	87.12% 🟰 ±0%	1529 / 1755
🔵	Branches	84.59% 🟰 ±0%	2130 / 2518

File Coverage

No changed files found.

Generated in workflow #3488 for commit 539e189 by the Vitest Coverage Report Action

[FUDCo]

Better isolation is good.