[wpfleger96]

GET /sessions/{id}/events/match reports 0 matched. It adds the stored timestamp_start to each SNORE event's relative time and compares the result with absolute device times, but timestamp_start is 0.0 on stored analysis results, so nothing lines up. On all 205 analyzed sessions I checked locally it matched nothing, which is the 0 matched and 0% sensitivity on Event Explorer, and it also made every device event a false negative and every SNORE event a false positive.

/waveforms/compare has the right time base but disagrees with it in other ways: it uses any-match false negatives, counts every device event type in machine_event_count, has no matched count, and hardcodes the 5 s tolerance.

This PR makes compare_events the one implementation and deletes /events/match. It now pools apneas and hypopneas on both sides and uses match_events_by_start_time with EVENT_MATCH_TOLERANCE_SECONDS, the batch-validation matcher, so each event is in at most one pair. The result gains matched_events, the name EventValidationResult already uses. Matched and Sensitivity move to the Event Comparison card on the Analysis page, and Event Explorer drops its match section, so it's now a device-only page. The card names its detection mode, follows the mode toggle, loads after a run from the page, and hides when the selected mode has no comparison. compare_events now finds its row through latest_analysis_row.

Removed: /events/match, EventMatchResult, EventService.match_events, get_machine_apnea_hypopnea_times, MATCHABLE_MACHINE_EVENT_TYPES, split_by_tolerance_match, HasStartTime and getEventMatch. convert_machine_events already keeps only the matchable types.

Changes that show up in numbers:

• Sensitivity goes from 0% to its real value. Across 200 analyzed local sessions that's 347 of 1,132 device apneas and hypopneas, about 31%.
• machine_event_count on the card and in snore waveform compare now counts only apneas and hypopneas, so it drops (1,149 to 1,132 on those sessions). The card says so, because the summary card on the same page uses the same label for all device event types.
• False-negative and false-positive totals can shift under one-to-one matching. On those sessions the totals didn't move (785 and 5,289), and new counts equal the old matching logic with the time base corrected on all 205 sessions.
• A missed device hypopnea now reports type H. It used to be unknown, because HypopneaEvent has no event_type.
• snore waveform compare prints the matched count, and its Machine line says "(apneas and hypopneas only)".
• snore analysis Missed and Extra lists are now one-to-one and time-ordered, so they can be longer than before. It still includes RERAs when the device scored them and snore waveform compare doesn't, so the two can differ on those sessions.
• False-positive and false-negative tables now page at 25 rows through a shared TablePager, which Events by Mode uses too.

These local analysis rows are STALE_VERSION, so the exact percentages will move after re-analysis. The sensitivity number is still SNORE's experimental detection scored against device events, not a clinical measurement.

ui/src/tests/experimentalBoundary.test.ts closes the gap the REST test can't see: a default page calling an experimental route. It calls every ui/src/api export against a fake adapter to find the wrappers that hit experimental operations, then scans all of ui/src except api, tests and types. The operation list lives in ui/src/tests/experimentalOperations.json, and EXPERIMENTAL_OPERATIONS reads the same file, so a new tagged route is covered on both sides. cancelAnalysisJob is the one exception, since ImportView needs it and it reads no metrics.

No migration, re-analysis, re-parse or recompute-days is needed.

Stack: #439 → #440 → this PR

[wpfleger96]

Screenshots

Event Comparison card

Matched and Sensitivity now sit on the Analysis page, under its page-level experimental banner. A missed device hypopnea shows H instead of unknown. Values here are mock data. Mobile below.

Event Explorer

The match section is gone, so the page shows device-scored events only.