Upload flow UI, meeting list correctness, processing states, meeting detail CRUD, and finalized meeting view for the upload-finalizes-meeting milestone.

Slice 3: App — Upload Entry Point and Finalized Meeting View

Owner: App engineer Domain: App Complexity: M Prerequisite: Slice 1 merged and ./dev gen all run

Delivers the complete user-facing path from audio upload to finalized meeting view. Also covers the correctness of the meeting list — including search, the full card data set, and CRUD actions on the meeting detail. No live recording capability is required or included.

Required Capabilities

Upload Entry Point

Expand the "New Meeting" button into a dropdown with two options: Upload Recording and Start Live Recording (disabled/hidden for this milestone — enabled in milestone 2)
Upload flow: file picker accepting audio/webm, audio/mp4, audio/m4a, audio/wav, audio/mpeg; on file selection, call POST /meetings then POST /meetings/{id}/audio; show upload progress bar while the multipart request is in flight

Processing State (WebSocket-driven, no polling)

After upload completes, navigate to the meeting detail page and subscribe to EntityChangedEvent { entity: "transcription" } over the existing WebSocket connection; on receipt, re-fetch GET /transcriptions/{id} via SWR invalidation to advance the processing indicator
Render a processing indicator that maps transcription.status to the four visible states: pending → transcribing → synthesizing → completed
Failed state: when transcription.status === "failed", show the status_message from Core and provide a clear CTA (retry upload or contact support)
Page state persists on refresh: a meeting in transcribing state still shows the correct indicator after a hard reload (derived from REST, not in-memory WebSocket state)

Meeting List

Title — primary label on every card; truncated gracefully at narrow widths
Date and time — grouped by day (Today / Yesterday / weekday + date for older); time shown as h:mm a
Attendee badges — stacked avatar initials for up to 3 attendees; +N overflow badge when more than 3 are present; no attendees renders gracefully (empty state, not an error)
Headline — displayed beneath the title when meeting.headline is present; omitted (no placeholder text) when absent
Source type indicator — icon distinguishing upload, live recording, text, and notes entries
Processing badge — shown when transcription.status is pending, transcribing, or synthesizing; resolved (badge removed) when EntityChangedEvent { entity: "transcription" } arrives and status becomes completed or failed; badge label reflects the current status, not a generic "Processing" string
Search — text input filters the visible meeting list client-side by title and headline; clearing the input restores the full list; search state is not persisted to the URL for this milestone

Meeting Detail — Edit and Delete

Edit title — title in the detail header is inline-editable for non-live meetings; on blur or Enter, call PATCH /meetings/{id} with { title }; optimistic update with revert on error; success does not show a toast (consistent with existing live recording behaviour)
Delete meeting — a delete action is accessible from the meeting detail (e.g. overflow menu or dedicated button); triggers a confirmation dialog before calling DELETE /meetings/{id}; on confirm, navigate back to the meeting list; on cancel, dismiss the dialog without any mutation
Deletion of a meeting that has an active recording must be blocked: show an explanatory error (409 from Core) rather than optimistically removing the item

Meeting Detail — Finalized Content

Overview tab: render headline, summary, and tasks once transcription.status === "completed"; notes textarea is always visible regardless of processing state; trigger re-fetch of summary and tasks on SynthesisUpdatedEvent
Transcript tab: render transcript_segments (speaker label + timestamp per segment), topics (sidebar navigation and inline), and talking points (per topic) once processing completes; trigger a full segment list reload on TranscriptRevisedEvent; trigger topics and talking points re-fetch on SynthesisUpdatedEvent

Dependencies

Core Slice 1 merged; ./dev gen all run so the generated API client and types are current
Existing WebSocket provider (WebSocketProvider) and SWR cache invalidation infrastructure

UI States

State	Trigger	What the user sees
Uploading	File selected, requests in flight	Progress bar; "Uploading…" label
Pending	`transcription.status === "pending"`	Badge: "Pending"
Transcribing	`transcription.status === "transcribing"`	Badge + spinner: "Transcribing"
Synthesizing	`transcription.status === "synthesizing"`	Badge + spinner: "Generating insights"
Completed	`transcription.status === "completed"`	No processing badge; full artefacts rendered
Failed	`transcription.status === "failed"`	Error message from `status_message`; retry CTA

Test Cases

Test cases map to tests/bets/meeting-recording/test_slice_app_upload_finalizes_meeting.py. Run via ./dev test bet meeting-recording.

Upload flow

Test	Location	Assertion
"New Meeting" dropdown renders Upload option	`test_app`	Dropdown contains an "Upload Recording" item
File upload calls `POST /meetings` then `POST /meetings/{id}/audio`	`test_app`	Both requests fired in order; audio request is multipart
Upload progress indicator visible	`test_app`	Progress element rendered while audio POST is in flight

Processing state

Test	Location	Assertion
`pending` status shows correct badge label	`test_app`	Badge text is "Pending", not a generic "Processing" string
`transcribing` status shows correct badge label	`test_app`	Badge text is "Transcribing" with spinner
`synthesizing` status shows correct badge label	`test_app`	Badge text is "Generating insights" with spinner
`EntityChangedEvent` clears badge on completion	`test_app`	Receiving `{ entity: "transcription", action: "updated" }` triggers re-fetch; badge absent when status is `completed`
Failed state renders `status_message`	`test_app`	Error text matches `status_message` from Core fixture
Processing state survives page refresh	`test_app`	Hard reload of a `transcribing` meeting renders processing indicator via REST, not WS state

Meeting list — card fields

Test	Location	Assertion
Meeting title rendered	`test_app`	Card heading matches `meeting.title`
Date grouping: today	`test_app`	Meeting from today grouped under "Today"
Date grouping: yesterday	`test_app`	Meeting from yesterday grouped under "Yesterday"
Date grouping: older	`test_app`	Meeting from last week grouped under weekday + date label
Time rendered correctly	`test_app`	Time shown in `h:mm a` format
Attendee badges render initials	`test_app`	Avatar shows correct initials for each attendee
Attendee overflow badge shown	`test_app`	4 attendees renders 3 avatars + "+1" badge
No attendees renders gracefully	`test_app`	Card renders without error when `attendees` is empty
Headline shown when present	`test_app`	`meeting.headline` text visible on card
Headline omitted when absent	`test_app`	No empty placeholder shown when `headline` is null
Source type icon correct for upload	`test_app`	FileAudio icon rendered for `source_type: "upload"`
Processing badge shown for `transcribing`	`test_app`	Badge visible on list card while status is `transcribing`
Processing badge removed on completion	`test_app`	Badge absent after `EntityChangedEvent` advances status to `completed`

Meeting list — search

Test	Location	Assertion
Search input renders on meeting list	`test_app`	Input element present in the meeting list toolbar
Search filters by title	`test_app`	Typing a title substring hides non-matching meetings
Search filters by headline	`test_app`	Typing a headline substring hides non-matching meetings
Clearing search restores full list	`test_app`	Clearing the input shows all meetings again
Empty search result shows empty state	`test_app`	No-match query renders a "No meetings found" message, not a blank list

Meeting detail — edit and delete

Test	Location	Assertion
Title is editable inline	`test_app`	Clicking title enters edit mode (input or contenteditable)
Title edit calls `PATCH /meetings/{id}`	`test_app`	`PATCH` called with `{ title: "new value" }` on blur
Title reverts on API error	`test_app`	Optimistic title change rolls back when PATCH returns an error
Delete action is reachable	`test_app`	Delete button/menu item present in the detail header or overflow menu
Delete shows confirmation dialog	`test_app`	Clicking delete renders a confirmation modal before any mutation
Confirming delete calls `DELETE /meetings/{id}`	`test_app`	DELETE request fired after user confirms; navigates to meetings list
Cancelling delete fires no request	`test_app`	No DELETE request if user dismisses the confirmation dialog
Delete blocked on active recording	`test_app`	`409` response renders an error message; meeting is not removed from the list

Meeting detail — finalized content

Test	Location	Assertion
Overview tab renders headline and summary	`test_app`	Both fields visible when `transcription.status === "completed"`
Overview tab renders tasks	`test_app`	Task list non-empty after system task reconciliation
Overview tab does not render topics or talking points	`test_app`	No topic or talking point elements present on the Overview tab
Notes textarea visible regardless of processing state	`test_app`	Textarea rendered on a meeting still in `transcribing` state
`SynthesisUpdatedEvent` triggers summary and task re-fetch	`test_app`	Overview re-fetches `GET /meetings/{id}/synthesis` and `GET /meetings/{id}/tasks` on receiving `meeting.synthesis.updated.v1`
Transcript tab renders segments with speaker labels	`test_app`	Each segment shows `speaker_label` and `start_ms` timestamp
Transcript tab renders topics	`test_app`	At least one topic visible in the transcript view after synthesis
Transcript tab renders talking points per topic	`test_app`	Talking points appear under their parent topic in the transcript view
`TranscriptRevisedEvent` triggers full segment reload	`test_app`	Transcript tab re-fetches `GET /transcriptions/{id}/segments` on receiving `transcript.revised.v1`
`SynthesisUpdatedEvent` triggers topics and talking points re-fetch on transcript tab	`test_app`	Transcript tab re-fetches topics and talking points on receiving `meeting.synthesis.updated.v1`

End-to-end

Test	Location	Assertion
Full upload-to-finalized flow	`test_system`	User uploads file → processing indicator shown → transcript populated → overview populated

Completion Checklist

Code merged and deployed
Bet progress tests pass (./dev test bet meeting-recording)
Permanent service tests implemented per testing strategy
Code review completed
API review completed (if new or modified API surfaces)
Testing review completed
System documentation updated (architecture docs, API reference, data flows as applicable)

App — Upload Entry Point and Finalized Meeting View

On this page