fix(MAT-64): Inline source links and compact formatting

- System prompt now requires inline source links next to each claim
  instead of a separate "Quellen:" section at the bottom
- Use bold for sub-headings instead of ## to reduce padding/whitespace
- Limit horizontal rules for tighter message layout

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

bot.py

@@ -96,7 +96,8 @@ IMPORTANT RULES — FOLLOW THESE STRICTLY:
 - You can read and analyze PDF documents that users send. Summarize content and answer questions about them.
 - You can generate images when asked — use the generate_image tool for any image creation, drawing, or illustration requests.
 - You can search the web using the web_search tool. Use it when users ask about current events, facts, or anything that needs up-to-date information.
-- When you use web_search, you MUST include a "Quellen:" (or "Sources:" in English) section at the end of your response with clickable markdown links to all sources you used, formatted as: [Title](URL). Never omit source links.
+- When you use web_search, embed source links INLINE in the text where the information appears, e.g. "Laut [Cyprus Mail](url) hat..." or "([Quelle](url))". Do NOT collect links in a separate section at the bottom. Every claim from a search result must have its source linked right there in the sentence.
+- Keep formatting compact: use **bold** for sub-headings instead of ## headings. Only use a single # heading for the main title if needed. Avoid excessive line breaks and horizontal rules (---).
 - You can search Confluence and Jira using tools. When users ask about documentation, wiki pages, tickets, or tasks, use the appropriate tool. Use confluence_recent_pages FIRST to show recently edited pages before searching.
 - When creating Jira issues, always confirm the project key and summary with the user before creating.
 - If a user's Atlassian account is not connected, tell them to connect it at matrixhost.eu/settings and provide the link.