Archive summary refinements and profile switching

openspec/specs/meeting-transcription/spec.md

@@ -201,6 +201,14 @@ Each speaker identity SHALL store a last-modified timestamp used by active-age f
 
 The configured maximum snippet count per identity SHALL prevent unbounded growth.
 
+Live speaker matching SHALL be read-only with respect to the speaker identity database. Candidate elimination, canonical promotion, transcription counters, stored snippet updates, and new unmatched identity creation SHALL happen only after transcription is finished and after automatic summary generation has completed, using the latest meeting note frontmatter.
+
+When the summary agent records a speaker override from a diarized transcript label to a named speaker, final speaker identity processing SHALL attach the current run speaker sample to an existing identity with that name when one exists, or create a new canonical speaker identity with that name when none exists.
+
+When a speaker override maps a current-run unnamed candidate to an existing named identity, Meeting Assistant SHALL merge the candidate's meeting reference and useful snippets into the named identity instead of leaving a duplicate candidate.
+
+When the summary agent records that a speaker identity was wrongfully matched, final speaker identity processing SHALL delete the matching identity from the local speaker identity database so it cannot be matched again unless it is newly created in the future.
+
 #### Scenario: Unknown speaker is learned from meeting attendees
 - **WHEN** a finished transcript contains an unmatched diarized speaker and the meeting note has attendees
 - **THEN** Meeting Assistant stores a new unnamed speaker identity with candidate names from the attendees that were not already matched in that meeting
@@ -214,6 +222,32 @@ The configured maximum snippet count per identity SHALL prevent unbounded growth
 - **WHEN** Meeting Assistant creates, identifies, updates candidates for, stores snippets for, stores references for, or merges a speaker identity
 - **THEN** Meeting Assistant updates that identity's last-modified timestamp
 
+#### Scenario: Final speaker identity learning uses summary-refined attendees
+- **GIVEN** the summary agent changes meeting note attendees during automatic summary generation
+- **WHEN** Meeting Assistant performs final speaker identity learning and candidate creation
+- **THEN** it uses the attendee list from the meeting note after the summary agent changes
+
+#### Scenario: Speaker override attaches to existing identity
+- **GIVEN** the speaker identity database contains canonical speaker `Sabrina`
+- **AND** the summary agent records that transcript speaker `Guest-01` is `Sabrina`
+- **WHEN** final speaker identity processing runs
+- **THEN** Meeting Assistant stores the meeting reference and current speaker sample on Sabrina's identity
+- **AND** does not create a separate unnamed candidate for `Guest-01`
+
+#### Scenario: Speaker override creates named identity
+- **GIVEN** the speaker identity database has no accepted name `Sabrina`
+- **AND** the summary agent records that transcript speaker `Guest-01` is `Sabrina`
+- **WHEN** final speaker identity processing runs
+- **THEN** Meeting Assistant creates a canonical speaker identity named `Sabrina`
+- **AND** stores the meeting reference and current speaker sample on that identity
+
+#### Scenario: Speaker identity deletion removes a wrong match
+- **GIVEN** the speaker identity database contains canonical speaker `Sabrina`
+- **AND** the summary agent records that `Sabrina` was wrongfully matched
+- **WHEN** final speaker identity processing runs
+- **THEN** Meeting Assistant removes Sabrina's identity from the speaker identity database
+- **AND** the relabeled transcript uses `Removed-1` instead of `Sabrina`
+
 ### Requirement: Speaker identities can be merged diagnostically
 Meeting Assistant SHALL expose a diagnostic endpoint that merges duplicate speaker identities.
 
@@ -317,7 +351,7 @@ Meeting Assistant SHALL run live matching incrementally at the configured interv
 
 When a speaker is matched during transcription, Meeting Assistant SHALL rewrite already-written live transcript segments for that diarized speaker and write future transcript segments using the canonical name.
 
-Live speaker matching SHALL be read-only with respect to the speaker identity database. Candidate elimination, canonical promotion, transcription counters, stored snippet updates, and new unmatched identity creation SHALL happen only after transcription is finished, using the latest meeting note frontmatter.
+Live speaker matching SHALL be read-only with respect to the speaker identity database. Candidate elimination, canonical promotion, transcription counters, stored snippet updates, and new unmatched identity creation SHALL happen only after transcription is finished and after automatic summary generation has completed, using the latest meeting note frontmatter.
 
 For backends that only provide diarization after finalization, Meeting Assistant SHALL defer speaker identity matching until finished diarization is available, extract candidate snippets from the completed temporary recording, complete identity matching, and only then allow summary generation to start.
 
@@ -391,3 +425,13 @@ When the Azure live streaming backend uses `ConversationTranscriber`, Meeting As
 - **WHEN** `AzureSpeech.PostProcessingOption` is empty
 - **THEN** Meeting Assistant does not set a post-processing option on the Azure Speech SDK configuration
 
+### 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