fix(cli): state the 100-row server cap in alert/alert-event --limit flag help

The alert list and alert-event list endpoints reject limit > 100 with
InvalidParameter. incident list already documents the cap in its --limit
flag help; mirror the same wording so the Flags section alone is enough
to get the first call right (the long description mentions the cap, but
--help readers who grep Flags never see it).

Author: ysyneu

internal/cli/alert.go

@@ -111,7 +111,7 @@ func newAlertListCmd() *cobra.Command {
 	cmd.Flags().BoolVar(&muted, "muted", false, "Show ever-muted only")
 	cmd.Flags().StringVar(&since, "since", "24h", "Start time")
 	cmd.Flags().StringVar(&until, "until", "now", "End time")
-	cmd.Flags().IntVar(&limit, "limit", 20, "Max results")
+	cmd.Flags().IntVar(&limit, "limit", 20, "Max results (max 100)")
 	cmd.Flags().IntVar(&page, "page", 1, "Page number")
 	cmd.Flags().StringVar(&fields, "fields", "", "Comma-separated fields to project in json/toon output (e.g. alert_id,title,alert_severity,created_at); ignored in table mode. Use to avoid dumping the full nested record.")
 

internal/cli/alert_event.go

@@ -104,7 +104,7 @@ func newAlertEventListCmd() *cobra.Command {
 	cmd.Flags().StringVar(&integrationType, "integration-type", "", "Comma-separated integration types")
 	cmd.Flags().StringVar(&since, "since", "1h", "Start time")
 	cmd.Flags().StringVar(&until, "until", "now", "End time")
-	cmd.Flags().IntVar(&limit, "limit", 20, "Max results")
+	cmd.Flags().IntVar(&limit, "limit", 20, "Max results (max 100)")
 	cmd.Flags().IntVar(&page, "page", 1, "Page number")
 	cmd.Flags().StringVar(&fields, "fields", "", "Comma-separated fields to project in json/toon output (e.g. event_id,alert_id,event_severity,event_status,event_time,title); ignored in table mode. Defaults to these compact event fields. Long strings are truncated as needed to keep structured output below 16 KiB.")