[EPIC][node] Publish Node.js adapter package for jongodb

[midagedev]

Goal

Publish a Node.js adapter package that makes jongodb usable from Node/Jest/Vitest integration tests without Docker or external MongoDB processes.

Scope

• npm package that starts/stops a jongodb server process and exposes a MongoDB URI
• deterministic lifecycle API for test runners
• minimal compatibility smoke tests with official Node MongoDB driver and Mongoose
• release pipeline for npm publication

Non-Goals (this epic)

• re-implementing MongoDB semantics in Node
• replacing JVM core engine with Node runtime
• broad framework integrations beyond initial Jest/Vitest hooks

Success Criteria

• package installable from npm and runnable on macOS/Linux CI
• integration tests can call start() and obtain usable mongodb://... URI
• smoke suites pass for mongodb driver and mongoose transaction baseline
• CI publishes prerelease/canary package from tags or manual workflow
• README includes setup, API, limitations, and troubleshooting

Parallel Orchestration Contract

• each child issue is developed on a separate branch and PR
• each PR must include at least one review comment and one follow-up patch before merge
• avoid file overlap across child issues except README.md (merge last)

Child Tracks

• [node][scaffold] Create @jongodb/memory-server package skeleton #107 scaffold/package
• [node][runtime] Implement start/stop process manager for jongodb #108 runtime process manager
• [node][testkit] Add Jest/Vitest integration helpers #109 Jest/Vitest integration API
• [node][compat] Add mongodb-driver and mongoose smoke suites #110 compatibility smoke tests
• [node][release] Add npm publish pipeline and release policy #111 npm publish workflow/docs

[midagedev]

Orchestration started (2026-02-24 UTC).\n\nWave 1 (parallel):\n- #107 package scaffold\n- #111 npm release workflow draft\n\nWave 2 (after #107):\n- #108 runtime process manager\n\nWave 3 (parallel after #108):\n- #109 Jest/Vitest helpers\n- #110 compatibility smoke suites\n\nMerge policy:\n- one issue -> one PR\n- each PR requires review comment + follow-up patch before merge\n- avoid overlapping files across active PRs

[midagedev]

Wave 1 active:\n- #107 -> PR #112\n- #111 -> PR #113 (depends on #107)\n\nNext wave starts after #107 merge: #108 runtime implementation.

[midagedev]

Wave 1 complete: #107 and #111 merged.\nWave 2 started: #108 runtime process manager implementation.