Warm up pyannote and FunASR runtimes

openspec/specs/meeting-transcription/spec.md

@@ -27,6 +27,8 @@ For real meeting recordings, Meeting Assistant SHALL derive the requested speake
 
 The configured pipeline SHALL receive audio chunks as they are captured rather than requiring the recording coordinator to finish a complete meeting audio file first.
 
+On application startup, Meeting Assistant SHALL start non-blocking warm-up for the default launch profile's speech recognition pipeline and for any named launch profile that selects the managed FunASR provider.
+
 #### Scenario: Streaming provider receives live audio
 - **WHEN** recording mode is active and the combined audio source emits a chunk
 - **THEN** Meeting Assistant can pass that chunk to the configured speech recognition pipeline before the audio source completes
@@ -63,6 +65,16 @@ The configured pipeline SHALL receive audio chunks as they are captured rather t
 - **WHEN** a meeting note has zero or one entry in `attendees`
 - **THEN** Meeting Assistant leaves the finished-transcript speaker count hint unset
 
+#### Scenario: Launch profile FunASR pipeline warms on startup
+- **GIVEN** a named launch profile selects `funasr`
+- **WHEN** Meeting Assistant starts
+- **THEN** it begins warming that profile's speech recognition pipeline without blocking startup
+
+#### Scenario: Non-default non-FunASR profile is not warmed
+- **GIVEN** a named launch profile selects a provider other than `funasr`
+- **WHEN** Meeting Assistant starts
+- **THEN** it does not create a startup warm-up pipeline for that named profile
+
 ### Requirement: Version 1 keeps local Whisper transcription available
 Meeting Assistant SHALL provide a local Whisper speech recognition pipeline as a fallback ASR backend for version 1.
 
@@ -471,6 +483,8 @@ If pyannote secondary validation cannot confirm that the unknown live sample and
 
 When pyannote secondary validation is disabled, Meeting Assistant SHALL preserve the primary identity matching behavior.
 
+When pyannote secondary validation is enabled, Meeting Assistant SHALL start a non-blocking startup warm-up that builds or verifies the configured pyannote runtime image and downloads the configured model into the persistent model cache before the first validation request when possible.
+
 #### Scenario: Multi-speaker sample is rejected
 - **GIVEN** pyannote secondary validation is enabled
 - **WHEN** pyannote reports multiple speakers in a candidate sample
@@ -486,3 +500,9 @@ When pyannote secondary validation is disabled, Meeting Assistant SHALL preserve
 - **GIVEN** pyannote secondary validation is disabled
 - **WHEN** the primary identity matcher confirms `Guest03` as `Chris`
 - **THEN** Meeting Assistant accepts the match without running pyannote secondary validation
+
+#### Scenario: Pyannote validation warms up on startup
+- **GIVEN** pyannote secondary validation is enabled
+- **WHEN** Meeting Assistant starts
+- **THEN** it begins preparing the configured pyannote runtime image and model cache without waiting for the first validation request
+- **AND** application startup is not blocked by the warm-up task