fix: reliable self-update restart (v7.5.2)

[vakovalskii]

Problem

Clicking Update Now installed the new version via npm i -g codbash-app@latest, but the server then died and never came back up — the port was freed yet nothing relistened. The UI kept showing the stale version (v7.4.0 → v7.5.1) and the auto location.reload() hit a dead server.

Root cause

/api/update spawned the restarter inside a process.on('exit') handler:

process.on('exit', () => {
  require('child_process').spawn(process.argv[0], process.argv.slice(1), {
    detached: true, stdio: 'inherit'
  }).unref();
});
process.exit(0);

At exit time the event loop is already draining — spawning there is unreliable and the detached child frequently never survives. Net result: server gone, no relisten.

Fix

• Spawn a fully-detached restarter (detached: true, stdio: 'ignore', own process group, .unref()) before exiting, then process.exit(0) after a 250ms tick so the port is released for the restarter.
• Restarter reuses the same --port/--host and passes --no-browser (the existing tab reloads itself — no duplicate window).
• Restarter loads freshly-installed code from the same argv[1] path npm just overwrote.
• Bumped npm-install timeout 60s → 120s for slower connections.

Version

Patch bump 7.5.1 → 7.5.2 + changelog entry.

Note: users currently on the broken updater will still hit the old path once; every self-update after they land on 7.5.2 is reliable.

Testing

• node -c syntax check passes on server.js and changelog.js.
• Manual restart verified: server comes up on 3847 and reports 7.5.2.

🤖 Generated with Claude Code