Archive meeting workflow and screenshot changes

README.md

@@ -9,6 +9,8 @@ The application is intended to:
 - create an Obsidian markdown note before transcription starts
 - keep meeting metadata, user notes, detected context, and links to generated output in that note
 - toggle recording/transcription mode through a configurable global hotkey
+- abort and discard an active recording through a configurable global hotkey
+- capture active-window screenshots through a configurable global hotkey
 - capture microphone input and computer output into one transcription stream
 - transcribe meetings with speaker attribution
 - use a configurable speech recognition pipeline, with local Whisper as the first version 1 fallback
@@ -67,6 +69,7 @@ GET /recording/status
 POST /recording/toggle
 POST /recording/start
 POST /recording/stop
+POST /recording/abort
 POST /asr/transcribe-file
 POST /asr/diarize-file
 POST /diagnostics/workflow/reload
@@ -83,7 +86,8 @@ Meeting Assistant uses normal .NET configuration under the `MeetingAssistant` se
 {
   "MeetingAssistant": {
     "Hotkey": {
-      "Toggle": "Ctrl+Alt+M"
+      "Toggle": "Ctrl+Alt+M",
+      "Abort": "Ctrl+Alt+D"
     },
     "Vault": {
       "TranscriptsFolder": "%USERPROFILE%\\OpenCloud\\Persönlich\\Vault\\Meetings\\Transcripts",
@@ -98,6 +102,7 @@ Meeting Assistant uses normal .NET configuration under the `MeetingAssistant` se
       "SampleRate": 16000,
       "Channels": 1,
       "StopProcessingTimeout": "00:10:00",
+      "MaxMetadataAttendeeImportCount": 30,
       "TemporaryRecordingsFolder": "%LOCALAPPDATA%\\MeetingAssistant\\Recordings"
     },
     "FunAsr": {
@@ -164,6 +169,18 @@ Meeting Assistant uses normal .NET configuration under the `MeetingAssistant` se
     "Automation": {
       "RulesPath": "meeting-rules.local.yaml"
     },
+    "Screenshots": {
+      "Hotkey": "Ctrl+Alt+S",
+      "AttachmentsFolder": "Attachments",
+      "Ocr": {
+        "Enabled": false,
+        "Endpoint": "",
+        "KeyEnv": "LITELLM_API_KEY",
+        "Model": "",
+        "Timeout": "00:02:00",
+        "Prompt": "This screenshot was captured during a meeting..."
+      }
+    },
     "Agent": {
       "Endpoint": "https://litellm.schweigert.cloud",
       "KeyEnv": "LITELLM_API_KEY",
@@ -205,8 +222,12 @@ For real meeting recordings, Meeting Assistant derives the optional finished-tra
 
 Meeting notes link to separate transcript, assistant context, and summary markdown artifacts using the configured vault folders.
 
+`Hotkey:Abort` configures a global discard shortcut. The default is `Ctrl+Alt+D`. Aborting an active recording stops capture/transcription, deletes the meeting note, transcript, assistant context, summary file if present, and linked screenshot attachments for that run, and skips automatic summary generation.
+
 Meeting note, transcript, assistant context, and summary artifacts use frontmatter links so they backlink to each other. Meeting note frontmatter includes `start_time` when recording starts and `end_time` when transcription processing finishes. Transcript and summary frontmatter copy the meeting title, start time, and end time from the meeting note; if the meeting has no title, the summary agent can provide one when writing the summary.
 
+`Recording:MaxMetadataAttendeeImportCount` limits how many attendees Outlook metadata enrichment imports into meeting-note frontmatter. The default is `30`; when an appointment has more attendees than that, Meeting Assistant still imports title, agenda, and scheduled end time, but leaves attendees empty because large invites are usually presentation-style meetings.
+
 Assistant context notes keep their artifact links in frontmatter and expose a lifecycle `state`: `collecting metadata`, `transcribing`, `speaker recognition`, `summarizing`, `finished`, or `error`. Meeting Assistant updates this state as metadata lookup, recording, final speaker recognition, and summary generation progress.
 
 `ProjectsFolder` contains project knowledge. Each direct subfolder is treated as one project, and a meeting binds projects by listing those subfolder names in the meeting note `projects` frontmatter.
@@ -217,6 +238,10 @@ See `docs/meeting-workflow-engine.md` for the detailed YAML format, supported va
 
 `POST /diagnostics/workflow/reload` reloads application configuration so workflow automation settings such as `Automation:RulesPath` can be changed without restarting the application. A meeting run that already captured its options keeps using those options.
 
+`Screenshots:Hotkey` configures a global hotkey that captures the currently active window during an active meeting. Screenshots are written under `Screenshots:AttachmentsFolder`, which defaults to an `Attachments` folder beside the assistant context note, and each capture appends a timestamped markdown image link to the assistant context. Launch profiles can override the screenshot hotkey with `LaunchProfiles:{profile}:Screenshots:Hotkey`; only explicitly configured profile hotkeys are registered, so profile-specific hotkeys do not silently inherit and collide with the default profile.
+
+`Screenshots:Ocr` optionally enables vision extraction for screenshots. When `Enabled` is true, Meeting Assistant sends the screenshot and prompt to an OpenAI-compatible Responses endpoint and replaces the screenshot OCR placeholder with the model output. Blank `Endpoint` or `Model` values fall back to the summary `Agent` endpoint and model, which keeps local OCR on the same LiteLLM backend as summarization. `Key` or `KeyEnv` can be set specifically for OCR; otherwise the summary agent key configuration is used. The default prompt asks the model to return pixel crop coordinates when it can confidently isolate only the presentation or shared-screen content; valid crop boxes are saved as `*-cropped.png` beside the original screenshot and linked before the OCR block. Automatic summarization waits for pending screenshot OCR work to complete or hit `Timeout` before the assistant context moves to `summarizing`.
+
 `Agent` configures the Microsoft Agent Framework summary pipeline. `Key` may be set directly for local testing, but `KeyEnv` is preferred; by default the API key is read from `LITELLM_API_KEY`. After transcription has fully finished, Meeting Assistant automatically runs the summary pipeline for the meeting. `ReconnectionAttempts` and `ReconnectionDelay` control retries for transient model endpoint failures such as LiteLLM token refresh or 5xx responses. If summary generation still fails, Meeting Assistant overwrites the configured summary note with a markdown failure report containing the exception details and linked meeting artifacts.
 
 `ContextWindowTokens`, `MaxOutputTokens`, `EnableCompaction`, and `CompactionRemainingRatio` configure summary-agent context monitoring. Meeting Assistant estimates the outgoing Responses payload size, logs the estimated token count and remaining context, and compacts the conversation when only the configured remaining ratio is left. It first attempts `POST /v1/{ResponsesCompactPath}` on the configured OpenAI-compatible endpoint. If that endpoint is unavailable or returns invalid data, it falls back to Microsoft Agent Framework compaction: collapse old tool results, summarize older message groups, preserve only the last four user turns if needed, and finally drop oldest groups until the request is back under budget.
@@ -235,6 +260,8 @@ Failure summary notes include a clickable retry link using `Api:PublicBaseUrl`,
 
 The summary agent currently has meeting-scoped tools to read the transcript, full meeting note including frontmatter, assistant context, user notes, glossary, and project files. Every read tool that returns file-like content can read the whole content or a clamped inclusive 1-based line range with `from` and `to`, so the agent can inspect large transcripts incrementally. The assistant context note is the agent's notebook and user-visible context window; the agent can write internal notes, discovered context, missing tool requests, suggested improvements, or follow-up task ideas there using line-based overwrite, replace, and insert modes. Project lookup and search tools are constrained to the projects listed in the meeting note frontmatter:
 
+When assistant context contains cropped screenshot links produced by OCR, the summary instructions tell the agent to include only the most relevant cropped screenshots in the summary and markdown-link them near the related summary text.
+
 - `read_meetingnote`
 - `list_projects`
 - `list_projectfiles`