From 0b1b8ce6c81b948f840aa36e7a94c7fcde9770e9 Mon Sep 17 00:00:00 2001
From: JEAN REGIS <240509606@firat.edu.tr>
Date: Fri, 3 Apr 2026 20:40:58 +0300
Subject: [PATCH] fix(chat): emit effective_message in response_complete event

Root cause:
stream_response built effective_message with attachment prefix but
passed user_message (original) to the response_complete event,
diverging from the DB record which correctly stores effective_message.

Solution:
Replace user_message with effective_message in the response_complete
event_data dict. effective_message equals user_message when no
attachments are present, so the no-attachment path is unaffected.

Impact:
Event log and DB record now consistent for all sessions.
Deterministic. Zero regression risk on attachment-free paths.

Signed-off-by: JEAN REGIS <240509606@firat.edu.tr>
---
 finbot/agents/chat.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/finbot/agents/chat.py b/finbot/agents/chat.py
index ba2a0bd7..362618f7 100644
--- a/finbot/agents/chat.py
+++ b/finbot/agents/chat.py
@@ -446,7 +446,7 @@ async def _keepalive_emitter() -> None:
                 "response_length": len(full_response),
                 "response_content": full_response,
                 "duration_ms": duration_ms,
-                "user_message": user_message,
+                "user_message": effective_message,
                 "vendor_id": self.session_context.current_vendor_id,
                 "llm_model": self._model,
             },