Build - fix(Session): prevent dangling pointers in DeleteAllSessions Remove database_ref_.Reset() calls during DeleteAllSessions() iteration. The issue: Reset() can trigger GC, which may finalize Session JS objects that are still in our iteration list, creating dangling pointers → SIGSEGV. Why this is safe: - Our iteration only uses pure C/C++ ops (no Napi calls that trigger GC) - When Sessions are later GC'd, Delete() returns early (session_ is nullptr) - Napi::ObjectReference destructor handles re...

Build - fix(Session): prevent dangling pointers in DeleteAllSessions Remove database_ref_.Reset() calls during DeleteAllSessions() iteration. The issue: Reset() can trigger GC, which may finalize Session JS objects that are still in our iteration list, creating dangling pointers → SIGSEGV. Why this is safe: - Our iteration only uses pure C/C++ ops (no Napi calls that trigger GC) - When Sessions are later GC'd, Delete() returns early (session_ is nullptr) - Napi::ObjectReference destructor handles re... #248