Get the monitor detail page's analytics panel data for a check

The response shape forks entirely on monitor_type, matching the dashboard detail page's own fork: an http monitor has no run-duration baseline (it has no "run" at all — just probes), and a heartbeat/ci monitor has no probe-derived uptime, so the two kinds never carry each other's fields.

• kind: "http" — 90-day probe-derived uptime (uptime_90d, null when the monitor has no probe results at all in the window — a real gap, never coerced to a percentage) and up to 30 recent latency samples, oldest first.
• kind: "runs" — the run-duration baseline (baseline: the archived one when the monitor has an archived day, else a live one from its measured runs in the last 30 days once there are at least 5; null before either exists) and a week-over-week trend sentence (trend, null unless both the last-7-days and prior-7-days windows have at least 3 measured runs each — below that a percentage change is noise dressed as a fact).

404 if the check does not exist in the authenticated project (no existence oracle).

Console stability note. This response is shaped by a console screen: the fields are the ones that screen draws, in the grouping it draws them in. It stays published because reading it is a reasonable thing to automate, and no field will be removed or change meaning without a version. Fields may be ADDED as the screen grows, so treat unknown keys as normal rather than as an error.