telegram: save user message before agent loop for session recall

session_search inside the agent loop could never find the current
turn's data. The user message was appended to an in-memory slice
but only persisted to disk AFTER RunWithMessages completed.

This meant the vector index never had the current conversation's
content, and deepSearch read a stale session file from disk.

Now the user message is saved to the Store immediately after
being appended, using a Store.Save call that bypasses the
TurnCount increment (which happens once at the normal end-of-turn
save).

Author: molty3000

cmd/odek/telegram.go

@@ -998,6 +998,24 @@ func handleChatMessage(
 	cs.Messages = append(cs.Messages, llm.Message{Role: "user", Content: text})
 	cs.LastActive = time.Now()
 
+	// Persist the user message immediately so session_search can find it
+	// inside the agent loop. Without this, the current turn is only in
+	// memory and invisible to both vector search and deepSearch.
+	// Build a session.Snapshot directly to avoid incrementing TurnCount
+	// (that happens once at the end in the normal Save path).
+	sess := &session.Session{
+		ID:        cs.SessionID,
+		CreatedAt: cs.CreatedAt,
+		UpdatedAt: time.Now(),
+		Model:     "",
+		Turns:     cs.TurnCount,
+		Task:      fmt.Sprintf("tg-%d", chatID),
+		Messages:  cs.Messages,
+	}
+	if err := sessionManager.Store.Save(sess); err != nil {
+		log.Error("save session before agent run", "chat_id", chatID, "error", err)
+	}
+
 	// Build the agent with Telegram approver.
 	tools := builtinTools(resolved.Dangerous, nil, approver, resolved.MaxConcurrency, resolved.APIKey, resolved.Transcription, sessionManager.Store)