Auto-record did not trigger for most Outlook events with Teams URLs #218

Description

On a day with 5 Outlook events (each with a Microsoft Teams join URL), calendar-driven auto-record fired for only 1 of 5 (the first event of the day). The other 4 had to be started manually, despite identical event structure and active meeting signals (camera + mic in Teams).

Reproduction

Setup as in #216 (Office 365 / Exchange calendar via macOS Internet Accounts). Ensure auto_record_meetings = true.

Observation

• Event Nemotron Streaming RNNT: CoreML decode produces empty transcripts #1 (08:00) — auto-record triggered ✅
• Events Update freedspeech.xyz landing page #2–Help wanted: Optimize Qwen3 ASR decoder speed via batch decoding #5 — no auto-record fired; each had to be manually started

All events had:

• Valid Outlook calendar entries (organizer, attendees, Teams URL in body)
• Camera + mic active in Teams during the meeting
• Teams app foregrounded for parts of the meeting

Hypothesis

This likely cascades from #216 (calendar event matching unreliable). If currentOrNearbyEvent() returns nil after the first successful match, the calendar-driven trigger never fires for subsequent events. The camera-based fallback path (MeetingDetector + BrowserMeetingActivityCollector) does not appear to pick up the slack for Teams meetings either.

Suggested investigation order

Resolve #216 first; this one likely improves as a side-effect. If after fixing #216 there are still events where auto-record does not fire even though the calendar match succeeds, investigate the trigger logic in MuesliController / wherever the auto-record decision is made.

Environment

• Muesli v0.7.0
• macOS 26.5 (arm64)
• Office 365 (Exchange) calendar via Internet Accounts
• auto_record_meetings = true
• All 5 events on the user's primary calendar, not disabled