Notes

Author: vcarl

notes/2025-12-15_3_invalid-session-cookie-clearing.md

@@ -11,10 +11,12 @@ When session cookies were invalid (expired database sessions, corrupted cookies,
 ## Solution
 
 Modified `getUserId()` in `session.server.ts` to detect when:
+
 1. Session cookies are present in the request (`__session` or `__client-session`)
 2. But no valid userId was found in the session
 
 When this condition is detected, we call `logout(request)` which:
+
 - Destroys both session cookies (sets them to expire)
 - Redirects to `/`
 
@@ -32,4 +34,4 @@ if (!userId) {
     throw await logout(request);
   }
 }
-```
+```

notes/2025-12-17_1_escalation-scheduling-refactor.md

@@ -23,20 +23,24 @@ AND scheduled_for <= datetime('now')
 ## Changes
 
 ### Migration (`20251217145416_add_scheduled_for.ts`)
+
 - Added `scheduled_for` text column
 - Backfills existing pending escalations based on current vote count
 
 ### Model (`escalationVotes.server.ts`)
+
 - `calculateScheduledFor(createdAt, voteCount)` - computes scheduled time
 - `updateScheduledFor(id, scheduledFor)` - persists new scheduled time
 - `getDueEscalations()` - queries escalations past their scheduled time
 - `createEscalation()` - now sets initial `scheduled_for` (36h from creation)
 
 ### Handlers (`handlers.ts`)
+
 - Vote handler: updates `scheduled_for` after recording vote
 - Re-escalation handler: updates `scheduled_for` when upgrading to majority voting
 
 ### Resolver (`escalationResolver.ts`)
+
 - Simplified to use `getDueEscalations()` instead of `getPendingEscalations()`
 - Removed `shouldAutoResolve()` check—query already filters for due escalations