#57 fix(local-llm): stop the managed daemon when the last session exits

[Anonymous]

Originally created by: sosidudku1

Closes [#52].

The managed llama-server is spawned detached so it survives the CLI on purpose, and the clean-exit path (q, Ctrl+C, SIGTERM) already stops it. The complaint in [#52] turned out to be the terminal-close path: closing the window sends SIGHUP, which had no handler, so the process died before orchestrator.shutdown() ran and the daemon kept holding RAM/VRAM until a manual models stop.

Changes

• SIGHUP is handled in the TUI entry alongside SIGINT/SIGTERM, and the alt-screen restore is EIO-safe so teardown still runs when the tty is already gone.
• New localModels.managed.stopOnExit flag, default true. Closing the last session frees the memory; false keeps the model warm between sessions for operators who prefer the old behavior. Config v33 → v34; older files transparently inherit true. Standalone daemons started with atomic-agent models start are never touched, same as before.
• New session registry (<dataDir>/sessions/<pid> marker files, same liveness pattern as telegram-lockfile.ts): only the last live session stops the daemon. This also fixes a pre-existing bug: with two parallel TUI windows, the first one to exit killed the model out from under the second. Stale markers from crashed sessions are reclaimed on scan.

Testing

• session-registry.test.ts: register/release, own-pid exclusion, live-other detection (via process.ppid), stale-marker reclamation.
• Orchestrator shutdown: stops by default as the last session, honors stopOnExit: false, leaves the daemon alone while another live session exists, never touches an unsupervised daemon.
• Config: default, explicit false, v33 file inheriting true.
• tsc --noEmit clean; full suite has the same pre-existing failures as main (verified against a clean checkout).

Manual verification checklist (needs a machine with a downloaded model)

1. Close the terminal window mid-session: ps shows llama-server gone.
2. Two parallel TUI sessions: first exit leaves the daemon up, second exit stops it.
3. Windows: closing the console window (CTRL_CLOSE_EVENT allows ~5 s; teardown uses a 2 s timeout).
4. stopOnExit: false: daemon survives exit and the next TUI start adopts the warm model.

Note

This PR and the telegram follow-up both bump USER_CONFIG_VERSION 33 → 34 for their own field. Whichever merges second gets a trivial rebase to 35.

[Anonymous]

Ticket changed by: Ooooze

• status: open --> closed