meeting-assistant/openspec/changes/unify-pyannote-validation-toggle/tasks.md

1. Single-toggle behavior

• 1.1 Add a failing behavior test proving enabled speaker validation invokes pyannote without a nested enable setting
• 1.2 Introduce toggle-free speaker-validation runtime options and make the validator use them
• 1.3 Add or update behavior coverage proving disabled validation bypasses pyannote and enabled validation warms the runtime
• 1.4 Keep application-level validation and warm-up consistent when named launch profiles contain speaker-validation overrides

2. Configuration migration

• 2.1 Remove the nested speaker-validation diarization toggle from canonical configuration and document the outer toggle as authoritative

3. Verification

• 3.1 Run focused speaker validation, warm-up, and pyannote finalizer tests
• 3.2 Run the full solution test suite and validate the OpenSpec change strictly