Fix systemd crash loop: forward SIGTERM during entry.ts respawn

[roshanasingh4]

Fixes #931

Problem

src/entry.ts conditionally respawns itself to inject --disable-warning=ExperimentalWarning into NODE_OPTIONS. Today that respawn used spawnSync(), which blocks the parent process. When running under systemd with KillMode=process, systemctl stop only terminates the parent PID. The spawned child (the actual gateway process holding the port) can survive as an orphan and keep the gateway port bound, causing restart loops with EADDRINUSE.

Fix

Switch the respawn from spawnSync() to a non-blocking spawn() wrapper that forwards termination signals (SIGTERM/SIGINT/SIGHUP/SIGQUIT) from the parent to the child. This ensures a systemd stop will also terminate the actual gateway process even under KillMode=process.

Tests

Adds a regression test for the signal-forwarding helper that simulates the parent receiving SIGTERM and asserts the child process is terminated and releases its listening port.

[steipete]

Thanks Roshan!

[roshanasingh4]

Thanks Roshan!

You're Welcome Peter...

[steipete]

Landed on main after rebasing onto a temp branch.

What changed:

• refactored respawn signal handling into a generic child-process bridge with cross-platform signal handling and error detach
• switched the fixture to run under node directly (no tsx bin) and kept the regression test
• added changelog entry

Tests: pnpm lint && pnpm build && pnpm test

Commits:

• d9f2ee4
• 154b8e3

Thanks @roshanasingh4!