Home search finds every saved meeting, including by speaker name

[r3dbars]

Requested by Justin · project thread

Before: searching on the Meetings page only looked at the ~10 meetings already on screen, and only at their title and date. Searching for last month's meeting or a person's name said "No meetings match your search. Older meetings load with Show more." (the button is actually "Load more", and each click adds only 10).

After: search looks through every saved meeting, by title, date, or speaker name. Results show newest first, 50 at a time, with "Load more" for the rest. While the first pass runs on a big library, the list says "Searching all meetings…" instead of "no matches".

Why

Paper cuts audit item 2 (paper-cuts/audit.md): people search for an old meeting or a person and get told nothing matches.

Product Impact

• Affects: meetings
• Lane: activation
• Why this matters: finding an old meeting is a core reason to keep transcripts around; today search silently misses almost everything.

What changed

• RecentMeetingsScanner.loadSearchIndex lists every saved meeting. Each row comes from, in order: the previous in-memory index (same file stamp), one bulk read of the SQLite metadata cache (RecentMeetingMetadataCache.allRows()), or a transcript parse that then fills the cache. No audio probes; audio is resolved only for the matches shown.
• Speaker names come from the transcript's speaker labels ([System/Alex], [System/[[Alex]]]), dropping the channel prefix, "You", and generic labels ("Speaker 2", "Unknown speaker", "Review later"). They're stored in the Home metadata cache. speakerNames is required on decode, so older cache rows miss once and get reparsed (same pattern as the system-audio verification field).
• New HomeMeetingSearchIndex (Foundation-pure) holds the rows plus a prepared haystack per row, reuses unchanged entries on rebuild, and pages matches. Matching reuses HomeMeetingListFilter so semantics are unchanged (every token, case/diacritic-insensitive).
• HomeViewModel debounces typing (150 ms), runs the search off-main with supersession guards, and rebuilds the index when Home refreshes or captures change on disk. Deleting a meeting drops it from results right away.
• Copy: "Find meetings" (field and toolbar help), "Find Meetings…" (⌘F menu), "No meetings match your search.", "Searching all meetings…".
• Benchmark: HomeRecentCaptureBenchmark now also times the search at 1k and 10k captures (cold index, index from SQLite cache, and warm rebuild+search), checks it finds the oldest meeting, and holds warm rebuild+search to the existing load budget. Uses a private cache file so fixture rows never land in the real cache.

How: the search is a separate in-memory index next to the existing paged Home list, so opening Home stays exactly as fast as before (it still loads only 10). The index is built the first time someone types and then kept warm.

How I checked it

• scripts/dev/agent-preflight.sh
• python3 scripts/dev/check-build-source-lists.py, check-duplicate-declarations.py, bash -n on touched scripts
• bash build.sh --no-open (no Swift toolchain in this session; CI builds it)
• bash run-tests.sh (CI) — new Tests/HomeMeetingSearchIndexTests.swift covers name extraction, the cache-miss-on-old-payload rule, paging, removal, finding a meeting outside the loaded slice by speaker name, and serving rows from cache/previous index without reading the transcript
• Performance budget (CI app-build job runs the Home recent-captures benchmark)
• Manual check: type a name from an old meeting on the Meetings page

Risk Review

• Privacy / local-first behavior reviewed — nothing new leaves the Mac; no analytics payload changes (reuses load_more_meetings)
• Storage path or migration impact reviewed — same cache file; old rows reparse once lazily
• Public-facing copy stays concrete and matches current product scope
• Release/update impact reviewed — none
• No private transcripts, audio, tokens, personal paths, or customer data are included

Notes

The Swift here has not been compiled locally; CI is the first build.

🤖 Generated with Claude Code

https://claude.ai/code/session_017s1xcNJjmfpSS9sjesJfHN

---

Generated by Claude Code