You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(mcp): correct monitor forecast pagination, coupling parity, and notes (TG-1092)
Addresses review findings on the forecast work:
- Render the forecast only on the first page — it is forward-looking and
page-independent, but its anchor (the latest event) was read from the current
page, producing a stale forecast on page >= 2.
- Match the dashboard's coupled-forecast precondition: a freshness-coupled
Volume/Metric monitor with no configured tolerance has no band on either
surface (it was entering the coupled path on the coupling flag alone).
- Resolve schedule holidays only after the next-update-window guards pass,
restoring the dashboard's short-circuit (no calendar work for non-Prediction
monitors); next_update_window now takes the test suite.
- Exclude Error-status freshness events from the next-update anchor, matching
the dashboard.
- Use an accurate note when a forecast is absent for a non-training reason
(elapsed window / no baseline) instead of telling a trained monitor to keep
training.
- Fix the dashboard unit test that imported the relocated forecast helper
(this broke the Python Tests CI job), and add coverage for the
coupled-without-tolerance case.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
0 commit comments