[Meeting Intelligence] Implement Drift Storage Schema & Migrations

[ucguy4u]

Problem

Meeting records, audio metadata, and transcript segments need offline-first database persistence.

Scope

• Create Drift tables (meeting_records, meeting_segments, transcript_chunks, meeting_action_items, meeting_summaries, meeting_audio_metadata).
• Implement migration steps and database schema version bump.

Acceptance Criteria

• Migration tests pass with correct table creation.
• Production repository implementation queries Drift tables correctly.

Estimate

6 hours

[ucguy4u]

Required Before Implementation: Use Cases + Automation Flow

Before coding this ticket, add a deterministic implementation note or child task covering:

• Primary user journey: actor, preconditions, trigger, happy path, success state.
• Alternate/failure paths: offline, missing model, permission denied, runtime/tool failure, cancel/retry, background/foreground.
• Automation flow: Given/When/Then steps, fixtures, mocks/stubs, UI assertions, state/database assertions, notification/tool-trace/memory assertions where relevant.
• Hardening checks: privacy redaction, accessibility, timeout/performance bounds, cleanup/reset.
• Delegation prompt: Ask a QA/test agent to write the automation flow before implementation begins.

Tracker: #323