Coordination plan: assign the synthetic meeting fixture

Co-Authored-By: Claude Opus 5.5 <[email protected]>

docs/plans/001-0-coordination.md

@@ -40,6 +40,11 @@ The integrator merges in this order, rebasing/fixing up each onto the result of
   `transcribeLongForm(audio: Float32Array, deps: LongFormDeps, options: LongFormOptions): Promise<LongFormResult>`
   where `LongFormOptions` includes `language?: string`, `task?: WhisperTask`, and `prompt?: string`
   (accepted and passed to every decode even before workstream 2 lands — a no-op when undefined).
+- **Synthetic meeting stand-in** (workstream 3 owns it): a test helper that builds it at test time
+  from the existing clips — `tests/meetingFixture.ts` exporting
+  `buildMeetingFixture(): Promise<{ audio: Float32Array; reference: string }>` (16 kHz mono; clips
+  joined with 2–8 s silences, `en_alien` excerpts included). Other workstreams may import it after
+  merge; before that they measure on the plain clips.
 - Parakeet (workstream 7) selects its engine from a catalog field it adds:
   `family?: "whisper" | "parakeet"` (absent ⇒ `"whisper"`), so existing entries need no edit.