Swiss AI Hub v0.302.0

Added

• 🦾 Agent-Generated Conversation Metadata: Agents now autonomously generate concise conversation titles (once
  per thread, when a clear topic emerges) and suggested follow-up questions (after each response), enriching the
  user experience by providing more contextual chat summaries and interaction prompts.
• 📄 Architectural Decision Record for Conversation Metadata: A new ADR
  (2026_06_18_conversation_metadata_as_explicit_per_agent_steps.md) has been added, detailing the design and
  implementation strategy for agents producing conversation titles and follow-up questions.
• ✨ New Display Events for Conversation Metadata: Introduced ConversationTitleEvent and FollowUpQuestionsEvent
  to transmit agent-generated metadata, ensuring these insights are seamlessly communicated through the event pipeline.
• 🚀 Integration Across Key Agents: The new conversation metadata generation has been integrated into several core
  conversational agents, including RAGAgent, ExpertRAGAgent, LLMWrappingAgent, FewShotAgent, and
  McpReactAgent, making these features widely available.
• 🌍 Multilingual Prompts and UI Elements for Metadata: Added comprehensive internationalization support for the new
  conversation metadata features, including prompts for title and follow-up question generation, and localized display
  names for the events in the UI.
• 🖼️ Web UI Components for Conversation Metadata: New web UI components (ConversationTitleEvent.vue,
  FollowUpQuestionsEvent.vue) have been added to visually display the agent-generated conversation titles and
  suggested follow-up questions to users.

Changed

• 🔄 Dynamic Thread Naming: Conversation threads are now dynamically named by observing agent-generated
  ConversationTitleEvents, replacing generic "chat" names with topic-relevant titles derived from the conversation
  content.
• ⚡️ Enhanced Agent Workflows for Metadata: Existing agent workflows have been updated to incorporate conversation
  metadata generation, either through dedicated step decorators for non-terminal LLM answers or inline calls for
  terminal stop events, ensuring robust, best-effort generation.
• 📡 API and WebSocket Event Schema Updates: The API and WebSocket event schemas have been extended to include the
  new ConversationTitleEvent and FollowUpQuestionsEvent within the DisplayEvents discriminated union, ensuring
  proper serialization and deserialization.