Blocking Supabase Writes Increasing Agent Response Latency

# Problem
```store_summary_to_database ``` was called directly within the agent's execution flow. This function performs a database upsert to Supabase. While the call is asynchronous (```await```), the agent's progress is still paused until the database confirms the write. Database I/O can be unpredictable and slow, which directly increases the latency of the user's message processing—even though the user doesn't need to wait for the summary to be saved before receiving a response.

### fix

To address this, the approach taken was to decouple the database write from the main agent execution flow, so that the summary storage is handled outside the immediate message-processing path rather than blocking the agent’s response generation.