fix: clarify credential and member id guidance

Author: ysyneu

internal/cli/incident.go

@@ -759,7 +759,7 @@ func newIncidentReassignCmd() *cobra.Command {
 		},
 	}
 
-	cmd.Flags().StringVar(&person, "person", "", "Comma-separated person IDs")
+	cmd.Flags().StringVar(&person, "person", "", "Comma-separated member IDs from 'flashduty member list'")
 	_ = cmd.MarkFlagRequired("person")
 
 	return cmd
@@ -774,8 +774,8 @@ func newIncidentAddResponderCmd() *cobra.Command {
 		Short: "Add responders to an incident",
 		Long: `Add one or more responders to an incident.
 
-Responder IDs are person IDs. Use 'flashduty member list' to find the right
-person ID before running this command. Optional notification flags let you ask
+Responder IDs are member IDs from 'flashduty member list'. Optional
+notification flags let you ask
 FlashDuty to notify added responders through their preferences, explicit
 personal channels, or a template.`,
 		Example: `  flashduty member list --name "Ada"
@@ -816,7 +816,7 @@ personal channels, or a template.`,
 		},
 	}
 
-	cmd.Flags().StringVar(&person, "person", "", "Comma-separated person IDs to add")
+	cmd.Flags().StringVar(&person, "person", "", "Comma-separated member IDs from 'flashduty member list'")
 	cmd.Flags().BoolVar(&followPreference, "follow-preference", false, "Follow each responder's notification preferences")
 	cmd.Flags().StringVar(&notifyChannel, "notify-channel", "", "Comma-separated notification channels, e.g. voice,sms,email")
 	cmd.Flags().StringVar(&templateID, "template-id", "", "Notification template ID")
@@ -945,8 +945,8 @@ func newIncidentWarRoomCreateCmd() *cobra.Command {
 		Long: `Create an incident war room in a configured IM integration.
 
 If --integration is omitted, the CLI uses the first war-room-enabled IM
-integration returned by FlashDuty. Use --member to invite person IDs directly.
-Use 'flashduty member list' to find person IDs. Use --add-observers to also
+integration returned by FlashDuty. Use --member to invite member IDs directly.
+Use 'flashduty member list' to find member IDs. Use --add-observers to also
 invite historical responders selected by FlashDuty.`,
 		Example: `  flashduty incident war-room create inc_123
   flashduty incident war-room create inc_123 --integration 42 --member 101,202
@@ -982,7 +982,7 @@ invite historical responders selected by FlashDuty.`,
 	}
 
 	cmd.Flags().Int64Var(&integrationID, "integration", 0, "IM integration ID; if omitted, first war-room-enabled IM integration is used")
-	cmd.Flags().StringVar(&member, "member", "", "Comma-separated member person IDs to invite")
+	cmd.Flags().StringVar(&member, "member", "", "Comma-separated member IDs to invite")
 	cmd.Flags().BoolVar(&addObservers, "add-observers", false, "Invite historical responders as extra war-room members")
 	return cmd
 }
@@ -1125,9 +1125,8 @@ func newIncidentWarRoomAddMemberCmd() *cobra.Command {
 		Long: `Add members to an existing incident war room by IM chat ID.
 
 This command requires --integration because chat IDs are scoped to an IM
-integration. Member IDs are person IDs. Use 'flashduty member list' to find
-person IDs, and 'flashduty incident war-room list' to find chat and integration
-IDs.`,
+integration. Use 'flashduty member list' to find member IDs, and
+'flashduty incident war-room list' to find chat and integration IDs.`,
 		Example: `  flashduty member list --name "Ada"
   flashduty incident war-room list inc_123
   flashduty incident war-room add-member chat_123 --integration 42 --member 101,202`,
@@ -1155,7 +1154,7 @@ IDs.`,
 	}
 
 	cmd.Flags().Int64Var(&integrationID, "integration", 0, "IM integration ID (required)")
-	cmd.Flags().StringVar(&member, "member", "", "Comma-separated member person IDs (required)")
+	cmd.Flags().StringVar(&member, "member", "", "Comma-separated member IDs (required)")
 	_ = cmd.MarkFlagRequired("integration")
 	_ = cmd.MarkFlagRequired("member")
 	return cmd

internal/cli/zz_generated_incidents.go

@@ -101,7 +101,7 @@ fduty automation fire <trigger-id> \
   --output-format toon
 ```
 
-`--dedup-key` makes retries idempotent for the same trigger. Do not invent a token; if it is missing, ask the user for the token or rotate the trigger token through `update`.
+`--dedup-key` makes retries idempotent for the same trigger. Do not invent a token. If it is missing, rotate the trigger token through `update` or ask the user to provide it through their secure shell/environment, not in chat.
 
 <!-- GENERATED:automation START · 由 fduty __dump-commands 同步 · 勿手改 fence 内 -->
 

skills/flashduty/reference/automation.md

@@ -38,6 +38,7 @@ fduty channel create --channel-name "production-api" --team-id <team-id> \
 # → returns channel_id; use it below
 
 # 3. add an escalation rule (all flags; layers is required via --data)
+# API field `person_ids` expects member IDs from `fduty member list`.
 fduty channel escalate-rule-create \
   --channel-id <channel-id> --rule-name "P1 on-call" --template-id <template-id> \
   --data '{"layers":[{"target":{"person_ids":[<member-id>],"by":{"critical":["voice","sms"],"warning":["feishu"]}},"notify_step":5,"max_times":3,"escalate_window":30}]}'

skills/flashduty/reference/channel.md

@@ -31,7 +31,7 @@ Prereq: `SKILL.md` read. Read verbs are free. **Mutating verbs notify responders
 | resolve with optional note | `resolve <incident-id> [<id2>...]` |
 | snooze / un-snooze | `snooze <id> [<id2>...]` / `wake <incident-id> [<id2>...]` |
 | add comment | `comment <id> [<id2>...]` |
-| add responder by person ID | `add-responder <id>` |
+| add responder by member ID | `add-responder <id>` |
 | replace responder list | `reassign <id>` |
 | merge duplicates (IRREVERSIBLE) | `merge <target_id>` |
 | stop auto-merging alerts in | `disable-merge <incident-id> [<id2>...]` |
@@ -317,10 +317,10 @@ Resolve incident
 - `--resolution` string — Optional resolution note applied to every resolved incident. (≤1024 chars)
 - `--root-cause` string — Optional root cause note applied to every resolved incident. (≤1024 chars)
 
-### responder-add <person-id> [<id2>...]
+### responder-add <member-id> [<id2>...]
 Add incident responder
 - `--incident-id` string (required) — Incident ID (MongoDB ObjectID).
-- `<person-ids>` (positional, required) intSlice — Member IDs to add as responders.
+- `<member-ids>` (positional, required) intSlice — Member IDs from `member list` to add as responders. The API field is named `person_ids`.
 - body-only (`--data`): notify (object)
 
 ### similar <id>
@@ -380,7 +380,7 @@ List incident war rooms
 Add war-room member
 - `<chat-id>` (positional, required) string — Chat ID of the war room within the IM platform.
 - `--integration-id` int64 (required) — IM integration that hosts the war room.
-- `--member-ids` intSlice (required) — Person IDs to add to the war room.
+- `--member-ids` intSlice (required) — Member IDs to add to the war room.
 
 ### war-room-create
 Create war room
@@ -424,7 +424,7 @@ List war rooms
 - **`--list` window cap**: `--since`/`--until` window must be < 31 days; `--limit` max 100. Empty result is authoritative — do not widen filters or retry.
 - **`merge` is irreversible**: source incidents are absorbed into target permanently. Always list and confirm both IDs before running.
 - **`remove --force`** bypasses the interactive confirmation prompt — never pass `--force` unless the user has explicitly said so.
-- **`assign` needs `--data` for the nested `assigned_to` object** (either `person_ids` or `escalate_rule_id`). Pass via `--data '{"incident_ids":["<id>"],"assigned_to":{"person_ids":[101]}}'`. `reassign <id> --person <ids>` is simpler for direct-person assignment.
+- **`assign` needs `--data` for the nested `assigned_to` object** (either `person_ids` or `escalate_rule_id`). Pass member IDs from `member list` in the API field: `--data '{"incident_ids":["<id>"],"assigned_to":{"person_ids":[101]}}'`. `reassign <id> --person <ids>` is simpler for direct member assignment.
 
 ## Worked example