fix: persist direct chat transcript before Goosed escalation

Prevent portal direct-chat history from being lost when snapshot cache
is invalidated on Goosed submit by writing non-empty messages to DB first,
and stop caching empty Goose placeholder messages in snapshots.

Co-authored-by: Cursor <cursoragent@cursor.com>

server.mjs

@@ -165,6 +165,7 @@ import { startScheduleReminderWorker } from './schedule-reminder-worker.mjs';
 import { createLlmProviderService, RELAY_BOOTSTRAP } from './llm-providers.mjs';
 import { createDirectChatService, isDirectChatSessionId, isPortalDirectChatSnapshot, sendDirectChatSessionEvents, shouldExpirePortalDirectChatSnapshot } from './direct-chat-service.mjs';
 import { repairSessionConversationFromDb } from './conversation-repair.mjs';
+import { filterNonemptyUserVisibleMessages } from './conversation-transcript-persist.mjs';
 import { createManagedChatIntentRouter } from './chat-intent-router.mjs';
 import { createSessionSnapshotService } from './session-snapshot.mjs';
 import { createConversationMemoryService } from './conversation-memory.mjs';
@@ -584,6 +585,7 @@ async function bootstrapUserAuth() {
       directChatService,
       chatIntentRouter,
       sessionSnapshotService,
+      conversationMemoryService,
       autoDispatch: ['1', 'true', 'yes', 'on'].includes(
         String(process.env.MEMIND_AGENT_RUN_AUTODISPATCH ?? '1').trim().toLowerCase(),
       ),
@@ -4523,8 +4525,7 @@ api.get('/sessions/:sessionId', async (req, res, next) => {
     }
     // Write-through: persist snapshot async, don't block the response.
     if (sessionSnapshotService?.isEnabled()) {
-      const messages = (gooseSession.conversation ?? [])
-        .filter((m) => m.metadata?.userVisible);
+      const messages = filterNonemptyUserVisibleMessages(gooseSession.conversation ?? []);
       if (messages.length > 0) {
         void sessionSnapshotService
           .save(sessionId, req.currentUser.id, gooseSession, messages)