chore: sync main into the alert integrations branch

api-reference/on-call.openapi.en.json

@@ -30374,13 +30374,14 @@
           },
           "change_status": {
             "type": "string",
-            "description": "Lifecycle status of the change event, reported by the change source as execution progresses.\n| Value | Meaning |\n|---|---|\n| `Planned` | Planned, not started. |\n| `Ready` | Ready for execution. |\n| `Processing` | Being executed. |\n| `Canceled` | Canceled. |\n| `Done` | Completed. |",
+            "description": "Lifecycle status of the change event, reported by the change source as execution progresses.\n| Value | Meaning |\n|---|---|\n| `Planned` | Planned, not started. |\n| `Ready` | Ready for execution. |\n| `Processing` | Being executed. |\n| `Canceled` | Canceled. |\n| `Done` | Completed. |\n| `Failed` | Failed. |",
             "enum": [
               "Planned",
               "Ready",
               "Processing",
               "Canceled",
-              "Done"
+              "Done",
+              "Failed"
             ]
           },
           "link": {
@@ -30468,13 +30469,14 @@
           },
           "change_status": {
             "type": "string",
-            "description": "Current lifecycle status of the change.\n| Value | Meaning |\n|---|---|\n| `Planned` | Planned, not started. |\n| `Ready` | Ready for execution. |\n| `Processing` | Being executed. |\n| `Canceled` | Canceled. |\n| `Done` | Completed. |",
+            "description": "Current lifecycle status of the change.\n| Value | Meaning |\n|---|---|\n| `Planned` | Planned, not started. |\n| `Ready` | Ready for execution. |\n| `Processing` | Being executed. |\n| `Canceled` | Canceled. |\n| `Done` | Completed. |\n| `Failed` | Failed. |",
             "enum": [
               "Planned",
               "Ready",
               "Processing",
               "Canceled",
-              "Done"
+              "Done",
+              "Failed"
             ]
           },
           "start_time": {

api-reference/on-call.openapi.zh.json

@@ -30374,13 +30374,14 @@
           },
           "change_status": {
             "type": "string",
-            "description": "变更事件的生命周期状态。由变更事件源按执行进度上报。\n| 值 | 含义 |\n|---|---|\n| `Planned` | 已计划，尚未开始。 |\n| `Ready` | 已就绪，待执行。 |\n| `Processing` | 正在执行。 |\n| `Canceled` | 已取消。 |\n| `Done` | 已完成。 |",
+            "description": "变更事件的生命周期状态。由变更事件源按执行进度上报。\n| 值 | 含义 |\n|---|---|\n| `Planned` | 已计划，尚未开始。 |\n| `Ready` | 已就绪，待执行。 |\n| `Processing` | 正在执行。 |\n| `Canceled` | 已取消。 |\n| `Done` | 已完成。 |\n| `Failed` | 失败。 |",
             "enum": [
               "Planned",
               "Ready",
               "Processing",
               "Canceled",
-              "Done"
+              "Done",
+              "Failed"
             ]
           },
           "link": {
@@ -30468,13 +30469,14 @@
           },
           "change_status": {
             "type": "string",
-            "description": "变更的当前生命周期状态。\n| 取值 | 含义 |\n|---|---|\n| `Planned` | 已计划，未开始。 |\n| `Ready` | 就绪，待执行。 |\n| `Processing` | 执行中。 |\n| `Canceled` | 已取消。 |\n| `Done` | 已完成。 |",
+            "description": "变更的当前生命周期状态。\n| 取值 | 含义 |\n|---|---|\n| `Planned` | 已计划，未开始。 |\n| `Ready` | 就绪，待执行。 |\n| `Processing` | 执行中。 |\n| `Canceled` | 已取消。 |\n| `Done` | 已完成。 |\n| `Failed` | 失败。 |",
             "enum": [
               "Planned",
               "Ready",
               "Processing",
               "Canceled",
-              "Done"
+              "Done",
+              "Failed"
             ]
           },
           "start_time": {

api-reference/openapi.en.json

@@ -1320,6 +1320,10 @@
             "description": "Alert description.",
             "type": "string"
           },
+          "detail_url": {
+            "description": "Console URL of this alert (`{console}/alert/detail/{alert_id}`). Empty when the deployment has no console base configured.",
+            "type": "string"
+          },
           "end_time": {
             "description": "Unix timestamp (seconds) when the alert recovered. 0 if still active.",
             "format": "int64",
@@ -1541,6 +1545,10 @@
             "description": "Alert description.",
             "type": "string"
           },
+          "detail_url": {
+            "description": "Console URL of this alert (`{console}/alert/detail/{alert_id}`). Empty when the deployment has no console base configured.",
+            "type": "string"
+          },
           "end_time": {
             "description": "Resolution time, Unix epoch seconds. 0 if still active.",
             "format": "int64",
@@ -4494,13 +4502,14 @@
             "type": "string"
           },
           "change_status": {
-            "description": "Lifecycle status of the change event, reported by the change source as execution progresses.\n| Value | Meaning |\n|---|---|\n| `Planned` | Planned, not started. |\n| `Ready` | Ready for execution. |\n| `Processing` | Being executed. |\n| `Canceled` | Canceled. |\n| `Done` | Completed. |",
+            "description": "Lifecycle status of the change event, reported by the change source as execution progresses.\n| Value | Meaning |\n|---|---|\n| `Planned` | Planned, not started. |\n| `Ready` | Ready for execution. |\n| `Processing` | Being executed. |\n| `Canceled` | Canceled. |\n| `Done` | Completed. |\n| `Failed` | Failed. |",
             "enum": [
               "Planned",
               "Ready",
               "Processing",
               "Canceled",
-              "Done"
+              "Done",
+              "Failed"
             ],
             "type": "string"
           },
@@ -4576,13 +4585,14 @@
             "type": "string"
           },
           "change_status": {
-            "description": "Current lifecycle status of the change.\n| Value | Meaning |\n|---|---|\n| `Planned` | Planned, not started. |\n| `Ready` | Ready for execution. |\n| `Processing` | Being executed. |\n| `Canceled` | Canceled. |\n| `Done` | Completed. |",
+            "description": "Current lifecycle status of the change.\n| Value | Meaning |\n|---|---|\n| `Planned` | Planned, not started. |\n| `Ready` | Ready for execution. |\n| `Processing` | Being executed. |\n| `Canceled` | Canceled. |\n| `Done` | Completed. |\n| `Failed` | Failed. |",
             "enum": [
               "Planned",
               "Ready",
               "Processing",
               "Canceled",
-              "Done"
+              "Done",
+              "Failed"
             ],
             "type": "string"
           },

api-reference/openapi.legacy.zh.json

@@ -28938,7 +28938,8 @@
               "Ready",
               "Processing",
               "Canceled",
-              "Done"
+              "Done",
+              "Failed"
             ]
           },
           "start_time": {
@@ -29007,7 +29008,8 @@
               "Ready",
               "Processing",
               "Canceled",
-              "Done"
+              "Done",
+              "Failed"
             ],
             "description": "变更状态"
           },

api-reference/openapi.zh.json

@@ -1320,6 +1320,10 @@
             "description": "告警描述。",
             "type": "string"
           },
+          "detail_url": {
+            "description": "这条告警的控制台页面（`{控制台}/alert/detail/{alert_id}`）。部署没有配置控制台地址时为空。",
+            "type": "string"
+          },
           "end_time": {
             "description": "告警恢复的 Unix 时间戳（秒），仍活跃时为 0。",
             "format": "int64",
@@ -1541,6 +1545,10 @@
             "description": "告警描述。",
             "type": "string"
           },
+          "detail_url": {
+            "description": "这条告警的控制台页面（`{控制台}/alert/detail/{alert_id}`）。部署没有配置控制台地址时为空。",
+            "type": "string"
+          },
           "end_time": {
             "description": "恢复时间，Unix 时间戳（秒）。活跃时为 0。",
             "format": "int64",
@@ -4494,13 +4502,14 @@
             "type": "string"
           },
           "change_status": {
-            "description": "变更事件的生命周期状态。由变更事件源按执行进度上报。\n| 值 | 含义 |\n|---|---|\n| `Planned` | 已计划，尚未开始。 |\n| `Ready` | 已就绪，待执行。 |\n| `Processing` | 正在执行。 |\n| `Canceled` | 已取消。 |\n| `Done` | 已完成。 |",
+            "description": "变更事件的生命周期状态。由变更事件源按执行进度上报。\n| 值 | 含义 |\n|---|---|\n| `Planned` | 已计划，尚未开始。 |\n| `Ready` | 已就绪，待执行。 |\n| `Processing` | 正在执行。 |\n| `Canceled` | 已取消。 |\n| `Done` | 已完成。 |\n| `Failed` | 失败。 |",
             "enum": [
               "Planned",
               "Ready",
               "Processing",
               "Canceled",
-              "Done"
+              "Done",
+              "Failed"
             ],
             "type": "string"
           },
@@ -4576,13 +4585,14 @@
             "type": "string"
           },
           "change_status": {
-            "description": "变更的当前生命周期状态。\n| 取值 | 含义 |\n|---|---|\n| `Planned` | 已计划，未开始。 |\n| `Ready` | 就绪，待执行。 |\n| `Processing` | 执行中。 |\n| `Canceled` | 已取消。 |\n| `Done` | 已完成。 |",
+            "description": "变更的当前生命周期状态。\n| 取值 | 含义 |\n|---|---|\n| `Planned` | 已计划，未开始。 |\n| `Ready` | 就绪，待执行。 |\n| `Processing` | 执行中。 |\n| `Canceled` | 已取消。 |\n| `Done` | 已完成。 |\n| `Failed` | 失败。 |",
             "enum": [
               "Planned",
               "Ready",
               "Processing",
               "Canceled",
-              "Done"
+              "Done",
+              "Failed"
             ],
             "type": "string"
           },

docs.json

@@ -1853,7 +1853,26 @@
                   {
                     "group": "变更集成",
                     "pages": [
-                      "zh/on-call/integration/change-integration/custom-event"
+                      "zh/on-call/integration/change-integration/custom-event",
+                      "zh/on-call/integration/change-integration/github",
+                      "zh/on-call/integration/change-integration/gitlab",
+                      "zh/on-call/integration/change-integration/hcp-terraform",
+                      "zh/on-call/integration/change-integration/argocd",
+                      "zh/on-call/integration/change-integration/netlify",
+                      "zh/on-call/integration/change-integration/vercel",
+                      "zh/on-call/integration/change-integration/jfrog-artifactory",
+                      "zh/on-call/integration/change-integration/buildkite",
+                      "zh/on-call/integration/change-integration/launchdarkly",
+                      "zh/on-call/integration/change-integration/jenkins",
+                      "zh/on-call/integration/change-integration/circleci",
+                      "zh/on-call/integration/change-integration/bitbucket",
+                      "zh/on-call/integration/change-integration/unleash",
+                      "zh/on-call/integration/change-integration/gitea",
+                      "zh/on-call/integration/change-integration/rundeck",
+                      "zh/on-call/integration/change-integration/flagsmith",
+                      "zh/on-call/integration/change-integration/azure-devops",
+                      "zh/on-call/integration/change-integration/argo-rollouts",
+                      "zh/on-call/integration/change-integration/octopus-deploy"
                     ]
                   },
                   {
@@ -3330,7 +3349,26 @@
                   {
                     "group": "Change Integration",
                     "pages": [
-                      "en/on-call/integration/change-integration/custom-event"
+                      "en/on-call/integration/change-integration/custom-event",
+                      "en/on-call/integration/change-integration/github",
+                      "en/on-call/integration/change-integration/gitlab",
+                      "en/on-call/integration/change-integration/hcp-terraform",
+                      "en/on-call/integration/change-integration/argocd",
+                      "en/on-call/integration/change-integration/netlify",
+                      "en/on-call/integration/change-integration/vercel",
+                      "en/on-call/integration/change-integration/jfrog-artifactory",
+                      "en/on-call/integration/change-integration/buildkite",
+                      "en/on-call/integration/change-integration/launchdarkly",
+                      "en/on-call/integration/change-integration/jenkins",
+                      "en/on-call/integration/change-integration/circleci",
+                      "en/on-call/integration/change-integration/bitbucket",
+                      "en/on-call/integration/change-integration/unleash",
+                      "en/on-call/integration/change-integration/gitea",
+                      "en/on-call/integration/change-integration/rundeck",
+                      "en/on-call/integration/change-integration/flagsmith",
+                      "en/on-call/integration/change-integration/azure-devops",
+                      "en/on-call/integration/change-integration/argo-rollouts",
+                      "en/on-call/integration/change-integration/octopus-deploy"
                     ]
                   },
                   {

en/ai-sre/environments.mdx

@@ -26,7 +26,9 @@ AI SRE provides two types of Environments:
   </Card>
 </CardGroup>
 
-The default selection logic is: **AI SRE uses an online BYOC Runner that the current member can use first; otherwise it uses the cloud Sandbox.** Usable Runners include Shared-scope (account-level) Runners and team-scoped Runners that belong to one of the current member's teams. You can also pin a session to the cloud Sandbox, or to a specific Runner, from the environment selector in the chat input.
+When you don't specify an environment manually, the system picks one for each new session in this order: it first uses an online BYOC Runner under the team bound to the session; if no such Runner is available online, it falls back to an online Shared-scope (account-level) Runner; if neither is available, it uses the cloud Sandbox.
+
+You can also pin the session manually from the environment selector in the chat input: force the cloud Sandbox, or pin a specific Runner.
 
 <Note>
 The console record is called an **Environment**. The process running on your machine is called a **Runner**. One BYOC Environment maps to one Runner process; cloud Sandbox instances are managed by the system per session.
@@ -403,7 +405,7 @@ The environment selector at the bottom of the chat input decides where a new ses
 
 | Option | Meaning |
 |---|---|
-| **Auto** | The default for new sessions. Uses an online Runner the current member can use; otherwise falls back to the cloud Sandbox. |
+| **Auto** | The default for new sessions. Tries an online BYOC Runner under the session's bound team, then an online Shared-scope (account-level) Runner, and falls back to the cloud Sandbox when neither is available. |
 | **Cloud Sandbox · Default** | Forces the system-managed cloud Sandbox and ignores self-hosted Runners. |
 | **Self-hosted Environment** | Lists Runners the current member can use. Offline, never-connected, or team-mismatched Runners cannot be selected; Runners in **Degraded** status **remain selectable**, and selecting one shows a "Degraded — you can continue, but responses may be slower" notice. |
 

en/ai-sre/sandbox.mdx

@@ -50,7 +50,7 @@ The **environment selector** at the bottom of the chat box decides where the ses
 
 | Option | Behavior |
 |---|---|
-| **Auto** | The default for new sessions. Prefers an online Runner the current member can use; otherwise **falls back to the cloud sandbox**. |
+| **Auto** | The default for new sessions. Tries an online BYOC Runner under the session's bound team, then an online Shared-scope (account-level) Runner, and falls back to the **cloud sandbox** when neither is available. |
 | **Cloud sandbox · Default** | Forces the cloud sandbox, ignoring all self-hosted Runners. |
 
 <Note>

en/developer/cli.mdx

@@ -842,8 +842,8 @@ The following commands support `--fields` with `json` or `toon` output. Supply c
 
 | Command | Structured output when `--fields` is omitted | Limit |
 | --- | --- | --- |
-| `flashduty incident list` | `incident_id`, `title`, `incident_severity`, `progress`, `start_time`, `channel_id` | 16 KiB |
-| `flashduty incident similar <id>` | `incident_id`, `title`, `incident_severity`, `progress`, `start_time`, `close_time`, `ack_time`, `alert_cnt`, `root_cause`, `score` | 16 KiB |
+| `flashduty incident list` | `incident_id`, `num`, `title`, `incident_severity`, `progress`, `start_time`, `channel_id`, `detail_url` | 16 KiB |
+| `flashduty incident similar <id>` | `incident_id`, `num`, `title`, `incident_severity`, `progress`, `start_time`, `close_time`, `ack_time`, `alert_cnt`, `root_cause`, `score`, `detail_url` | 16 KiB |
 | `flashduty incident detail <id>` | Returns full detail when `--fields` is omitted; otherwise returns only the selected fields | 8 KiB for projections only |
 | `flashduty alert-event list` | `event_id`, `alert_id`, `event_severity`, `event_status`, `event_time`, `title` | 16 KiB |
 | `flashduty channel escalate-rule-list <channel-id>` | `rule_id`, `rule_name`, `status`, `priority`, `filters` | 16 KiB |

en/on-call/incident/search-view-incident.mdx

@@ -277,7 +277,7 @@ The change event list displays the following information:
 
 | Column | Description |
 | :--- | :--- |
-| **Status** | Current status of the change event, including Planned, Ready, Processing, Canceled, Done |
+| **Status** | Current status of the change event, including Planned, Ready, Processing, Canceled, Done, Failed |
 | **Change Key** | Unique identifier of the change event |
 | **Title** | Brief description of the change event |
 | **Description** | Detailed information about the change event |

en/on-call/integration/alert-integration/alert-sources/argocd.mdx

@@ -148,7 +148,7 @@ kubectl exec -n argocd deploy/argocd-notifications-controller -- \
   /usr/local/bin/argocd admin notifications template notify flashduty-health <app-name> --recipient flashduty
 ```
 
-No error output means Flashduty accepted the request. When the application is `Healthy`, this is a recovery message and creates no alert; in an intermediate state such as `Progressing`, Flashduty ignores it.
+The command prints debug logs of the request and response, including the full push URL with its `integration_key`, so do not paste the output anywhere public. A `200 OK` status on the `Received response:` line means Flashduty accepted the request. When the application is `Healthy`, this is a recovery message and creates no alert; in an intermediate state such as `Progressing`, Flashduty ignores it.
 
 </Step>