fix(v1.5.2): notif/name prefs survive restart for fresh sessions

A new session created in scan() started in WAITING and was only persisted
to config.sessions on its first state transition. Toggling the bell on a
brand-new session and restarting the app before any transition meant
config.notifications[sid] existed but config.sessions[sid] did not — the
startup orphan purge then deleted the bell pref. Same path nuked custom
names and sessionOrder slots.

Fix: persist immediately when a new session is created in scan(), so the
purge's "known ids" set always covers live sessions.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: Invictorius

package.json

@@ -1,6 +1,6 @@
 {
   "name": "aby-claude-watcher",
-  "version": "1.5.1",
+  "version": "1.5.2",
   "description": "Aby Claude Watcher — dashboard desktop pour monitorer en temps réel vos sessions Claude Code",
   "main": "main.js",
   "scripts": {

watcher.js

@@ -215,6 +215,10 @@ class SessionWatcher extends EventEmitter {
               wasResumed: false,
             });
             this.watchJsonl(effectiveId);
+            // Persist immediately so a fresh session that hasn't yet transitioned
+            // state is known to config.sessions. Otherwise the startup orphan
+            // purge would nuke its notif/name/order prefs on next launch.
+            this.persistSession(this.sessions.get(effectiveId));
             this.emit('session-added', this.sessions.get(effectiveId));
           } else {
             const session = this.sessions.get(effectiveId);