Force rebuild of Matrix session error fixes

- Add timestamp comments to force browser cache refresh
- Ensure Matrix session ID checks are properly applied
- Both useChatEngine.ts and useMessageStream.ts now skip backend calls for Matrix sessions
- Matrix room IDs (starting with '!') are properly filtered out from Goose session API calls

This should resolve the persistent 'Failed to read session: Session not found' errors.

Author: spencrmartin

ui/desktop/src/hooks/useChatEngine.ts

@@ -17,6 +17,8 @@ import { ChatType } from '../types/chat';
 import { ChatState } from '../types/chatState';
 import { getSession } from '../api';
 
+// Force rebuild timestamp: 2025-01-15T02:35:00Z - Fixed Matrix session token fetching
+
 // Helper function to determine if a message is a user message
 const isUserMessage = (message: Message): boolean => {
   if (message.role === 'assistant') {

ui/desktop/src/hooks/useMessageStream.ts

@@ -4,6 +4,8 @@ import { createUserMessage, hasCompletedToolCalls, Message, Role } from '../type
 import { getSession, Session } from '../api';
 import { ChatState } from '../types/chatState';
 
+// Force rebuild timestamp: 2025-01-15T02:35:00Z - Fixed Matrix session SSE stream error
+
 let messageIdCounter = 0;
 
 function generateMessageId(): string {