Service "Signal" (project vigilant-balance) has been crash-looping continuously for over an hour, restarting every 1-2 seconds without ever stabilizing. Every crash shows the identical native trace:

Assertion failed: (env) != nullptr

node::RemoveEnvironmentCleanupHook(...)

Database::~Database() [better-sqlite3]

It happens within about 1 second of "Mounting volume on: ..." every single time.

I've ruled out code and config as the cause:

• Reverted to a commit confirmed stable minutes earlier — still crashes
• • Full rebuild/redeploy (not just restart) — still crashes
• • Removed a newly-added env var as a controlled test — still crashes
• • CPU/memory graphs show no spike before the crash
• • Railway status page shows no incident

Given the consistency (crashing every single boot, not intermittently), I suspect either a corrupted/locked SQLite file on the attached volume, or a degraded host. No backups are available on my plan to test a restore. Would really appreciate help checking server-side infra health for this service, or whether the database file on the attached volume needs inspection.