Fullbleed for Node.js 0.1.3

Render promises now wait for their worker to exit on success, render failure, timeout, and cancellation. Serial await renderPdf() calls no longer overlap worker lifetimes. This also fixes cleanup when an abort fires synchronously during worker construction. Fullbleed's underlying engine remains 2.5.6.

npm install --save-exact fullbleed@0.1.3

Each caller can still render independently. Bound server concurrency according to available memory. A deadline or abort starts worker termination; promise settlement includes the time needed to stop that worker.

Verification retained with this release:

• All 20 render tests pass, including seven real-worker lifecycle regressions. Six of those seven fail against the old wrapper.
• The same packed tarball passes isolated installation checks across Node 22, 24, and 26 on Linux, Windows, and macOS, including ESM, CommonJS, cold-timeout recovery, and worker shutdown before completion.
• Seven native/WebAssembly fixtures retain matching PDF and preview bytes. An independent PDF reader verifies the installed smoke document's text.
• Windows and Linux lifecycle probes show zero live workers when calls settle and a serial peak of one worker, with the fixture PDF unchanged from 0.1.2.

The separate intermittent Linux SIGSEGV investigation in #7 remains open. This patch establishes worker cleanup behavior; it does not establish the crash's cause or resolution.

See release-verification.json and verification-evidence.zip for the tested versions, hashes, and retained output. These checks are scoped to their fixtures and do not constitute PDF standards certification.