refactor(cli): drop webhook/api from autopilot trigger-add

These trigger kinds exist in the DB schema but nothing on the server
fires them:

- autopilot_scheduler.ClaimDueScheduleTriggers filters kind='schedule'
  (pkg/db/queries/autopilot.sql:150)
- DispatchAutopilot is reached only from the scheduler (source:schedule)
  or POST /api/autopilots/{id}/trigger (source:manual); no inbound
  webhook or api endpoint exists
- The UI only surfaces schedule creation

Exposing them in the CLI lets users create triggers that sit in the DB
doing nothing. Drop --kind from trigger-add, require --cron, always
send kind=schedule. Re-add the flag when the server grows a dispatch
path for the other kinds.

CLI_AND_DAEMON.md

@@ -496,15 +496,16 @@ multica autopilot runs <id>
 multica autopilot runs <id> --limit 50 --output json
 ```
 
-### Triggers (Schedule / Webhook / API)
+### Schedule Triggers
 
 ```bash
-multica autopilot trigger-add <autopilot-id> --kind schedule --cron "0 9 * * 1-5" --timezone "America/New_York"
-multica autopilot trigger-add <autopilot-id> --kind webhook
+multica autopilot trigger-add <autopilot-id> --cron "0 9 * * 1-5" --timezone "America/New_York"
 multica autopilot trigger-update <autopilot-id> <trigger-id> --enabled=false
 multica autopilot trigger-delete <autopilot-id> <trigger-id>
 ```
 
+Only cron-based `schedule` triggers are currently exposed via the CLI. The data model also defines `webhook` and `api` kinds, but there is no server endpoint that fires them yet, so they're not surfaced here.
+
 ## Other Commands
 
 ```bash

server/cmd/multica/cmd_autopilot.go

@@ -68,7 +68,7 @@ var autopilotRunsCmd = &cobra.Command{
 
 var autopilotTriggerAddCmd = &cobra.Command{
 	Use:   "trigger-add <autopilot-id>",
-	Short: "Add a trigger (schedule/webhook/api) to an autopilot",
+	Short: "Add a schedule trigger to an autopilot",
 	Args:  exactArgs(1),
 	RunE:  runAutopilotTriggerAdd,
 }
@@ -138,10 +138,9 @@ func init() {
 	autopilotRunsCmd.Flags().Int("offset", 0, "Pagination offset")
 	autopilotRunsCmd.Flags().String("output", "table", "Output format: table or json")
 
-	// trigger-add
-	autopilotTriggerAddCmd.Flags().String("kind", "", "Trigger kind: schedule, webhook, or api (required)")
-	autopilotTriggerAddCmd.Flags().String("cron", "", "Cron expression (required for kind=schedule)")
-	autopilotTriggerAddCmd.Flags().String("timezone", "", "IANA timezone for schedule (default UTC)")
+	// trigger-add — only schedule triggers are supported end-to-end today
+	autopilotTriggerAddCmd.Flags().String("cron", "", "Cron expression (required)")
+	autopilotTriggerAddCmd.Flags().String("timezone", "", "IANA timezone (default UTC)")
 	autopilotTriggerAddCmd.Flags().String("label", "", "Optional human-readable label")
 	autopilotTriggerAddCmd.Flags().String("output", "json", "Output format: table or json")
 
@@ -470,21 +469,18 @@ func runAutopilotTriggerAdd(cmd *cobra.Command, args []string) error {
 		return err
 	}
 
-	kind, _ := cmd.Flags().GetString("kind")
-	if kind == "" {
-		return fmt.Errorf("--kind is required (schedule, webhook, or api)")
-	}
-	if kind != "schedule" && kind != "webhook" && kind != "api" {
-		return fmt.Errorf("--kind must be schedule, webhook, or api")
-	}
+	// Only schedule triggers are dispatched end-to-end today. The server
+	// schema also defines "webhook" and "api" kinds, but no inbound endpoint
+	// fires them — they'd sit in the DB forever. Re-add kind selection here
+	// when those paths are implemented.
 	cron, _ := cmd.Flags().GetString("cron")
-	if kind == "schedule" && cron == "" {
-		return fmt.Errorf("--cron is required for kind=schedule")
+	if cron == "" {
+		return fmt.Errorf("--cron is required")
 	}
 
-	body := map[string]any{"kind": kind}
-	if cron != "" {
-		body["cron_expression"] = cron
+	body := map[string]any{
+		"kind":            "schedule",
+		"cron_expression": cron,
 	}
 	if v, _ := cmd.Flags().GetString("timezone"); v != "" {
 		body["timezone"] = v