Swiss AI Hub v0.310.0

Added

• ✨ Introduced IMAP Read Capability for Agents: Agents can now connect to IMAP inboxes, list unread messages, and
  fetch selected messages along with their attachments. This foundational capability enables agents to interact with
  email workflows.
• 🦾 New IMAP Agent Demonstrator: A new ImapAgent (non-conversational) has been added to the playground, showcasing
  how to list unread mail and fetch messages with S3-referenced attachments.
• 📦 Core IMAP Configuration and Event Types: Added ImapClientConfig for configuring IMAP connections, and new
  event types like UnreadMailListedEvent, MailFetchedEvent, MailAttachmentRef, and UnreadMailSummary for
  structured communication of IMAP data.
• ☁️ S3 Integration for Agent Attachments: The agent runtime now includes native S3 client integration, allowing
  mail attachments to be stored securely in S3 and referenced by file_id within agent events, preventing event bloat.
• 🔒 Configurable Message Size Limits: Implemented deployment-fixed caps for raw message size, body size, and
  attachment size to protect agents from hostile or oversized emails and prevent exceeding message-size limits in the
  audit trail and WebSocket streams.
• 🌍 Internationalization for IMAP Features: Added translations for IMAP configuration fields and new IMAP-related
  events in German, English, French, and Italian.
• 📄 Architectural Decision Record for IMAP: A new ADR documents the design decisions behind the agent's IMAP read
  capability, covering exposure, event handling, and attachment storage.

Changed

• 🚀 Agent Runtime Dependency on S3: The agent runtime now depends on S3 for storing mail attachments, expanding its
  infrastructure requirements.
• 📡 IMAP Events Exposed via WebSocket: UnreadMailListedEvent and MailFetchedEvent are now included in the
  DisplayEvents type, making them visible in the frontend's event timeline via WebSocket.
• 🧩 Filename Sanitization for Attachments: Improved security by sanitizing attachment filenames to prevent path
  traversal vulnerabilities.

Security

• 🔑 HTML Body Exclusion from Events: The raw HTML body of fetched emails is deliberately not surfaced in
  MailFetchedEvent (which is persisted and streamed to the frontend) to mitigate Cross-Site Scripting (XSS) risks from
  hostile sender markup.