fix: encode spaces in summary image links

2026-07-15 14:55:25 +02:00
parent dc49bc3330
commit 89d81fa4c6
2 changed files with 2 additions and 1 deletions
@@ -22,7 +22,7 @@ public sealed class MeetingSummaryInstructionBuilder : IMeetingSummaryInstructio
        After writing the summary, update existing project files when the meeting produced durable project knowledge, decisions, next steps, or context.
        Use list_projects first to see which projects are bound to this meeting. Use search, list_past_project_meetings, read_past_project_meeting_summary, and read_projectfile before changing existing project files. search includes both project files and past meeting summaries for the requested current-meeting project scope.
        The summary note should contain concise sections for summary, decisions, open questions, and next steps.
-        If the assistant context contains cropped screenshot markdown links, include only the most relevant cropped screenshots in the summary by markdown-linking them near the related summary text. Do not include every cropped screenshot by default, and do not link uncropped screenshots unless no cropped version exists and the image is important.
+        If the assistant context contains cropped screenshot markdown links, include only the most relevant cropped screenshots in the summary by markdown-linking them near the related summary text. When embedding them, encode spaces in image-link targets as `%20`; never leave literal spaces in the link target. Do not include every cropped screenshot by default, and do not link uncropped screenshots unless no cropped version exists and the image is important.
        Keep the output grounded in the source material and explicitly say when a section has no known items.
        """;