fix(audit): bundling-safe CLI guard in apply-triggers (stop worker crash-loop) (#469)

`require.main === module` is unreliable once apply-triggers.ts is bundled: esbuild inlines
it into dist/workers/auditLogWorker.js, where `require.main === module` evaluates TRUE for the
bundle entry. That ran the apply-triggers CLI main() inside the audit-log worker, which connected
to the worker's placeholder DATABASE_URL (localhost:5432), hit ECONNREFUSED, and process.exit(1) —
crash-looping the worker so the audit-logs queue stopped draining and Loop B materialization
stalled. (The Next/webpack web build was unaffected, so the web canary passed.)

Gate the CLI on the process entry-script path instead: argv[1] contains "apply-triggers" only when
invoked directly (tsx scripts/apply-triggers.ts), never when bundled into the worker or the Next
server. applyAuditTriggers() remains a side-effect-free import for the boot hooks.

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

Author: therealbrad

testplanit/scripts/apply-triggers.ts

@@ -355,9 +355,14 @@ async function main() {
   await applyAuditTriggers();
 }
 
-// CLI entry only — guarded so importing applyAuditTriggers() (e.g. the instrumentation boot hook)
-// never auto-runs the apply or calls process.exit. `require.main` is undefined when bundled.
-if (typeof require !== "undefined" && require.main === module) {
+// CLI entry only. `require.main === module` is NOT safe here: esbuild inlines this file into the
+// worker bundle (dist/workers/auditLogWorker.js), where `require.main === module` is TRUE for the
+// bundle entry — so it would wrongly run the CLI, connect to the worker's placeholder DB, and crash
+// it on a loop. Gate on the actual process entry-script path instead: argv[1] only contains
+// "apply-triggers" when this is invoked directly as the CLI (tsx scripts/apply-triggers.ts), and
+// never when bundled into auditLogWorker.js or the Next server.
+const isCliEntry = /apply-triggers/.test(process.argv[1] ?? "");
+if (isCliEntry) {
   main().catch((err) => {
     console.error("[apply-triggers] apply failed:", err);
     process.exit(1);