Ingest: catch exceptions in --dev

[janezd]

In some cases that I cannot replicate, ingest --dev would get an uncaught exception and kill the app without killing the background server process.

This PR

• wraps the update into a try-catch block. update is supposed to catch all exceptions, but some (perhaps in other code, like chokidar?) fall through.
• terminates the server if update workers (and with them the main process) terminate

[Copilot]

Pull request overview

This PR hardens the ingest --dev workflow by (1) preventing unexpected exceptions during ingestion updates from crashing the process and (2) ensuring the background Next.js server is terminated when the ingest process terminates unexpectedly.

Changes:

• Add a try/catch around updatePaths() inside updateDb() to prevent unhandled exceptions from bubbling out.
• In scripts/ingest.ts, run Next.js in a detached process and add process-level handlers (uncaughtException, unhandledRejection, signals) to terminate the Next.js process tree.
• Add the tree-kill dependency (and lockfile entry) for process-tree termination.

Reviewed changes

Copilot reviewed 3 out of 4 changed files in this pull request and generated 2 comments.

File	Description
ingest/index.ts	Wraps updatePaths() in try/catch to prevent uncaught exceptions from escaping update runs.
scripts/ingest.ts	Adds dev-mode shutdown handlers and uses tree-kill to terminate the spawned Next.js process tree.
package.json	Adds tree-kill dependency.
yarn.lock	Lockfile update for tree-kill.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.