Archive summary refinements and profile switching

2026-05-27 23:11:21 +02:00
parent c12febe029
commit 7777b349a5
37 changed files with 3190 additions and 121 deletions
@@ -0,0 +1,14 @@
+# Change: Switch transcription profile during an active meeting
+
+## Why
+Meetings can change spoken language or transcription requirements without being separate meetings. The user needs to switch from one launch profile to another during an active recording, for example from German to English, without creating new meeting artifacts or prematurely starting summarization.
+
+## What Changes
+- Profile hotkeys pressed during active recording switch the active meeting to that profile instead of stopping and summarizing the meeting.
+- Switching keeps the current meeting note, transcript, assistant context, summary path, and metadata.
+- Switching stops and drains the current speech recognition pipeline, buffers captured audio while the old pipeline drains, inserts a transcript marker, clears run-local speaker label mappings, and starts a new speech recognition pipeline using the requested profile options.
+- The final stop after one or more switches still summarizes once for the same meeting.
+
+## Impact
+- Affects recording coordinator lifecycle, launch-profile hotkey semantics, live transcription buffering, speaker mapping lifecycle, and transcript output.
+- Adds behavior tests for profile switching without metadata recollection or new artifacts.
@@ -0,0 +1,34 @@
+## ADDED Requirements
+### Requirement: Active recording can switch launch profiles
+Meeting Assistant SHALL allow a launch profile hotkey or named-profile recording toggle request to switch the active meeting to that profile while recording capture is active.
+
+When switching profiles during an active meeting, Meeting Assistant SHALL keep the existing meeting note, transcript, assistant context, summary path, user notes, calendar metadata, projects, attendees, and assistant-context state.
+
+When switching profiles during an active meeting, Meeting Assistant SHALL NOT create new meeting artifacts, SHALL NOT collect calendar metadata again, and SHALL NOT run the summary pipeline for the old profile segment.
+
+When switching profiles during an active meeting, Meeting Assistant SHALL stop and drain the current speech recognition pipeline, append a transcript marker indicating the target profile, start a new speech recognition pipeline using the target profile's resolved options, and continue writing live transcription to the same transcript file.
+
+When audio is captured while the old speech recognition pipeline is draining, Meeting Assistant SHALL buffer that audio and send it to the new profile's speech recognition pipeline after it is ready.
+
+When switching profiles during an active meeting, Meeting Assistant SHALL clear run-local speaker label mappings for future transcript segments because backend speaker IDs can change across speech recognition processes. Already-written named transcript segments SHALL remain unchanged.
+
+#### Scenario: Active meeting switches to named profile
+- **GIVEN** a meeting was started with the default launch profile
+- **WHEN** the user triggers launch profile `english` while recording is active
+- **THEN** Meeting Assistant keeps the existing meeting artifacts
+- **AND** drains the old speech recognition pipeline without running summary generation
+- **AND** appends a transcript marker for the profile switch
+- **AND** starts transcription with the resolved `english` profile
+- **AND** continues writing transcript segments to the same transcript file
+
+#### Scenario: Captured audio is buffered while switching
+- **GIVEN** a meeting is switching from one launch profile to another
+- **WHEN** audio chunks are captured before the new speech recognition pipeline is ready
+- **THEN** Meeting Assistant buffers those chunks
+- **AND** sends the buffered chunks to the new speech recognition pipeline after it starts
+
+#### Scenario: Switching clears future speaker mappings only
+- **GIVEN** a live speaker label was mapped to a named speaker before switching profiles
+- **WHEN** Meeting Assistant switches to another launch profile
+- **THEN** already-written transcript text keeps the named speaker
+- **AND** later transcript segments from the new pipeline do not reuse the old backend speaker label mapping
@@ -0,0 +1,11 @@
+## ADDED Requirements
+### Requirement: Speech recognition can be restarted within one meeting
+Meeting Assistant SHALL support replacing the active speech recognition pipeline for a recording run while preserving the run's meeting artifacts and transcript session.
+
+The replacement speech recognition pipeline SHALL use the target launch profile's resolved transcription options.
+
+#### Scenario: Replacement pipeline uses target profile options
+- **GIVEN** a recording run started with one launch profile
+- **WHEN** the active transcription profile is switched to another launch profile
+- **THEN** the new speech recognition pipeline is created from the target profile options
+- **AND** it receives audio captured after the switch request and audio buffered during the switch
@@ -0,0 +1,8 @@
+## 1. Implementation
+- [x] 1.1 Add behavior tests for switching from default to named launch profile during an active recording.
+- [x] 1.2 Keep existing meeting artifacts and skip metadata recollection when switching profile.
+- [x] 1.3 Drain the old speech recognition pipeline without moving to summarizing.
+- [x] 1.4 Buffer captured audio during the switch and feed it to the new profile pipeline.
+- [x] 1.5 Append a transcript marker when the profile changes.
+- [x] 1.6 Clear run-local speaker label mappings for the new transcription process.
+- [x] 1.7 Update README and run focused/full tests plus `openspec validate switch-transcription-profile --strict`.