Manuel/meeting-assistant
Public Access
1
0
Fork 0
Code Issues Pull Requests 4 Actions Packages Projects Releases Wiki Activity Open in Coder

Archive summary refinements and profile switching
PR and Push Build/Test / build-and-test (push) Successful in 6m37s
Details

Browse Source
This commit is contained in:
codex
2026-05-27 23:11:21 +02:00
parent c12febe029
commit 7777b349a5
37 changed files with 3190 additions and 121 deletions
Download Patch File Download Diff File Expand all files Collapse all files
openspec/specs/meeting-recording/spec.md
+34
View File
@@ -107,3 +107,37 @@ Meeting Assistant SHALL use the selected launch profile's summary-agent settings
- **GIVEN** two launch profiles configure the same toggle hotkey
- **WHEN** Meeting Assistant resolves launch profiles
- **THEN** Meeting Assistant rejects the configuration before registering global hotkeys
### 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