fix: skip stale signal_triage rows instead of re-inserting during snapshot restore (#33)

When a snapshot row is older than the existing database row, the previous
logic fell through to the insert branch and violated the signal_triage
primary key. Stale rows are now skipped.

Co-authored-by: JW-90124 <jww2708@gmail.com>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

Author: 3 people

src/pipeline/snapshot.ts

@@ -871,8 +871,10 @@ async function restoreSnapshot(
       details_json: JSON.stringify(value.details ?? {}),
       updated_at: optionalString(value.updatedAt) ?? requiredString(value, "createdAt"),
     };
-    if (existing && compareTimestamp(row.updated_at, existing.updated_at) >= 0) {
-      await db.updateTable("signal_triage").set(row).where("signal_id", "=", signalId).execute();
+    if (existing) {
+      if (compareTimestamp(row.updated_at, existing.updated_at) >= 0) {
+        await db.updateTable("signal_triage").set(row).where("signal_id", "=", signalId).execute();
+      }
     } else {
       await db
         .insertInto("signal_triage")