fix: Prevent Message Misrouting on Conversation Refresh 🔄

[danny-avila]

fix: Prevent Message Misrouting on Conversation Refresh 🔄

Summary

Addresses a critical bug where refreshing the conversation page led to messages being sent to a new, incorrect conversation. This bug fix ensures that the conversation state is preserved on refresh and integrated properly with remote model updates (/api/models).

This change further decouples the new UI route handling from routes/Root.tsx, which is for the better.

Change Type

• Bug fix (non-breaking change which fixes an issue)

Testing

To ensure the fix works as intended, the following testing process was performed:

1. Opened a conversation within the application.
2. Refreshed the page to simulate the user's refresh action.
3. Sent a message to check if it is routed to the currently active conversation.

Instructions for reproducing the test:

• Open any conversation in the application.
• Refresh the browser page.
• Send a new message and verify it is delivered to the correct conversation.

Test Configuration:

• Browser: Chrome Version 104.0.5112.101
• Server Environment: Localhost with a simulated connection to remote message handling services.

Checklist

• My code adheres to this project's style guidelines
• I have performed a self-review of my own code
• I have commented in any complex areas of my code
• My changes do not introduce new warnings
• I have written tests demonstrating that my changes are effective or that my feature works
• Local unit tests pass with my changes