fix(jobs): unref parentPort after job completes to prevent Bun NAPI crash

The prior commit's premise was wrong. The actual root cause is a Bun 1.3.13
bug: calling process.exit() in a worker_threads.Worker that has lmdb-js
loaded, while sibling workers are running, triggers a NAPI fatal error
(panic: NAPI FATAL ERROR: Error::New napi_create_error) crashing the whole
process.

The crash chain for the CSV upsert integration test:
1. northnwd.suppliers has schemaDefined=false (create_table without attributes)
2. CSV upsert with a new column triggers addAttributes → signalSchemaChange
   → broadcastWithAcknowledgement, which calls port.ref() on ALL ports
   including parentPort
3. After ACKs received, parentPort is never unref'd (by design for regular
   workers, but wrong for job workers)
4. parentPort ref keeps the event loop alive until the 3s unref'd timer fires
5. realExit() → process.exit() in the lmdb-bearing job worker → Bun crash

Fix: unref parentPort after updateJob so the event loop drains naturally,
avoiding process.exit() entirely. Remove the setInterval keepalive which
was based on the incorrect premise.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: kriszyp

server/jobs/jobProcess.ts

@@ -15,6 +15,7 @@ import { cloneDeep } from 'lodash';
 
 import { pathToFileURL } from 'node:url';
 import { join } from 'node:path';
+import { parentPort } from 'node:worker_threads';
 import { getEnvBuiltInComponents } from './../../components/Application.ts';
 import { PACKAGE_ROOT } from '../../utility/packageUtils.js';
 const JOB_NAME = process.env[(hdbTerms as any).PROCESS_NAME_ENV_PROP] as string;
@@ -26,12 +27,6 @@ const JOB_ID = JOB_NAME.substring(4);
  * @returns {Promise<void>}
  */
 (async function job() {
-	// Bun's event loop does not keep the loop alive for pending NAPI async callbacks
-	// (e.g. RocksDB transaction commit passing resolve/reject into native code). Job
-	// workers have no other ref'd work (HTTP server, ref'd ports), so Bun exits the
-	// loop before the callback fires. A ref'd interval prevents that.
-	const bunEventLoopKeepAlive =
-		typeof (globalThis as any).Bun !== 'undefined' ? setInterval(() => {}, 1000) : undefined;
 	// The request value could potentially be quite large so it's set to undefined to clear it out after being processed.
 	let jobObj: any = { id: JOB_ID, request: undefined };
 	let exitCode = 0;
@@ -83,7 +78,11 @@ const JOB_ID = JOB_NAME.substring(4);
 		jobObj.end_datetime = moment().valueOf();
 	} finally {
 		await jobs.updateJob(jobObj);
-		if (bunEventLoopKeepAlive) clearInterval(bunEventLoopKeepAlive);
+		// On Bun 1.3.13, calling process.exit() in a worker thread with lmdb-js loaded
+		// while sibling workers are running causes a NAPI fatal error crash. Unref
+		// parentPort (which broadcastWithAcknowledgement may have ref'd during schema
+		// changes) so the event loop drains naturally without calling process.exit().
+		parentPort?.unref();
 		setTimeout(() => {
 			realExit(exitCode);
 		}, 3000).unref();