diff --git a/.github/workflows/upload.yml b/.github/workflows/upload.yml
index af4f4639..02c34ec1 100644
--- a/.github/workflows/upload.yml
+++ b/.github/workflows/upload.yml
@@ -1,11 +1,14 @@
 # Upload documentation to Meilisearch for AI Q&A bot indexing.
 #
+# Every run syncs the whole doc set: all docs are upserted and index documents
+# whose source file is gone are deleted.
+#
 # Uses GitHub Environments for dev/prod separation. Create two environments in
 # Settings > Environments: "development" and "production".
 #
 # Per-environment secrets (all required, keep as secrets to hide Meilisearch endpoint):
 #   MEILI_ENDPOINT  - Meilisearch instance URL
-#   MEILI_API_KEY   - API key with documents write permission
+#   MEILI_API_KEY   - API key with documents read/write permission
 #   MEILI_INDEX     - Target index name
 #
 # Branch mapping: main -> production, test -> development
@@ -29,22 +32,19 @@ on:
         options:
           - production
           - development
-      full_upload:
-        description: 'Re-upload all docs (use after clearing index or changing settings)'
-        required: false
-        default: false
-        type: boolean
 
 jobs:
   upload:
     runs-on: ubuntu-latest
     environment: ${{ github.event.inputs.environment || (github.ref == 'refs/heads/main' && 'production' || 'development') }}
+    # One sync per index at a time: an older run listing the index while a
+    # newer one uploads would delete the newer run's added docs.
+    concurrency:
+      group: meilisearch-upload-${{ github.event.inputs.environment || (github.ref == 'refs/heads/main' && 'production' || 'development') }}
+      cancel-in-progress: false
     steps:
       - name: Checkout
         uses: actions/checkout@v4
-        with:
-          # Need history for git diff in incremental mode
-          fetch-depth: 2
 
       - name: Install dependencies
         run: |
@@ -57,7 +57,6 @@ jobs:
           MEILI_ENDPOINT: ${{ secrets.MEILI_ENDPOINT }}
           MEILI_API_KEY: ${{ secrets.MEILI_API_KEY }}
           MEILI_INDEX: ${{ secrets.MEILI_INDEX }}
-          FULL_UPLOAD: ${{ github.event.inputs.full_upload || 'false' }}
         run: |
           chmod +x ./scripts/upload.sh
           bash ./scripts/upload.sh
diff --git a/api-reference/monitors.openapi.en.json b/api-reference/monitors.openapi.en.json
index 145d7dab..bb59ed9f 100644
--- a/api-reference/monitors.openapi.en.json
+++ b/api-reference/monitors.openapi.en.json
@@ -5923,6 +5923,7 @@
             "items": {
               "$ref": "#/components/schemas/InvestigationTarget"
             },
+            "maxItems": 20,
             "description": "Drill-down entries linked from the alert event detail page; at most 20 items, duplicates rejected. On update the field is presence-based: omit it to keep the current value, pass `[]` to clear.",
             "x-flashduty-preserve-absence": true
           },
@@ -6223,14 +6224,23 @@
       },
       "InvestigationTarget": {
         "type": "object",
-        "description": "Drill-down entry linked to alert events. A deliberately closed tagged union: new kinds require explicit server support.",
+        "description": "Alert-event drill-down entry. A deliberately closed tagged union: new kinds require explicit server support, and unknown fields inside a target are rejected.",
         "properties": {
           "kind": {
             "type": "string",
             "enum": [
-              "dashboard"
+              "dashboard",
+              "query"
             ],
-            "description": "Entry type; currently only `dashboard` is supported."
+            "description": "Entry kind: `dashboard` opens a dashboard panel, `query` opens an Explore query. It decides whether `dashboard` or `query` must be supplied; supplying the other one is rejected."
+          },
+          "time_range": {
+            "$ref": "#/components/schemas/InvestigationTimeRange",
+            "description": "Window around the event time, required on every saved entry. A zero-length window is rejected; defaults belong to the editor."
+          },
+          "query": {
+            "$ref": "#/components/schemas/QueryInvestigationTarget",
+            "description": "Configuration for the `query` kind; required when `kind` is `query`, and rejected when `kind` is `dashboard`."
           },
           "dashboard": {
             "$ref": "#/components/schemas/DashboardInvestigationTarget",
@@ -6238,7 +6248,8 @@
           }
         },
         "required": [
-          "kind"
+          "kind",
+          "time_range"
         ]
       },
       "DashboardInvestigationTarget": {
@@ -6253,37 +6264,103 @@
             "type": "string",
             "description": "Panel ID inside the dashboard; must be a canonical UUIDv7. Optional."
           },
-          "variable_bindings": {
+          "variables": {
             "type": "object",
             "additionalProperties": {
-              "$ref": "#/components/schemas/InvestigationVariableBinding"
+              "type": "string"
             },
-            "description": "Dashboard variable bindings, keyed by dashboard variable name."
+            "description": "Dashboard variable values, keyed by variable name. Values may reference event labels through `{{ }}` templates; defaults to an empty object."
+          }
+        },
+        "required": [
+          "dashboard_id",
+          "variables"
+        ]
+      },
+      "InvestigationTimeRange": {
+        "type": "object",
+        "description": "Window around the alert event time, expressed as two offsets. Both directions must be non-negative and at least one must be greater than zero, so an entry never resolves to an empty window.",
+        "properties": {
+          "before_seconds": {
+            "type": "integer",
+            "format": "int64",
+            "minimum": 0,
+            "maximum": 9007199254740,
+            "description": "Seconds to look back from the event time."
+          },
+          "after_seconds": {
+            "type": "integer",
+            "format": "int64",
+            "minimum": 0,
+            "maximum": 9007199254740,
+            "description": "Seconds to look forward from the event time, so behaviour after the event stays visible."
           }
         },
         "required": [
-          "dashboard_id"
+          "before_seconds",
+          "after_seconds"
         ]
       },
-      "InvestigationVariableBinding": {
+      "QueryInvestigationTarget": {
         "type": "object",
-        "description": "Binding between a dashboard variable and alert event data.",
+        "description": "Explore query used by a `query` drill-down entry. The expression may reference event labels through `{{ }}` templates, while `args` values may not.",
         "properties": {
-          "source": {
+          "datasource_id": {
+            "type": "integer",
+            "format": "int64",
+            "minimum": 1,
+            "maximum": 9007199254740991,
+            "description": "Data source the query runs against."
+          },
+          "query": {
+            "$ref": "#/components/schemas/DashboardQuery",
+            "description": "Query payload."
+          }
+        },
+        "required": [
+          "datasource_id",
+          "query"
+        ]
+      },
+      "DashboardQuery": {
+        "type": "object",
+        "description": "Query payload shared by dashboards and drill-down entries.",
+        "properties": {
+          "mode": {
             "type": "string",
             "enum": [
-              "event_label"
+              "instant",
+              "range",
+              "window"
             ],
-            "description": "Where the bound value comes from; currently only `event_label` (the alert event's label value) is supported."
+            "description": "Evaluation mode: `instant` evaluates at a single timestamp, `range` evaluates a stepped series, `window` returns raw rows inside a time window."
           },
-          "key": {
+          "expr": {
             "type": "string",
-            "description": "Alert event label name; must follow Prometheus label naming rules and must not be a reserved label."
+            "description": "Query expression in the target data source's language. May reference event labels through `{{ }}` templates."
+          },
+          "args": {
+            "type": "object",
+            "additionalProperties": {
+              "type": "string"
+            },
+            "description": "Named query arguments; defaults to an empty object. Values are passed through verbatim and must not contain `{{ }}` templates."
+          },
+          "min_step_seconds": {
+            "type": [
+              "integer",
+              "null"
+            ],
+            "format": "int64",
+            "minimum": 1,
+            "maximum": 9007199254740,
+            "description": "Minimum step, in seconds. Only accepted when `mode` is `range`, and must be greater than zero; omit or pass null to let the server decide."
           }
         },
         "required": [
-          "source",
-          "key"
+          "mode",
+          "expr",
+          "args"
         ]
       }
     }
diff --git a/api-reference/monitors.openapi.zh.json b/api-reference/monitors.openapi.zh.json
index 4cea844d..d5aa2d4d 100644
--- a/api-reference/monitors.openapi.zh.json
+++ b/api-reference/monitors.openapi.zh.json
@@ -5923,6 +5923,7 @@
             "items": {
               "$ref": "#/components/schemas/InvestigationTarget"
             },
+            "maxItems": 20,
             "description": "告警事件详情页关联的排障入口列表，最多 20 项，不允许重复。更新接口中该字段按 presence 处理：省略时保留原配置，传 `[]` 清空。",
             "x-flashduty-preserve-absence": true
           },
@@ -6223,14 +6224,23 @@
       },
       "InvestigationTarget": {
         "type": "object",
-        "description": "告警事件的关联排障入口，为封闭的 tagged union：新增类型需服务端显式支持。",
+        "description": "告警事件的关联排障入口，为封闭的 tagged union：新增类型需服务端显式支持，入口内出现未知字段会被拒绝。",
         "properties": {
           "kind": {
             "type": "string",
             "enum": [
-              "dashboard"
+              "dashboard",
+              "query"
             ],
-            "description": "排障入口类型，目前仅支持 `dashboard`。"
+            "description": "入口类型：`dashboard` 打开仪表盘面板，`query` 打开 Explore 查询。它决定必须提供 `dashboard` 还是 `query`，提供另一个会被拒绝。"
+          },
+          "time_range": {
+            "$ref": "#/components/schemas/InvestigationTimeRange",
+            "description": "事件时间前后的取数窗口，每个已保存的入口都必填。长度为 0 的窗口会被拒绝；默认值由前端编辑器提供。"
+          },
+          "query": {
+            "$ref": "#/components/schemas/QueryInvestigationTarget",
+            "description": "`query` 类型的入口配置；`kind` 为 `query` 时必填，`kind` 为 `dashboard` 时不允许出现。"
           },
           "dashboard": {
             "$ref": "#/components/schemas/DashboardInvestigationTarget",
@@ -6238,7 +6248,8 @@
           }
         },
         "required": [
-          "kind"
+          "kind",
+          "time_range"
         ]
       },
       "DashboardInvestigationTarget": {
@@ -6253,37 +6264,103 @@
             "type": "string",
             "description": "仪表盘内目标面板 ID，须为规范的 UUIDv7；可选。"
           },
-          "variable_bindings": {
+          "variables": {
             "type": "object",
             "additionalProperties": {
-              "$ref": "#/components/schemas/InvestigationVariableBinding"
+              "type": "string"
             },
-            "description": "仪表盘变量绑定，键为仪表盘变量名。"
+            "description": "仪表盘变量取值，键为变量名。值可通过 `{{ }}` 模板引用事件标签；默认空对象。"
+          }
+        },
+        "required": [
+          "dashboard_id",
+          "variables"
+        ]
+      },
+      "InvestigationTimeRange": {
+        "type": "object",
+        "description": "以两个偏移量表示告警事件时间前后的取数窗口。两个方向都必须非负，且至少一个大于 0，因此入口不会解析出空窗口。",
+        "properties": {
+          "before_seconds": {
+            "type": "integer",
+            "format": "int64",
+            "minimum": 0,
+            "maximum": 9007199254740,
+            "description": "相对事件时间向前回溯的秒数。"
+          },
+          "after_seconds": {
+            "type": "integer",
+            "format": "int64",
+            "minimum": 0,
+            "maximum": 9007199254740,
+            "description": "相对事件时间向后延伸的秒数，用于保留事件发生后的表现。"
           }
         },
         "required": [
-          "dashboard_id"
+          "before_seconds",
+          "after_seconds"
         ]
       },
-      "InvestigationVariableBinding": {
+      "QueryInvestigationTarget": {
         "type": "object",
-        "description": "仪表盘变量与告警事件数据的绑定。",
+        "description": "`query` 类型入口使用的 Explore 查询。表达式可通过 `{{ }}` 模板引用事件标签，`args` 的值不允许包含模板。",
         "properties": {
-          "source": {
+          "datasource_id": {
+            "type": "integer",
+            "format": "int64",
+            "minimum": 1,
+            "maximum": 9007199254740991,
+            "description": "查询所用的数据源。"
+          },
+          "query": {
+            "$ref": "#/components/schemas/DashboardQuery",
+            "description": "查询内容。"
+          }
+        },
+        "required": [
+          "datasource_id",
+          "query"
+        ]
+      },
+      "DashboardQuery": {
+        "type": "object",
+        "description": "仪表盘与排障入口共用的查询内容。",
+        "properties": {
+          "mode": {
             "type": "string",
             "enum": [
-              "event_label"
+              "instant",
+              "range",
+              "window"
             ],
-            "description": "绑定值来源，目前仅支持 `event_label`（取告警事件的标签值）。"
+            "description": "求值模式：`instant` 在单个时间点求值，`range` 求值一条按步长采样的曲线，`window` 返回时间窗口内的原始数据。"
           },
-          "key": {
+          "expr": {
             "type": "string",
-            "description": "告警事件标签名，须符合 Prometheus 标签命名规则，且不能使用保留标签。"
+            "description": "目标数据源语法下的查询表达式，可通过 `{{ }}` 模板引用事件标签。"
+          },
+          "args": {
+            "type": "object",
+            "additionalProperties": {
+              "type": "string"
+            },
+            "description": "命名查询参数，默认空对象。值按原样透传，不允许包含 `{{ }}` 模板。"
+          },
+          "min_step_seconds": {
+            "type": [
+              "integer",
+              "null"
+            ],
+            "format": "int64",
+            "minimum": 1,
+            "maximum": 9007199254740,
+            "description": "最小步长（秒）。仅在 `mode` 为 `range` 时可用，且必须大于 0；省略或传 null 由服务端决定。"
           }
         },
         "required": [
-          "source",
-          "key"
+          "mode",
+          "expr",
+          "args"
         ]
       }
     }
diff --git a/api-reference/on-call.openapi.en.json b/api-reference/on-call.openapi.en.json
index 252afe6a..a76fc6d4 100644
--- a/api-reference/on-call.openapi.en.json
+++ b/api-reference/on-call.openapi.en.json
@@ -22750,6 +22750,14 @@
             "type": "integer",
             "format": "int64",
             "description": "Soft-delete time, Unix epoch milliseconds. Omitted when not deleted."
+          },
+          "via": {
+            "type": "string",
+            "description": "Surface that wrote the entry on a user's behalf; currently only `ai_sre`. Omitted when a user created the entry directly."
+          },
+          "agent_session_id": {
+            "type": "string",
+            "description": "AI SRE session that produced the entry. Omitted when no agent wrote it."
           }
         }
       },
@@ -28552,6 +28560,20 @@
             "type": "string",
             "description": "Zoom bot message template source."
           },
+          "incident_card_closed_action_apps": {
+            "type": "array",
+            "items": {
+              "type": "string",
+              "enum": [
+                "feishu_app",
+                "dingtalk_app",
+                "wecom_app",
+                "slack_app",
+                "teams_app"
+              ]
+            },
+            "description": "IM apps whose closed-incident cards keep the custom action buttons. Supported values: `feishu_app`, `dingtalk_app`, `wecom_app`, `slack_app`, `teams_app`. An empty list hides the buttons on every app."
+          },
           "incident_card_hidden_fields": {
             "$ref": "#/components/schemas/IncidentCardHiddenFields",
             "description": "Incident card fields hidden per IM app type."
@@ -28626,6 +28648,7 @@
           "updated_by",
           "created_at",
           "updated_at",
+          "incident_card_closed_action_apps",
           "incident_card_hidden_fields"
         ],
         "properties": {
@@ -28725,6 +28748,20 @@
             "type": "string",
             "description": "Zoom bot message template source."
           },
+          "incident_card_closed_action_apps": {
+            "type": "array",
+            "items": {
+              "type": "string",
+              "enum": [
+                "feishu_app",
+                "dingtalk_app",
+                "wecom_app",
+                "slack_app",
+                "teams_app"
+              ]
+            },
+            "description": "IM apps whose closed-incident cards keep the custom action buttons. Supported values: `feishu_app`, `dingtalk_app`, `wecom_app`, `slack_app`, `teams_app`. An empty list hides the buttons on every app."
+          },
           "incident_card_hidden_fields": {
             "$ref": "#/components/schemas/IncidentCardHiddenFields",
             "description": "Incident card fields hidden per IM app type; an empty object when none are configured."
@@ -29015,6 +29052,20 @@
             ],
             "description": "Zoom bot message template source. Omit to keep the current content; send an empty string to clear it."
           },
+          "incident_card_closed_action_apps": {
+            "type": "array",
+            "items": {
+              "type": "string",
+              "enum": [
+                "feishu_app",
+                "dingtalk_app",
+                "wecom_app",
+                "slack_app",
+                "teams_app"
+              ]
+            },
+            "description": "Replaces the retained-app list when sent. Supported values: `feishu_app`, `dingtalk_app`, `wecom_app`, `slack_app`, `teams_app`. Omit the field to leave it unchanged."
+          },
           "incident_card_hidden_fields": {
             "$ref": "#/components/schemas/IncidentCardHiddenFields",
             "description": "Incident card fields hidden per IM app type."
@@ -29691,7 +29742,8 @@
           "incident_id",
           "status",
           "created_at",
-          "plugin_type"
+          "plugin_type",
+          "chat_name"
         ],
         "properties": {
           "account_id": {
@@ -29734,6 +29786,14 @@
           "plugin_type": {
             "type": "string",
             "description": "IM plugin type (e.g. `feishu`, `dingtalk`, `wecom`, `slack`)."
+          },
+          "chat_name": {
+            "type": "string",
+            "description": "Display name of the group chat on the IM side."
+          },
+          "integration_unavailable": {
+            "type": "boolean",
+            "description": "True when the IM integration behind this war room is disabled or no longer exists."
           }
         }
       },
diff --git a/api-reference/on-call.openapi.zh.json b/api-reference/on-call.openapi.zh.json
index c203decf..3d49ef29 100644
--- a/api-reference/on-call.openapi.zh.json
+++ b/api-reference/on-call.openapi.zh.json
@@ -22750,6 +22750,14 @@
             "type": "integer",
             "format": "int64",
             "description": "软删除时间，Unix 时间戳（毫秒）。未删除时不返回该字段。"
+          },
+          "via": {
+            "type": "string",
+            "description": "由 AI SRE 代为写入该记录时的来源标识，目前只有 `ai_sre`；用户直接操作创建的记录不返回该字段。"
+          },
+          "agent_session_id": {
+            "type": "string",
+            "description": "写入该记录的 AI SRE 会话 ID；非智能体写入时不返回该字段。"
           }
         }
       },
@@ -28552,6 +28560,20 @@
             "type": "string",
             "description": "Zoom 机器人消息模板源。"
           },
+          "incident_card_closed_action_apps": {
+            "type": "array",
+            "items": {
+              "type": "string",
+              "enum": [
+                "feishu_app",
+                "dingtalk_app",
+                "wecom_app",
+                "slack_app",
+                "teams_app"
+              ]
+            },
+            "description": "已关闭故障的卡片仍保留自定义操作按钮的 IM 应用。可选值：`feishu_app`、`dingtalk_app`、`wecom_app`、`slack_app`、`teams_app`；空列表表示所有应用都隐藏这些按钮。"
+          },
           "incident_card_hidden_fields": {
             "$ref": "#/components/schemas/IncidentCardHiddenFields",
             "description": "按 IM 应用类型隐藏的故障卡片字段。"
@@ -28626,6 +28648,7 @@
           "updated_by",
           "created_at",
           "updated_at",
+          "incident_card_closed_action_apps",
           "incident_card_hidden_fields"
         ],
         "properties": {
@@ -28725,6 +28748,20 @@
             "type": "string",
             "description": "Zoom 机器人消息模板源。"
           },
+          "incident_card_closed_action_apps": {
+            "type": "array",
+            "items": {
+              "type": "string",
+              "enum": [
+                "feishu_app",
+                "dingtalk_app",
+                "wecom_app",
+                "slack_app",
+                "teams_app"
+              ]
+            },
+            "description": "已关闭故障的卡片仍保留自定义操作按钮的 IM 应用。可选值：`feishu_app`、`dingtalk_app`、`wecom_app`、`slack_app`、`teams_app`；空列表表示所有应用都隐藏这些按钮。"
+          },
           "incident_card_hidden_fields": {
             "$ref": "#/components/schemas/IncidentCardHiddenFields",
             "description": "按 IM 应用类型配置的故障卡片隐藏字段，未配置时为空对象。"
@@ -29015,6 +29052,20 @@
             ],
             "description": "Zoom 机器人消息模板源。省略时保持当前内容；传空字符串表示清空。"
           },
+          "incident_card_closed_action_apps": {
+            "type": "array",
+            "items": {
+              "type": "string",
+              "enum": [
+                "feishu_app",
+                "dingtalk_app",
+                "wecom_app",
+                "slack_app",
+                "teams_app"
+              ]
+            },
+            "description": "传入时整体替换保留自定义操作按钮的应用列表。可选值：`feishu_app`、`dingtalk_app`、`wecom_app`、`slack_app`、`teams_app`；不传该字段则保持不变。"
+          },
           "incident_card_hidden_fields": {
             "$ref": "#/components/schemas/IncidentCardHiddenFields",
             "description": "按 IM 应用类型隐藏的故障卡片字段。"
@@ -29691,7 +29742,8 @@
           "incident_id",
           "status",
           "created_at",
-          "plugin_type"
+          "plugin_type",
+          "chat_name"
         ],
         "properties": {
           "account_id": {
@@ -29734,6 +29786,14 @@
           "plugin_type": {
             "type": "string",
             "description": "IM 插件类型（如 `feishu`、`dingtalk`、`wecom`、`slack`）。"
+          },
+          "chat_name": {
+            "type": "string",
+            "description": "IM 侧群聊的显示名称。"
+          },
+          "integration_unavailable": {
+            "type": "boolean",
+            "description": "该作战室背后的 IM 集成已禁用或已不存在时为 true。"
           }
         }
       },
diff --git a/api-reference/openapi.en.json b/api-reference/openapi.en.json
index 6f739801..50243ea7 100644
--- a/api-reference/openapi.en.json
+++ b/api-reference/openapi.en.json
@@ -3494,7 +3494,8 @@
           },
           "limit": {
             "default": 20,
-            "description": "Page size.",
+            "description": "Page size. Values below 1 fall back to 20; values above 200 are capped at 200.",
+            "maximum": 200,
             "type": "integer"
           },
           "p": {
@@ -7575,6 +7576,46 @@
           }
         }
       },
+      "PendingUserMessage": {
+        "type": "object",
+        "description": "A queued user message that the agent has not consumed yet, as carried by `pending_messages`.",
+        "required": [
+          "invocation_id",
+          "person_id",
+          "query"
+        ],
+        "properties": {
+          "invocation_id": {
+            "type": "string",
+            "description": "Invocation ID of the queued message."
+          },
+          "client_msg_id": {
+            "type": "string",
+            "description": "Client-supplied message ID, echoed back for de-duplication. Omitted when absent."
+          },
+          "person_id": {
+            "type": "integer",
+            "format": "int64",
+            "description": "Person ID of the sender."
+          },
+          "steering": {
+            "type": "boolean",
+            "description": "True when the message was sent as a mid-turn steering instruction. Omitted when false."
+          },
+          "query": {
+            "type": "string",
+            "description": "Message text."
+          },
+          "parts": {
+            "type": "array",
+            "items": {
+              "type": "object",
+              "additionalProperties": true
+            },
+            "description": "Request parts passed through verbatim (text, file, ref, or skill entries). Omitted when the original message carried none."
+          }
+        }
+      },
       "PrometheusQueryParams": {
         "type": "object",
         "additionalProperties": true,
@@ -10511,6 +10552,14 @@
             "description": "Last update timestamp in Unix epoch milliseconds.",
             "format": "int64",
             "type": "integer"
+          },
+          "via": {
+            "type": "string",
+            "description": "Surface that wrote the entry on a user's behalf; currently only `ai_sre`. Omitted when a user created the entry directly."
+          },
+          "agent_session_id": {
+            "type": "string",
+            "description": "AI SRE session that produced the entry. Omitted when no agent wrote it."
           }
         },
         "required": [
@@ -19376,6 +19425,14 @@
             "$ref": "#/components/schemas/RumApplicationLinks",
             "description": "Optional external-link integration configuration."
           },
+          "repositories": {
+            "type": "array",
+            "items": {
+              "$ref": "#/components/schemas/RumApplicationRepository"
+            },
+            "maxItems": 10,
+            "description": "Source code repositories to link, in order; the first entry is the primary repository. At most 10 entries."
+          },
           "no_geo": {
             "description": "Do not infer geographic location.",
             "type": "boolean"
@@ -19522,6 +19579,14 @@
             "$ref": "#/components/schemas/RumApplicationLinks",
             "description": "External-link integration configuration."
           },
+          "repositories": {
+            "type": "array",
+            "items": {
+              "$ref": "#/components/schemas/RumApplicationRepository"
+            },
+            "maxItems": 10,
+            "description": "Linked source code repositories, in order; the first entry is the primary repository. Linking grants no access by itself: AI sessions can only read repositories granted to the account's GitHub App installations."
+          },
           "no_geo": {
             "description": "If `true`, geographic location is not inferred from IP.",
             "type": "boolean"
@@ -19778,6 +19843,15 @@
             "description": "External-link integration configuration. Omit to leave unchanged.",
             "x-flashduty-preserve-absence": true
           },
+          "repositories": {
+            "type": "array",
+            "items": {
+              "$ref": "#/components/schemas/RumApplicationRepository"
+            },
+            "maxItems": 10,
+            "description": "Replaces the linked source code repositories when present; an empty array removes all links, and omitting the field leaves them unchanged. At most 10 entries.",
+            "x-flashduty-preserve-absence": true
+          },
           "no_geo": {
             "description": "When `true`, stop inferring geographic location from IP; when `false`, resume inferring it. Omit to leave unchanged.",
             "type": [
@@ -23651,13 +23725,21 @@
           "suggest_init": {
             "description": "Account-wide onboarding flag: true when the account has zero knowledge packs in any scope; not specific to this session.",
             "type": "boolean"
+          },
+          "pending_messages": {
+            "type": "array",
+            "items": {
+              "$ref": "#/components/schemas/PendingUserMessage"
+            },
+            "description": "Human messages queued but not yet picked up by the agent, in execution order. Always an array — empty when nothing is queued."
           }
         },
         "required": [
           "session",
           "events",
           "has_more_older",
-          "suggest_init"
+          "suggest_init",
+          "pending_messages"
         ],
         "type": "object"
       },
@@ -23768,6 +23850,10 @@
             "description": "True when an agent turn is currently in flight for this session.",
             "type": "boolean"
           },
+          "standing_tasks": {
+            "type": "integer",
+            "description": "Number of process-type tasks (background shell or monitor) still alive when the response was rendered."
+          },
           "last_event_at": {
             "description": "Unix timestamp in milliseconds of the most recent assistant-side event.",
             "format": "int64",
@@ -23781,6 +23867,10 @@
             "description": "Creator person id.",
             "type": "string"
           },
+          "creator_name": {
+            "type": "string",
+            "description": "Display name of the session creator, resolved when the response is rendered. Omitted when the member lookup fails."
+          },
           "pinned_at": {
             "description": "Caller's per-user pin time as a Unix timestamp in milliseconds; 0 means not pinned.",
             "format": "int64",
@@ -23872,6 +23962,7 @@
           "archived_at",
           "pinned_at",
           "is_running",
+          "standing_tasks",
           "has_unread",
           "current_turn_started_at",
           "current_turn_active_ms",
@@ -26107,6 +26198,20 @@
             "type": "boolean",
             "description": "Show the Create War Room button on Feishu app cards."
           },
+          "incident_card_closed_action_apps": {
+            "type": "array",
+            "items": {
+              "type": "string",
+              "enum": [
+                "feishu_app",
+                "dingtalk_app",
+                "wecom_app",
+                "slack_app",
+                "teams_app"
+              ]
+            },
+            "description": "IM apps whose closed-incident cards keep the custom action buttons. Supported values: `feishu_app`, `dingtalk_app`, `wecom_app`, `slack_app`, `teams_app`. An empty list hides the buttons on every app."
+          },
           "incident_card_hidden_fields": {
             "$ref": "#/components/schemas/IncidentCardHiddenFields",
             "description": "Incident card fields hidden per IM app type."
@@ -26265,6 +26370,20 @@
             "type": "boolean",
             "description": "Whether Feishu app cards show the Create War Room button. Hidden when the incident has no responders."
           },
+          "incident_card_closed_action_apps": {
+            "type": "array",
+            "items": {
+              "type": "string",
+              "enum": [
+                "feishu_app",
+                "dingtalk_app",
+                "wecom_app",
+                "slack_app",
+                "teams_app"
+              ]
+            },
+            "description": "IM apps whose closed-incident cards keep the custom action buttons. Supported values: `feishu_app`, `dingtalk_app`, `wecom_app`, `slack_app`, `teams_app`. An empty list hides the buttons on every app."
+          },
           "incident_card_hidden_fields": {
             "$ref": "#/components/schemas/IncidentCardHiddenFields",
             "description": "Incident card fields hidden per IM app type; an empty object when none are configured."
@@ -26373,6 +26492,7 @@
           "updated_by",
           "created_at",
           "updated_at",
+          "incident_card_closed_action_apps",
           "incident_card_hidden_fields"
         ],
         "type": "object"
@@ -26532,6 +26652,20 @@
             ],
             "description": "When set, show or hide the Create War Room button on Feishu app cards. Omit to keep the existing setting."
           },
+          "incident_card_closed_action_apps": {
+            "type": "array",
+            "items": {
+              "type": "string",
+              "enum": [
+                "feishu_app",
+                "dingtalk_app",
+                "wecom_app",
+                "slack_app",
+                "teams_app"
+              ]
+            },
+            "description": "Replaces the retained-app list when sent. Supported values: `feishu_app`, `dingtalk_app`, `wecom_app`, `slack_app`, `teams_app`. Omit the field to leave it unchanged."
+          },
           "incident_card_hidden_fields": {
             "$ref": "#/components/schemas/IncidentCardHiddenFields",
             "description": "Incident card fields hidden per IM app type."
@@ -28021,6 +28155,14 @@
               "deleted"
             ],
             "type": "string"
+          },
+          "chat_name": {
+            "type": "string",
+            "description": "Display name of the group chat on the IM side."
+          },
+          "integration_unavailable": {
+            "type": "boolean",
+            "description": "True when the IM integration behind this war room is disabled or no longer exists."
           }
         },
         "required": [
@@ -28031,7 +28173,8 @@
           "incident_id",
           "status",
           "created_at",
-          "plugin_type"
+          "plugin_type",
+          "chat_name"
         ],
         "type": "object"
       },
@@ -28641,6 +28784,7 @@
             "items": {
               "$ref": "#/components/schemas/InvestigationTarget"
             },
+            "maxItems": 20,
             "description": "Drill-down entries linked from the alert event detail page; at most 20 items, duplicates rejected. On update the field is presence-based: omit it to keep the current value, pass `[]` to clear.",
             "x-flashduty-preserve-absence": true
           },
@@ -28941,14 +29085,23 @@
       },
       "InvestigationTarget": {
         "type": "object",
-        "description": "Drill-down entry linked to alert events. A deliberately closed tagged union: new kinds require explicit server support.",
+        "description": "Alert-event drill-down entry. A deliberately closed tagged union: new kinds require explicit server support, and unknown fields inside a target are rejected.",
         "properties": {
           "kind": {
             "type": "string",
             "enum": [
-              "dashboard"
+              "dashboard",
+              "query"
             ],
-            "description": "Entry type; currently only `dashboard` is supported."
+            "description": "Entry kind: `dashboard` opens a dashboard panel, `query` opens an Explore query. It decides whether `dashboard` or `query` must be supplied; supplying the other one is rejected."
+          },
+          "time_range": {
+            "$ref": "#/components/schemas/InvestigationTimeRange",
+            "description": "Window around the event time, required on every saved entry. A zero-length window is rejected; defaults belong to the editor."
+          },
+          "query": {
+            "$ref": "#/components/schemas/QueryInvestigationTarget",
+            "description": "Configuration for the `query` kind; required when `kind` is `query`, and rejected when `kind` is `dashboard`."
           },
           "dashboard": {
             "$ref": "#/components/schemas/DashboardInvestigationTarget",
@@ -28956,7 +29109,8 @@
           }
         },
         "required": [
-          "kind"
+          "kind",
+          "time_range"
         ]
       },
       "DashboardInvestigationTarget": {
@@ -28971,37 +29125,103 @@
             "type": "string",
             "description": "Panel ID inside the dashboard; must be a canonical UUIDv7. Optional."
           },
-          "variable_bindings": {
+          "variables": {
             "type": "object",
             "additionalProperties": {
-              "$ref": "#/components/schemas/InvestigationVariableBinding"
+              "type": "string"
             },
-            "description": "Dashboard variable bindings, keyed by dashboard variable name."
+            "description": "Dashboard variable values, keyed by variable name. Values may reference event labels through `{{ }}` templates; defaults to an empty object."
           }
         },
         "required": [
-          "dashboard_id"
+          "dashboard_id",
+          "variables"
         ]
       },
-      "InvestigationVariableBinding": {
+      "InvestigationTimeRange": {
         "type": "object",
-        "description": "Binding between a dashboard variable and alert event data.",
+        "description": "Window around the alert event time, expressed as two offsets. Both directions must be non-negative and at least one must be greater than zero, so an entry never resolves to an empty window.",
         "properties": {
-          "source": {
+          "before_seconds": {
+            "type": "integer",
+            "format": "int64",
+            "minimum": 0,
+            "maximum": 9007199254740,
+            "description": "Seconds to look back from the event time."
+          },
+          "after_seconds": {
+            "type": "integer",
+            "format": "int64",
+            "minimum": 0,
+            "maximum": 9007199254740,
+            "description": "Seconds to look forward from the event time, so behaviour after the event stays visible."
+          }
+        },
+        "required": [
+          "before_seconds",
+          "after_seconds"
+        ]
+      },
+      "QueryInvestigationTarget": {
+        "type": "object",
+        "description": "Explore query used by a `query` drill-down entry. The expression may reference event labels through `{{ }}` templates, while `args` values may not.",
+        "properties": {
+          "datasource_id": {
+            "type": "integer",
+            "format": "int64",
+            "minimum": 1,
+            "maximum": 9007199254740991,
+            "description": "Data source the query runs against."
+          },
+          "query": {
+            "$ref": "#/components/schemas/DashboardQuery",
+            "description": "Query payload."
+          }
+        },
+        "required": [
+          "datasource_id",
+          "query"
+        ]
+      },
+      "DashboardQuery": {
+        "type": "object",
+        "description": "Query payload shared by dashboards and drill-down entries.",
+        "properties": {
+          "mode": {
             "type": "string",
             "enum": [
-              "event_label"
+              "instant",
+              "range",
+              "window"
             ],
-            "description": "Where the bound value comes from; currently only `event_label` (the alert event's label value) is supported."
+            "description": "Evaluation mode: `instant` evaluates at a single timestamp, `range` evaluates a stepped series, `window` returns raw rows inside a time window."
           },
-          "key": {
+          "expr": {
             "type": "string",
-            "description": "Alert event label name; must follow Prometheus label naming rules and must not be a reserved label."
+            "description": "Query expression in the target data source's language. May reference event labels through `{{ }}` templates."
+          },
+          "args": {
+            "type": "object",
+            "additionalProperties": {
+              "type": "string"
+            },
+            "description": "Named query arguments; defaults to an empty object. Values are passed through verbatim and must not contain `{{ }}` templates."
+          },
+          "min_step_seconds": {
+            "type": [
+              "integer",
+              "null"
+            ],
+            "format": "int64",
+            "minimum": 1,
+            "maximum": 9007199254740,
+            "description": "Minimum step, in seconds. Only accepted when `mode` is `range`, and must be greater than zero; omit or pass null to let the server decide."
           }
         },
         "required": [
-          "source",
-          "key"
+          "mode",
+          "expr",
+          "args"
         ]
       },
       "MemberNotifyRequest": {
@@ -29054,6 +29274,10 @@
           "html": {
             "type": "string",
             "description": "Only present when `dry_run` is `true`: the complete email HTML exactly as recipients would receive it, after sanitization."
+          },
+          "agent_instructions": {
+            "type": "string",
+            "description": "Present when the submitted HTML body does not follow the default email layout (no `max-width:600px` wrapper table): guidance telling the calling AI SRE agent how to conform. Advisory only — a format the caller deliberately chose needs no change. Returned on dry runs and real sends alike."
           }
         }
       },
@@ -29091,6 +29315,29 @@
             "description": "Why the recipient was skipped. Only present when `status` is `skipped`. `not_member` — not an active member of the caller's account; `no_email` — the member has no email address on file; `email_disabled` — the member's notification preferences for this kind of message exclude email; `duplicate` — this recipient already received a message from the same AI SRE session turn; `rate_limited` — this recipient has already been sent 20 emails through this endpoint within the last hour; `send_failed` — enqueueing the email failed."
           }
         }
+      },
+      "RumApplicationRepository": {
+        "type": "object",
+        "description": "Source code repository that builds the application.",
+        "required": [
+          "repo"
+        ],
+        "properties": {
+          "repo": {
+            "type": "string",
+            "description": "GitHub repository in `owner/name` form.",
+            "examples": [
+              "acme/web-app"
+            ]
+          },
+          "subdir": {
+            "type": "string",
+            "description": "Directory holding the application inside the repository, relative to the repository root. `.` is the repository root; an empty value is saved as `.`.",
+            "examples": [
+              "apps/web"
+            ]
+          }
+        }
       }
     },
     "securitySchemes": {
diff --git a/api-reference/openapi.zh.json b/api-reference/openapi.zh.json
index 401b058d..ddaf0e7a 100644
--- a/api-reference/openapi.zh.json
+++ b/api-reference/openapi.zh.json
@@ -3494,7 +3494,8 @@
           },
           "limit": {
             "default": 20,
-            "description": "每页数量。",
+            "description": "每页数量。小于 1 时回退为 20，大于 200 时按 200 处理。",
+            "maximum": 200,
             "type": "integer"
           },
           "p": {
@@ -7575,6 +7576,46 @@
           }
         }
       },
+      "PendingUserMessage": {
+        "type": "object",
+        "description": "尚未被智能体消费的排队用户消息，由 `pending_messages` 返回。",
+        "required": [
+          "invocation_id",
+          "person_id",
+          "query"
+        ],
+        "properties": {
+          "invocation_id": {
+            "type": "string",
+            "description": "该排队消息的 invocation ID。"
+          },
+          "client_msg_id": {
+            "type": "string",
+            "description": "客户端传入的消息 ID，原样返回用于去重；未传时不返回。"
+          },
+          "person_id": {
+            "type": "integer",
+            "format": "int64",
+            "description": "发送者 person ID。"
+          },
+          "steering": {
+            "type": "boolean",
+            "description": "该消息是轮次中的 steering 指令时为 true；false 时不返回。"
+          },
+          "query": {
+            "type": "string",
+            "description": "消息正文。"
+          },
+          "parts": {
+            "type": "array",
+            "items": {
+              "type": "object",
+              "additionalProperties": true
+            },
+            "description": "原样透传的请求 parts（text / file / ref / skill 等）；原消息未携带时不返回。"
+          }
+        }
+      },
       "PrometheusQueryParams": {
         "type": "object",
         "additionalProperties": true,
@@ -10511,6 +10552,14 @@
             "description": "最后更新时间，Unix 毫秒时间戳。",
             "format": "int64",
             "type": "integer"
+          },
+          "via": {
+            "type": "string",
+            "description": "由 AI SRE 代为写入该记录时的来源标识，目前只有 `ai_sre`；用户直接操作创建的记录不返回该字段。"
+          },
+          "agent_session_id": {
+            "type": "string",
+            "description": "写入该记录的 AI SRE 会话 ID；非智能体写入时不返回该字段。"
           }
         },
         "required": [
@@ -19376,6 +19425,14 @@
             "$ref": "#/components/schemas/RumApplicationLinks",
             "description": "外部链接集成配置，可选。"
           },
+          "repositories": {
+            "type": "array",
+            "items": {
+              "$ref": "#/components/schemas/RumApplicationRepository"
+            },
+            "maxItems": 10,
+            "description": "要关联的代码仓库，有序；第一个为主仓库。最多 10 个。"
+          },
           "no_geo": {
             "description": "不推断地理位置。",
             "type": "boolean"
@@ -19522,6 +19579,14 @@
             "$ref": "#/components/schemas/RumApplicationLinks",
             "description": "外部链接集成配置。"
           },
+          "repositories": {
+            "type": "array",
+            "items": {
+              "$ref": "#/components/schemas/RumApplicationRepository"
+            },
+            "maxItems": 10,
+            "description": "关联的代码仓库，有序；第一个为主仓库。关联本身不授予任何访问权限：AI 会话只能读取本账户 GitHub App 安装已授权的仓库。"
+          },
           "no_geo": {
             "description": "为 `true` 时不推断地理位置。",
             "type": "boolean"
@@ -19778,6 +19843,15 @@
             "description": "外部链接集成配置；不传则保持不变。",
             "x-flashduty-preserve-absence": true
           },
+          "repositories": {
+            "type": "array",
+            "items": {
+              "$ref": "#/components/schemas/RumApplicationRepository"
+            },
+            "maxItems": 10,
+            "description": "传入时整体替换关联的代码仓库；传空数组表示清空，不传则保持不变。最多 10 个。",
+            "x-flashduty-preserve-absence": true
+          },
           "no_geo": {
             "description": "为 `true` 时不再基于 IP 推断地理位置，为 `false` 时恢复推断；不传则保持不变。",
             "type": [
@@ -23651,13 +23725,21 @@
           "suggest_init": {
             "description": "账户级引导标志：当账户在任何范围内都没有知识包时为 true；并非该会话独有的属性。",
             "type": "boolean"
+          },
+          "pending_messages": {
+            "type": "array",
+            "items": {
+              "$ref": "#/components/schemas/PendingUserMessage"
+            },
+            "description": "已排队但尚未被智能体消费的用户消息，按执行顺序排列。始终返回数组；无排队消息时为空数组。"
           }
         },
         "required": [
           "session",
           "events",
           "has_more_older",
-          "suggest_init"
+          "suggest_init",
+          "pending_messages"
         ],
         "type": "object"
       },
@@ -23768,6 +23850,10 @@
             "description": "当该会话当前有正在进行的智能体轮次时为 true。",
             "type": "boolean"
           },
+          "standing_tasks": {
+            "type": "integer",
+            "description": "渲染响应时仍存活的进程型任务数（后台命令或 monitor）。"
+          },
           "last_event_at": {
             "description": "最近一条助手侧事件的时间，Unix 毫秒时间戳。",
             "format": "int64",
@@ -23781,6 +23867,10 @@
             "description": "创建者人员 ID。",
             "type": "string"
           },
+          "creator_name": {
+            "type": "string",
+            "description": "会话创建者的显示名，渲染响应时解析得到；成员查询失败时不返回该字段。"
+          },
           "pinned_at": {
             "description": "调用者的个人置顶时间，Unix 毫秒时间戳；0 表示未置顶。",
             "format": "int64",
@@ -23872,6 +23962,7 @@
           "archived_at",
           "pinned_at",
           "is_running",
+          "standing_tasks",
           "has_unread",
           "current_turn_started_at",
           "current_turn_active_ms",
@@ -26107,6 +26198,20 @@
             "type": "boolean",
             "description": "飞书应用卡片展示「创建作战室」按钮。"
           },
+          "incident_card_closed_action_apps": {
+            "type": "array",
+            "items": {
+              "type": "string",
+              "enum": [
+                "feishu_app",
+                "dingtalk_app",
+                "wecom_app",
+                "slack_app",
+                "teams_app"
+              ]
+            },
+            "description": "已关闭故障的卡片仍保留自定义操作按钮的 IM 应用。可选值：`feishu_app`、`dingtalk_app`、`wecom_app`、`slack_app`、`teams_app`；空列表表示所有应用都隐藏这些按钮。"
+          },
           "incident_card_hidden_fields": {
             "$ref": "#/components/schemas/IncidentCardHiddenFields",
             "description": "按 IM 应用类型隐藏的故障卡片字段。"
@@ -26265,6 +26370,20 @@
             "type": "boolean",
             "description": "飞书应用卡片是否展示「创建作战室」按钮；故障无响应人时不展示。"
           },
+          "incident_card_closed_action_apps": {
+            "type": "array",
+            "items": {
+              "type": "string",
+              "enum": [
+                "feishu_app",
+                "dingtalk_app",
+                "wecom_app",
+                "slack_app",
+                "teams_app"
+              ]
+            },
+            "description": "已关闭故障的卡片仍保留自定义操作按钮的 IM 应用。可选值：`feishu_app`、`dingtalk_app`、`wecom_app`、`slack_app`、`teams_app`；空列表表示所有应用都隐藏这些按钮。"
+          },
           "incident_card_hidden_fields": {
             "$ref": "#/components/schemas/IncidentCardHiddenFields",
             "description": "按 IM 应用类型配置的故障卡片隐藏字段，未配置时为空对象。"
@@ -26373,6 +26492,7 @@
           "updated_by",
           "created_at",
           "updated_at",
+          "incident_card_closed_action_apps",
           "incident_card_hidden_fields"
         ],
         "type": "object"
@@ -26532,6 +26652,20 @@
             ],
             "description": "设置后决定飞书应用卡片是否展示「创建作战室」按钮；省略时保持当前设置。"
           },
+          "incident_card_closed_action_apps": {
+            "type": "array",
+            "items": {
+              "type": "string",
+              "enum": [
+                "feishu_app",
+                "dingtalk_app",
+                "wecom_app",
+                "slack_app",
+                "teams_app"
+              ]
+            },
+            "description": "传入时整体替换保留自定义操作按钮的应用列表。可选值：`feishu_app`、`dingtalk_app`、`wecom_app`、`slack_app`、`teams_app`；不传该字段则保持不变。"
+          },
           "incident_card_hidden_fields": {
             "$ref": "#/components/schemas/IncidentCardHiddenFields",
             "description": "按 IM 应用类型隐藏的故障卡片字段。"
@@ -28021,6 +28155,14 @@
               "deleted"
             ],
             "type": "string"
+          },
+          "chat_name": {
+            "type": "string",
+            "description": "IM 侧群聊的显示名称。"
+          },
+          "integration_unavailable": {
+            "type": "boolean",
+            "description": "该作战室背后的 IM 集成已禁用或已不存在时为 true。"
           }
         },
         "required": [
@@ -28031,7 +28173,8 @@
           "incident_id",
           "status",
           "created_at",
-          "plugin_type"
+          "plugin_type",
+          "chat_name"
         ],
         "type": "object"
       },
@@ -28641,6 +28784,7 @@
             "items": {
               "$ref": "#/components/schemas/InvestigationTarget"
             },
+            "maxItems": 20,
             "description": "告警事件详情页关联的排障入口列表，最多 20 项，不允许重复。更新接口中该字段按 presence 处理：省略时保留原配置，传 `[]` 清空。",
             "x-flashduty-preserve-absence": true
           },
@@ -28941,14 +29085,23 @@
       },
       "InvestigationTarget": {
         "type": "object",
-        "description": "告警事件的关联排障入口，为封闭的 tagged union：新增类型需服务端显式支持。",
+        "description": "告警事件的关联排障入口，为封闭的 tagged union：新增类型需服务端显式支持，入口内出现未知字段会被拒绝。",
         "properties": {
           "kind": {
             "type": "string",
             "enum": [
-              "dashboard"
+              "dashboard",
+              "query"
             ],
-            "description": "排障入口类型，目前仅支持 `dashboard`。"
+            "description": "入口类型：`dashboard` 打开仪表盘面板，`query` 打开 Explore 查询。它决定必须提供 `dashboard` 还是 `query`，提供另一个会被拒绝。"
+          },
+          "time_range": {
+            "$ref": "#/components/schemas/InvestigationTimeRange",
+            "description": "事件时间前后的取数窗口，每个已保存的入口都必填。长度为 0 的窗口会被拒绝；默认值由前端编辑器提供。"
+          },
+          "query": {
+            "$ref": "#/components/schemas/QueryInvestigationTarget",
+            "description": "`query` 类型的入口配置；`kind` 为 `query` 时必填，`kind` 为 `dashboard` 时不允许出现。"
           },
           "dashboard": {
             "$ref": "#/components/schemas/DashboardInvestigationTarget",
@@ -28956,7 +29109,8 @@
           }
         },
         "required": [
-          "kind"
+          "kind",
+          "time_range"
         ]
       },
       "DashboardInvestigationTarget": {
@@ -28971,37 +29125,103 @@
             "type": "string",
             "description": "仪表盘内目标面板 ID，须为规范的 UUIDv7；可选。"
           },
-          "variable_bindings": {
+          "variables": {
             "type": "object",
             "additionalProperties": {
-              "$ref": "#/components/schemas/InvestigationVariableBinding"
+              "type": "string"
             },
-            "description": "仪表盘变量绑定，键为仪表盘变量名。"
+            "description": "仪表盘变量取值，键为变量名。值可通过 `{{ }}` 模板引用事件标签；默认空对象。"
           }
         },
         "required": [
-          "dashboard_id"
+          "dashboard_id",
+          "variables"
         ]
       },
-      "InvestigationVariableBinding": {
+      "InvestigationTimeRange": {
         "type": "object",
-        "description": "仪表盘变量与告警事件数据的绑定。",
+        "description": "以两个偏移量表示告警事件时间前后的取数窗口。两个方向都必须非负，且至少一个大于 0，因此入口不会解析出空窗口。",
         "properties": {
-          "source": {
+          "before_seconds": {
+            "type": "integer",
+            "format": "int64",
+            "minimum": 0,
+            "maximum": 9007199254740,
+            "description": "相对事件时间向前回溯的秒数。"
+          },
+          "after_seconds": {
+            "type": "integer",
+            "format": "int64",
+            "minimum": 0,
+            "maximum": 9007199254740,
+            "description": "相对事件时间向后延伸的秒数，用于保留事件发生后的表现。"
+          }
+        },
+        "required": [
+          "before_seconds",
+          "after_seconds"
+        ]
+      },
+      "QueryInvestigationTarget": {
+        "type": "object",
+        "description": "`query` 类型入口使用的 Explore 查询。表达式可通过 `{{ }}` 模板引用事件标签，`args` 的值不允许包含模板。",
+        "properties": {
+          "datasource_id": {
+            "type": "integer",
+            "format": "int64",
+            "minimum": 1,
+            "maximum": 9007199254740991,
+            "description": "查询所用的数据源。"
+          },
+          "query": {
+            "$ref": "#/components/schemas/DashboardQuery",
+            "description": "查询内容。"
+          }
+        },
+        "required": [
+          "datasource_id",
+          "query"
+        ]
+      },
+      "DashboardQuery": {
+        "type": "object",
+        "description": "仪表盘与排障入口共用的查询内容。",
+        "properties": {
+          "mode": {
             "type": "string",
             "enum": [
-              "event_label"
+              "instant",
+              "range",
+              "window"
             ],
-            "description": "绑定值来源，目前仅支持 `event_label`（取告警事件的标签值）。"
+            "description": "求值模式：`instant` 在单个时间点求值，`range` 求值一条按步长采样的曲线，`window` 返回时间窗口内的原始数据。"
           },
-          "key": {
+          "expr": {
             "type": "string",
-            "description": "告警事件标签名，须符合 Prometheus 标签命名规则，且不能使用保留标签。"
+            "description": "目标数据源语法下的查询表达式，可通过 `{{ }}` 模板引用事件标签。"
+          },
+          "args": {
+            "type": "object",
+            "additionalProperties": {
+              "type": "string"
+            },
+            "description": "命名查询参数，默认空对象。值按原样透传，不允许包含 `{{ }}` 模板。"
+          },
+          "min_step_seconds": {
+            "type": [
+              "integer",
+              "null"
+            ],
+            "format": "int64",
+            "minimum": 1,
+            "maximum": 9007199254740,
+            "description": "最小步长（秒）。仅在 `mode` 为 `range` 时可用，且必须大于 0；省略或传 null 由服务端决定。"
           }
         },
         "required": [
-          "source",
-          "key"
+          "mode",
+          "expr",
+          "args"
         ]
       },
       "MemberNotifyRequest": {
@@ -29054,6 +29274,10 @@
           "html": {
             "type": "string",
             "description": "仅当 `dry_run` 为 `true` 时返回：清洗后、收件人将收到的完整邮件 HTML。"
+          },
+          "agent_instructions": {
+            "type": "string",
+            "description": "当提交的 HTML 正文不符合默认邮件版式（缺少 `max-width:600px` 外层包裹表格）时返回：告知调用的 AI SRE agent 如何对齐的指引。仅为建议——调用方有意选择的格式无需改动。dry run 与真实发送均会返回。"
           }
         }
       },
@@ -29091,6 +29315,29 @@
             "description": "跳过原因，仅当 `status` 为 `skipped` 时出现。`not_member` —— 不是调用方账户的活跃成员；`no_email` —— 该成员没有邮箱地址；`email_disabled` —— 该成员针对此类消息的通知偏好中未包含邮件；`duplicate` —— 该收件人在同一个 AI SRE 会话轮次中已经收到过一次消息；`rate_limited` —— 该收件人通过该接口在过去一小时内已被发送 20 封邮件；`send_failed` —— 邮件入队失败。"
           }
         }
+      },
+      "RumApplicationRepository": {
+        "type": "object",
+        "description": "构建该应用的代码仓库。",
+        "required": [
+          "repo"
+        ],
+        "properties": {
+          "repo": {
+            "type": "string",
+            "description": "GitHub 仓库，格式为 `owner/name`。",
+            "examples": [
+              "acme/web-app"
+            ]
+          },
+          "subdir": {
+            "type": "string",
+            "description": "应用在仓库内所在的目录，相对仓库根目录。`.` 表示仓库根目录；传空值时保存为 `.`。",
+            "examples": [
+              "apps/web"
+            ]
+          }
+        }
       }
     },
     "securitySchemes": {
diff --git a/api-reference/platform.openapi.en.json b/api-reference/platform.openapi.en.json
index 47f747d4..f5c5e26a 100644
--- a/api-reference/platform.openapi.en.json
+++ b/api-reference/platform.openapi.en.json
@@ -4581,6 +4581,10 @@
           "html": {
             "type": "string",
             "description": "Only present when `dry_run` is `true`: the complete email HTML exactly as recipients would receive it, after sanitization."
+          },
+          "agent_instructions": {
+            "type": "string",
+            "description": "Present when the submitted HTML body does not follow the default email layout (no `max-width:600px` wrapper table): guidance telling the calling AI SRE agent how to conform. Advisory only — a format the caller deliberately chose needs no change. Returned on dry runs and real sends alike."
           }
         }
       },
diff --git a/api-reference/platform.openapi.zh.json b/api-reference/platform.openapi.zh.json
index 3cca6c26..22d69cb8 100644
--- a/api-reference/platform.openapi.zh.json
+++ b/api-reference/platform.openapi.zh.json
@@ -4581,6 +4581,10 @@
           "html": {
             "type": "string",
             "description": "仅当 `dry_run` 为 `true` 时返回：清洗后、收件人将收到的完整邮件 HTML。"
+          },
+          "agent_instructions": {
+            "type": "string",
+            "description": "当提交的 HTML 正文不符合默认邮件版式（缺少 `max-width:600px` 外层包裹表格）时返回：告知调用的 AI SRE agent 如何对齐的指引。仅为建议——调用方有意选择的格式无需改动。dry run 与真实发送均会返回。"
           }
         }
       },
diff --git a/api-reference/rum.openapi.en.json b/api-reference/rum.openapi.en.json
index eca2d6ac..61dd9d3b 100644
--- a/api-reference/rum.openapi.en.json
+++ b/api-reference/rum.openapi.en.json
@@ -610,6 +610,14 @@
             "$ref": "#/components/schemas/RumApplicationLinks",
             "description": "Optional external-link integration configuration."
           },
+          "repositories": {
+            "type": "array",
+            "items": {
+              "$ref": "#/components/schemas/RumApplicationRepository"
+            },
+            "maxItems": 10,
+            "description": "Source code repositories to link, in order; the first entry is the primary repository. At most 10 entries."
+          },
           "no_geo": {
             "description": "Do not infer geographic location.",
             "type": "boolean"
@@ -756,6 +764,14 @@
             "$ref": "#/components/schemas/RumApplicationLinks",
             "description": "External-link integration configuration."
           },
+          "repositories": {
+            "type": "array",
+            "items": {
+              "$ref": "#/components/schemas/RumApplicationRepository"
+            },
+            "maxItems": 10,
+            "description": "Linked source code repositories, in order; the first entry is the primary repository. Linking grants no access by itself: AI sessions can only read repositories granted to the account's GitHub App installations."
+          },
           "no_geo": {
             "description": "If `true`, geographic location is not inferred from IP.",
             "type": "boolean"
@@ -1012,6 +1028,15 @@
             "description": "External-link integration configuration. Omit to leave unchanged.",
             "x-flashduty-preserve-absence": true
           },
+          "repositories": {
+            "type": "array",
+            "items": {
+              "$ref": "#/components/schemas/RumApplicationRepository"
+            },
+            "maxItems": 10,
+            "description": "Replaces the linked source code repositories when present; an empty array removes all links, and omitting the field leaves them unchanged. At most 10 entries.",
+            "x-flashduty-preserve-absence": true
+          },
           "no_geo": {
             "description": "When `true`, stop inferring geographic location from IP; when `false`, resume inferring it. Omit to leave unchanged.",
             "type": [
@@ -3938,6 +3963,29 @@
           }
         },
         "type": "object"
+      },
+      "RumApplicationRepository": {
+        "type": "object",
+        "description": "Source code repository that builds the application.",
+        "required": [
+          "repo"
+        ],
+        "properties": {
+          "repo": {
+            "type": "string",
+            "description": "GitHub repository in `owner/name` form.",
+            "examples": [
+              "acme/web-app"
+            ]
+          },
+          "subdir": {
+            "type": "string",
+            "description": "Directory holding the application inside the repository, relative to the repository root. `.` is the repository root; an empty value is saved as `.`.",
+            "examples": [
+              "apps/web"
+            ]
+          }
+        }
       }
     },
     "securitySchemes": {
diff --git a/api-reference/rum.openapi.zh.json b/api-reference/rum.openapi.zh.json
index c0362e4d..213c0676 100644
--- a/api-reference/rum.openapi.zh.json
+++ b/api-reference/rum.openapi.zh.json
@@ -610,6 +610,14 @@
             "$ref": "#/components/schemas/RumApplicationLinks",
             "description": "外部链接集成配置，可选。"
           },
+          "repositories": {
+            "type": "array",
+            "items": {
+              "$ref": "#/components/schemas/RumApplicationRepository"
+            },
+            "maxItems": 10,
+            "description": "要关联的代码仓库，有序；第一个为主仓库。最多 10 个。"
+          },
           "no_geo": {
             "description": "不推断地理位置。",
             "type": "boolean"
@@ -756,6 +764,14 @@
             "$ref": "#/components/schemas/RumApplicationLinks",
             "description": "外部链接集成配置。"
           },
+          "repositories": {
+            "type": "array",
+            "items": {
+              "$ref": "#/components/schemas/RumApplicationRepository"
+            },
+            "maxItems": 10,
+            "description": "关联的代码仓库，有序；第一个为主仓库。关联本身不授予任何访问权限：AI 会话只能读取本账户 GitHub App 安装已授权的仓库。"
+          },
           "no_geo": {
             "description": "为 `true` 时不推断地理位置。",
             "type": "boolean"
@@ -1012,6 +1028,15 @@
             "description": "外部链接集成配置；不传则保持不变。",
             "x-flashduty-preserve-absence": true
           },
+          "repositories": {
+            "type": "array",
+            "items": {
+              "$ref": "#/components/schemas/RumApplicationRepository"
+            },
+            "maxItems": 10,
+            "description": "传入时整体替换关联的代码仓库；传空数组表示清空，不传则保持不变。最多 10 个。",
+            "x-flashduty-preserve-absence": true
+          },
           "no_geo": {
             "description": "为 `true` 时不再基于 IP 推断地理位置，为 `false` 时恢复推断；不传则保持不变。",
             "type": [
@@ -3938,6 +3963,29 @@
           }
         },
         "type": "object"
+      },
+      "RumApplicationRepository": {
+        "type": "object",
+        "description": "构建该应用的代码仓库。",
+        "required": [
+          "repo"
+        ],
+        "properties": {
+          "repo": {
+            "type": "string",
+            "description": "GitHub 仓库，格式为 `owner/name`。",
+            "examples": [
+              "acme/web-app"
+            ]
+          },
+          "subdir": {
+            "type": "string",
+            "description": "应用在仓库内所在的目录，相对仓库根目录。`.` 表示仓库根目录；传空值时保存为 `.`。",
+            "examples": [
+              "apps/web"
+            ]
+          }
+        }
       }
     },
     "securitySchemes": {
diff --git a/api-reference/safari.openapi.en.json b/api-reference/safari.openapi.en.json
index 8c513b5e..3ede44fa 100644
--- a/api-reference/safari.openapi.en.json
+++ b/api-reference/safari.openapi.en.json
@@ -5816,7 +5816,8 @@
           "limit": {
             "type": "integer",
             "default": 20,
-            "description": "Page size."
+            "description": "Page size. Values below 1 fall back to 20; values above 200 are capped at 200.",
+            "maximum": 200
           },
           "scope": {
             "type": "string",
@@ -7049,6 +7050,46 @@
           "preflight"
         ]
       },
+      "PendingUserMessage": {
+        "type": "object",
+        "description": "A queued user message that the agent has not consumed yet, as carried by `pending_messages`.",
+        "required": [
+          "invocation_id",
+          "person_id",
+          "query"
+        ],
+        "properties": {
+          "invocation_id": {
+            "type": "string",
+            "description": "Invocation ID of the queued message."
+          },
+          "client_msg_id": {
+            "type": "string",
+            "description": "Client-supplied message ID, echoed back for de-duplication. Omitted when absent."
+          },
+          "person_id": {
+            "type": "integer",
+            "format": "int64",
+            "description": "Person ID of the sender."
+          },
+          "steering": {
+            "type": "boolean",
+            "description": "True when the message was sent as a mid-turn steering instruction. Omitted when false."
+          },
+          "query": {
+            "type": "string",
+            "description": "Message text."
+          },
+          "parts": {
+            "type": "array",
+            "items": {
+              "type": "object",
+              "additionalProperties": true
+            },
+            "description": "Request parts passed through verbatim (text, file, ref, or skill entries). Omitted when the original message carried none."
+          }
+        }
+      },
       "PreflightResult": {
         "type": "object",
         "description": "Readiness checks computed before a manual run is allowed to start.",
@@ -7215,13 +7256,21 @@
           "suggest_init": {
             "type": "boolean",
             "description": "Account-wide onboarding flag: true when the account has zero knowledge packs in any scope; not specific to this session."
+          },
+          "pending_messages": {
+            "type": "array",
+            "items": {
+              "$ref": "#/components/schemas/PendingUserMessage"
+            },
+            "description": "Human messages queued but not yet picked up by the agent, in execution order. Always an array — empty when nothing is queued."
           }
         },
         "required": [
           "session",
           "events",
           "has_more_older",
-          "suggest_init"
+          "suggest_init",
+          "pending_messages"
         ]
       },
       "SessionItem": {
@@ -7259,6 +7308,10 @@
             "type": "string",
             "description": "Creator person id."
           },
+          "creator_name": {
+            "type": "string",
+            "description": "Display name of the session creator, resolved when the response is rendered. Omitted when the member lookup fails."
+          },
           "team_id": {
             "type": "integer",
             "format": "int64",
@@ -7387,6 +7440,10 @@
             "type": "boolean",
             "description": "True when an agent turn is currently in flight for this session."
           },
+          "standing_tasks": {
+            "type": "integer",
+            "description": "Number of process-type tasks (background shell or monitor) still alive when the response was rendered."
+          },
           "has_unread": {
             "type": "boolean",
             "description": "True when there is assistant output the caller has not yet viewed."
@@ -7436,6 +7493,7 @@
           "archived_at",
           "pinned_at",
           "is_running",
+          "standing_tasks",
           "has_unread",
           "current_turn_started_at",
           "current_turn_active_ms",
diff --git a/api-reference/safari.openapi.zh.json b/api-reference/safari.openapi.zh.json
index be93ac17..3b78f429 100644
--- a/api-reference/safari.openapi.zh.json
+++ b/api-reference/safari.openapi.zh.json
@@ -5816,7 +5816,8 @@
           "limit": {
             "type": "integer",
             "default": 20,
-            "description": "每页数量。"
+            "description": "每页数量。小于 1 时回退为 20，大于 200 时按 200 处理。",
+            "maximum": 200
           },
           "scope": {
             "type": "string",
@@ -7049,6 +7050,46 @@
           "preflight"
         ]
       },
+      "PendingUserMessage": {
+        "type": "object",
+        "description": "尚未被智能体消费的排队用户消息，由 `pending_messages` 返回。",
+        "required": [
+          "invocation_id",
+          "person_id",
+          "query"
+        ],
+        "properties": {
+          "invocation_id": {
+            "type": "string",
+            "description": "该排队消息的 invocation ID。"
+          },
+          "client_msg_id": {
+            "type": "string",
+            "description": "客户端传入的消息 ID，原样返回用于去重；未传时不返回。"
+          },
+          "person_id": {
+            "type": "integer",
+            "format": "int64",
+            "description": "发送者 person ID。"
+          },
+          "steering": {
+            "type": "boolean",
+            "description": "该消息是轮次中的 steering 指令时为 true；false 时不返回。"
+          },
+          "query": {
+            "type": "string",
+            "description": "消息正文。"
+          },
+          "parts": {
+            "type": "array",
+            "items": {
+              "type": "object",
+              "additionalProperties": true
+            },
+            "description": "原样透传的请求 parts（text / file / ref / skill 等）；原消息未携带时不返回。"
+          }
+        }
+      },
       "PreflightResult": {
         "type": "object",
         "description": "在允许发起手动运行前计算出的就绪检查结果。",
@@ -7215,13 +7256,21 @@
           "suggest_init": {
             "type": "boolean",
             "description": "账户级引导标志：当账户在任何范围内都没有知识包时为 true；并非该会话独有的属性。"
+          },
+          "pending_messages": {
+            "type": "array",
+            "items": {
+              "$ref": "#/components/schemas/PendingUserMessage"
+            },
+            "description": "已排队但尚未被智能体消费的用户消息，按执行顺序排列。始终返回数组；无排队消息时为空数组。"
           }
         },
         "required": [
           "session",
           "events",
           "has_more_older",
-          "suggest_init"
+          "suggest_init",
+          "pending_messages"
         ]
       },
       "SessionItem": {
@@ -7259,6 +7308,10 @@
             "type": "string",
             "description": "创建者人员 ID。"
           },
+          "creator_name": {
+            "type": "string",
+            "description": "会话创建者的显示名，渲染响应时解析得到；成员查询失败时不返回该字段。"
+          },
           "team_id": {
             "type": "integer",
             "format": "int64",
@@ -7387,6 +7440,10 @@
             "type": "boolean",
             "description": "当该会话当前有正在进行的智能体轮次时为 true。"
           },
+          "standing_tasks": {
+            "type": "integer",
+            "description": "渲染响应时仍存活的进程型任务数（后台命令或 monitor）。"
+          },
           "has_unread": {
             "type": "boolean",
             "description": "当存在调用者尚未查看的助手输出时为 true。"
@@ -7436,6 +7493,7 @@
           "archived_at",
           "pinned_at",
           "is_running",
+          "standing_tasks",
           "has_unread",
           "current_turn_started_at",
           "current_turn_active_ms",
diff --git a/docs.json b/docs.json
index d8e68309..ba716c72 100644
--- a/docs.json
+++ b/docs.json
@@ -1680,6 +1680,7 @@
                       "zh/on-call/integration/alert-integration/alert-sources/prometheus",
                       "zh/on-call/integration/alert-integration/alert-sources/grafana",
                       "zh/on-call/integration/alert-integration/alert-sources/datadog",
+                      "zh/on-call/integration/alert-integration/alert-sources/new-relic",
                       "zh/on-call/integration/alert-integration/alert-sources/zabbix",
                       "zh/on-call/integration/alert-integration/alert-sources/flashcat",
                       "zh/on-call/integration/alert-integration/alert-sources/open-falcon",
@@ -1694,6 +1695,7 @@
                       "zh/on-call/integration/alert-integration/alert-sources/aliyun-cm-metrics",
                       "zh/on-call/integration/alert-integration/alert-sources/aliyun-sls",
                       "zh/on-call/integration/alert-integration/alert-sources/aliyun-prometheus",
+                      "zh/on-call/integration/alert-integration/alert-sources/aliyun-dataworks-op",
                       "zh/on-call/integration/alert-integration/alert-sources/aws-cloudwatch",
                       "zh/on-call/integration/alert-integration/alert-sources/aws-eventbridge",
                       "zh/on-call/integration/alert-integration/alert-sources/azure-monitor",
@@ -3048,6 +3050,7 @@
                       "en/on-call/integration/alert-integration/alert-sources/prometheus",
                       "en/on-call/integration/alert-integration/alert-sources/grafana",
                       "en/on-call/integration/alert-integration/alert-sources/datadog",
+                      "en/on-call/integration/alert-integration/alert-sources/new-relic",
                       "en/on-call/integration/alert-integration/alert-sources/zabbix",
                       "en/on-call/integration/alert-integration/alert-sources/flashcat",
                       "en/on-call/integration/alert-integration/alert-sources/open-falcon",
@@ -3062,6 +3065,7 @@
                       "en/on-call/integration/alert-integration/alert-sources/aliyun-cm-metrics",
                       "en/on-call/integration/alert-integration/alert-sources/aliyun-sls",
                       "en/on-call/integration/alert-integration/alert-sources/aliyun-prometheus",
+                      "en/on-call/integration/alert-integration/alert-sources/aliyun-dataworks-op",
                       "en/on-call/integration/alert-integration/alert-sources/aws-cloudwatch",
                       "en/on-call/integration/alert-integration/alert-sources/aws-eventbridge",
                       "en/on-call/integration/alert-integration/alert-sources/azure-monitor",
diff --git a/en/ai-sre/apps.mdx b/en/ai-sre/apps.mdx
index 7961befe..6f1edfb4 100644
--- a/en/ai-sre/apps.mdx
+++ b/en/ai-sre/apps.mdx
@@ -31,7 +31,7 @@ AI SRE sessions run in a **Flashduty cloud sandbox** by default. The sandbox is
 
 ---
 
-Go to **Plugins → Apps**. Apps is the **first and default** tab in the Plugins area — opening Plugins lands you here.
+Go to **Plugins → Apps**. Opening the Plugins area lands on the **Overview** tab by default; Apps is one of its tabs (the tab order is Overview / Apps / Skill / MCP / Agents).
 
 <Note>
 Viewing the Apps tab requires the appropriate permission; without it, the tab is hidden. Authorizing, disconnecting / revoking, and enabling / disabling each require their own action permission — when you lack one, the corresponding button is shown disabled.
diff --git a/en/ai-sre/artifacts.mdx b/en/ai-sre/artifacts.mdx
index 852600d7..448be8fd 100644
--- a/en/ai-sre/artifacts.mdx
+++ b/en/ai-sre/artifacts.mdx
@@ -60,6 +60,8 @@ The top-right of the list page offers a **Card view / List view** toggle; your c
 
 The **Created at** and **Updated at** columns support header sorting (ascending / descending toggle); sorting is executed server-side, with **Updated at descending** as the default.
 
+Scope, search term, sorting, and page number are all reflected in the page URL (for example `?scope=team&teams=1,2&q=rebuild&page=2`), so copying the address shares or bookmarks a **filtered** list; returning from an artifact's detail page also lands back on the same filters and position instead of resetting to the default view.
+
 ### Artifact cards
 
 Each card shows:
diff --git a/en/ai-sre/automations.mdx b/en/ai-sre/automations.mdx
index aa3fd513..ca06040f 100644
--- a/en/ai-sre/automations.mdx
+++ b/en/ai-sre/automations.mdx
@@ -170,7 +170,7 @@ If you create or update a rule through the API, use these fields:
 
 When a matching event arrives, the system creates a run with `trigger_kind: "oncall_incident"` and passes event context such as `incident_id`, `channel_id`, and `severity` into the session. The same trigger and the same `incident_id` reuse the same run, avoiding duplicate hidden sessions for one incident.
 
-When the run finishes, AI SRE writes one summary comment back to the incident that triggered it: conclusion first, body kept concise, with a link to the full session at the end. The comment travels through the incident's existing notification chain (for example, incident card refreshes and thread replies in IM), so whoever is watching the incident sees the analysis without opening the console. This applies to every rule with the On-call incident trigger enabled — including rules with custom prompts — with no extra configuration.
+When the run finishes, AI SRE writes one summary comment back to the incident that triggered it: conclusion first, body kept concise, with a link to the full session at the end. That write-back record also carries a persistent **Continue conversation** entry, so you can open that session straight from the conclusion on the incident timeline — see [Incident Timeline · AI SRE Action Records](/en/on-call/incident/search-view-incident#ai-sre-action-records). The comment travels through the incident's existing notification chain (for example, incident card refreshes and thread replies in IM), so whoever is watching the incident sees the analysis without opening the console. This applies to every rule with the On-call incident trigger enabled — including rules with custom prompts — with no extra configuration.
 
 ## Run History
 
diff --git a/en/ai-sre/im.mdx b/en/ai-sre/im.mdx
index 32e86ba7..caeb7410 100644
--- a/en/ai-sre/im.mdx
+++ b/en/ai-sre/im.mdx
@@ -50,7 +50,7 @@ IM interaction requires that you have already connected the corresponding platfo
 Open the corresponding IM integration under **On-call → Integration Center → Integration List → Instant Messaging** and configure its AI SRE behavior under **Enhanced features**. The following switches are on by default:
 
 - **Automatically start AI incident analysis**: available after you enable War Room. When the integration creates a war room, AI SRE starts one preliminary diagnosis and posts the result back to the room.
-- **Allow group chat @ AI SRE**: available without enabling War Room. It allows group @mentions to enter AI SRE. In Slack, the switch is labeled **Allow group chat @ AI SRE and /fd command**; turning it off makes both group @mentions and `/fd` commands silent.
+- **Allow AI SRE conversations in IM**: available without enabling War Room. It controls both entry points — **group @mentions** and **direct chats with the bot**; in Slack it also controls the `/fd` command. Turning it off makes group @mentions and direct chats with the bot (and, in Slack, `/fd`) silent. In WeCom's Third-party App mode, only direct chats with the bot are available; group @mentions require Custom App Integration mode.
 - **Use thread replies in normal group chats**: available only for Feishu/Lark and Slack. When enabled, each normal-group thread has an independent session; War Rooms still receive replies directly in the group.
 
 <Note>
@@ -61,7 +61,7 @@ If AI SRE is not enabled for the account, these switches do not take effect. Aft
 
 ---
 
-In a connected IM group where group chat @ AI SRE is allowed, **@mention the bot** and type your question (for example, "@AI SRE check why the payment service's 5xx rate is spiking") — the message is forwarded to AI SRE for processing via the platform webhook:
+In a connected IM group where **Allow AI SRE conversations in IM** is enabled, **@mention the bot** and type your question (for example, "@AI SRE check why the payment service's 5xx rate is spiking") — the message is forwarded to AI SRE for processing via the platform webhook:
 
 <Steps>
   <Step title="Detect the mention">
@@ -120,6 +120,21 @@ While any standing task is alive, the IM session's root message stays open (the
 
 Notification rounds follow a silent "no message = no news" semantics: if a notification round has nothing new to deliver, AI SRE closes that round silently — **no placeholder receipt** is posted to the chat, and the monitoring card is not re-posted either. A new message appears in the chat only when there is a real new finding.
 
+## Connections and Authorization
+
+---
+
+When a credential is missing, the console renders inline cards (**"Authorize [resource name] to continue"**, **"Connect [vendor] to continue"** — see [Console](/en/ai-sre/sessions#when-authorization-is-required)). **IM and API channels get no card** — the agent hands the matter to you according to this session's channel, as follows:
+
+| Situation | Behavior on IM / API channels |
+| --- | --- |
+| Your OAuth authorization is missing (`per_user_oauth`) | The agent pastes the authorize link into the chat as a plain message (not a card); open it in a **desktop / PC browser** to complete the authorization, then reply **"已授权"** (or `authorized` in an English session) to continue. Continuing is your explicit action — a successful OAuth callback does not resume the task by itself |
+| Your secret-type credential is missing (`per_user_secret`) | There is no safe way to collect it over IM: the agent simply tells you to open **this same session in the web console** and complete it there. It never asks you to paste the secret into the chat, and never points you at a settings page instead |
+| The whole connection is missing (in the marketplace catalog, not connected in the account) | The agent gives the connect URL (a deep link into the console's plugins page) as a plain link; connect, then reply **"继续"** (or `continue`) to carry on |
+| A shared server's own credentials (environment variables / headers) | Not any of the above: fill them in under **Plugins → MCP** (that server), then tell the agent to retry |
+
+On the automation channel nobody is watching and no reply will ever arrive: the agent does not wait and does not phrase anything as a question — it **records the missing connection or authorization as a blocker** in its final report and delivers whatever the evidence already supports.
+
 ## In-session Switch Commands
 
 ---
diff --git a/en/ai-sre/knowledge.mdx b/en/ai-sre/knowledge.mdx
index 36c7b0cd..c9008d08 100644
--- a/en/ai-sre/knowledge.mdx
+++ b/en/ai-sre/knowledge.mdx
@@ -71,11 +71,24 @@ After reading `DUTY.md`, the agent decides which `@references` to expand based o
 
 ---
 
-Go to the **Knowledges** management page to create, edit, enable/disable, or delete Knowledge Packs for your account or teams. The list shows each pack's **Name / Scope / Files / Status / Actions**, and a scope filter at the top lets you switch between Shared and Team views.
+Go to the **Knowledges** management page to create, edit, enable/disable, or delete Knowledge Packs for your account or teams. Once packs exist, the list shows each pack's **Name / Scope / Files / Status / Actions**, and a scope filter at the top lets you switch between Shared and Team views.
+
+**First visit (empty state)**: when the current scope has no Knowledge Pack and the account has none at all, the page is taken over by the empty state. It lists five sources that can be drafted automatically — **Code repositories** (services, dependencies, tech stack), **Deployment topology** (environments, clusters, workloads), **Infrastructure** (cloud accounts, databases, middleware), **Changes** (releases and config changes), and **Monitoring** (metrics, logs, alert rules) — each showing how much has already been read from your connected tools and from Flashduty (labels like "N repositories", "N clusters", "N connections", "N in the last 30 days"); a source with nothing yet shows **Connect →**, which jumps to the plugins page to connect it. Below the cards the page notes that unconnected parts are left blank and can be filled in later, and that schedules, escalation rules, and handling records are read straight from Flashduty with no connection needed.
+
+While the empty state owns the page, the only two ways to start a pack are its own buttons:
+
+| Entry | Behavior |
+| --- | --- |
+| **Initialize AI-SRE** | Opens a new AI SRE session and **sends** `/init` immediately: the agent drafts content from those five sources and saves it after confirming each item with you |
+| **Upload existing documents** | Opens a new AI SRE session with `/init` **pre-filled** in the input box (not sent) and the attachment picker open, so you can hand existing documents to the agent for distillation |
+
+**While the empty state owns the page, the 创建 (Create) button in the page header, the scope switcher, and the search box all disappear**: there is nothing to filter over, and a second entry point would only compete with the two buttons in the empty state. Once a pack exists the page returns to its regular layout — **Create** in the top-right corner, the scope filter and search at the top. When you enter within a team scope, the two empty-state entries bind the new session to that selected team.
+
+If you lack account-level edit permission, account scope shows a one-liner — "no account knowledge base yet" — instead of the full empty state; the toolbar stays, so you can switch to a team scope and inspect that team's pack.
 
 <Steps>
   <Step title="Create a Knowledge Pack">
-    Click **Create** in the top-right corner of the page to open the "Create knowledge base" dialog. A Knowledge Pack has no editable name of its own — it's a singleton resource per target (account or team), so the dialog only asks you to choose a **Scope**: Shared or a specific team. To create a team-level pack, you must belong to the target team; Shared-scope creation is limited to the Account Owner or admins. Each target can own only one pack. Accounts and teams that already have a pack remain in the dropdown and are marked as having an existing Knowledge Pack; after you select one, the primary button becomes **Open knowledge base** and opens that pack instead of creating another. Choose a scope without a pack and click **Create** to make one. The console checks again immediately before creation, so if someone else has just created a pack for that scope, it opens the existing pack instead. The console uses the scope (Shared / team name) as the pack's display identifier.
+    Click **Create** in the top-right corner of the page (this button appears only once a pack already exists — see the empty-state note above) to open the "Create knowledge base" dialog. A Knowledge Pack has no editable name of its own — it's a singleton resource per target (account or team), so the dialog only asks you to choose a **Scope**: Shared or a specific team. To create a team-level pack, you must belong to the target team; Shared-scope creation is limited to the Account Owner or admins. Each target can own only one pack. Accounts and teams that already have a pack remain in the dropdown and are marked as having an existing Knowledge Pack; after you select one, the primary button becomes **Open knowledge base** and opens that pack instead of creating another. Choose a scope without a pack and click **Create** to make one. The console checks again immediately before creation, so if someone else has just created a pack for that scope, it opens the existing pack instead. The console uses the scope (Shared / team name) as the pack's display identifier.
   </Step>
   <Step title="Edit Files">
     Click any row in the list to open the inspector. The left panel shows the file tree; the right panel is an inline editor. Click **New File** to enter a filename (e.g., `runbook.md`), or use **Upload** to import a local file. Markdown files support both **Preview** and **Source** views. Click **Save** after editing.
diff --git a/en/ai-sre/mcp.mdx b/en/ai-sre/mcp.mdx
index 8ae3b3d6..a68e5500 100644
--- a/en/ai-sre/mcp.mdx
+++ b/en/ai-sre/mcp.mdx
@@ -43,38 +43,43 @@ In AI SRE, MCP extends an agent's capability from "built-in tools" to "any exter
 
 ---
 
-Go to **Plugins → MCP** and click **Browse Marketplace** to open the **MCP Directory**, where you can browse Flashduty's curated selection of third-party MCP server templates.
+Go to **Plugins → Overview** to see Flashduty's curated catalog of third-party MCP templates. The catalog is grouped into category tabs (All / Observability / Cloud & Infrastructure / Database & Middleware / Code & Collaboration / Skill), and the search box in the top-right corner filters it by name or description.
+
+The **Recommended** block above the catalog ("Recommended from your alert sources and common usage. Once connected, AI SRE can use them during investigations.") picks the templates that match the **alert integrations already configured** in your account (ranked by alert count over the last 30 days), then fills in the picks promoted for your current locale, showing at most 3. Installed templates, templates that need a Runner, and templates you may not install never appear here.
 
 <Steps>
-  <Step title="Open the directory">
-    Click **Browse Marketplace** on the MCP list page to open a directory dialog that displays all available MCP server templates in a card grid. Each card shows the MCP server name, author, description, and tags.
+  <Step title="Find the template to connect">
+    Each catalog row shows the template name and description; when MCP / App / Skill rows are mixed on the same screen, the row also carries a kind tag. An uninstalled row has a round **+** button on its right: clicking **+** or clicking the row itself opens the **Connect** dialog. When a template needs a self-hosted Runner and the account has no Runner available, the row's tag reads **Requires a self-hosted runner**; for a template you may not install, the row shows no **+** and is not clickable.
   </Step>
-  <Step title="View details">
-    Click any MCP server card to open the detail view, which shows the full description, transport, authorization mode, whether a BYOC Runner is required, the vendor, connection parameter documentation, and a link to the vendor's official docs. Cards for already-installed MCP servers display a gear icon; clicking it takes you directly to that server's edit form.
+  <Step title="Review the template and fill in the connection parameters">
+    The dialog first shows the template's details: the vendor ("Official Datadog · MCP" or "Community · MCP"), a link to its official docs, its description, and a set of "**Ask things like this once connected**" example questions. Then come the connection parameters the template declares — URL / endpoint placeholders and environment variables. **Shared** fields (shared account-wide under service authorization) are labelled "Shared by the whole account."; in **Member authorization (key)** mode there is also a "**Your API token**" field (a password input) labelled "Only for your own use — other members fill in their own the first time they use it.", with a "How to get one" docs link beside it.
   </Step>
-  <Step title="Start an install conversation">
-    For MCP servers not yet installed, click the **Install** button on the card. The system opens a new AI SRE session and injects the server's template metadata. The agent then guides you through entering the endpoint URL, completing credential authorization, and calls `tool_search` (probing the server's tools by name) to verify connectivity — the entire install flow happens **inside the conversation**, not through a one-click write to the database.
+  <Step title="Pick an execution environment and submit">
+    Choose the **execution environment** this connection should be made from — "Connects in the session's own environment by default."; for a template that needs a self-hosted Runner, the hint reads "If 〈name〉 is only reachable on your internal network, pick a self-hosted Runner on that network." The primary button is **Connect**; for a **Member authorization (OAuth)** template it reads "**Authorize 〈name〉**" and creates the connector first, then opens the browser authorization window (OAuth discovery, Dynamic Client Registration, and token exchange all run from the chosen environment).
   </Step>
-  <Step title="Confirm the installation">
-    Once the agent verifies connectivity, it writes the MCP server into the account via the `/safari/mcp/server/create` endpoint. The server then appears in the MCP list and is marked as "Installed" on the catalog card.
+  <Step title="Confirm the result">
+    On submit, the system creates the connector and runs one connection test against it. On success the dialog shows "**〈name〉 connected**" plus the example questions: click **Done** to close it, or click an example question to open a new chat with that question **prefilled** (it is not sent automatically). On failure it shows "**The connection test failed**" with the raw error: click **Retry** to re-run the test; for a template that needs a Runner, a non-cloud environment also offers a "Let AI SRE install it on the Runner" entry, which opens a new chat that carries no token and asks the agent to install the missing command-line tools (`npx`'s Node.js, `uvx`'s uv) on the self-hosted Runner.
   </Step>
 </Steps>
 
 <Note>
-The marketplace directory is **browse-only** — there is no one-click install endpoint. This is intentional: installing an MCP server must involve credential entry and connectivity verification. Skipping those steps would leave dead configurations in the account that can never actually connect. Conversational install ensures every MCP server has been validated by a real agent invocation before it is considered ready.
+The dialog creates the connector on the **first submit only**. After that its connection parameters are locked, and it shows "This connector already exists, created from the values you first submitted. To change them, edit it under Plugins → MCP." When the name collides with a connector that already exists, the dialog no longer echoes the backend error and instead shows "This account already has a connector named “〈name〉”. If that is the one you want, finish authorizing it under Plugins → MCP; otherwise an account owner or admin has to rename or delete it there first, then connect again."
 </Note>
 
 Installed MCP servers record a `source_template_name` field that points back to the originating template, making it easy to trace the server's provenance later. **Marketplace-installed MCP servers are fixed to Shared scope** (account-level, `team_id` is 0) and available to all members of the account; no team owner can be chosen at install time, and the same template can only produce one instance per account.
 
 <Warning>
-MCP servers marked **requires Runner** (shown by the `requires_runner` flag in the detail view; `requires_runner` is independent of transport, and the entire current curated catalog is HTTP Streaming and needs no Runner) can only be used in environments where you have a BYOC Runner deployed; cloud Sandboxes do not support them. Before installing, confirm your account has a working BYOC Runner configured. See [Environments (BYOC)](/en/ai-sre/environments).
+A template that **requires a Runner** (the `requires_runner` flag in its details) can only be used in an environment where you have deployed a BYOC Runner; cloud Sandboxes do not support it. `requires_runner` is independent of transport, and today's 55-template catalog contains both kinds: 27 **HTTP Streaming** templates that need no Runner, and 28 **stdio** templates that do — including Alibaba Cloud OpenAPI, Alibaba Cloud Observability, Nightingale (n9e), Gitee, GreptimeDB, Prometheus, Grafana (Self-Hosted), Kafka (Confluent), AWS, ClickHouse, MySQL, PostgreSQL, Alibaba Cloud RDS, Redis, and MongoDB. Those stdio templates are launched locally on each environment via `uvx` / `npx`, and a cloud Sandbox cannot launch local subprocesses; confirm your account has a working BYOC Runner configured before installing. See [Environments (BYOC)](/en/ai-sre/environments).
 </Warning>
 
 ## Adding an MCP Server
 
 ---
 
-Go to **Plugins → MCP**, click **Add Server** in the top-right corner, and fill in the form to define an MCP server.
+Go to **Plugins → MCP**. The list page has two entries in the top-right corner:
+
+- **Add MCP**: opens a form for defining an MCP server by hand (its fields are listed under "Basic Fields" below).
+- **Add in chat**: opens a new AI SRE session with this prompt prefilled — "I want to add an MCP server. First ask whether I want to connect my own service or install an existing one. If it is an existing one, ask which system I want to connect. If the plugin catalog has it, install it; if not, search the web and show me a few to pick from. Install the one I choose." The agent first asks whether you want to connect your own service or install an existing one; for an existing one it checks the plugin catalog first and only searches the web for candidates when the catalog has none, then completes the connection once you pick (nothing is sent automatically — you can edit the prompt first). The button appears only when there is an unambiguous scope to write into: always when you can author at account scope, otherwise when the current scope filter selects exactly one team you belong to (or you belong to exactly one team).
 
 ### Basic Fields
 
@@ -176,6 +181,8 @@ The MCP list displays each server's **name** (including its AI description), **s
 <AccordionGroup>
   <Accordion title="Enable / Disable" icon="toggle-on">
     Toggle the switch in the list. Only **enabled** servers are available to the agent; disabled servers are invisible to agents and cannot be called.
+
+    A disabled connector (any status other than `enabled`) is **not reported as connected** by the connect entry point: opening its **Connect** dialog shows "**Connector disabled**" and "This connector is disabled, so AI SRE can't use it. An account owner or admin has to re-enable it under Plugins → MCP.", with an **Open Plugins → MCP** button that jumps to that connector's row. An account owner or admin re-enables it there with the **Enable** toggle. Disabled connectors also drop out of the **Enabled** strip on Plugins → Overview.
   </Accordion>
   <Accordion title="Edit" icon="pen-to-square">
     Click the edit button (or click the row) to open the form. You can modify the name, transport, description, endpoint/command, authorization mode, and scope. If you do not have edit permission, the form opens in **read-only** mode with an explanation.
@@ -210,7 +217,7 @@ MCP shares the same **two-level scope** model as other resources (Skills, Knowle
 
 **Edit permissions**: team-level MCP servers can be acted on only by members of that team — organization admins must join the team first; Shared-scope MCP servers can be acted on only by the account owner or admins. There is no creator-retains-rights exception. When you lack edit permission, the toggle and action buttons for that row appear as **read-only**.
 
-**Create and reassign**: to create a new team-level MCP server, you must belong to the target team; Shared-scope creation is limited to the account owner or admins. **Marketplace installs are the exception**: they are fixed to Shared scope, and any account member can install one (no owner/admin permission required). When editing an existing MCP server, the account owner or admins can move it to any team to recover resources left behind by empty teams or departed members; regular members can move it only to teams they belong to. However, **Marketplace-installed MCP servers cannot be reassigned to a team** — their scope is shown as a fixed Shared value in the edit form. A small number of legacy team-scoped Marketplace rows from earlier versions can still be changed back to Shared scope; the reverse is not allowed. **Promoting to Shared scope carries the same gate as Shared-scope creation: only the account owner or admins can do it** — a regular member is denied even for servers belonging to their own team, and the prompt now reads "ask an admin to make it shared" instead of naming the owning team.
+**Create and reassign**: to create a new team-level MCP server, you must belong to the target team; Shared-scope creation is limited to the account owner or admins. **Marketplace installs are the exception**: they are fixed to Shared scope and started by the installer, and any account member can install an ordinary template (no owner/admin permission required). One class of template is the exception to that exception: when a template in a **member authorization** mode (key or OAuth) also asks for a free-form address / host parameter, the installer would effectively decide where other members' credentials are sent — so, to keep other members' credentials from flowing to a host the installer chose, installing and connecting that template is **limited to the account owner or admins**. A regular member sees no **+** on that row (and cannot click it), and opening its **Connect** dialog directly says "You don't have permission to install this. Ask your account owner or an admin." When editing an existing MCP server, the account owner or admins can move it to any team to recover resources left behind by empty teams or departed members; regular members can move it only to teams they belong to. However, **Marketplace-installed MCP servers cannot be reassigned to a team** — their scope is shown as a fixed Shared value in the edit form. A small number of legacy team-scoped Marketplace rows from earlier versions can still be changed back to Shared scope; the reverse is not allowed. **Promoting to Shared scope carries the same gate as Shared-scope creation: only the account owner or admins can do it** — a regular member is denied even for servers belonging to their own team, and the prompt now reads "ask an admin to make it shared" instead of naming the owning team.
 
 **Runtime visibility**: At session start, the agent is offered only **Shared-scope** MCP servers and servers belonging to the **team bound to the current session**. Once the agent reads a team's knowledge during an investigation, that team's MCP servers and Skills are mounted into the session on demand. **The account is the only security boundary at runtime; the team is an ownership and editing tag only.**
 
diff --git a/en/ai-sre/overview.mdx b/en/ai-sre/overview.mdx
index b7fe196d..d8d6a6fc 100644
--- a/en/ai-sre/overview.mdx
+++ b/en/ai-sre/overview.mdx
@@ -53,17 +53,30 @@ AI SRE is more than a chat box in the console — it covers multiple collaborati
 
 ---
 
-AI SRE is available to accounts on an On-call Pro or higher subscription, with no application needed.
+AI SRE is available to accounts holding a **valid (enabled)** On-call Pro or higher subscription, with no application needed.
 
 <AccordionGroup>
 <Accordion title="Billing" icon="gift">
   AI SRE is billed on actual usage starting September 16, 2026, 08:00 Beijing time, settled in credits (1 credit = ¥1); usage before that date isn't charged. Metered items are model usage, sandbox online time, and web search. Activation is free, eligible accounts get gift credits each billing period, and you can also buy credit packages (1,000 / 5,000 / 20,000 credits for ¥950 / ¥4,500 / ¥17,000, valid 365 days from payment). Pay-as-you-go is off by default; an admin can turn it on and optionally set a per-period cap. Full terms: [AI SRE Credit Package Purchase Agreement](/en/compliance/ai-sre-credit-package-purchase-agreement).
+
+  When the gift credits, credit packages, and wallet balance are all used up, AI SRE refuses new conversation requests: the composer is disabled and a **non-dismissible** notice stays pinned above it (the text comes from the server and covers all three shapes — "not activated yet", "this period's allowance is spent", and "the wallet is empty"), with a **Go to AI SRE billing** button that opens the billing center (`/wallet/plan?product=ai-sre`). An admin turns on pay-as-you-go, buys a credit package, or tops up the wallet there; once the state recovers, you can continue the conversation.
 </Accordion>
 <Accordion title="Human Authorization" icon="user-check">
   Production changes, restarts, rollbacks, and external notifications all require your confirmation before they execute.
 </Accordion>
 </AccordionGroup>
 
+### When the subscription lapses
+
+Every request re-checks the account's On-call subscription, so a subscription that lapses pauses AI SRE immediately. The interface shows the server's own sentence, and distinguishes two cases whose remedies differ — don't apply the wrong one:
+
+| Case | Notice | Remedy |
+|------|--------|--------|
+| The subscription's tier is Pro or higher, but the subscription isn't enabled (expired, or disabled for any other reason) | "This account's On-call subscription is no longer active (expired or disabled), so AI SRE is paused. It resumes automatically once the On-call subscription is renewed." | Renew the On-call subscription |
+| The account has no subscription, or its subscription is below Pro (whether or not it is enabled) | "AI SRE requires the On-call Professional plan. Upgrade the subscription to continue." | Upgrade to Pro or higher |
+
+The notice also appears in the console chat page (pinned above the composer, with a **Go to AI SRE billing** entry on its right), in IM sessions, in automation run records, and in A2A call errors; the credits overview reports the same sentence as `blocked_reason=no_license`. Recovery needs no re-activation: once the renewal or upgrade lands, the next request is admitted automatically.
+
 ## Core Capabilities
 
 ---
diff --git a/en/ai-sre/sessions.mdx b/en/ai-sre/sessions.mdx
index 9175641a..e07c6715 100644
--- a/en/ai-sre/sessions.mdx
+++ b/en/ai-sre/sessions.mdx
@@ -137,7 +137,11 @@ When the console publishes a new version, a **version update notice** appears ab
     **Inline truncation of large files**: apart from archives (which are not parsed — the agent gets only their sandbox path), attachments reach the agent as extracted text. When the extracted text exceeds **64 KB**, only the first **32 KB** is inlined (cut at a valid UTF-8 boundary), and the attachment envelope carries a pointer to the full file staged in the sandbox (like `~/.flashduty/attachments/...`) — if the full content matters, ask the agent to read the file from the sandbox with the read / bash tools; nothing is lost. In addition, PDFs larger than **3 MB** are no longer passed natively to the model; they fall back to text extraction under the same truncation rule.
   </Accordion>
   <Accordion title="Context references" icon="link">
-    When you enter AI SRE from an incident, alert, monitor rule, or monitor target page, the related object is embedded into the input box as a **reference capsule** — a small inline tag indicating the kind of object referenced — an incident, alert event, alert, monitor rule, host, monitor target, or on-call analytics — that travels with the message so the agent can start its analysis from that object directly. Click the capsule to open the referenced object in a new tab, or click its close button to remove the reference before sending. A single message can carry multiple references. Besides objects carried in automatically from a related page, you can also type `@` directly in any session's input box to trigger an incident search dropdown (supporting fuzzy keyword search and a list of recent incidents); selecting one inserts the same kind of reference capsule — a standalone entry point available at any time. Typing an email address does not false-trigger it: when the `@` directly follows an email-address character (a letter, a digit, or one of `._%+-`), the picker does not open; an `@` after a space or adjacent to Chinese text still triggers it.
+    When you enter AI SRE from an incident, alert, monitor rule, monitor target, or datasource page, the related object is embedded into the input box as a **reference capsule** — a small inline tag indicating the kind of object referenced — an incident, alert event, alert, monitor rule, host, monitor target, datasource, or on-call analytics — that travels with the message so the agent can start its analysis from that object directly. Click the capsule to open the referenced object in a new tab, or click its close button to remove the reference before sending.
+
+    **These entry points also carry a default question**, and the capsule sits at the spot the entry marks inside that sentence. Entering from a monitor target page, for instance, pre-fills "请分析这个监控对象 〈reference capsule〉：基于真实观测数据判断当前是否有问题或隐患，说明依据与影响面，并给出下一步排查或处置建议。请区分已确认事实、合理推断和待确认项；证据不足时明确说明不确定，不要过度归因"; entering from the datasource list pre-fills "调用 〈reference capsule〉 的 overview tool，校验 overview tool 是否可用". The prefill is only a draft — edit it, delete it, or send it as-is.
+
+    **A multi-object batch handoff pre-fills nothing**: when you click **AI analysis** on several incidents from the incident list, the input box gets no default question (it may stay empty) and no reference capsule lands in it — those references travel with the message instead. A single message can carry multiple references. Besides objects carried in automatically from a related page, you can also type `@` directly in any session's input box to trigger an incident search dropdown (supporting fuzzy keyword search and a list of recent incidents); selecting one inserts the same kind of reference capsule — a standalone entry point available at any time. Typing an email address does not false-trigger it: when the `@` directly follows an email-address character (a letter, a digit, or one of `._%+-`), the picker does not open; an `@` after a space or adjacent to Chinese text still triggers it.
   </Accordion>
   <Accordion title="Knowledge and skills" icon="book">
     When a session starts, the knowledge packs and skills for the bound team are loaded automatically. See <a href="/en/ai-sre/knowledge">Knowledges</a> and <a href="/en/ai-sre/skills">Skills</a> for details.
@@ -221,6 +225,36 @@ When a tool or MCP call is blocked because it lacks credentials or has not compl
 OAuth authorization links expire. After expiry, the card shows "Authorization link expired, please retrigger the task" — you need to start a new task to get a fresh authorization link.
 </Note>
 
+<Note>
+Channel differences: only the console (`web`) renders this card. IM and API channels get no card — the agent pastes the OAuth authorize link into its reply as plain text, and you open it in a desktop browser, complete the authorization, then reply "authorized" or "已授权" to continue (continuing is your explicit action, not an automatic OAuth callback side effect); for a secret-type credential there is no safe way to collect it over IM, so the agent tells you to open **this same session in the web console** and **never** asks you to paste the secret into the chat. On the automation channel nobody is watching, so the agent does not wait — it records the missing authorization as a blocker and delivers what it can. See [IM Platforms](/en/ai-sre/im#connections-and-authorization).
+</Note>
+
+### When a Connection Is Required
+
+When the agent searches for a capability to fulfil your request (`tool_search`), that search matches no tool at all, and the query happens to name a vendor that **exists in the marketplace catalog but your account has not connected**, a **"Connect [vendor] to continue"** card appears inline in the chat stream: the vendor's icon and name on the left, a **Connect** button on the right, and nothing else.
+
+This means you **don't have to go hunting in the plugins marketplace first**: name the vendor right in the conversation (for example, "connect Datadog for me") and you reach the connection step from there. If the catalog has no connector for that vendor at all, the agent just says so instead of showing a card.
+
+Clicking **Connect** opens that vendor's connect dialog (the same one as in the plugins marketplace: enter credentials, complete authorization and the connection test). Once the connection succeeds, the card flips in place:
+
+| Phase | Card state |
+|---|---|
+| Not connected | Title **"Connect [vendor] to continue"**, the vendor's description underneath, button **Connect** |
+| Connected | Title **"[vendor] connected"**, subtitle "Click Continue task and AI SRE will pick up where it left off", button **Continue task** |
+
+Clicking **Continue task** makes the console send "连接已完成，请继续之前的任务。" to the agent on your behalf so it resumes the original task — **closing the connect dialog does not resume the turn by itself**; resuming is always an explicit click from you. After a page reload the card still shows as connected: the console re-derives that from the template's own install state in the account, not from temporary browser state.
+
+In the following cases **no card** appears and the agent just says so in one sentence:
+
+- The account already has a connector for that vendor (in any team, in any environment): the agent says it is connected (or that it must be enabled or its credentials re-entered).
+- Only an account Owner or admin may connect that vendor: the agent says an admin has to do it.
+- The vendor's template requires a self-hosted Runner and this session has no Runner available.
+- The search matched a connected tool — a connect card only appears for "zero matches + the query names an unconnected marketplace template".
+
+<Note>
+Channel differences: only the console (`web`) renders this card. IM and API channels get no card — the agent gives the connect URL as a plain link and asks you to reply "继续" or "continue" once connected, then carries on; on the automation channel nobody is watching, so the agent does not wait — it records the missing connection as a blocker and delivers what it can. The full per-channel behavior is in [IM Platforms](/en/ai-sre/im#connections-and-authorization).
+</Note>
+
 ### Subagents
 
 When the agent delegates a subtask, a clickable **dispatch reference line** appears in the conversation: a status ring, a type badge (Agent / A2A), the subtask's name and current intent, and right-aligned status and elapsed time; once finished it adds the tool-call count / token usage / total duration, and on failure a red reason line appears underneath. The reference line is a compact single row and carries **no stop button** — stopping lives in the task panel's detail header (see "Task Panel and Background Tasks" below). Clicking the line opens a subagent session panel on the right, side by side with the main conversation — the main chat area shrinks accordingly rather than being covered by a modal. The panel can be expanded to fill the main area, or collapsed back to the side-by-side layout.
diff --git a/en/ai-sre/skills.mdx b/en/ai-sre/skills.mdx
index 164cc4c5..b70d55a9 100644
--- a/en/ai-sre/skills.mdx
+++ b/en/ai-sre/skills.mdx
@@ -1,6 +1,6 @@
 ---
 title: Skills
-description: A Skill is a reusable capability bundle — a SKILL.md instruction file plus a declared set of allowed tools — that the AI SRE agent can invoke on demand during a conversation. Install from the Marketplace, upload your own, or create one in conversation with skill-creator.
+description: A Skill is a reusable capability bundle — a SKILL.md instruction file plus a declared set of allowed tools — that the AI SRE agent can invoke on demand during a conversation. Install from the Marketplace, upload your own, or have skill-creator add one in a conversation — either authored from scratch or found online.
 keywords: ["AI SRE", "Skill", "SKILL.md", "Marketplace", "skill-creator", "agent", "resources"]
 sidebarTitle: Skills
 ---
@@ -48,6 +48,9 @@ tags:
   - tag2
 author: author-name
 license: MIT
+examples:
+  - zh: 帮我看看这个服务最近的延迟为什么升高
+    en: Why has this service's latency gone up recently?
 allowed-tools: bash, read, task
 ---
 
@@ -68,6 +71,7 @@ Frontmatter fields:
 | `license` | string | No | License identifier. |
 | `allowed-tools` | string[] | No | List of tools this skill is allowed to use. Leave empty for no additional restrictions. |
 | `venues` | string[] | No | Restricts this skill to specific kinds of execution environment. Accepts `cloud` (Cloud Sandbox) and `byoc` (self-hosted Runner); multiple values allowed. Leave empty to make it available everywhere. Values are validated at upload time and an invalid one is rejected. |
+| `examples` | object[] (`{zh, en}`) | No | "Try asking" sample questions. At most **10** entries, and both the Chinese and the English text are required. Each is validated under the same rule as `description` (no angle brackets `<` / `>`, at most 1024 characters), and an oversized or invalid entry is **rejected at upload time**. |
 
 <Note>
 Use `venues` for skills that structurally depend on one kind of environment — for example, a skill that needs a local binary, local files, or a private-network service on the environment's host simply cannot work inside a Cloud Sandbox. With `venues: [byoc]` declared, the skill neither appears in the agent's available-skills list nor can be triggered by `/<skill-name>` in a Cloud Sandbox session; only sessions bound to a self-hosted Runner can see and call it.
@@ -86,25 +90,22 @@ The AI SRE runtime bundles a few skills that are available without installation.
 
 ---
 
-Go to **Plugins → Skill** and click **Browse Marketplace** to open the skill **catalog**, where you can browse and install skill templates provided by Flashduty and Anthropic.
+The skill catalog is part of the plugin catalog on **Plugins → Overview**: skill templates are listed alongside MCP templates and the built-in Apps, grouped by category, with skills in their own **Skill** category (they also appear under the "All" tab, tagged `Skill`). The search box above the catalog filters by name or description, the tabs narrow the list to one category, and "See all N" next to a category heading expands that category; the search term and the selected tab live in the page URL, so leaving and coming back lands you where you were.
 
 <Steps>
-  <Step title="Open the catalog">
-    On the skill list page, click **Browse Marketplace** to open the catalog dialog, which displays all available skill templates in a card grid.
-  </Step>
-  <Step title="Search and filter">
-    Use the search box at the top to search by name or description. The **Filter** in the top-right corner lets you view only "Installed" or "Not Installed" skills; **Sort** supports "Installed First" or "Name A–Z".
+  <Step title="Find the template">
+    On **Plugins → Overview**, find the template under the **Skill** category; each row shows the template name and description.
   </Step>
   <Step title="Confirm the install">
-    Click the **+** button on any uninstalled card to open the `Install skill "<name>"` confirmation dialog, which notes "Installs to the account — available to all members": Marketplace installs are always **shared scope** (shared = account level), with no owner selection. Click **Install** to actually call the install endpoint — this copies the template content into your account as a regular skill entry and marks its source template (shown as a `v<version>` badge on the card to indicate "from Marketplace").
+    An uninstalled row has a round **+** button on its right; clicking **+** or the row itself opens the `Install skill "<name>"` confirmation dialog: "Installs to the account — available to all members." Marketplace installs are always **shared scope** (shared = account level), with no owner selection. Click **Install** to actually call the install endpoint — this copies the template content into your account as a regular skill entry and marks its source template (shown on the list as a `From Marketplace — <template name> v<version>` tooltip). A successful install reports `"<name>" installed`.
   </Step>
-  <Step title="Manage installed skills">
-    An installed card shows a gear icon in the top-right corner. Click it to open that skill's detail panel for management.
+  <Step title="Manage what is installed">
+    An installed row no longer shows **+**; it shows **Enabled**. Managing and updating it happens on the **Plugins → Skill** list — see "Management and Inspection" and "Automatic and Manual Updates" below.
   </Step>
 </Steps>
 
 <Note>
-New accounts are automatically pre-installed with a set of official Marketplace templates: `browser-automation` (a browser automation CLI for operating websites, dashboards, and monitoring UIs), `mcp-builder` (guides you through building an MCP server), `monit-query` (Monit data source queries), and `skill-creator` (see "Create in conversation" below). These pre-installed skills behave exactly like manually installed skills — you can enable/disable, uninstall, or update them to the latest version under "Management and Inspection" below.
+New accounts are automatically pre-installed with a set of official Marketplace templates: `browser-automation` (a browser automation CLI for operating websites, dashboards, and monitoring UIs), `mcp-builder` (guides you through building an MCP server), `monit-query` (Monit data source queries), and `skill-creator` (see "Add in conversation" below). These pre-installed skills behave exactly like manually installed skills — you can enable/disable, uninstall, or update them to the latest version under "Management and Inspection" below.
 </Note>
 
 <Warning>
@@ -156,11 +157,14 @@ When you want to replace an existing skill with a new version, the upload endpoi
 
 Both modes return the updated skill object on success. If the target skill does not exist, a 404 error is returned — neither mode silently creates a new skill. **Without the `replace` parameter (the default), a name collision is rejected outright**; the upload endpoint never implicitly overwrites an existing skill.
 
-### Create in conversation (skill-creator)
+### Add in conversation (skill-creator)
 
 Besides uploading a zip, you can **create and refine skills right inside an AI SRE session**. `skill-creator` is a Flashduty-provided Marketplace skill, pre-installed into your account by default, that exists specifically to "build skills." Trigger it with `/skill-creator` in any session, or just describe what you want in natural language:
 
+**Add in conversation** at the top right of the skill list page opens a new session with a pre-filled brief: "I want to add a Skill. First ask me whether I'm authoring it myself or installing an existing one from the web. For an existing one, search a few candidates for me to pick from, and install the one I choose." In other words the agent first asks whether you want to **author a new one** or **install an existing one**; for an existing one it checks the plugin catalog / Marketplace first, searches the web only when the catalog has nothing, and installs what you pick. The prompt is only pre-filled, never sent automatically. The button appears only when you have a scope you can author into: always when you can author at account scope, otherwise when the current scope filter selects exactly one team you belong to (or you belong to only one team).
+
 - **Create from scratch**: say "help me create a skill for troubleshooting X," or after an investigation, "turn that workflow into a skill." skill-creator clarifies your intent, drafts the `SKILL.md`, optionally sets up test cases and iterates on them, and saves the result as a skill in your account once you're happy.
+- **Find an existing one online**: when you enter through "Add in conversation" and choose to install an existing skill, the agent checks the plugin catalog first and searches the web only when the catalog has nothing; once you pick one it completes the install, which becomes a regular skill entry.
 - **Rewrite & optimize**: click **"Edit in Chat"** in a skill's detail panel to have skill-creator rewrite that skill; it can also tune the `description` to improve triggering accuracy.
 
 Once the draft is ready, the agent saves it as a skill with one click. If the name conflicts with an existing skill, a "Replace" confirmation dialog appears — under the hood this invokes the replace-by-name mode (`replace=true`, no `skill_id`).
@@ -201,6 +205,7 @@ Click any row in the list to open the skill's **detail panel**:
 - **Right side**: content preview of the selected file, with the skill description shown at the top.
 - **Header area**: skill name (short reference in the form `skill-xxxxxx`), scope label (shared / team name), source template version badge (hover to see "From Marketplace — template name `v<version>`"), **Update available** marker, author, `version`, and the full SkillID.
 - **Actions**: try in chat (injects `/<skill-name>` into a new session), update to latest version, edit in chat, replace, download, uninstall.
+- **Try asking**: if the skill declares `examples` in the `SKILL.md` frontmatter, the detail panel lists up to 2 sample questions; clicking one opens a new session with that skill plus the question pre-filled (never sent automatically).
 
 <Tip>
 When a skill package is **too large to preview**, the detail panel displays the file size and suggests using "Download" instead.
diff --git a/en/changelog/changelog.mdx b/en/changelog/changelog.mdx
index 49da8087..3ecca226 100644
--- a/en/changelog/changelog.mdx
+++ b/en/changelog/changelog.mdx
@@ -4,6 +4,51 @@ description: "This page documents important updates and feature releases for Fla
 keywords: ["Changelog", "Product Release", "Feature Updates", "Flashduty", "Version History"]
 ---
 
+<Update label="2026-09-16" description="💰 AI SRE billing goes live, the plugin catalog consolidates onto Overview">
+
+### AI SRE billing goes live
+
+AI SRE becomes a paid product on **September 16, 2026, 08:00 Beijing time**: usage is metered in credits for model usage, sandbox online time, and web search (1 credit = ¥1), and usage before that date isn't charged. Activation is free, eligible accounts get gift credits each billing period, and you can also buy credit packages (1,000 / 5,000 / 20,000 credits); pay-as-you-go is off by default, and an admin can turn it on with a per-period cap.
+
+- When the gift credits, credit packages, and wallet balance are all spent, the session is refused: the composer is disabled with a **non-dismissible** notice pinned above it and a "Go to AI SRE billing" entry. An admin turning on pay-as-you-go, buying a package, or topping up the wallet restores it
+- A lapsed On-call subscription (expired or disabled) pauses AI SRE the same way, with the notice "This account's On-call subscription is no longer active (expired or disabled), so AI SRE is paused" — it **resumes automatically on renewal**, with no re-activation; a subscription below Pro is told to upgrade
+
+See [AI SRE Overview · Activation and billing](/en/ai-sre/overview#activation-and-billing) and the [AI SRE Credit Package Purchase Agreement](/en/compliance/ai-sre-credit-package-purchase-agreement).
+
+### Plugin catalog consolidates onto Overview; marketplace access is now the "Connect" dialog
+
+**Plugins → Overview** is now a full plugin catalog: MCP templates, the built-in Apps (GitHub / GitLab / Kubernetes), and marketplace skills are listed together under category tabs, with search and "See all N" — the search term and the selected tab live in the page URL.
+
+- Connecting a marketplace MCP template is now the round **+** on its row → the **Connect** dialog (fill in the connection parameters, pick the environment, run the connection test); installs no longer happen inside a conversation
+- For a skill template, **+** opens the "Install skill" confirmation, which installs at account (shared) scope; an installed row shows "Enabled"
+- The conversational entry on the skill list page changed from "Create in conversation" to "**Add in conversation**": it opens a session with a pre-filled brief that first asks whether you're authoring a skill yourself or installing an existing one, and for an existing one checks the plugin catalog before searching the web
+
+See [MCP (External Tools)](/en/ai-sre/mcp) and [Skills](/en/ai-sre/skills).
+
+### Edge alerting engine supports server-pushed automatic upgrades
+
+A Linux (systemd) alerting engine receives its target version from the platform in the heartbeat response, downloads and verifies the artifact, and atomically swaps the binary; the replaced process then enters a probation window of about 180 seconds — the first successful heartbeat commits the upgrade, and otherwise it rolls back to the previous version. Docker and Kubernetes deployments do not take part and are still upgraded by changing the image version; the `--alerter.disableAutoUpdate` startup flag opts a single instance out. See [Alerting Engine](/en/monitors/engine/engine#automatic-upgrades).
+
+### New "Continue conversation" entries on the incident timeline
+
+Actions AI SRE performed on a member's behalf (for example, an automation rule finishing an investigation and writing its conclusion back to the incident) are recorded on the incident timeline under a joint signature of `{{name}} and AI SRE`: every such row now carries a persistent **Continue conversation** entry that reopens that session in the AI SRE panel, and the hover card on the AI SRE part of the signature offers the same button — relabelled from "View session" to "Continue conversation". See [Viewing incidents](/en/on-call/incident/search-view-incident#ai-sre-action-records).
+
+</Update>
+
+<Update label="2026-09-15" description="📉 Cloud-log data sources no longer support per-series no-data detection">
+
+### Cloud-log data sources no longer support per-series no-data detection
+
+Tencent Cloud CLS and Alibaba Cloud SLS are cloud-log data sources. They no longer support **per-series** no-data detection ("alert if previously found data is now missing") and keep only **Alert when all queries return no data**:
+
+- When you edit an alert rule, the per-series detection card no longer appears for cloud-log data sources. For these alerts the **recovery mode** is fixed to "recover automatically when any query finds data again" and is shown as read-only text — there is no dropdown
+- Existing rules with per-series detection enabled get that check **automatically turned off** when you open the edit page, with a notice; it takes effect on save. Not opening the edit page leaves the rule configuration untouched. If that was the rule's only enabled check, the save is blocked by the "at least one check" validation and you must reconfigure explicitly
+- Tencent Cloud CLS already rejected this check through a hard server-side validation; this change aligns the cloud-log data sources on one product rule
+
+We recommend switching these rules to **Alert when all queries return no data**. See [Alibaba Cloud SLS](/en/monitors/alert-rules/sls) and [Tencent Cloud CLS](/en/monitors/alert-rules/tencent-cls).
+
+</Update>
+
 <Update label="2026-09-11" description="🔗 Invite links and QR codes, join restrictions, AI query assistant for alert rules">
 
 ### Invite links and invite QR codes
diff --git a/en/developer/cli.mdx b/en/developer/cli.mdx
index 7d2559ca..bc135366 100644
--- a/en/developer/cli.mdx
+++ b/en/developer/cli.mdx
@@ -587,6 +587,26 @@ Core fields for `datasource-create` / `datasource-update`:
 - `kafka`: `sasl_mechanism` (`none` default / `plain` / `scram-sha-256` / `scram-sha-512`, the latter three require username and password), `username` / `password`, `timeout_ms` (default 5000), TLS fields (`tls_min_version` defaults to 1.2, max 1.3).
 - Passwords and `kafka.tls_key` support `${env:NAME}` references (resolved on the edge); literal values are omitted from responses, only `${env:...}` references are echoed. **On update, omit those fields to preserve stored secrets; explicitly send an empty string to clear**.
 
+#### `prometheus-api-v1-label-{label_name}-values` — Query Prometheus label values
+
+`GET /monit/prometheus/api/v1/label/{label_name}/values` (operationId `monit-prometheus-read-label-values`) carries a path parameter, so it is excluded from code generation and provided by a hand-written command. The command name follows the generated path-derived naming (the `monit` group plus the remaining path segments joined by hyphens), so it shows up under `flashduty monit --help` but cannot be guessed intuitively — use it as written here:
+
+```bash
+flashduty monit prometheus-api-v1-label-{label_name}-values <label_name> --data-source-id <datasource-id>
+flashduty monit prometheus-api-v1-label-{label_name}-values job --data-source-id 12345   # List all values of the label job
+```
+
+| Argument | Description |
+|----------|-------------|
+| `<label_name>` | Positional argument (required, exactly one), such as `job` or `instance` |
+| `--data-source-id` | Datasource ID (required, minimum 1), from `monit datasource-list`; must be a Prometheus-compatible datasource owned by the current account |
+
+The response body is the **datasource's native Prometheus payload**, not the Flashduty `{request_id, error, data}` envelope: on success it is `{"status":"success","data":["api","db","worker"]}`. When the datasource itself rejects a query (an unknown label name, say), the command fails with a non-zero exit code and the error text is whatever the datasource (or the Monitors proxy) returned verbatim — Prometheus's own error looks like `{"status":"error","errorType":"bad_data","error":"unknown label name"}` and is unrelated to Flashduty's error-code scheme.
+
+<Note>
+This command only reads the value set of one label; to fetch time series from an expression or run richer PromQL queries, use `monit-query <datasource-id> --tool 'prometheus.query'` as described above.
+</Note>
+
 ### alert — Alert and alert-event queries
 
 ```bash
@@ -663,7 +683,7 @@ In `json`/`toon` mode the rows default to the compact fields `incident_id`, `tit
 
 ### Full command coverage
 
-Beyond the curated commands above, the CLI now provides **full coverage** of the Flashduty OpenAPI through a spec-driven code generator. The current OpenAPI contains **337 API operations**, and the CLI generates resource-organized commands for **334** of them; the remaining three — the streaming export `session-read-export` and the multipart uploads `mapping-data-write-upload` and `skill-write-upload` — are provided by hand-written commands (`session export`, `enrichment mapping-data-upload`, `safari skill-upload`). In addition to the On-call domain (incident, incident-trigger-subscription, change, channel, field, status-page, template, and more), it also covers:
+Beyond the curated commands above, the CLI now provides **full coverage** of the Flashduty OpenAPI through a spec-driven code generator. The OpenAPI spec the generator reads contains **340 API operations**, and the CLI generates resource-organized commands for **336** of them; the remaining four are provided by hand-written commands — the streaming export `session-read-export` (`session export`), the multipart uploads `mapping-data-write-upload` and `skill-write-upload` (`enrichment mapping-data-upload`, `safari skill-upload`), and the path-parameterized `monit-prometheus-read-label-values` (`monit prometheus-api-v1-label-{label_name}-values`, see "Query Prometheus label values" below) — and are organized into top-level command groups alongside the generated ones. In addition to the On-call domain (incident, incident-trigger-subscription, change, channel, field, status-page, template, and more), it also covers:
 
 - **AI SRE (`safari`)**: a2a-agents, artifacts, automations, knowledge, mcp-servers, sessions, skills, and more
 - **Alerting & noise reduction**: alert, alert-event, enrichment (alert-rules, rule-sets), route
diff --git a/en/developer/go-sdk.mdx b/en/developer/go-sdk.mdx
index 7996a2d0..347564be 100644
--- a/en/developer/go-sdk.mdx
+++ b/en/developer/go-sdk.mdx
@@ -184,8 +184,12 @@ Endpoints are grouped by service and hang off the client: the call convention is
 
 `client.Artifacts` (AI SRE artifacts) covers the 11 operations under `/safari/artifact/*`: on the gallery read side `ReadGet` (get a single published artifact by ID), `ReadList` (list artifacts visible to the caller, with title substring search and `scope` (`all` / `personal` / `team`) plus `team_ids` filtering), and `ReadGetFileState` (probe up to 50 presented-file IDs (`pf_` prefix) in one call for ones that already have a live published artifact); on the file side `ReadSign` (issue short-lived download/preview URLs for a presented file, valid 5 minutes, `expires_in` is fixed at 300) and `ReadStream` (download or preview the file's bytes with a signed token — the success body is a file, not a JSON envelope, with the raw bytes on `Response.Raw`); on the write side `WritePublish` (publish a session-produced file to the gallery), `WriteUpdate` (rename the artifact or transfer it between personal and team scope), and `WriteDelete` (detach it from the gallery; the source file stays with its session); public sharing `WriteShareEnable` (turn on anonymous public sharing and return the public link — anyone with the link can view it, no login required), `WriteShareRevoke` (turn sharing off; the link stops resolving immediately), and `WriteShareSync` (refresh the public snapshot with the latest content — when `share_enabled` is true and `share_file_id` differs from `file_id`, the snapshot is stale and calling this refreshes it). Exported types include `PublishedArtifactItem`, `ArtifactShareState`, `SignedUrLs`, and the various `Artifact*Request` / `Artifact*Response` structs.
 
+`client.Members.MemberNotify` (`POST /member/notify`, `memberNotify`) sends an email to account members on behalf of the caller, and is callable only with a credential minted for an AI SRE session — any other credential, a plain `app_key` included, is rejected with `AccessDenied` (check it with `IsAccessDenied` / `ErrorCodeOf`). Request fields: `subject` (required, 1–200 characters) and `html` (required, the entire email body the recipients see; the server sanitizes it, stripping tags such as `script`, `style`, and `iframe` plus every `on*` event handler, keeping images only when `src` is `https` and links only for `http`, `https`, and `mailto`), while `person_ids` is optional (at most 20, no duplicates; omitted or empty sends to the caller only). Call it once with `dry_run` set to `true` before sending: nothing is queued, the response's `html` is the exact email recipients would get — so you can confirm the sanitizer kept everything the body depends on — and neither the hourly limit nor the per-turn duplicate check is consumed. Delivery is asynchronous, so `accepted` only means the email was queued; the response returns one entry per recipient in `recipients[]` (`person_id` plus `status`), where `status` is `accepted` or `skipped`, and a skipped entry carries a `reason` of `not_member`, `no_email`, `email_disabled`, `duplicate`, `rate_limited` (at most 20 emails per recipient per hour), or `send_failed`.
+
 `client.Diagnostics.QueryData` runs a synchronous query via `POST /monit/query/data` and returns a stable `query_result.v1` structured result (`result.kind` is one of `frames`, `records`, or `samples`). This API requires monit-edge v0.65.0 or later. For log-pattern and metric-trend analysis, use `client.DataSources.ToolsInvoke` with `prometheus.metric_trends`, `loki.log_patterns`, or `victorialogs.log_patterns`.
 
+`client.Diagnostics.QueryExplore` (`POST /monit/query/explore`, `monit-read-query-explore`) runs an explore query against a configured data source and returns the data source's native `explore_result.v1` shape: `ExploreData.format` is always `explore_result.v1`; `result.kind` is `frames` (columnar tables or time series, see `ExploreFrame` / `ExploreField`), `samples` (instant values with labels, `ExploreSample`), or `logs` (log entries as `ExploreLogEntry`, at most 1,000, with `has_more` set when truncated and `applied_limit` reporting the effective cap); and `execution.effective_step_seconds` echoes the step actually used after applying `max_data_points` and `min_step_seconds`. Request fields: `datasource_id` (from `/monit/datasource/list`, and it must belong to the authenticated account), `expr` (a query expression in the data source's native language — PromQL, LogsQL, SQL, and so on), `args` (macro substitutions keyed by variable name, used for Grafana-style variables; required in the request, so pass an empty `map[string]string{}` when you have none — a nil Go map serializes to `null`, which does not satisfy the schema), and `execution` (`QueryExploreExecution`: `kind` is `instant`, `range`, or `window`; `to_ms` is required for all three; `range` additionally requires `from_ms` and `max_data_points`, `window` additionally requires `from_ms`; `min_step_seconds` is accepted only for `range`). How it differs from `QueryData`: reach for `QueryExplore` when you need the data source's native result shape (raw logs included) and `QueryData` when you need the stable `query_result.v1` contract. This API requires the **data source view** (`monit`) permission and monit-edge v0.68.0 or later in supported deployments.
+
 Beyond application management, `client.Applications` (RUM applications) covers the five **RUM remote configuration** methods: `RemoteConfigReadGet` (`POST /rum/application/remote-config/get`, read the live configuration and its `version`), `RemoteConfigReadHistoryList` (`/rum/application/remote-config/history/list`, page through published history versions), `RemoteConfigReadPreview` (`/rum/application/remote-config/preview`, evaluate a draft configuration against a simulated client's `env` / `app_version` / `sdk` and return the matching rule index `hit_rule_index` plus the `values` finally delivered, without publishing), `RemoteConfigWriteUpdate` (`/rum/application/remote-config/update`, publish a complete new configuration), and `RemoteConfigWriteHistoryRevert` (`/rum/application/remote-config/history/revert`, republish a history version's content as a new version). Main types: `RemoteConfig` (`enabled`, `activation`, `default`, `rules`, `custom`, `refresh_on_foreground`), `RemoteConfigValues` (the four SDK knobs a configuration can set), `RemoteConfigRule` (`match` conditions plus the `set` values), `RemoteConfigHistoryItem` (with `version`, `reason`, `content_hash`, and `updated_by`), and the `GetRemoteConfigRequest` / `ListRemoteConfigHistoryRequest` / `PreviewRemoteConfigRequest` / `UpdateRemoteConfigRequest` / `RevertRemoteConfigRequest` structs with their matching `*Response` types.
 
 `client.DataSources.ToolsInvoke` (`POST /monit/datasource/tools/invoke`, `monit-datasource-tools-invoke`) executes one deterministic tool against a configured datasource: `tool` is a single tool name prefixed by the datasource type (e.g. `mysql.overview`), and `params` is the tool-specific JSON parameters (omitted means `{}`; an explicit `null` is invalid). Alongside diagnostic tools, the entry supports `<type>.query` query tools (`prometheus`, `mysql`, `postgres`, `oracle`, `clickhouse`, `elasticsearch`, `loki`, `victorialogs`, `sls`, `tencent_cls`); the `/monit/query/data` entry stays unchanged. It requires all currently online routable Edge sessions in the cluster to support the v0.71.0 base invoke protocol (individual tools may require a newer implementation), and there is no tool catalog, no automatic replay, and no fallback to legacy diagnose. The request body limit is 128 KiB, the complete success response limit is 10 MiB, and the tool timeout is at most 25 seconds; the response is a `DatasourceToolResult` (`data` is tool-specific JSON, never null, `summary` is optional, and a `truncated` object with `reason` indicates truncation).
@@ -207,6 +211,8 @@ if err != nil {
 out, _, err := client.DataSources.ToolsInvoke(ctx, req)
 ```
 
+`client.DataSources.ReadPrometheusLabelValues(ctx, dataSourceID, labelName)` (`GET /monit/prometheus/api/v1/label/{label_name}/values`, `monit-prometheus-read-label-values`) lists every value of one label on a Prometheus-compatible data source through the monitoring proxy: the label name goes in the URL path (the SDK escapes it), and the target data source is selected by the `X-DSID` request header — the SDK sets it from the `dataSourceID` argument (a `0` ID or an empty `labelName` errors immediately), with the ID taken from `/monit/datasource/list` and required to be a Prometheus-compatible data source of the current account. It is the only method whose success body is not the Flashduty `{request_id, data}` envelope: the response decodes straight into `PrometheusLabelValuesResponse` (`data` carries the label-value strings when `status` is `success`; `errorType` and `error` are present when it is `error`). Failures before the data source is reached (`X-DSID` missing or invalid, data source absent, or not a Prometheus type) come back as `text/plain`, while the data source's own failures use its own JSON error shape; the SDK treats both alike and carries the raw body as-is on `*ErrorResponse.Message`. Supported deployments require monit-edge v0.35.0 or later.
+
 For `client.DataSources`, the `payload` selects a type-specific configuration block by `type_ident`. Fifteen `type_ident` values are allowed: `prometheus`, `loki`, `mysql`, `oracle`, `postgres`, `clickhouse`, `elasticsearch`, `sls`, `tencent_cls`, `victorialogs`, plus the new diagnostic-only types `redis_node`, `redis_sentinel`, `mongodb_mongod`, `mongodb_mongos`, and `kafka` — diagnostic-only types always have `alerting_enabled` false (which does not block non-alerting queries or tools) and reject true. Connection address rules: Redis/MongoDB diagnostic types take a single `host:port` (bracket IPv6), with no URI, userinfo, or query; `kafka` takes 1–32 unique comma-separated `host:port` bootstrap addresses (at most 4096 characters after normalization, and the payload has no broker list); for `mongodb_mongod` / `mongodb_mongos` the configuration block's `auth_source` defaults to `admin`, username and password must be configured together, and client certificates are unsupported; the Redis node configuration's `database` defaults to 0. Sensitive fields such as the diagnostic types' `password` and Kafka's `tls_key` support `${env:NAME}` references: literal values are omitted from responses (only `${env:...}` references are echoed back), omitting the fields on update preserves the stored values, and explicitly sending an empty string clears them.
 
 `enabled` and `alerting_enabled` are independent: `enabled` (whether business execution is enabled) defaults to true on create; `alerting_enabled` (whether alert evaluation is allowed; alerting also requires `enabled` true and an alerting-capable type) defaults to true for alerting types and false for diagnostic-only types on create. On update, omitting either preserves the current value and an explicit `null` is invalid; disabling (`enabled` false) is rejected with a conflict when enabled rules reference the datasource. Also note that `payload` is always `null` in `/monit/datasource/list` responses (the list query does not read the payload column); it is populated in create/update/info responses.
@@ -294,7 +300,9 @@ An unsuccessful call returned by the Flashduty API — whether the envelope carr
 When the API returns 429, the error is promoted to `*RateLimitError`: it embeds `*ErrorResponse` (so `errors.As` for `*ErrorResponse` still matches) and additionally carries a `RetryAfter` hint.
 
 <Note>
-If you receive a non-2xx response with a non-JSON body, the SDK returns a plain `error`, not `*ErrorResponse`. This indicates that a gateway, load balancer, proxy, or other intermediary produced the response, usually because the request exceeded an intermediary timeout. Retry the request or split a long-running batch into smaller batches, and do not assume that `errors.As(err, &apiErr)` matches this error.
+For **generated endpoints**, if you receive a non-2xx response with a non-JSON body, the SDK returns a plain `error`, not `*ErrorResponse`. This indicates that a gateway, load balancer, proxy, or other intermediary produced the response, usually because the request exceeded an intermediary timeout. Retry the request or split a long-running batch into smaller batches, and do not assume that `errors.As(err, &apiErr)` matches this error.
+
+The hand-written `client.DataSources.ReadPrometheusLabelValues` method is the exception: it parses no envelope and instead puts a non-2xx response's raw body verbatim into `*ErrorResponse.Message`, treating the platform's `text/plain` 4xx/5xx bodies and the data source's own JSON error shape alike (429 is still promoted to `*RateLimitError`). `errors.As(err, &apiErr)` therefore does match there — `Code` is usually empty, so read `Message` and `Response.StatusCode` to identify the cause.
 </Note>
 
 ```go
diff --git a/en/monitors/alert-rules/clickhouse.mdx b/en/monitors/alert-rules/clickhouse.mdx
index c85c8d89..80ca7071 100644
--- a/en/monitors/alert-rules/clickhouse.mdx
+++ b/en/monitors/alert-rules/clickhouse.mdx
@@ -100,9 +100,9 @@ This mode is used to monitor scenarios where "data is expected but actually miss
 
 ### Recovery Logic
 
-No-data alerts support configuring the **alert ending mode**, which decides how the alert ends:
+A no-data alert's **recovery mode** is configured inside the "Alert if previously found data is now missing" card and decides how that alert ends:
 
-| Ending Mode | Description |
+| Recovery mode | Description |
 |------|------|
 | **End automatically when data reappears** | Default. The alert ends automatically once the data reappears |
 | **End when data reappears or the timeout expires** | The alert ends when the data reappears or the automatic close timeout is reached. The timeout is in seconds with a minimum of 1. Available only when the "Alert if previously found data is now missing" mode is enabled |
diff --git a/en/monitors/alert-rules/elasticsearch.mdx b/en/monitors/alert-rules/elasticsearch.mdx
index 98f6b2a5..520e57ba 100644
--- a/en/monitors/alert-rules/elasticsearch.mdx
+++ b/en/monitors/alert-rules/elasticsearch.mdx
@@ -130,9 +130,9 @@ This mode is used to monitor scenarios where "data is expected but actually miss
 
 ### Recovery Logic
 
-No-data alerts support configuring the **alert ending mode**, which decides how the alert ends:
+A no-data alert's **recovery mode** is configured inside the "Alert if previously found data is now missing" card and decides how that alert ends:
 
-| Ending Mode | Description |
+| Recovery mode | Description |
 |------|------|
 | **End automatically when data reappears** | Default. Once that `host_name` reappears in query results, the alert ends automatically |
 | **End when data reappears or the timeout expires** | The alert ends when the data reappears or the automatic close timeout is reached. The timeout is in seconds with a minimum of 1. Available only when the "Alert if previously found data is now missing" mode is enabled |
diff --git a/en/monitors/alert-rules/loki.mdx b/en/monitors/alert-rules/loki.mdx
index aa1dd57d..fe8b635f 100644
--- a/en/monitors/alert-rules/loki.mdx
+++ b/en/monitors/alert-rules/loki.mdx
@@ -95,9 +95,9 @@ rate({job="node-logs"} [1m])
 
 ### Recovery Logic
 
-No-data alerts support configuring the **alert ending mode**, which decides how the alert ends:
+A no-data alert's **recovery mode** is configured inside the "Alert if previously found data is now missing" card and decides how that alert ends:
 
-| Ending Mode | Description |
+| Recovery mode | Description |
 |------|------|
 | **End automatically when data reappears** | Default. The alert ends automatically once the data reappears |
 | **End when data reappears or the timeout expires** | The alert ends when the data reappears or the automatic close timeout is reached. The timeout is in seconds with a minimum of 1. Available only when the "Alert if previously found data is now missing" mode is enabled |
diff --git a/en/monitors/alert-rules/mysql.mdx b/en/monitors/alert-rules/mysql.mdx
index c373e00f..18a21e43 100644
--- a/en/monitors/alert-rules/mysql.mdx
+++ b/en/monitors/alert-rules/mysql.mdx
@@ -100,9 +100,9 @@ This mode is used to monitor scenarios where "data is expected but actually miss
 
 ### Recovery Logic
 
-No-data alerts support configuring the **alert ending mode**, which decides how the alert ends:
+A no-data alert's **recovery mode** is configured inside the "Alert if previously found data is now missing" card and decides how that alert ends:
 
-| Ending Mode | Description |
+| Recovery mode | Description |
 |------|------|
 | **End automatically when data reappears** | Default. The alert ends automatically once the data reappears |
 | **End when data reappears or the timeout expires** | The alert ends when the data reappears or the automatic close timeout is reached. The timeout is in seconds with a minimum of 1. Available only when the "Alert if previously found data is now missing" mode is enabled |
diff --git a/en/monitors/alert-rules/oracle.mdx b/en/monitors/alert-rules/oracle.mdx
index 4ddc21d6..e4405fea 100644
--- a/en/monitors/alert-rules/oracle.mdx
+++ b/en/monitors/alert-rules/oracle.mdx
@@ -100,9 +100,9 @@ This mode is used to monitor scenarios where "data is expected but actually miss
 
 ### Recovery Logic
 
-No-data alerts support configuring the **alert ending mode**, which decides how the alert ends:
+A no-data alert's **recovery mode** is configured inside the "Alert if previously found data is now missing" card and decides how that alert ends:
 
-| Ending Mode | Description |
+| Recovery mode | Description |
 |------|------|
 | **End automatically when data reappears** | Default. The alert ends automatically once the data reappears |
 | **End when data reappears or the timeout expires** | The alert ends when the data reappears or the automatic close timeout is reached. The timeout is in seconds with a minimum of 1. Available only when the "Alert if previously found data is now missing" mode is enabled |
diff --git a/en/monitors/alert-rules/postgres.mdx b/en/monitors/alert-rules/postgres.mdx
index 909ea24a..ecd7b1c5 100644
--- a/en/monitors/alert-rules/postgres.mdx
+++ b/en/monitors/alert-rules/postgres.mdx
@@ -100,9 +100,9 @@ This mode is used to monitor scenarios where "data is expected but actually miss
 
 ### Recovery Logic
 
-No-data alerts support configuring the **alert ending mode**, which decides how the alert ends:
+A no-data alert's **recovery mode** is configured inside the "Alert if previously found data is now missing" card and decides how that alert ends:
 
-| Ending Mode | Description |
+| Recovery mode | Description |
 |------|------|
 | **End automatically when data reappears** | Default. The alert ends automatically once the data reappears |
 | **End when data reappears or the timeout expires** | The alert ends when the data reappears or the automatic close timeout is reached. The timeout is in seconds with a minimum of 1. Available only when the "Alert if previously found data is now missing" mode is enabled |
diff --git a/en/monitors/alert-rules/prometheus.mdx b/en/monitors/alert-rules/prometheus.mdx
index 3b6b5023..b0a773ba 100644
--- a/en/monitors/alert-rules/prometheus.mdx
+++ b/en/monitors/alert-rules/prometheus.mdx
@@ -138,16 +138,20 @@ Triggers an alert when **all queries return empty results for N consecutive chec
 Both sub-modes can be enabled simultaneously and run independently.
 </Note>
 
-### Alert Ending Mode
+### Recovery Mode
 
-After enabling either sub-mode, you can configure the **alert ending mode**, which decides how the no-data alert ends:
+The **recovery mode** (field `end_mode`) appears only inside Sub-mode 1 (Per-Series Monitoring, the card labelled "Alert if previously found data is now missing") and applies only to the condition in that card. Sub-mode 2's recovery mode is not configurable: the engine fixes it to "Recovers automatically once any query returns data again", shown as read-only text with no dropdown.
 
-| Ending Mode | Description |
+The recovery modes selectable inside Sub-mode 1:
+
+| Recovery mode | Description |
 |------|------|
 | **End automatically when data reappears** | Default. The alert ends automatically once the data reappears |
-| **End when data reappears or the timeout expires** | The alert ends when the data reappears or the automatic close timeout is reached. The timeout is in seconds with a minimum of 1. Available only when Sub-mode 1 (Per-Series Monitoring) is enabled |
+| **End when data reappears or the timeout expires** | The alert ends when the data reappears or the automatic close timeout is reached. The timeout is in seconds with a minimum of 1 (field `auto_close_after_seconds`) |
 | **Manual close only** | The alert stays active until you close it manually |
 
+The recovery mode belongs to a single condition rather than being a tab-wide shared setting, so it is not part of the **Trigger & recovery conditions** card — that card holds only the fields shared by all enabled conditions (`Trigger mode`, `Trigger condition`, `Recovery condition`).
+
 ### Comparison with Prometheus Native `absent()` Function
 
 | Method | Description |
diff --git a/en/monitors/alert-rules/sls.mdx b/en/monitors/alert-rules/sls.mdx
index b8824cb0..f1a54296 100644
--- a/en/monitors/alert-rules/sls.mdx
+++ b/en/monitors/alert-rules/sls.mdx
@@ -82,6 +82,12 @@ This mode is suitable for scenarios where filter logic is written directly in SQ
 
 This mode is used to monitor scenarios where "data is expected but actually missing".
 
+SLS is a cloud log service data source and does not support per-series no-data detection. It keeps only one condition, **Alert when all queries return no data**:
+
+- The UI shows a single condition card, "Alert when all queries return no data", backed by the `alert_on_empty_result` and `alert_on_empty_result_severity` fields.
+- The per-series card, "Alert if previously found data is now missing", is not rendered for SLS rules, so its config field `check_nodata.enabled` cannot be set at all.
+- Tencent Cloud CLS also disables this condition, and enforces it in the backend (submitting `check_nodata.enabled` is rejected with a 400); SLS is currently disabled by the frontend, without a backend guard.
+
 ### Configuration
 
 1. **Query Statement**: Write a query that is expected to continuously return data.
@@ -89,17 +95,32 @@ This mode is used to monitor scenarios where "data is expected but actually miss
     ```sql
     * | SELECT host, max(__time__) as last_seen GROUP BY host
     ```
-2. **Evaluation Rules**: If a `host` appeared in previous cycles but cannot be found in current and N consecutive cycles, triggers "No Data" alert.
+2. **Evaluation Rules**: The alert fires when all queries return empty results for N consecutive checks. N comes from the **Trigger condition** shared by the tab.
+
+### Existing Rules with Per-Series Detection Enabled
+
+For an existing SLS rule that has per-series no-data detection enabled, opening its edit page turns that condition off automatically (`check_nodata.enabled` is loaded as off) and shows a toast:
+
+<Warning>
+This datasource type does not support "Alert if previously found data is now missing"; the check has been turned off automatically and takes effect on save
+</Warning>
+
+The rule detail page is read-only and does not show this toast. The condition is turned off inside the edit page: as long as you do not open the edit page, the rule's config does not change; once you open it and save, the off state is written back to the rule. The automatic turn-off applies to this condition only, so at save time:
+
+- If the rule still has other enabled conditions (threshold evaluation, data exists), the "at least one must be enabled" validation does not block this downgrade, and per-series detection stops working with that save — which is exactly why the toast above is shown.
+- If this was the rule's only condition, the save is blocked by the "Threshold evaluation, Data missing, Data exists at least one must be enabled" validation, and you must change the configuration explicitly before it can be saved.
+
+After opening such a rule, switch its no-data detection to "Alert when all queries return no data", make sure at least one alert condition is enabled, and then save.
 
 ### Recovery Logic
 
-No-data alerts support configuring the **alert ending mode**, which decides how the alert ends:
+The **recovery mode** of "Alert when all queries return no data" is not configurable. The engine fixes it to **Recovers automatically once any query returns data again**, shown as read-only text in the UI:
 
-| Ending Mode | Description |
+| Recovery mode | Description |
 |------|------|
-| **End automatically when data reappears** | Default. The alert ends automatically once the data reappears |
-| **End when data reappears or the timeout expires** | The alert ends when the data reappears or the automatic close timeout is reached. The timeout is in seconds with a minimum of 1. Available only when the "Alert if previously found data is now missing" mode is enabled |
-| **Manual close only** | The alert stays active until you close it manually |
+| `Recovers automatically once any query returns data again` | A fixed value, not an option; there is no dropdown for it in the UI |
+
+The former recovery-mode dropdown (`End automatically when data reappears` / `End when data reappears or the timeout expires` / `Manual close only`) exists only inside the per-series card, so it is unavailable for SLS. The only configurable items shared by the conditions on the no-data tab are the trigger and recovery settings (`Trigger mode`, `Trigger condition`, `Recovery condition`).
 
 ## 4. Advanced Configuration
 
diff --git a/en/monitors/alert-rules/tencent-cls.mdx b/en/monitors/alert-rules/tencent-cls.mdx
index cffe2da0..5dcd5503 100644
--- a/en/monitors/alert-rules/tencent-cls.mdx
+++ b/en/monitors/alert-rules/tencent-cls.mdx
@@ -74,9 +74,9 @@ The topic picker supports searching by name or pasting a topic ID directly. Only
 
 Tencent CLS does not support per-series no-data detection:
 
-- Only "**Alert when all queries return no data**" is supported.
-- The "Alert if previously found data is now missing; recover when data is found again" option is not available — the backend rejects it, so the card does not appear in the UI.
-- Alert ending modes are limited to "End automatically when data reappears" and "Manual close only"; "End when data reappears or the timeout expires" is not offered.
+- Only one condition card is supported: "**Alert when all queries return no data**".
+- The "Alert if previously found data is now missing" option is not available — enabling it submits `check_nodata.enabled`, which the backend rejects with a 400 — so the card does not appear in the UI.
+- The **recovery mode** is not configurable: there are no options, and the engine fixes it to "Recovers automatically once any query returns data again", shown as read-only text in the UI. "Manual close only" does not exist here — the recovery-mode dropdown (`End automatically when data reappears` / `End when data reappears or the timeout expires` / `Manual close only`) is rendered only inside the per-series card, which never appears for CLS rules, so none of the three is selectable.
 
 ## Recovery Queries and Related Queries
 
diff --git a/en/monitors/alert-rules/victorialogs.mdx b/en/monitors/alert-rules/victorialogs.mdx
index 1c73488a..f6858533 100644
--- a/en/monitors/alert-rules/victorialogs.mdx
+++ b/en/monitors/alert-rules/victorialogs.mdx
@@ -134,9 +134,9 @@ Scenario: A service should always have INFO log output; if no INFO logs are gene
 
 ### Recovery Logic
 
-No-data alerts support configuring the **alert ending mode**, which decides how the alert ends:
+A no-data alert's **recovery mode** is configured inside the "Alert if previously found data is now missing" card and decides how that alert ends:
 
-| Ending Mode | Description |
+| Recovery mode | Description |
 |------|------|
 | **End automatically when data reappears** | Default. The alert ends automatically once the data reappears |
 | **End when data reappears or the timeout expires** | The alert ends when the data reappears or the automatic close timeout is reached. The timeout is in seconds with a minimum of 1. Available only when the "Alert if previously found data is now missing" mode is enabled |
diff --git a/en/monitors/data-sources/data-sources.mdx b/en/monitors/data-sources/data-sources.mdx
index 88026296..11a48d14 100644
--- a/en/monitors/data-sources/data-sources.mdx
+++ b/en/monitors/data-sources/data-sources.mdx
@@ -40,10 +40,24 @@ The data source list displays all configured data sources with the following inf
 - **Type**: Data source type with icon
 - **Connection URL**: The access address of the data source
 - **Associated Alert Engine**: The bound alert engine cluster name, with engine online status indicator
+- **Enable datasource**: An inline switch controlling whether the data source takes part in business queries and diagnostics — this column is where you enable or disable a data source in the console
 - **Notes**: Supplementary description
 
 You can filter data sources by name or type using the search box. The list auto-refreshes every 5 seconds to reflect real-time engine connection status.
 
+### Enable datasource
+
+The **Enable datasource** column on the right of the list is the console entry point for enabling and disabling a data source; a toggle takes effect immediately. The tooltip icon beside the column header explains what disabling does:
+
+| State | Meaning |
+|-------|---------|
+| **On** | The data source takes part in business queries and data source diagnostics as usual. |
+| **Off** | No queries, diagnostics or alert evaluations run against it, but the configuration — connection parameters, credentials, associated alert engine — is kept in full and it can be re-enabled at any time; disabling does not change `alerting_enabled`. |
+
+- **Permission**: toggling the switch requires the data source edit permission (`MonitDatasourceUpdate`); without it the switch is disabled and the column is read-only.
+- **New data sources are enabled by default**: they are always created with `enabled=true`, and the create/edit drawer has no such switch; to disable a data source, switch it off in the list after creating it.
+- **List badge**: the Name column no longer shows a separate "disabled" badge — the switch alone carries the enabled/disabled state. A "Not used for alerting" badge on the Name column means `alerting_enabled=false` and is unrelated to enabling or disabling.
+
 ## Create a data source
 
 <Steps>
@@ -89,6 +103,7 @@ Data sources have two independent switches, controlling business execution and a
 | **Enabled** | `enabled` | Whether business execution is enabled. When disabled, the data source rejects business queries and datasource tools, but `alerting_enabled` is unchanged |
 | **Alert evaluation** | `alerting_enabled` | Whether the data source may participate in alert rule queries and evaluation. Alert evaluation also requires `enabled=true` and an alerting-capable type; `false` does not block non-alerting queries and datasource tools |
 
+- **Console entry point**: the `enabled` switch is the **Enable datasource** column in the data source list (see [Enable datasource](#enable-datasource)); the create/edit drawer has no such switch. `alerting_enabled` is set in the create/edit drawer.
 - **Create defaults**: `enabled` defaults to `true`; `alerting_enabled` defaults to `true` for alerting-capable types and `false` for diagnostic-only types.
 - **Update behavior**: omitting either field preserves the current value; an explicit `null` is invalid.
 - **Diagnostic-only types** (`redis_node`, `redis_sentinel`, `mongodb_mongod`, `mongodb_mongos`, `kafka`) reject `alerting_enabled=true`.
@@ -110,6 +125,8 @@ Data sources have two independent switches, controlling business execution and a
 | **Minimum / Maximum TLS version** | Options: TLS 1.0, 1.1, 1.2, 1.3; defaults to system default. The minimum version must not be higher than the maximum version |
 | **Skip server certificate verification** | When checked, the server certificate is not verified |
 
+When **Basic Authentication** is enabled, **Username** and **Password** accept `${env:NAME}` references, resolved locally by each Edge (see [Reference credentials locally in Edge](#reference-credentials-locally-in-edge)); the **Server URL** and **Params** do not support this syntax.
+
 ### MySQL / Oracle / PostgreSQL
 
 Relational databases share a similar configuration structure:
@@ -126,6 +143,8 @@ Relational databases share a similar configuration structure:
 
 In addition to the basic connection settings above, Oracle supports multiple key-value **Options**. MySQL and PostgreSQL additionally support TLS/SSL encrypted connections, selected via the **TLS/SSL mode** dropdown.
 
+In the table above, **Username** and **Password** accept `${env:NAME}` references, resolved locally by each Edge (see [Reference credentials locally in Edge](#reference-credentials-locally-in-edge)); the connection address does not support this syntax.
+
 #### TLS/SSL modes for MySQL
 
 | Mode | Description |
@@ -171,6 +190,8 @@ Elasticsearch supports Cloud and Self-Managed deployments. Cloud is selected by
 | **CA certificate** | - | Optional | - |
 | **Certificate fingerprint** | - | Optional | - |
 
+In Cloud mode, **Cloud ID** and **API Key** accept `${env:NAME}` references; in Self-Managed mode, **Username / Password** and **Service Token** do. Each Edge resolves the reference locally (see [Reference credentials locally in Edge](#reference-credentials-locally-in-edge)).
+
 ### Loki / VictoriaLogs
 
 Loki and VictoriaLogs use the same HTTP connection structure as Prometheus: server URL, Headers, Params, Basic Authentication, and TLS settings such as a custom CA, mTLS, server name, TLS versions, and skipping certificate verification.
@@ -182,6 +203,8 @@ Loki and VictoriaLogs use the same HTTP connection structure as Prometheus: serv
 
 These addresses are input examples; the form does not save them as defaults automatically.
 
+When **Basic Authentication** is enabled, **Username** and **Password** likewise accept `${env:NAME}` references (see [Reference credentials locally in Edge](#reference-credentials-locally-in-edge)); the server URL and **Params** do not support this syntax.
+
 ### ClickHouse
 
 | Config Item | Description | Default |
@@ -198,6 +221,8 @@ These addresses are input examples; the form does not save them as defaults auto
 
 After you enable **TLS**, you can configure a custom CA, mTLS, server name, minimum / maximum TLS versions, and skipping server certificate verification. Disabling TLS clears these TLS fields from the form.
 
+**Username / Password** accept `${env:NAME}` references, resolved locally by each Edge (see [Reference credentials locally in Edge](#reference-credentials-locally-in-edge)); the connection address does not support this syntax.
+
 ### Aliyun SLS
 
 | Config Item | Description |
@@ -287,7 +312,7 @@ Alert rules of the Tencent CLS type can bind exactly one data source and do not
 | **Connection address** | Single `host:port`; bracket IPv6; no URI, userinfo, or query parameters | - |
 | **Username / Password** | Authentication credentials; must be configured together; supports `${env:NAME}` references; literal password is not echoed after saving | - |
 | **Authentication database** | Database used for authentication | `admin` |
-| **Timeout (milliseconds)** | Connection timeout | `3000` |
+| **Timeout (milliseconds)** | Connection timeout; range 1000–10000 | `3000` |
 | **TLS** | Whether TLS is enabled | Disabled |
 | **CA certificate** | PEM CA certificates or an `${env:NAME}` reference | - |
 | **Minimum / Maximum TLS version** | TLS 1.2 (default) or 1.3; the maximum must not be below the minimum | 1.2 / no constraint |
@@ -305,7 +330,7 @@ MongoDB does not support client certificate authentication (mTLS).
 | **Connection address** | 1–32 unique `host:port` addresses, comma-separated | - |
 | **SASL mechanism** | `none` (credentials not accepted), `plain`, `scram-sha-256`, `scram-sha-512` (the last three require username and password) | `none` |
 | **Username / Password** | SASL credentials; supports `${env:NAME}` references; literal password is not echoed after saving | - |
-| **Timeout (milliseconds)** | Connection timeout | `5000` |
+| **Timeout (milliseconds)** | Connection timeout; range 1000–10000 | `5000` |
 | **TLS** | Whether TLS is enabled | Disabled |
 | **CA certificate** | PEM CA certificates or an `${env:NAME}` reference | - |
 | **Client certificate / key** | PEM format; must be configured as a pair; the literal key is not echoed after saving; supports `${env:NAME}` references | - |
diff --git a/en/monitors/engine/engine.mdx b/en/monitors/engine/engine.mdx
index b531f3ed..bf4b8a7a 100644
--- a/en/monitors/engine/engine.mdx
+++ b/en/monitors/engine/engine.mdx
@@ -63,6 +63,25 @@ The page automatically generates install and upgrade commands based on your sele
 | **Docker** | Containerized deployment for environments with Docker already set up |
 | **Kubernetes** | Cloud-native environments, deployed as a Deployment |
 
+### Automatic upgrades
+
+The alert engine on a Linux deployment supports server-pushed automatic upgrades. When you pick **Linux** as the deployment method, the page shows this note:
+
+> The alert engine on Linux supports server-pushed automatic upgrades. When enabled, no manual upgrade command is needed; the command above remains available as a manual fallback.
+
+Whether a version is pushed is decided platform-side — the console has no switch. Once you have deployed with the installation configuration above, a Linux instance upgrades itself when a push arrives; while push upgrades are not enabled, keep copying the generated **upgrade command** and running it on the target machine.
+
+| Item | Description |
+|------|-------------|
+| **Applicable deployment methods** | Linux (systemd) only; Docker and Kubernetes deployments do not take part in automatic upgrades and are still upgraded by changing the image version |
+| **How it runs** | After the engine receives a target version in a heartbeat reply, it downloads and verifies the artifact itself, atomically replaces the binary, and continues running the new version — no command to run on the host at any point |
+| **Upgrade success** | The replaced process enters a probation window of about 180 seconds; the first successful heartbeat counts as a successful upgrade and completes it |
+| **Failure rollback** | If no heartbeat succeeds within the probation window (for example the new version cannot complete authentication or protocol exchange), or the new version keeps starting without committing a heartbeat (at most 3 boot attempts), the engine automatically rolls back to the previous version |
+| **Retry behavior** | A target version that rolled back on this host is not attempted again until a newer version is published; after a failed attempt the same version is not retried for about 30 minutes |
+| **Opting out** | The `--alerter.disableAutoUpdate` startup flag makes a single instance stop accepting automatic upgrades; container environments and unwritable binary directories are skipped automatically as well |
+
+Automatic upgrades require the engine to reach the artifact mirror, which is a public mirror by default; in offline or private-network environments point `--alerter.updateMirror` at an internal mirror. See "Automatic upgrade flags" in [Engine CLI flag reference](#engine-cli-flag-reference).
+
 ## API Key management
 
 API Keys are used for authentication between the alert engine and the SaaS. You can click **Manage API Key** on the engine installation/upgrade page to open the management panel.
@@ -123,3 +142,12 @@ Earlier versions used `alerter.serverConcurrency` and `alerter.serverRetry` to c
 - **High-throughput deployments** (many alert rules, high alert frequency): increase `alerter.alertRuleDeliveryWorkers` (e.g. 128) to reduce event queue backlog; raise `alerter.alertRuleEventQueueSize` as well if needed.
 - **Constrained network or CPU**: lower `alerter.alertRuleDeliveryWorkers` (e.g. 16–32) to limit outbound connections and avoid competing with other traffic.
 - **High packet-loss or unreliable networks**: consider a larger `alerter.serverSleep` (e.g. 10s) so backoff starts from a longer initial interval, reducing futile requests during congestion.
+
+### Automatic upgrade flags
+
+| Flag | Default | Description |
+|------|---------|-------------|
+| `alerter.disableAutoUpdate` | `false` | Disables server-pushed automatic upgrades. Set to `true` and the instance no longer performs automatic upgrades; container environments are detected and skipped automatically, and this flag takes precedence |
+| `alerter.updateMirror` | `https://static.flashcat.cloud/monitedge` | Mirror root URL for automatic upgrade artifacts. The engine downloads the artifact and checksum file from `<mirror root>/releases/download/<vX.Y.Z>/`; offline or private-network environments must point this at an internal mirror |
+
+Automatic upgrades take effect on Linux (systemd) deployments only and require the engine to reach the artifact mirror. If these conditions are not met, copy the **upgrade command** in the console and upgrade manually.
diff --git a/en/monitors/quickstart/quickstart.mdx b/en/monitors/quickstart/quickstart.mdx
index 69f1cc35..7cf41896 100644
--- a/en/monitors/quickstart/quickstart.mdx
+++ b/en/monitors/quickstart/quickstart.mdx
@@ -66,7 +66,7 @@ For an engine cluster composed of multiple instances, as long as at least one in
 
 There may be many alert rules. Monitors provides a tree-structured grouping for categorized management. Each alert rule must belong to a group. You can create groups first, then create alert rules under the groups.
 
-The create/edit alert rule page is a single-page form divided into five numbered sections — **Basic Configuration**, **Data Sources**, **Query Detection Method**, **Detection Frequency & Effective Time**, and **Event Configuration** — arranged top to bottom, so you fill them in by scrolling a single page; there is no step wizard.
+The create/edit alert rule page is a single-page form divided into five numbered sections — **Basic Configuration**, **Data Sources and Queries**, **Alert Conditions**, **Detection Frequency & Effective Time**, and **Event Configuration** — arranged top to bottom, so you fill them in by scrolling a single page; there is no step wizard.
 
 ### Basic Configuration
 
@@ -78,10 +78,16 @@ The create/edit alert rule page is a single-page form divided into five numbered
 | **Rule Name** | Name of the alert rule; does not support variable references (fixed names facilitate filtering and grouping operations). It must be unique within its group; imports, edits, and moves fail if the target group already contains that name |
 | **Additional Labels** | Similar to `labels` in Prometheus; attached to all alert events for filtering, routing, and inhibition |
 
-### Data Source Selection
+### Data Sources and Queries
+
+Section 2 has two parts: **Data Sources** decides which data sources the rule applies to, and **Query Statements** decides what to query and how.
+
+#### Data Sources
 
 ![Data source selection](https://docs-cdn.flashcat.cloud/imges/mon/9971af45b4bc19bfe807898bf1bf10a0.png)
 
+To the right of the sub-heading there is a hint icon explaining the scope of the binding, plus a **Go to Data Source Management** entry — it opens in a new tab so unsaved edits in the current form are not lost.
+
 First choose a **data source type**. Only types that **already have at least one configured data source** are listed here — types with none don't appear, so you can't end up picking a type with no data sources to query. When you're editing an existing rule, its current type always stays visible, even if all the data sources under that type have since been deleted.
 
 If the list is empty (showing "No data sources available"), your account hasn't configured any data sources yet — click **Go to Data Source Management** to create one first. If only the selected type has none, the page shows "The current data source type has no available data sources. Create one or switch type." If the type list fails to load, a **Reload** button appears.
@@ -97,11 +103,11 @@ Both methods can be used together, and at least one must be specified. The rule
 If you need stable rule bindings that are unaffected by data source renames, prefer exact match. See [Data Source Management](/en/monitors/data-sources/data-sources) for details.
 </Tip>
 
-### Query Detection Method
+#### Query Statements
 
-![Query detection method](https://docs-cdn.flashcat.cloud/imges/mon/4e38b46952d6cbbfb97c2d28843dcdbe.png)
+![Query statements](https://docs-cdn.flashcat.cloud/imges/mon/4e38b46952d6cbbfb97c2d28843dcdbe.png)
 
-Configure how to query data sources and how to evaluate alert conditions. Please read the usage instructions on the right side of **Query Detection Method** on the page.
+Under the **Query Statements** sub-heading you configure the query type and the statements themselves. To the right of the sub-heading is the **Usage guide** entry, which opens a drawer titled "Query Statements" with the guide to writing statements. For how value fields, label fields, and additional information are mapped from tabular query results, see [Query result field mapping](/en/monitors/alert-rules/query-result-fields).
 
 #### AI Query Assistant
 
@@ -111,9 +117,56 @@ Every query statement input has a rainbow **Write with AI** button in its top-ri
 - The entry is available on the main query, the recovery queries for threshold and data-exists modes, related queries, the query preview dialog, and the entity tree's rule PromQL and entity-category discovery PromQL. In the entity tree, the assistant only writes back the statement and never switches the data source.
 - Applying a statement changes the current form only; the rule is not saved automatically. Confirm that the statement matches the alert thresholds before saving.
 
+### Alert Conditions
+
+Section 3 offers three check modes, presented as tabs: **Threshold evaluation**, **Missing data**, and **Data exists**. Each tab has an enable switch; an enabled tab shows a check mark after its title.
+
+| Tab | What it evaluates |
+|-----|-------------------|
+| **Threshold evaluation** | Set a threshold expression per level; once a condition is met for the required number of checks, an alert of that level fires. When a higher-level threshold triggers, lower-level thresholds are skipped. With this tab enabled, at least one of Critical, Warning, and Info must be filled in |
+| **Missing data** | Evaluates "alert if previously found data is now missing" or "alert when all queries return no data"; the two cards can be enabled independently |
+| **Data exists** | Any returned data counts as a match; once the trigger count is reached, an alert of the configured level fires |
+
+The settings are grouped into cards: except on the **Missing data** tab, each tab has an **Alert fired** card and an **Alert recovered** card; the **Missing data** tab merges both into a single **Trigger & recovery conditions** card that applies to all enabled conditions above. The rows inside these cards are:
+
+| Field | Description |
+|-------|-------------|
+| **Trigger mode** | `Consecutive` or `Cumulative`; see the next section |
+| **Trigger condition** | The sentence matching the trigger mode. On the **Threshold evaluation** tab, the level expression rows (`Critical` / `Warning` / `Info`) sit above the trigger mode and are the trigger condition itself |
+| **Alert level** | `Critical`, `Warning`, or `Info`; defaults to `Critical`. The **Threshold evaluation** tab has no such row — the level comes from whichever expression row matched; on the **Data exists** and **Missing data** tabs it is set per condition |
+| **Recovery mode** | Sits in the **Alert recovered** card; on the **Missing data** tab it is set per condition — see the end of this section |
+| **Recovery condition** | **N consecutive normal checks to recover**, defaults to 1. At 1, a single check that meets the recovery condition produces a recovery event; above 1, several consecutive normal checks are required |
+
+#### Trigger mode: consecutive vs cumulative
+
+| Trigger mode | Meaning | Trigger condition sentence |
+|--------------|---------|----------------------------|
+| **Consecutive** (default) | Alerts after the set number of consecutive matches | `alert after N consecutive checks all match` — the rule alerts only after N consecutive checks meet the condition, where N is the **Matches** count, default 3 |
+| **Cumulative** | Alerts when enough of the last checks match, even if not consecutive | `alert once N of the last M checks match` — the rule alerts when N of the last M checks meet the condition, where M is the **Checks** count, defaulting to `max(Matches, 5)` when you switch to cumulative |
+
+- Under **Cumulative**, the match count cannot exceed the check count, and the check count cannot be lower than the match count. Neither can exceed 10000; going over is reported as a validation error rather than being silently clamped to the maximum
+- The two modes are mutually exclusive: after switching back to **Consecutive**, the check count is no longer submitted with the rule (the server tells the modes apart by whether that field is present), so the "N of the last M checks" semantics cannot linger
+- The underlying rule fields: match count `alerting_check_times`, check count `alerting_window_size`, recovery condition `recovery_check_times`
+
+<Note>
+**Cumulative matching requires alert engine ≥ `v0.69.0`.** When you select **Cumulative**, a "Supported in v0.69.0+" badge appears next to the option. Older engines fall back to consecutive matches, which may delay or miss alerts, but never fires earlier than the new semantics.
+</Note>
+
+#### Alert recovery
+
+The available recovery modes depend on the check mode:
+
+| Tab | Recovery mode |
+|-----|---------------|
+| **Threshold evaluation** | `Recovery when no thresholds are triggered` (default), `Recovery only when conditions are met` (requires an extra recovery expression), `Recovery when expression finds data` (requires a recovery query statement), `Keep the alert active until it is closed manually` |
+| **Data exists** | `Recover if no data` (default), `Recover when results found` (requires a recovery query statement), `Keep the alert active until it is closed manually` |
+| **Missing data** | For `Alert when all queries return no data` the recovery mode is fixed to "Recovers automatically once any query returns data again"; for `Alert if previously found data is now missing` you can choose `End automatically when data reappears` (default), `End when data reappears or the timeout expires` (requires an **Automatic close timeout** in seconds, minimum 1), or `Manual close only` |
+
 ### Detection Frequency and Effective Time
 
-This section is collapsed by default and only shows a one-line summary in the format detection frequency · rule timezone · effective time, e.g. `@every 15s · Asia/Shanghai · Always active`. Click **Expand** on the right to edit the settings, then click **Collapse** to fold it again. When you click save, if the detection frequency, rule timezone, effective time, or query time offset has a validation error, the section automatically expands and scrolls to the first error.
+This section is always visible: there is no one-line summary and no expand/collapse control — the detection frequency, query time offset, rule timezone, and effective time fields are laid out directly in the section.
+
+When you click save, if a field fails validation the page scrolls to and highlights the first invalid field: if the error is inside a tab of **Alert Conditions**, that tab is activated first, and if it is inside **Custom Fields & Related Queries** in **Event Configuration**, that area is expanded first.
 
 ![Detection frequency & effective time](https://docs-cdn.flashcat.cloud/imges/mon/0980d71a653985a1706243fc6795685e.png)
 
@@ -143,6 +196,8 @@ Saving a rule also validates its runtime configuration: the repeat notification
 
 ### Event Configuration
 
+Section 5 contains, in order, **Custom Fields & Related Queries** (collapsed by default, with Expand / Collapse on the right; while collapsed the summary line shows how many custom fields and related queries are configured, or a hint line when there are none), the notes description, and the repeat notification settings.
+
 | Config Item | Description |
 |--------|------|
 | **Custom Fields** | Similar to `annotations` in Prometheus; can attach dashboard URLs, SOP URLs, etc. |
diff --git a/en/on-call/advanced/war-room.mdx b/en/on-call/advanced/war-room.mdx
index 93dcc72b..3ed1aee3 100644
--- a/en/on-call/advanced/war-room.mdx
+++ b/en/on-call/advanced/war-room.mdx
@@ -61,7 +61,7 @@ Flashduty On-call War Room is an automated collaboration feature designed for in
         <Frame caption="Automatic sync in War Room">
           ![Create War Room in App](https://docs-cdn.flashcat.cloud/images/gif/war-room-create-app-en.gif)
         </Frame>
-        For Feishu/Lark app notifications, the **👥 Create War Room** button at the bottom of the incident card is controlled by a switch in the notification template: edit the Feishu/Lark app template under **Template Management** and turn on **Create War Room** in the card-fields panel of the **Additional info** tab (off by default). Only then does the button appear at the bottom of the card, provided the group-creation conditions are met. The card's **More Actions** area is now a dropdown menu (custom actions, snooze durations, and unacknowledge), and the war room is no longer one of its entries.
+        When notifying through the Feishu/Lark, Dingtalk, or Slack app, the **👥 Create War Room** button at the bottom of the incident card is controlled by a switch in the notification template: edit the app template for that channel under **Template Management** and turn on **Create War Room** in the card-fields panel of the **Additional info** tab (off by default). Only then does the button appear at the bottom of the card, provided the group-creation conditions are met. The card's **More Actions** area is now a dropdown menu (custom actions, snooze durations, and unacknowledge), and the war room is no longer one of its entries.
       </Tab>
       <Tab title="Mobile App">
         Open the Flashduty App, go to the incident details page, and tap the **⋯** button in the bottom action bar to open **More Actions**, then choose **Create war room**. Review the responder list and pick stakeholders in the panel, then submit. The entry is hidden when the incident already has a war room or is closed; when the incident has no responders, the entry is disabled with the toast "This incident has no responders, so a war room cannot be created".
diff --git a/en/on-call/channel/escalation-rule.mdx b/en/on-call/channel/escalation-rule.mdx
index 61b9aaf7..09dce253 100644
--- a/en/on-call/channel/escalation-rule.mdx
+++ b/en/on-call/channel/escalation-rule.mdx
@@ -88,7 +88,7 @@ Determines how users are reached.
   <Tab title="Group Chat (Reach Groups)">
     Send to instant messaging groups, with support for @ mentioning relevant personnel.
 
-    - **IM App Groups**: Supports Feishu/Lark, Dingtalk, WeCom, Slack, and Microsoft Teams groups (WeCom is only available for existing configurations and cannot be selected when creating new rules), requires completing [IM Integration](/en/on-call/integration/instant-messaging/lark) first. The group-chat picker automatically excludes platform-created chats such as war rooms (placeholder: "Select … group chat (war rooms excluded)"); stale targets render as **Chat unavailable** and can be removed
+    - **IM App Groups**: Supports Feishu/Lark, Dingtalk, WeCom, Slack, and Microsoft Teams groups (WeCom is only available for existing configurations and cannot be selected when creating new rules), requires completing [IM Integration](/en/on-call/integration/instant-messaging/lark) first. Disabled IM apps stay in the app dropdown, labelled "(Disabled)", and cannot be selected as a notification target — re-enable the app in Integrations first. The group-chat picker automatically excludes platform-created chats such as war rooms (placeholder: "Select … group chat (war rooms excluded)"); stale targets render as **Chat unavailable** and can be removed
     - **Group Bots**: Supports Feishu/Lark, Dingtalk, WeCom, Slack, Telegram, Zoom, and other Webhook bots. Telegram requires configuring a Webhook notification address and Chat IDs, Zoom requires configuring a Webhook address and Verify Token, and supports enabling @ mention functionality. See [Notification Channel Configuration](/en/on-call/configuration/notifications)
 
     <Note>
diff --git a/en/on-call/configuration/schedule.mdx b/en/on-call/configuration/schedule.mdx
index dbedbbb3..9cdb026b 100644
--- a/en/on-call/configuration/schedule.mdx
+++ b/en/on-call/configuration/schedule.mdx
@@ -64,7 +64,7 @@ Understanding these concepts before configuration will help you better plan your
       - **Follow personal preference**: Each responder receives notifications via their personally configured channels
       - **Follow unified settings**: Administrators select notification channels (SMS, email, and integrated IM apps)
     - **Group Chat Channels**: Send notifications to group chats, supporting the following platforms:
-      - Feishu app, DingTalk app, Slack app (select chat groups via integrated IM apps; the picker automatically excludes platform-created chats such as war rooms, and stale targets render as **Chat unavailable** and can be removed)
+      - Feishu app, DingTalk app, Slack app (select chat groups via integrated IM apps; disabled IM apps stay in the app dropdown, labelled "(Disabled)", and cannot be selected as a notification target — re-enable the app in Integrations first; the picker automatically excludes platform-created chats such as war rooms, and stale targets render as **Chat unavailable** and can be removed)
       - WeCom bot, DingTalk bot, Feishu bot (send via webhook URL)
       - Slack bot, Telegram bot, Zoom bot
 
diff --git a/en/on-call/configuration/templates.mdx b/en/on-call/configuration/templates.mdx
index 387672f4..9f47e6b0 100644
--- a/en/on-call/configuration/templates.mdx
+++ b/en/on-call/configuration/templates.mdx
@@ -367,9 +367,9 @@ Requires [Feishu/Lark integration](/en/on-call/integration/instant-messaging/lar
 
 When editing a Feishu/Lark app template, the **Additional info** tab next to the **Content** tab provides a card-fields switch panel ("These fields are rendered by the system. Use the switches to show or hide them at the bottom of the message."), which controls whether system fields such as channel, severity, responders, the details button, and AI analysis are rendered at the bottom of the card.
 
-**Create war room** is a Feishu/Lark-only switch (backed by the `feishu_app_war_room_enabled` field, **off** by default; save the template to apply the change):
+**Create war room** can be configured on Feishu/Lark app, Dingtalk app, and Slack app templates (backed respectively by the `feishu_app_war_room_enabled`, `dingtalk_app_war_room_enabled`, and `slack_app_war_room_enabled` fields, **off** by default; save the template to apply the change). The switch itself is labelled **Create war room**, and the panel describes it as "Once enabled, a dedicated Create War Room button is shown at the bottom of the card when the group-creation conditions are met."
 
-- **On**: when the incident is not closed, has no war room yet, and has responders, the Feishu/Lark incident card shows a dedicated **👥 Create War Room** button at the bottom; clicking it starts group creation
+- **On**: when the incident is not closed, has no war room yet, and has responders, the card for that channel shows a dedicated **👥 Create War Room** button at the bottom; clicking it starts group creation
 - **Off**: no such button is shown
 
 The card's bottom action area has changed as well: **More Actions** (that placeholder is its label) is now a dropdown select menu holding custom actions, snooze durations, and unacknowledge — the war room button is no longer one of its entries.
@@ -394,6 +394,8 @@ Requires [Dingtalk integration](/en/on-call/integration/instant-messaging/dingta
 <Frame caption="Dingtalk App Notification Effect">
 <img src="https://download.flashcat.cloud/flashduty/changelog/20230720/dingtalk_app_render.png" alt="Dingtalk App Notification" />
 </Frame>
+
+As with the Feishu/Lark app, the **Additional info** tab next to the **Content** tab provides a card-fields switch panel ("These fields are rendered by the system. Use the switches to show or hide them at the bottom of the message."), controlling whether system fields such as channel, snooze deadline, severity, aggregated alert count, responders, the details button, and AI analysis are rendered at the bottom of the card; the Dingtalk app template also offers the **Create war room** switch (backed by the `dingtalk_app_war_room_enabled` field, **off** by default; save the template to apply the change).
 </Tab>
 
 <Tab title="WeCom App">
@@ -447,6 +449,8 @@ When displaying images, separate images from other content with `---`, format st
 <Frame caption="Slack App Notification Effect">
 <img src="https://download.flashcat.cloud/flashduty/integration/slack/slack_app_message.png" alt="Slack App Notification" />
 </Frame>
+
+As with the Feishu/Lark app, the **Additional info** tab next to the **Content** tab provides a card-fields switch panel ("These fields are rendered by the system. Use the switches to show or hide them at the bottom of the message."), controlling whether system fields such as channel, snooze deadline, severity, aggregated alert count, responders, the details button, and AI analysis are rendered at the bottom of the card; the Slack app template also offers the **Create war room** switch (backed by the `slack_app_war_room_enabled` field, **off** by default; save the template to apply the change).
 </Tab>
 
 <Tab title="Microsoft Teams">
diff --git a/en/on-call/incident/escalate-dispatch-incident.mdx b/en/on-call/incident/escalate-dispatch-incident.mdx
index 820d18d7..414a04a3 100644
--- a/en/on-call/incident/escalate-dispatch-incident.mdx
+++ b/en/on-call/incident/escalate-dispatch-incident.mdx
@@ -34,7 +34,7 @@ Similar to **Reassign**, adding responders only allows selecting schedules or in
 </Frame>
 
 <Tip>
-These operations are also available in the [Flashduty App](/en/on-call/quickstart/mobile-app): **Reassign** and **Escalate** live under **More actions (⋮)** on the incident detail page, while **Add responders** lives in the **Responders** section of the incident detail page.
+These operations are also available in the [Flashduty App](/en/on-call/quickstart/mobile-app): **Reassign** and **Escalate** live under **More actions (⋮)** on the incident detail page, while **Add responders** lives in the **Responders** panel of the incident detail page. When the incident is **closed**, **Add responders** is hidden in the App along with **Reassign** — the **Responders** panel degrades to a read-only list that still shows who acknowledged the incident and when.
 </Tip>
 
 ## FAQ
diff --git a/en/on-call/incident/search-view-incident.mdx b/en/on-call/incident/search-view-incident.mdx
index a07d4afb..17707810 100644
--- a/en/on-call/incident/search-view-incident.mdx
+++ b/en/on-call/incident/search-view-incident.mdx
@@ -180,6 +180,15 @@ Every operation on [action items and follow-ups](/en/on-call/incident/work-items
 | `i_wi_auto_converted` | Converted N unfinished actions to follow-ups: title, title… (a batch conversion on incident close; one record summarizes all items) |
 | `i_wi_deleted` | Deleted action / Deleted follow-up |
 
+### AI SRE Action Records
+
+Actions that AI SRE performed on behalf of a member — for example when an [automation rule](/en/ai-sre/automations) finishes a run and writes its conclusion back to the incident — are recorded on the timeline under a **joint signature**: the byline reads `{{name}} and AI SRE`, and both names carry equal weight because AI SRE acts with that member's identity and permissions. Such records are flagged `via: ai_sre` on the backend.
+
+- **Signature hover card**: hovering the **AI SRE** part of the byline opens a hover card that states "Acting as `{{name}}` with their permissions" and offers a **Continue conversation** button, which opens that session in the AI SRE panel
+- **Always-visible entry**: every AI-performed action row also carries a persistent **Continue conversation** entry with a ↗ icon, so you can jump straight into the session without hovering; one incident can contain several AI sessions, so the entry sits on each row rather than being a single incident-level entry
+
+Both entries require the AI SRE module to be enabled and the current member to hold the `AiSreChatVisit` permission. When the session is a personal session (visible only to its creator) or has expired, the always-visible entry is not rendered and the hover card shows "This session is visible only to its creator or has expired" instead; when the row has no associated session, the hover card shows "This action is not linked to a session".
+
 ### Timeline Comments
 
 The top of the Timeline tab provides a Markdown comment box that supports:
diff --git a/en/on-call/integration/alert-integration/alert-sources/aliyun-dataworks-op.mdx b/en/on-call/integration/alert-integration/alert-sources/aliyun-dataworks-op.mdx
new file mode 100644
index 00000000..c865c0f3
--- /dev/null
+++ b/en/on-call/integration/alert-integration/alert-sources/aliyun-dataworks-op.mdx
@@ -0,0 +1,170 @@
+---
+title: "Alibaba Cloud DataWorks Integration"
+description: "Sync alert events from Alibaba Cloud DataWorks Intelligent Monitoring (Operation Center) to Flashduty On-call through a custom webhook, with automated alert noise reduction"
+keywords: ["alert integration", "Alibaba Cloud DataWorks", "DataWorks Intelligent Monitoring", "Operation Center", "monitoring alerts", "data ingestion"]
+---
+
+
+<div className="hide">
+
+## In Flashduty On-call
+---
+You can obtain an integration push URL in either of the following two ways.
+
+### Use an exclusive integration
+
+Choose this option when you do not need to route alert events to different collaboration spaces. It is simpler.
+
+<AccordionGroup>
+  <Accordion title="Expand">
+  
+  1. Go to the Flashduty console, select **Collaboration Spaces**, and open a space's detail page
+  2. Select the **Integrated Data** tab, click **Add an integration**, and open the add-integration page
+  3. Select the **Alibaba Cloud DataWorks Operation Center** integration and click **Save** to generate a card
+  4. Click the card to view the **push URL**, copy it for later use, and you are done
+  
+    
+</Accordion>
+</AccordionGroup>
+
+### Use a shared integration
+
+Choose this option when you need to route alerts to different collaboration spaces based on the alert payload.
+
+<AccordionGroup>
+  <Accordion title="Expand">
+  
+  1. Go to the Flashduty console and select **Integration Center => Alert Events** to open the integration selection page
+  2. Select the **Alibaba Cloud DataWorks Operation Center** integration:
+        - **Integration name**: define a name for this integration
+  3. Configure the default route and select the corresponding collaboration space (after creation, you can go to `Routing` to configure more routing rules)
+  4. Click **Save**, then copy the newly generated **push URL** on the current page for later use
+  5. Done
+    
+</Accordion>
+</AccordionGroup>
+</div>
+
+## In Alibaba Cloud DataWorks
+---
+**Step 1: Create a custom webhook**
+
+<div className="md-block">
+
+1. Log in to the Alibaba Cloud console and open the **DataWorks** product
+2. Go to **DataStudio** or **Operation Center** and open the **Intelligent Monitoring** page
+3. Open the alarm receiver configuration (the custom webhook entry) and create a new webhook
+4. Set the request URL to the Flashduty integration push URL copied above; the request method is POST
+5. After saving, you can click **Send test message**. DataWorks pushes a connectivity test message (`message.content`); Flashduty returns success without creating an alert event
+
+</div>
+
+**Step 2: Enable the webhook in monitoring rules**
+
+<div className="md-block">
+
+1. In **Intelligent Monitoring**, open the **custom rules** (instance status alerts, resource group alerts), **baseline management**, or **event management** page
+2. Create or edit a rule, and select the custom webhook created above as an alarm channel
+3. Save the rule. Alerts triggered by this rule are pushed to Flashduty in real time
+
+</div>
+
+## Supported alert types
+---
+<div className="md-block">
+
+DataWorks Intelligent Monitoring wraps every custom webhook message in a `message` field, distinguished by `message.title`. This integration supports the following three alert families:
+
+| message.title | Alert family | Description |
+| ------------- | ------------ | ----------- |
+| `DataWorks_Remind` | Custom alert | Instance status alerts (remind_unit: Task, Baseline, Project, BizProcess) and resource group alerts (ScheduleResourceGroup, DiResourceGroup) |
+| `DataWorks_Baseline_Alert` | Baseline alert | Baseline warning (dangerous) and SLA breach (overSla) |
+| `DataWorks_Event_Remind` | Event alert | Task error (ERROR) and task slowdown (SLOW) |
+
+The connectivity test message (`message.content`) is used only to verify the push URL and never creates an alert event.
+
+</div>
+
+## Severity mapping
+---
+<div className="md-block">
+
+Mapping from custom alert `remind_type` to Flashduty severity:
+
+| DataWorks remind_type | Flashduty | State |
+| --------------------- | --------- | ----- |
+| error | Critical | Critical |
+| exhausted error | Critical | Critical |
+| uncompleted | Warning | Warning |
+| cycle uncompleted | Warning | Warning |
+| run over time | Warning | Warning |
+| resGroup use ratio | Warning | Warning |
+| the number of waiting task in resGroup | Warning | Warning |
+| completed | Info | Info |
+| empty or unknown value | Warning | Warning |
+
+Mapping from baseline alert `status`:
+
+| DataWorks status | Flashduty | State |
+| ---------------- | --------- | ----- |
+| overSla (SLA breach) | Critical | Critical |
+| dangerous (warning) | Warning | Warning |
+| empty or unknown value | Warning | Warning |
+
+Mapping from event alert `event_type`:
+
+| DataWorks event_type | Flashduty | State |
+| -------------------- | --------- | ----- |
+| ERROR | Critical | Critical |
+| SLOW | Warning | Warning |
+| empty or unknown value | Warning | Warning |
+
+</div>
+
+## Alert Key and alert merging
+---
+<div className="md-block">
+
+DataWorks Intelligent Monitoring webhooks are **one-shot events**: the official protocol defines alert notifications only, with **no recovery** or update semantics, and it provides no vendor-level deduplication ID or fingerprint field. Therefore this integration never automatically recovers (closes) any alert; every event is delivered in a triggered state.
+
+Every webhook delivery receives a fresh random UUID as its Alert Key, so each push creates an independent alert event and repeated triggers are not merged automatically. To reduce noise, configure alert grouping or convergence policies in Flashduty.
+
+</div>
+
+## Field label mapping
+---
+<div className="md-block">
+
+Key fields from the push message are preserved as labels on the alert event and can be used for routing, silencing, and template rendering:
+
+| Label | Source field | Description |
+| ----- | ------------ | ----------- |
+| alert_type | title | Alert family (DataWorks_Remind, etc.) |
+| remind_name | remind_name | Rule name |
+| remind_unit | remind_unit | Monitoring granularity (Task, ScheduleResourceGroup, etc.) |
+| remind_type | remind_type | Raw trigger condition |
+| occur_time | occur_time | Raw occurrence time string |
+| remind_founder | remind_founder | Rule creator |
+| more_information | more_information | Operation Center instance URL |
+| task_size / number_of_alerts | same-name fields | Task count / nth alert notification |
+| node_id_list / node_name_list / node_owner_list | same-name fields | Node IDs / names / owners (comma-separated, up to 5) |
+| resource_group_name / threshold / duration | same-name fields | Resource group name / threshold / duration (minutes), resource group monitoring only |
+| baseline_name / baseline_owners | same-name fields | Baseline name / baseline owners |
+| cycle_number / key_instance / sla_time / buffer / status | same-name fields | Cycle number / key instance / SLA time / buffer (minutes) / baseline status |
+| task_name / task_owner_name / event_type / event_name | same-name fields | Task name / owner / event type / event name |
+
+</div>
+
+## FAQ
+---
+<div className="md-block">
+
+**Why are alerts never automatically recovered?**
+
+The DataWorks Intelligent Monitoring webhook protocol defines no resolve message; it is a one-shot notification with no recovery semantics. To close an alert, handle it manually in the Flashduty console or configure alert convergence policies for the rule.
+
+**Why is no alert visible after sending a test message?**
+
+The DataWorks connectivity test message (`message.content`) only verifies that the push URL is reachable. Flashduty returns success without creating an alert event. Trigger a real rule to verify the end-to-end flow.
+
+</div>
diff --git a/en/on-call/integration/alert-integration/alert-sources/new-relic.mdx b/en/on-call/integration/alert-integration/alert-sources/new-relic.mdx
new file mode 100644
index 00000000..2d5e8967
--- /dev/null
+++ b/en/on-call/integration/alert-integration/alert-sources/new-relic.mdx
@@ -0,0 +1,112 @@
+---
+title: "New Relic alert integration"
+description: "Send New Relic Issues to Flashduty On-call through Workflow webhooks and correlate activation, update, and closure notifications."
+keywords: ["alert integration", "New Relic", "Workflow", "webhook", "Issue"]
+---
+
+Use a New Relic Workflow webhook to send Issues to Flashduty On-call. One New Relic Issue maps to one Flashduty alert. Priority changes, Alert Event additions or closures, Issue merges, and closure notifications update that alert.
+
+<div className="hide">
+
+## In Flashduty On-call
+---
+
+Create either a dedicated or shared **New Relic** alert integration and copy its complete Push URL.
+
+</div>
+
+## Configure New Relic
+---
+
+<Steps>
+<Step title="Create a webhook destination">
+
+1. In New Relic, go to **Alerts → Enrich and Notify → Destinations**
+2. Create a **Webhook** destination named `Flashduty`
+3. Paste the complete Flashduty integration Push URL into Endpoint URL
+
+</Step>
+
+<Step title="Create a workflow">
+
+Create a Workflow whose Issue filters select the required policies, conditions, entities, or tags. Add the webhook destination. Enable at least **Activated** and **Closed**. Also enable **Priority changed** and **Other updates** to receive priority changes, Alert Event membership changes, and post-merge snapshots.
+
+</Step>
+
+<Step title="Configure the payload">
+
+```json
+{
+  "issue_id": "{{issueId}}",
+  "issue_url": {{json issuePageUrl}},
+  "title": {{json issueTitle}},
+  "description": {{json accumulations.conditionDescription.[0]}},
+  "priority": "{{priority}}",
+  "state": "{{state}}",
+  "trigger_event": "{{triggerEvent}}",
+  "is_correlated": {{isCorrelated}},
+  "account_id": {{nrAccountId}},
+  "incident_ids": {{json incidentIds}},
+  "sources": {{json accumulations.sources}},
+  "policy_names": {{json accumulations.policyName}},
+  "condition_names": {{json accumulations.conditionName}},
+  "entity_names": {{json entitiesData.names}},
+  "entity_ids": {{json entitiesData.ids}},
+  "workflow_name": {{json workflowName}}
+}
+```
+
+Keep `issue_id`, `state`, and `priority`. Flashduty rejects a missing `issue_id` because a random key cannot correlate later updates and closure.
+
+</Step>
+
+<Step title="Verify the lifecycle">
+
+Open a real Issue and confirm an active Flashduty alert. Change its priority or add another Alert Event and confirm an update on the same alert. Finally close the Issue and confirm the original alert recovers. A test notification proves connectivity only, not lifecycle correlation.
+
+</Step>
+</Steps>
+
+## Alert Key and Issue merges
+---
+
+Flashduty uses `issue_id` (`issueId`) directly as the Alert Key. Titles, priorities, policies, conditions, entities, and `incident_ids` do not affect it. `incident_ids` is the list of Alert Events aggregated into the Issue and is stored only as context.
+
+For `trigger_event=MERGE_REQUEST`, Flashduty updates the surviving Issue identified by the payload's `issue_id`. This version does not invoke Flashduty's internal alert merge operation or infer and close a source Issue.
+
+## Status and severity
+---
+
+| New Relic value | Flashduty status or severity |
+| :--- | :--- |
+| `state = CLOSED` | Recovered |
+| `state = CREATED` or `ACTIVATED` | Active alert |
+| `priority = CRITICAL` | Critical |
+| `priority = HIGH` | Warning |
+| `priority = MEDIUM` or `LOW` | Info |
+| Empty or unknown priority | Warning |
+
+New Relic warning thresholds create `HIGH` priority Alert Events, so `HIGH` maps to Flashduty Warning. Use an [Alert Processing Pipeline](/en/on-call/integration/alert-integration/alert-pipelines) for a different mapping.
+
+## Add custom labels
+---
+
+Add a top-level `custom_labels` object to send more Workflow variables:
+
+```json
+{
+  "issue_id": "{{issueId}}",
+  "priority": "{{priority}}",
+  "state": "{{state}}",
+  "custom_labels": {
+    "team": {{json accumulations.tag.team.[0]}},
+    "environment": {{json accumulations.tag.environment.[0]}},
+    "muting_state": "{{mutingState}}",
+    "open_alert_events": {{openIncidentsCount}}
+  }
+}
+```
+
+`custom_labels` accepts at most 50 entries. Use snake_case keys. Strings, numbers, booleans, arrays, and objects are accepted; arrays and objects are stored as JSON strings. Empty values are discarded, built-in labels win collisions, and the final event may contain at most 50 labels. Never send secrets.
+
+For the complete variable list, see [New Relic Workflow variables](https://docs.newrelic.com/docs/alerts/get-notified/custom-variables-alert-event-workflows/).
diff --git a/en/on-call/integration/instant-messaging/dingtalk.mdx b/en/on-call/integration/instant-messaging/dingtalk.mdx
index 1dc5c3df..b5b9e7da 100644
--- a/en/on-call/integration/instant-messaging/dingtalk.mdx
+++ b/en/on-call/integration/instant-messaging/dingtalk.mdx
@@ -212,10 +212,10 @@ Only one IM integration can have War Room enabled at a time. If you've already e
 
 ### AI SRE Controls
 
-After you enable **War Room**, the configuration page shows the following AI SRE controls. Both are enabled by default:
+Configure the following AI SRE controls under **Enhanced Features**. Both are enabled by default:
 
-- **Automatically start AI incident analysis**: Starts an AI incident analysis when a War Room is created successfully.
-- **Allow group @ AI SRE**: Lets users start a conversation by @mentioning AI SRE in a group chat connected through this integration. When disabled, this entry point does not respond.
+- **Automatically start AI incident analysis**: Appears only after you enable War Room. Starts an AI incident analysis when a War Room is created successfully.
+- **Allow AI SRE conversations in IM**: Available without enabling War Room. When enabled, people can @mention AI SRE in a group chat connected through this integration or start a direct conversation with the bot. When disabled, neither entry point triggers an AI SRE reply.
 
 These controls do not take effect until AI SRE is enabled for the account.
 
diff --git a/en/on-call/integration/instant-messaging/lark.mdx b/en/on-call/integration/instant-messaging/lark.mdx
index a5bcadeb..0e8a71a6 100644
--- a/en/on-call/integration/instant-messaging/lark.mdx
+++ b/en/on-call/integration/instant-messaging/lark.mdx
@@ -153,7 +153,7 @@ Only one IM integration can have War Room enabled at a time. If you've already e
 Configure the following AI SRE controls separately under **Enhanced Features**. They are enabled by default:
 
 - **Automatically start AI incident analysis**: Available after you enable War Room. Starts an AI incident analysis when a War Room is created successfully.
-- **Allow group @ AI SRE**: Available without enabling War Room. Lets users start a conversation by @mentioning AI SRE in a group chat connected through this integration. When disabled, this entry point does not respond.
+- **Allow AI SRE conversations in IM**: Available without enabling War Room. When enabled, people can @mention AI SRE in a group chat connected through this integration or start a direct conversation with the bot. When disabled, neither entry point triggers an AI SRE reply.
 - **Use thread replies in normal group chats**: Available without enabling War Room. When enabled, each normal-group thread has an independent session; War Rooms still receive replies directly in the group.
 
 These controls do not take effect until AI SRE is enabled for the account.
diff --git a/en/on-call/integration/instant-messaging/slack.mdx b/en/on-call/integration/instant-messaging/slack.mdx
index 09bf2244..b9e9ed92 100644
--- a/en/on-call/integration/instant-messaging/slack.mdx
+++ b/en/on-call/integration/instant-messaging/slack.mdx
@@ -101,7 +101,7 @@ After completing the previous steps, in the Flashduty On-call integration config
 Configure the following AI SRE controls separately under **Enhanced Features**. They are enabled by default:
 
 - **Automatically start AI incident analysis**: Available after you enable War Room. Starts an AI incident analysis when a War Room is created successfully.
-- **Allow group @ AI SRE and /fd commands**: Available without enabling War Room. Lets users @mention AI SRE or use `/fd` in a Slack group connected through this integration. When disabled, neither entry point responds.
+- **Allow AI SRE conversations in IM**: Available without enabling War Room. When enabled, people can @mention AI SRE or use `/fd` in a Slack group connected through this integration, or start a direct conversation with the bot. When disabled, none of these entry points triggers an AI SRE reply.
 - **Use thread replies in normal group chats**: Available without enabling War Room. When enabled, each normal-group thread has an independent session; War Rooms still receive replies directly in the group.
 
 These controls do not take effect until AI SRE is enabled for the account.
diff --git a/en/on-call/integration/instant-messaging/wecom.mdx b/en/on-call/integration/instant-messaging/wecom.mdx
index 653d37a6..0f77c53f 100644
--- a/en/on-call/integration/instant-messaging/wecom.mdx
+++ b/en/on-call/integration/instant-messaging/wecom.mdx
@@ -119,16 +119,25 @@ Only one IM integration can have War Room enabled at a time. If you've already e
 
 ### AI SRE Controls
 
-After you enable **War Room**, the configuration page shows the following AI SRE controls. Both are enabled by default:
+Configure the following AI SRE controls in the integration configuration page's **Enhanced Features** module. They are enabled by default:
 
-- **Automatically start AI incident analysis**: Starts an AI incident analysis when a War Room is created successfully.
-- **Allow group @ AI SRE**: Lets users start a conversation by @mentioning AI SRE in a group chat connected through this integration. When disabled, this entry point does not respond.
+- **Automatically start AI incident analysis**: Appears only after you enable War Room. Starts an AI incident analysis when a War Room is created successfully.
+- **Allow AI SRE conversations in IM**: Available without enabling War Room. It controls both entry points of this integration — @ AI SRE in group chats and direct chats with the bot. When disabled, the corresponding entry point does not trigger an AI SRE reply.
+
+The two WeCom app modes support different AI SRE entry points. **Allow AI SRE conversations in IM** is shown in both modes, and the integration detail preview also shows its status:
+
+| App mode | @ AI SRE in group chats | Direct chat with the bot |
+| :--- | :--- | :--- |
+| **Custom App Integration** | Supported | Supported |
+| **Third-party App** | Not supported; switch to **Custom App Integration** mode | Supported |
+
+In Third-party App mode, the switch is described as "When enabled, people can start a direct conversation with the bot. @ AI SRE in group chats is available only for self-built enterprise apps."
 
 These controls do not take effect until AI SRE is enabled for the account.
 
 ## 4. Configure AISRE
 
-To use AISRE with WeCom, enable **War Room** for the Flashduty WeCom integration first. Then create an additional Smart Robot in WeCom and connect it to Flashduty in API mode.
+To use AISRE with WeCom, confirm that **Allow AI SRE conversations in IM** is enabled in the Flashduty WeCom integration (War Room is not required), then create an additional Smart Robot in WeCom and connect it to Flashduty in API mode. The Smart Robot credentials are filled in on the integration configuration page of **Custom App Integration** mode.
 
 1. In the WeCom app, open **Workspace** from the left sidebar, then go to Smart Robot management.
 2. Create a new Smart Robot. Select **Manual creation**, then select **Create in API mode**.
diff --git a/en/on-call/quickstart/faq.mdx b/en/on-call/quickstart/faq.mdx
index 77980caa..6d8d8da6 100644
--- a/en/on-call/quickstart/faq.mdx
+++ b/en/on-call/quickstart/faq.mdx
@@ -215,7 +215,7 @@ description: "Learn about the most common questions when using Flashduty On-call
         <CardGroup cols={4}>
           <Card title="🇨🇳 Mainland China" icon="message" />
           <Card title="🇲🇴 Macao Special Administrative Region of China" icon="message" />
-          <Card title="🇹🇼 Taiwan region of China" icon="message" />
+          <Card title="Taiwan region of China" icon="message" />
           <Card title="🇭🇰 Hong Kong Special Administrative Region of China" icon="message" />
         </CardGroup>
       </Tab>
diff --git a/en/on-call/quickstart/mobile-app.mdx b/en/on-call/quickstart/mobile-app.mdx
index 0936cffa..6597449e 100644
--- a/en/on-call/quickstart/mobile-app.mdx
+++ b/en/on-call/quickstart/mobile-app.mdx
@@ -83,6 +83,8 @@ Available items under **More actions** adapt to the incident's state:
 | **War room** | Create war room, add stakeholders to war room, dissolve war room (Pro plan; requires an IM integration that supports war rooms) |
 | **Jira and custom actions** | Custom actions such as Jira and ServiceNow configured by admins in integrations |
 
+The **Responders** area on the incident detail page opens a responder-list panel, whose bottom button **Add responders** appends responders (newly added people are pulled into the war room automatically). When the incident is **closed**, **Add responders** is hidden along with the panel's **Reassign** action, leaving a read-only list.
+
 <Note>
 Consistent with the console: if an admin has configured a custom form for actions such as acknowledge or close, performing these actions in the App requires filling out the form first.
 </Note>
diff --git a/en/rum/performance/diagnosis-optimization.mdx b/en/rum/performance/diagnosis-optimization.mdx
index 2b3b6447..78c89981 100644
--- a/en/rum/performance/diagnosis-optimization.mdx
+++ b/en/rum/performance/diagnosis-optimization.mdx
@@ -15,9 +15,20 @@ You can navigate to the optimization page, located under the Performance Monitor
   <Step title="Metric Selection">
     After selecting a page and metric, you can start performance data analysis:
 
-    1. Click on a metric card to select the metric to analyze (currently supports LCP, FCP, INP, CLS)
+    1. Click on a metric card to select the metric to analyze
     2. Select a group in "Show Filter Breakdown"
     3. Evaluate metrics at different percentiles (e.g., p75 represents the 75th percentile value)
+
+    The metric cards adapt to the application's platform, so they always show the metrics that platform actually reports:
+
+    | Platform | Metric cards |
+    |----------|--------------|
+    | **Browser (Web) / Electron (renderer)** | `LCP`, `FCP`, `INP`, `CLS` |
+    | **WeChat Mini Program** | `first_render` (First Render), `lcp`, `fcp`, `onload_to_onshow`, `onshow_to_onready` |
+
+    <Note>
+    The platform is determined by the application's own type, so no manual switching is required. `first_render`, `onload_to_onshow`, and `onshow_to_onready` come from the WeChat Mini Program SDK: `first_render` is the time to first render, while `onload_to_onshow` and `onshow_to_onready` correspond to the two segments of the mini program page lifecycle and help you troubleshoot slow cold starts. After you switch applications, the metric cards refresh to the new platform's metric set, and the tree map (metric view) metric dropdown likewise lists only the metrics available for the current application platform.
+    </Note>
   </Step>
   <Step title="Data Viewing">
     You can view the data performance of the metric under different conditions by adjusting the data aggregation method or modifying filter conditions, thereby advancing diagnosis and optimization work.
diff --git a/en/rum/performance/performance-analysis.mdx b/en/rum/performance/performance-analysis.mdx
index 4d6dcb37..2f8307f3 100644
--- a/en/rum/performance/performance-analysis.mdx
+++ b/en/rum/performance/performance-analysis.mdx
@@ -24,7 +24,7 @@ Navigate to the Performance Monitoring menu, where you can analyze performance e
   <Tab title="Metric Perspective">
     Switch to tree view to see the list of resources to optimize from a specific metric perspective:
 
-    - Switch between different metrics to view their distribution
+    - Switch between different metrics to view their distribution. The dropdown lists only the metrics available for the current app's platform (WeChat Mini Program and browser / Electron have different metric sets); the options change with the app
     - View resource distribution and proportion under "Good", "Poor", and "Average" categories to quickly locate problem resources
     - Click on the block representing a page to view metric details for that page, facilitating further problem diagnosis
 
diff --git a/integration-docs/src/doc-map.mjs b/integration-docs/src/doc-map.mjs
index 7893bbba..362e04db 100644
--- a/integration-docs/src/doc-map.mjs
+++ b/integration-docs/src/doc-map.mjs
@@ -64,7 +64,9 @@ export const docMap = {
   JDCloudMonitor: `${alertBase}/jdcloud.mdx`,
   KSCloudMonitor: `${alertBase}/kscloud-monitor.mdx`,
   Datadog: `${alertBase}/datadog.mdx`,
+  NewRelic: `${alertBase}/new-relic.mdx`,
   AliyunPrometheus: `${alertBase}/aliyun-prometheus.mdx`,
+  AliyunDataWorksOp: `${alertBase}/aliyun-dataworks-op.mdx`,
   HttpPull: `${alertBase}/http-pull.mdx`,
   DbPull: `${alertBase}/db-pull.mdx`,
   Emqx: `${alertBase}/emqx.mdx`,
diff --git a/scripts/upload.sh b/scripts/upload.sh
index f9ad7d2e..91dffae0 100644
--- a/scripts/upload.sh
+++ b/scripts/upload.sh
@@ -1,19 +1,17 @@
 #!/usr/bin/env bash
 #
-# Upload documentation to Meilisearch for AI Q&A bot indexing.
+# Sync documentation to Meilisearch for AI Q&A bot indexing.
 #
-# Supports two modes:
-#   - Incremental (default): uses git diff to upload only changed docs and
-#     delete removed ones from the index.
-#   - Full: scans all docs in zh/ and en/ and uploads everything.
+# Every run makes the index match the docs in zh/ and en/: all docs are
+# upserted (Meilisearch only re-embeds documents whose content changed) and
+# index documents whose source file no longer exists are deleted.
 #
 # Required env vars: MEILI_ENDPOINT, MEILI_API_KEY, MEILI_INDEX
 # Optional:
-#   FULL_UPLOAD  - set to "true" for full re-upload (default: false)
-#   BASE_URL     - docs base URL (default: https://docs.flashduty.com)
+#   BASE_URL  - docs base URL (default: https://docs.flashduty.com)
 #
 # Usage:
-#   sh scripts/upload.sh [--full] [--dry-run] [--help]
+#   bash scripts/upload.sh [--dry-run] [--help]
 #
 # License: Same as the repository
 
@@ -25,29 +23,28 @@ cd "$REPO_ROOT"
 
 SCRIPT_NAME=$(basename "$0")
 BASE_URL="${BASE_URL:-https://docs.flashduty.com}"
-FULL_UPLOAD="${FULL_UPLOAD:-false}"
 DRY_RUN=false
 BATCH_SIZE=5
 # DashScope text-embedding-v4 accepts up to 8192 tokens per input.
 # Truncate content to stay safely within this limit after cleanup.
 MAX_CONTENT_CHARS=6000
+LIST_PAGE_SIZE=1000
 
 usage() {
   cat <<EOF
 Usage: $SCRIPT_NAME [OPTIONS]
 
-Upload documentation (zh/, en/) to Meilisearch for AI Q&A bot indexing.
+Sync documentation (zh/, en/) to Meilisearch for AI Q&A bot indexing:
+upload every doc and delete index documents whose source file is gone.
 
 Options:
-  --full       Re-upload all docs (overrides FULL_UPLOAD env var)
-  --dry-run    Validate and list files without uploading
+  --dry-run    List what would be uploaded and deleted without writing
   -h, --help   Show this help
 
 Environment variables:
   MEILI_ENDPOINT   Meilisearch instance URL (required)
-  MEILI_API_KEY    API key with documents write permission (required)
+  MEILI_API_KEY    API key with documents read/write permission (required)
   MEILI_INDEX      Target index name (required)
-  FULL_UPLOAD      Set to "true" for full re-upload (default: false)
   BASE_URL         Docs base URL (default: $BASE_URL)
 EOF
 }
@@ -55,17 +52,14 @@ EOF
 for arg in "$@"; do
   case "$arg" in
     -h|--help) usage; exit 0 ;;
-    --full) FULL_UPLOAD=true ;;
     --dry-run) DRY_RUN=true ;;
     *) echo "Unknown option: $arg" >&2; usage >&2; exit 1 ;;
   esac
 done
 
-if [[ "$DRY_RUN" != true ]]; then
-  if [[ -z "${MEILI_ENDPOINT:-}" || -z "${MEILI_API_KEY:-}" || -z "${MEILI_INDEX:-}" ]]; then
-    echo "Error: MEILI_ENDPOINT, MEILI_API_KEY, and MEILI_INDEX must be set." >&2
-    exit 1
-  fi
+if [[ -z "${MEILI_ENDPOINT:-}" || -z "${MEILI_API_KEY:-}" || -z "${MEILI_INDEX:-}" ]]; then
+  echo "Error: MEILI_ENDPOINT, MEILI_API_KEY, and MEILI_INDEX must be set." >&2
+  exit 1
 fi
 
 if ! command -v jq &> /dev/null; then
@@ -139,27 +133,16 @@ dir_for_file() {
   fi
 }
 
-is_doc_file() {
-  local file=$1
-  [[ "$file" == zh/*.md || "$file" == zh/*.mdx || "$file" == en/*.md || "$file" == en/*.mdx ]] || return 1
-  local base
-  base=$(basename "$file")
-  [[ "$base" != "index.md" && "$base" != "index.mdx" ]] || return 1
-  # Exclude api-reference/: auto-generated OpenAPI JSON served via Mintlify's
-  # native OpenAPI integration; it should not be indexed for the AI Q&A bot.
-  [[ "$file" != api-reference/* ]] || return 1
-  return 0
-}
-
-# Clean raw MDX content for embedding: strip frontmatter, HTML/MDX tags,
-# import statements, and collapse whitespace, then truncate.
+# Clean raw MDX content for embedding: strip frontmatter, import statements and
+# HTML/MDX tags, collapse whitespace, then truncate. Tags are stripped after
+# lines are joined so a tag whose attributes span several lines goes too; a tag
+# must start with a letter or '/', which keeps comparisons like "a < b" intact.
 clean_content() {
   local file=$1
   awk 'BEGIN{skip=0} NR==1 && /^---$/{skip=1;next} skip && /^---$/{skip=0;next} !skip' "$file" \
     | grep -v '^import ' \
-    | sed 's/<[^>]*>//g' \
     | tr '\n' ' ' \
-    | sed 's/  */ /g' \
+    | sed -E 's/<[A-Za-z/][^<>]*>//g; s/ +/ /g' \
     | cut -c1-"$MAX_CONTENT_CHARS"
 }
 
@@ -183,6 +166,45 @@ build_doc_json() {
     '{id: $id, title: $title, content: $content, locale: $locale, url: $url}' 2>/dev/null
 }
 
+# Write "id<TAB>url" for every document in the index to $1. Fails unless the
+# pages add up to exactly the total the index reports, so an incomplete
+# listing can never drive deletions.
+list_index_docs() {
+  local out=$1
+  local offset=0
+  local total=""
+  local page page_total listed
+
+  while :; do
+    if ! page=$(curl -sS --fail-with-body --connect-timeout 30 --max-time 60 \
+      -H "Authorization: Bearer $MEILI_API_KEY" \
+      "$MEILI_ENDPOINT/indexes/$MEILI_INDEX/documents?fields=id,url&limit=$LIST_PAGE_SIZE&offset=$offset"); then
+      echo "Listing index documents failed: $page" >&2
+      return 1
+    fi
+    if ! page_total=$(jq -er '.total' <<<"$page"); then
+      echo "Unexpected listing response: $page" >&2
+      return 1
+    fi
+    if [[ -z "$total" ]]; then
+      total=$page_total
+    elif [[ "$page_total" != "$total" ]]; then
+      echo "Index changed while listing (total $total -> $page_total)" >&2
+      return 1
+    fi
+    jq -r '.results[] | [.id, (.url // "")] | @tsv' <<<"$page" >> "$out" || return 1
+
+    offset=$((offset + LIST_PAGE_SIZE))
+    [[ $offset -lt $total ]] || break
+  done
+
+  listed=$(cut -f1 "$out" | sort -u | wc -l | xargs)
+  if [[ "$listed" -ne "$total" ]]; then
+    echo "Listed $listed unique documents but the index reports $total" >&2
+    return 1
+  fi
+}
+
 # Upload a batch of documents (JSON array) to Meilisearch
 upload_batch() {
   local payload=$1
@@ -300,99 +322,59 @@ upload_files() {
 
 # --- Main ---
 
-echo "=== Meilisearch Doc Upload ==="
-echo "Index: ${MEILI_INDEX:-<not set>}"
+echo "=== Meilisearch Doc Sync ==="
+echo "Index: $MEILI_INDEX"
 echo "Base URL: $BASE_URL"
-echo "Mode: $([ "$FULL_UPLOAD" = "true" ] && echo "full" || echo "incremental")"
-[[ "$DRY_RUN" == true ]] && echo "(dry-run mode — no uploads)"
+[[ "$DRY_RUN" == true ]] && echo "(dry-run mode — no writes)"
 echo ""
 
-if [[ "$FULL_UPLOAD" == "true" ]]; then
-  # Full mode: scan all docs
-  echo "Scanning all documentation files..."
-  temp_files=$(mktemp)
-  {
-    [[ -d "zh" ]] && find zh -type f \( -name "*.md" -o -name "*.mdx" \) ! -name "index.md" ! -name "index.mdx"
-    [[ -d "en" ]] && find en -type f \( -name "*.md" -o -name "*.mdx" \) ! -name "index.md" ! -name "index.mdx"
-  } | sort > "$temp_files"
-
-  file_count=$(wc -l < "$temp_files" | xargs)
-  echo "Found $file_count documentation files"
-  echo ""
-
-  upload_files "$temp_files"
-  result=$?
-  rm -f "$temp_files"
-  exit $result
-fi
+work_dir=$(mktemp -d)
+trap 'rm -rf "$work_dir"' EXIT
 
-# Incremental mode: use git diff to find changed files
-if ! git rev-parse HEAD~1 > /dev/null 2>&1; then
-  echo "No previous commit found — falling back to full upload"
-  FULL_UPLOAD=true
-  exec bash "$0" --full $([ "$DRY_RUN" = true ] && echo "--dry-run")
+echo "Scanning all documentation files..."
+find zh en -type f \( -name "*.md" -o -name "*.mdx" \) ! -name "index.md" ! -name "index.mdx" \
+  | sort > "$work_dir/files"
+file_count=$(wc -l < "$work_dir/files" | xargs)
+echo "Found $file_count documentation files"
+if [[ $file_count -eq 0 ]]; then
+  echo "Error: no documentation files found; refusing to sync an empty doc set." >&2
+  exit 1
 fi
 
-echo "Detecting changed files since last commit..."
-
-# Files added or modified
-changed_files=$(mktemp)
-git diff --name-only --diff-filter=ACMR HEAD~1 -- zh/ en/ | while IFS= read -r file; do
-  is_doc_file "$file" && echo "$file"
-done > "$changed_files" || true
-
-# Files deleted
-deleted_files=$(mktemp)
-git diff --name-only --diff-filter=D HEAD~1 -- zh/ en/ | while IFS= read -r file; do
-  is_doc_file "$file" && echo "$file"
-done > "$deleted_files" || true
-
-changed_count=$(wc -l < "$changed_files" | xargs)
-deleted_count=$(wc -l < "$deleted_files" | xargs)
+while IFS= read -r file; do
+  file_to_id "$file"
+done < "$work_dir/files" | LC_ALL=C sort -u > "$work_dir/current_ids"
 
-echo "Changed/added: $changed_count files"
-echo "Deleted: $deleted_count files"
+echo "Listing documents in index..."
+if ! list_index_docs "$work_dir/index_docs"; then
+  echo "Error: could not list the whole index; nothing was written." >&2
+  exit 1
+fi
+echo "Index has $(wc -l < "$work_dir/index_docs" | xargs) documents"
 echo ""
 
-if [[ $changed_count -eq 0 && $deleted_count -eq 0 ]]; then
-  echo "No documentation changes detected. Nothing to do."
-  rm -f "$changed_files" "$deleted_files"
-  exit 0
-fi
+# Index documents with no source file in the current doc set
+LC_ALL=C sort "$work_dir/index_docs" \
+  | LC_ALL=C join -t $'\t' -v 1 - "$work_dir/current_ids" > "$work_dir/stale_docs"
+stale_count=$(wc -l < "$work_dir/stale_docs" | xargs)
 
 result=0
 
-# Upload changed files
-if [[ $changed_count -gt 0 ]]; then
-  echo "--- Uploading changed documents ---"
-  upload_files "$changed_files" || result=1
-fi
-
-# Delete removed files from index
-if [[ $deleted_count -gt 0 ]]; then
-  echo ""
-  echo "--- Removing deleted documents ---"
-
-  ids_json="["
-  first=true
-  while IFS= read -r file; do
-    [[ -z "$file" ]] && continue
-    id=$(file_to_id "$file")
-    if [[ "$first" == true ]]; then
-      first=false
-    else
-      ids_json="${ids_json},"
-    fi
-    ids_json="${ids_json}\"${id}\""
-    echo "Will delete: $file (id: $id)"
-  done < "$deleted_files"
-  ids_json="${ids_json}]"
+echo "--- Uploading documents ---"
+upload_files "$work_dir/files" || result=1
 
-  delete_documents "$ids_json" "$deleted_count" || result=1
+echo ""
+echo "--- Removing documents with no source file ---"
+if [[ $stale_count -eq 0 ]]; then
+  echo "None."
+else
+  while IFS=$'\t' read -r id url; do
+    echo "Will delete: $url (id: $id)"
+  done < "$work_dir/stale_docs"
+  ids_json=$(cut -f1 "$work_dir/stale_docs" | jq -Rn '[inputs]')
+  delete_documents "$ids_json" "$stale_count" || result=1
 fi
 
-rm -f "$changed_files" "$deleted_files"
-
 echo ""
 echo "All done."
 exit $result
diff --git a/zh/ai-sre/apps.mdx b/zh/ai-sre/apps.mdx
index a1dd9ec9..50151ecd 100644
--- a/zh/ai-sre/apps.mdx
+++ b/zh/ai-sre/apps.mdx
@@ -31,7 +31,7 @@ AI SRE 的会话默认运行在 **Flashduty 云端沙箱**里。沙箱是干净
 
 ---
 
-进入 **插件 → Apps**。Apps 是插件区的**第一个、也是默认**标签页——打开插件区即落在这里。
+进入 **插件 → Apps**。插件区打开时默认落在 **概览** 标签页，Apps 是其中一个标签页（页签顺序为 概览 / Apps / Skill / MCP / Agents）。
 
 <Note>
 查看 Apps 标签页需要相应权限；没有权限时该标签页不可见。授权、断开 / 撤销、启用 / 禁用各自还需对应的操作权限——无权限时对应按钮以禁用态显示。
diff --git a/zh/ai-sre/artifacts.mdx b/zh/ai-sre/artifacts.mdx
index 4f248d0a..8889c665 100644
--- a/zh/ai-sre/artifacts.mdx
+++ b/zh/ai-sre/artifacts.mdx
@@ -60,6 +60,8 @@ sidebarTitle: 产物
 
 **生成时间** 与 **修改时间** 列支持点击列头排序（升序 / 降序切换），排序在服务端执行；默认按 **修改时间降序**。
 
+范围、搜索词、排序与页码都会反映在页面地址上（形如 `?scope=team&teams=1,2&q=重建&page=2`），因此直接复制地址就能分享或收藏一份**已筛选**的列表；从产物详情页返回时也会回到原来的筛选与位置，而不是被重置成默认视图。
+
 ### 产物卡片
 
 每张卡片展示：
diff --git a/zh/ai-sre/automations.mdx b/zh/ai-sre/automations.mdx
index f530787b..dc5fa288 100644
--- a/zh/ai-sre/automations.mdx
+++ b/zh/ai-sre/automations.mdx
@@ -170,7 +170,7 @@ curl -X POST 'https://<触发地址>' \
 
 匹配事件到达后，系统会以 `oncall_incident` 作为 `trigger_kind` 创建运行，并把 `incident_id`、`channel_id`、`severity` 等事件上下文传给会话。相同触发器与相同 `incident_id` 会复用同一次运行，避免同一故障重复拉起多个隐藏会话。
 
-运行结束时，AI SRE 会把一条总结评论写回触发它的故障：结论写在最前面、正文简明，末尾附本次运行的完整会话链接。评论沿故障现有的通知链路送达（例如 IM 里故障卡片的刷新与回帖），关注这条故障的人不用打开控制台就能看到分析结果。该行为对所有启用 On-call 故障触发的规则自动生效——包括自定义提示词的规则，无需额外配置。
+运行结束时，AI SRE 会把一条总结评论写回触发它的故障：结论写在最前面、正文简明，末尾附本次运行的完整会话链接。这条写回记录本身也带有一个常显的 **接续对话** 入口，在故障时间线上读结论时就能直接进入当次会话，见[故障时间线 · AI SRE 代操作记录](/zh/on-call/incident/search-view-incident#ai-sre-代操作记录)。评论沿故障现有的通知链路送达（例如 IM 里故障卡片的刷新与回帖），关注这条故障的人不用打开控制台就能看到分析结果。该行为对所有启用 On-call 故障触发的规则自动生效——包括自定义提示词的规则，无需额外配置。
 
 ## 运行历史
 
diff --git a/zh/ai-sre/im.mdx b/zh/ai-sre/im.mdx
index a9072e07..f7e54c6a 100644
--- a/zh/ai-sre/im.mdx
+++ b/zh/ai-sre/im.mdx
@@ -50,7 +50,7 @@ IM 交互依赖你已在 Flashduty 中接入对应平台的机器人（用于告
 在 **On-call → 集成中心 → 集成列表 → 即时消息** 打开对应 IM 集成详情，在 **增强功能** 中分别配置该集成的 AI SRE 行为。以下开关默认均为开启：
 
 - **自动发起 AI 故障分析**：开启作战室后可配置；集成成功创建作战室时，自动发起一次 AI SRE 初步诊断并把结果回贴到作战室。
-- **允许群聊 @ AI SRE**：无需开启作战室即可配置，允许群聊中的 @ 提及进入 AI SRE。Slack 中该开关显示为 **允许群聊 @ AI SRE 和 /fd 命令**；关闭后，群聊 @ 提及和 `/fd` 命令都不会触发 AI SRE。
+- **允许在 IM 中使用 AI SRE**：无需开启作战室即可配置，同时控制 **群聊 @ 提及** 与 **机器人私聊** 两个入口；Slack 在此之外还控制 `/fd` 命令。关闭后，群聊 @ 提及、机器人私聊（Slack 另含 `/fd` 命令）都不会触发 AI SRE 回复。企业微信的第三方应用模式只支持机器人私聊，群聊 @ 提及需使用企业自建应用模式。
 - **普通群聊中 AI SRE 使用话题回复**：仅飞书/Lark 与 Slack 提供。开启后，普通群聊中的每个话题对应一个独立 Session；作战室仍直接在群内回复。
 
 <Note>
@@ -61,7 +61,7 @@ IM 交互依赖你已在 Flashduty 中接入对应平台的机器人（用于告
 
 ---
 
-在已接入且允许群聊 @ AI SRE 的 IM 群里 **@ 机器人** 并写下你的问题（例如「@AI SRE 看下 payment 服务为什么 5xx 飙升」），消息会通过平台 webhook 转给 AI SRE 处理：
+在已接入并开启了 **允许在 IM 中使用 AI SRE** 的 IM 群里 **@ 机器人** 并写下你的问题（例如「@AI SRE 看下 payment 服务为什么 5xx 飙升」），消息会通过平台 webhook 转给 AI SRE 处理：
 
 <Steps>
   <Step title="识别提及">
@@ -120,6 +120,21 @@ Agent 的当前回合结束时，如果它留下的**常驻进程类任务**还
 
 通知回合遵循「无消息 = 没有新进展」的静默语义：如果某个通知回合没有新内容要投递，AI SRE 会静默关闭该回合，**不向聊天发送任何占位回执**，也不会重复投递监控中卡片；只有真正有新结论时才会在聊天里出现新消息。
 
+## 连接与授权
+
+---
+
+控制台在凭证缺失时会渲染内联卡片（**授权〈资源名〉以继续**、**连接〈厂商名〉以继续**，见 [控制台](/zh/ai-sre/sessions#需要授权时)）。**IM 与 API 渠道不出卡**——Agent 会根据本次会话的渠道改用下面这套办法把这件事交给你：
+
+| 情况 | IM / API 渠道的行为 |
+| --- | --- |
+| 缺少你的 OAuth 授权（`per_user_oauth`） | Agent 把授权链接原样贴成一条普通消息（不是卡片），请你在**桌面 / PC 浏览器**打开完成授权，然后回到会话回复 **「已授权」**（英文会话回复 `authorized`）继续。继续是你的一次显式动作，OAuth 成功回调本身不会自动接着跑 |
+| 缺少你的密钥类凭证（`per_user_secret`） | IM 里没有安全的收取渠道：Agent 只会请你在**网页控制台打开同一个会话**完成填写，不会让你在聊天里粘贴密钥，也不会把你指到某个设置页 |
+| 缺少整个连接（市场目录里有、账户未连接） | Agent 把连接地址（控制台插件页的深链）作为一条普通链接给出，请你连接后回复 **「继续」**（英文会话回复 `continue`）再接着做 |
+| 共享服务器自身的凭证（环境变量 / Header） | 不走上面任何流程：在 **插件 → MCP**（该服务器）里填写，填完让 Agent 重试 |
+
+自动化（`automation`）渠道没有人值守、也不会有回复：Agent 不会等待、不会把话写成问句，而是把缺失的连接或授权**记为阻塞项**写进最终报告，并交付已有证据能支持的部分。
+
 ## IM 会话内切换命令
 
 ---
diff --git a/zh/ai-sre/knowledge.mdx b/zh/ai-sre/knowledge.mdx
index c6c692d2..ecf254b2 100644
--- a/zh/ai-sre/knowledge.mdx
+++ b/zh/ai-sre/knowledge.mdx
@@ -71,11 +71,24 @@ Agent 读取 `DUTY.md` 后，会根据当前故障判断需要展开哪些 `@引
 
 ---
 
-进入 **知识库**（Knowledges）管理页，您可以为账户或团队创建、编辑、启用/禁用、删除 Knowledge Pack。列表按 **名称 / 范围 / 文件 / 状态 / 操作** 展示每个 Pack，并通过顶部的范围筛选器在共享、团队之间切换。
+进入 **知识库**（Knowledges）管理页，您可以为账户或团队创建、编辑、启用/禁用、删除 Knowledge Pack。已有知识库时，列表按 **名称 / 范围 / 文件 / 状态 / 操作** 展示每个 Pack，并通过顶部的范围筛选器在共享、团队之间切换。
+
+**首次进入（空状态）**：当前范围下还没有任何知识库、账户里也一个都没有时，页面由空状态接管。它列出五个可以自动起草的来源——**代码仓库**（服务、依赖和技术栈）、**部署拓扑**（环境、集群和工作负载）、**基础设施**（云账号、数据库、中间件）、**变更**（发布和配置变更）、**监控**（指标、日志和告警规则），并显示已从您已连接的工具与 Flashduty 里各读到多少内容（文案形如「N 个仓库」「N 个集群」「N 个连接」「近 30 天 N 次」）；尚无数据的来源显示 **连接 →**，点击跳到插件页去连接。卡片下方同时说明「没连接的部分先留空，连上后再补」，值班、升级规则与处置记录直接从 Flashduty 读取、无需连接。
+
+此时页面上唯一的两个建库入口就来自空状态本身：
+
+| 入口 | 行为 |
+| --- | --- |
+| **初始化 AI-SRE** | 新开一个 AI SRE 对话，并**直接发送** `/init`：由 Agent 从上述五个来源起草内容，逐项与您确认后保存 |
+| **上传已有文档** | 新开一个 AI SRE 对话，把 `/init` **预填**进输入框（不自动发送）并打开附件选择器，由您把现有文档交给 Agent 提炼入库 |
+
+**空状态接管页面时，页头右上角的 创建 按钮、范围切换与搜索框都不出现**：此时没有任何可筛选的内容，再摆一个入口只会和空状态里的两个按钮竞争。已有 Pack 之后页面恢复常规版面——右上角 **创建** + 顶部范围筛选 + 搜索。在团队范围内进入时，空状态的两个入口会把新开的对话绑定到当前所选的团队。
+
+若您没有账号级知识库的编辑权限，账号范围下看到的不是上面这套空状态，而是一句「还没有账号知识库」；工具栏仍在，可切到团队范围查看团队知识库。
 
 <Steps>
   <Step title="创建知识库">
-    点击页面右上角的 **创建**，弹出「创建知识库」对话框。Knowledge Pack 本身没有可编辑的名称——它是按目标（账户或团队）的单例资源，弹窗里只需选择 **范围**：共享或某个团队。创建团队级 Pack 时，您必须是目标团队成员；共享范围创建仅限账户 Owner 或管理员。每个目标只能拥有一个 Pack。已有 Pack 的账户或团队仍会出现在下拉列表中，并标记为「已有知识库」；选择后主按钮变为 **打开知识库**，点击即可直接进入该 Pack，不会重复创建。选择没有 Pack 的范围后，点击 **新建** 完成创建；提交前控制台会再次检查，若该范围刚被其他人创建为 Pack，则改为打开已有 Pack。控制台用范围（共享 / 团队名）作为该 Pack 的显示标识。
+    点击页面右上角的 **创建**（该按钮只在已有知识库时出现，见上文空状态说明），弹出「创建知识库」对话框。Knowledge Pack 本身没有可编辑的名称——它是按目标（账户或团队）的单例资源，弹窗里只需选择 **范围**：共享或某个团队。创建团队级 Pack 时，您必须是目标团队成员；共享范围创建仅限账户 Owner 或管理员。每个目标只能拥有一个 Pack。已有 Pack 的账户或团队仍会出现在下拉列表中，并标记为「已有知识库」；选择后主按钮变为 **打开知识库**，点击即可直接进入该 Pack，不会重复创建。选择没有 Pack 的范围后，点击 **新建** 完成创建；提交前控制台会再次检查，若该范围刚被其他人创建为 Pack，则改为打开已有 Pack。控制台用范围（共享 / 团队名）作为该 Pack 的显示标识。
   </Step>
   <Step title="编辑文件">
     点击列表中的某一行打开检视器。左侧是文件树，右侧是行内编辑器。点击 **新建文件** 输入文件名（如 `runbook.md`），或用 **上传** 导入本地文件；Markdown 文件支持 **预览** 与 **源码** 两种视图。编辑后点击 **保存**。
diff --git a/zh/ai-sre/mcp.mdx b/zh/ai-sre/mcp.mdx
index 71e5efd8..ac2c1584 100644
--- a/zh/ai-sre/mcp.mdx
+++ b/zh/ai-sre/mcp.mdx
@@ -43,38 +43,43 @@ sidebarTitle: MCP
 
 ---
 
-进入 **插件 → MCP** 页面，点击 **浏览 Marketplace** 打开 **MCP 市场**，可以浏览 Flashduty 精选的第三方 MCP 服务器模板。
+进入 **插件 → 概览** 页面，即可看到 Flashduty 精选的第三方 MCP 模板目录。目录按类别分页签展示（全部 / 可观测 / 云与基础设施 / 数据库与中间件 / 代码与协作 / Skill），右上角的搜索框按名称或描述过滤。
+
+目录上方的 **推荐** 区（说明文字：「按告警来源和常用程度推荐。连接后，AI SRE 排查时能直接用。」）按您账户**已配置的告警集成**挑出匹配的模板（按近 30 天告警量排序），再补上当前语言的精选项，最多展示 3 个；已安装、需要 Runner、或您无权安装的模板不会出现在推荐里。
 
 <Steps>
-  <Step title="打开市场">
-    在 MCP 列表页点击 **浏览 Marketplace**，弹出市场对话框，以卡片网格展示所有可用的 MCP 服务器模板。每张卡片展示 MCP 服务器名称、作者、简介与标签。
+  <Step title="找到要连接的模板">
+    目录每一行展示模板名称与简介；同一屏里混有 MCP / App / Skill 多种类型时，还会带一个类型标签。未安装的行右侧有一个圆形 **+** 按钮：点击 **+** 或点击整行，都会打开「**连接**」对话框。模板需要自托管 Runner、而当前账户又没有可用 Runner 时，行的标签会显示 **需要自托管 Runner**；您无权安装的模板，行上不显示 **+**、整行也不可点击。
   </Step>
-  <Step title="查看详情">
-    点击任意 MCP 服务器卡片打开详情页，可查看完整描述、传输方式、授权模式、是否需要 BYOC Runner、供应商、连接参数说明与官方文档链接。已安装的 MCP 服务器卡片以齿轮图标标识，点击可直接跳转到该 MCP 服务器的编辑表单。
+  <Step title="核对模板信息并填写连接参数">
+    对话框先展示模板信息：供应商（如「Datadog 官方 · MCP」或「社区版 · MCP」）、官方文档链接、简介，以及一组「**连接后可以这样问**」示例问题。随后是模板声明的连接参数字段——URL / 端点占位符与环境变量等；**共享**字段（服务授权模式下全账号共用）下方标注「全账号共用。」。若模板是「成员授权（密钥）」模式，另有「**你的 API Token**」字段（密码输入框），下方标注「只给你自己用，其他成员第一次使用时各自填写。」，并在字段旁给出「如何获取」文档链接。
   </Step>
-  <Step title="发起安装对话">
-    对尚未安装的 MCP 服务器，点击卡片上的 **安装** 按钮，系统会打开一个新的 AI SRE 会话并注入该 MCP 服务器的模板信息。Agent 随即引导您填写端点地址、完成凭证授权，并调用 `tool_search`（按服务器名探测其工具）验证连通性——整个安装流程**在对话中完成**，而不是一键写库。
+  <Step title="选择运行环境并提交">
+    在「**运行环境**」里选择这次连接从哪个环境发起——默认在会话所在的环境里连接；模板需要自托管 Runner 时，提示「〈名称〉只在内网能访问时，选内网里的自托管 Runner。」。主按钮是 **连接**；若模板是「成员授权（OAuth）」模式，主按钮为「**去〈名称〉授权**」，点击后先创建连接器、再打开浏览器授权窗口（OAuth 的发现、动态客户端注册与令牌交换都从所选环境发起）。
   </Step>
-  <Step title="确认安装完成">
-    Agent 验证连通性通过后，会通过 `/safari/mcp/server/create` 端点将 MCP 服务器写入账户。此后它会出现在 MCP 列表中，并在卡片上以「已安装」状态标识。
+  <Step title="确认连接结果">
+    提交后系统创建连接器并对它执行一次连接测试。通过则显示「**〈名称〉已连接**」与示例问题，点 **完成** 关闭对话框，或直接点某个示例问题新建一条**已预填**该问题的对话（不会自动发送）。不通过则显示「**连接测试没通过**」与原始错误：可点 **重试** 重跑测试；需要 Runner 的模板在非云端环境下还会给出「让 AI SRE 在 Runner 上装好」入口，新建一条不含任何令牌的对话，让 Agent 到自托管 Runner 上安装缺失的命令行工具（如 `npx` 对应的 Node.js、`uvx` 对应的 uv）。
   </Step>
 </Steps>
 
 <Note>
-市场是**只读浏览**——没有一键安装端点。这是有意为之：MCP 服务器的安装必须经过凭证录入与连通性验证，跳过这两步会在账户里留下永远无法连接的死配置。对话式安装确保每台 MCP 服务器在正式可用前都已通过 Agent 的实际调用验证。
+对话框只在**首次提交**时创建连接器。提交后其中的连接参数即被锁定，并提示「连接器已创建，参数以首次提交为准；如需修改，请到「插件 → MCP」编辑。」。名称与账户内已有连接器冲突时，不再回显后端错误，而是提示「这个账号里已经有名为「〈名称〉」的连接器。要用的就是它，请到「插件 → MCP」完成授权；否则需要账户所有者或管理员先在那里改名或删除，再回来连接。」。
 </Note>
 
 安装完成的 MCP 服务器会在其配置中记录 `source_template_name`，指向来源模板名称，便于日后追溯其原始出处。**市场安装的 MCP 服务器固定为共享范围**（即账户级，`team_id` 为 0），账户内所有成员可用，安装时不提供团队归属选择；同一模板在同一账户内只能安装出一个实例。
 
 <Warning>
-需要 **BYOC Runner** 的 MCP 服务器（详情页有 `requires_runner` 标识；`requires_runner` 与传输方式相互独立，当前精选市场均为 HTTP 流式且不需要 Runner）只能在您自己部署了 Runner 的运行环境中使用，云 Sandbox 不支持。安装前请确认您的账户已配置可用的 BYOC Runner，详见 [运行环境（BYOC）](/zh/ai-sre/environments)。
+需要 **BYOC Runner** 的模板（详情中的 `requires_runner` 标识）只能在您自己部署了 Runner 的运行环境中使用，云 Sandbox 不支持。`requires_runner` 与传输方式相互独立，当前市场的 55 个模板里两种都有：27 个是 **HTTP 流式**、不需要 Runner，另外 28 个是 **stdio**、需要 Runner——包括阿里云 OpenAPI、阿里云可观测、夜莺 Nightingale、Gitee、GreptimeDB、Prometheus、Grafana (Self-Hosted)、Kafka (Confluent)、AWS、ClickHouse、MySQL、PostgreSQL、阿里云 RDS、Redis、MongoDB 等。这些 stdio 模板以 `uvx` / `npx` 命令在各环境上本地启动，云 Sandbox 无法启动本地子进程，因此安装前请确认您的账户已配置可用的 BYOC Runner，详见 [运行环境（BYOC）](/zh/ai-sre/environments)。
 </Warning>
 
 ## 添加 MCP 服务器
 
 ---
 
-进入 **插件 → MCP** 页面，点击右上角的 **添加服务器**，在弹出的表单中定义一台 MCP 服务器。
+进入 **插件 → MCP** 页面，列表页右上角有两个入口：
+
+- **添加 MCP**：点击后弹出表单，手工定义一台 MCP 服务器（字段见下文「基础字段」）。
+- **在对话中添加**：新建一条 AI SRE 会话，并预填提示词「我想添加一个 MCP。先问我是接入自己的服务，还是找现成的来装。找现成的就问我要接什么系统，插件目录里有就直接装，没有再上网搜几个给我挑，我选好再装。」——由 Agent 先问您要接入自己的服务还是装现成的；装现成的先查插件目录，目录里没有再联网搜索候选给您挑，选好后再完成接入（不会自动发送，您可以先修改提示词）。该按钮只在有明确可写入范围时显示：您能授权到账户范围时始终显示，否则需要当前范围筛选恰好只选中一个您所属的团队（或您只属于一个团队）。
 
 ### 基础字段
 
@@ -176,6 +181,8 @@ MCP 列表以表格展示每台服务器的**名称**（含 AI 描述）、**范
 <AccordionGroup>
   <Accordion title="启用 / 禁用" icon="toggle-on">
     用列表里的开关切换。只有**已启用**的服务器才会对 Agent 可见；禁用后 Agent 看不到、也无法调用它。
+
+    已停用（状态不是 `enabled`）的连接器在「连接」入口里**不会被当作已连接**：打开它的「连接」对话框会显示「**连接器已停用**」与「该连接器已停用，AI SRE 暂时无法使用它。需要账户所有者或管理员在「插件 → MCP」里重新启用。」，并给出 **去「插件 → MCP」** 按钮直接跳到该连接器所在行。恢复方式是由账户所有者或管理员在那里用**启用**开关重新启用。已停用的连接器也不再出现在「插件 → 概览」的**已启用**区。
   </Accordion>
   <Accordion title="编辑" icon="pen-to-square">
     点击编辑按钮（或直接点击行）打开表单，可修改名称、传输方式、描述、端点 / 命令、授权模式与作用域。无编辑权限时表单以**只读**模式打开，并提示原因。
@@ -210,7 +217,7 @@ MCP 与其他资源（Skill、知识库、Agent、运行环境）共用同一套
 
 **编辑权限**：团队级 MCP 服务器仅该团队的成员可以操作，组织管理员也需要先加入该团队；共享范围 MCP 服务器仅账户所有者或管理员可以操作；没有「创建者保留权限」这一例外。无编辑权限时，列表对应行的开关与操作显示为**只读**。
 
-**创建与改归属**：创建新的团队级 MCP 服务器时，您必须是目标团队成员；共享范围创建仅限账户所有者或管理员。**从市场安装是例外**：安装固定为共享范围，账户内任何成员都可以安装，不需要所有者或管理员权限。编辑已有 MCP 服务器时，账户所有者或管理员可以把它移动到任意团队，用于恢复空团队或离职成员留下的资源；普通成员只能移动到自己所属的团队。但**市场安装的 MCP 服务器不可改归属到团队**——编辑表单中其作用域固定显示为共享；极少量早期遗留的团队级市场行仍可把作用域改回共享，反向则不允许。**该提升操作与共享范围创建同门槛，仅限账户 Owner 或管理员**：普通成员即使属于该服务器所在团队也不能自助操作，被拒绝时会提示「请管理员把它设为共享」。
+**创建与改归属**：创建新的团队级 MCP 服务器时，您必须是目标团队成员；共享范围创建仅限账户所有者或管理员。**从市场安装是例外**：安装固定为共享范围，由安装者发起，普通模板账户内任何成员都可以安装，不需要所有者或管理员权限。但有一类模板例外：在**成员授权**模式（密钥或 OAuth）下还要求填写自由格式的地址 / 主机参数时，安装者实际上决定了其他成员凭证发往哪个主机，为避免他人凭证流向安装者指定的地址，这类模板的安装与连接**仅限账户 Owner 或管理员**——普通成员在该模板行上看不到 **+**、行不可点击，直接打开「连接」对话框会提示「你没有安装权限，请联系账户所有者或管理员。」。编辑已有 MCP 服务器时，账户所有者或管理员可以把它移动到任意团队，用于恢复空团队或离职成员留下的资源；普通成员只能移动到自己所属的团队。但**市场安装的 MCP 服务器不可改归属到团队**——编辑表单中其作用域固定显示为共享；极少量早期遗留的团队级市场行仍可把作用域改回共享，反向则不允许。**该提升操作与共享范围创建同门槛，仅限账户 Owner 或管理员**：普通成员即使属于该服务器所在团队也不能自助操作，被拒绝时会提示「请管理员把它设为共享」。
 
 **运行时可见性**：会话开始时，只会向 Agent 提供**共享范围** MCP 服务器，以及**当前会话所绑定团队**的服务器。当 Agent 在排障中读取另一个团队的知识后，该团队的 MCP 服务器与 Skill 才会被按需挂载进当前会话。**账户是运行时唯一的安全边界，团队只是归属与编辑的标记。**
 
diff --git a/zh/ai-sre/overview.mdx b/zh/ai-sre/overview.mdx
index e5be0042..aab574c6 100644
--- a/zh/ai-sre/overview.mdx
+++ b/zh/ai-sre/overview.mdx
@@ -53,17 +53,30 @@ AI SRE 不止是控制台里的一个对话框——它围绕「故障从触发
 
 ---
 
-AI SRE 面向 On-call 专业版及以上订阅的账户开放，无需申请。
+AI SRE 面向持有**有效（已启用）**On-call 专业版及以上订阅的账户开放，无需申请。
 
 <AccordionGroup>
 <Accordion title="计费规则" icon="gift">
   AI SRE 自 2026 年 9 月 16 日 8 点（北京时间）起按实际用量计费，以 credits 结算，1 credit = ¥1；此前的用量不收费。计量项为模型用量、沙箱在线时长和联网检索。开通免费，符合条件的账户每个计费周期赠送体验额度，也可以购买资源包（1,000 / 5,000 / 20,000 credits，对应 ¥950 / ¥4,500 / ¥17,000，自支付起 365 天有效）。按量付费默认关闭，由管理员开启，可设置每周期上限。完整规则见[《AI SRE credits 资源包购买协议》](/zh/compliance/ai-sre-credit-package-purchase-agreement)。
+
+  体验额度、资源包与钱包余额都用尽时，AI SRE 会拒绝新的对话请求：输入区被禁用，上方常驻一条**不可关闭**的提示（文案由服务端给出，覆盖「尚未开通」「本周期额度用尽」「钱包余额不足」三种情形），并附带 **前往 AI SRE 计费** 入口，跳转到费用中心（`/wallet/plan?product=ai-sre`）。由管理员在那里开通按量付费、购买资源包或充值，状态恢复后即可继续对话。
 </Accordion>
 <Accordion title="人工授权" icon="user-check">
   生产变更、重启、回滚和外部通知，最终都由您确认后才会执行。
 </Accordion>
 </AccordionGroup>
 
+### 订阅失效与恢复
+
+AI SRE 的准入在每次请求时都会重新校验账户的 On-call 订阅，所以订阅一旦失效，AI SRE 会立即暂停。界面会直接给出服务端生成的提示，并区分两种情形——它们的处理方式不同，别照着错误的那个做：
+
+| 情形 | 提示 | 处理方式 |
+|------|------|----------|
+| 订阅版本高于或等于专业版，但订阅未启用（已过期，或因其它原因被停用） | 「本账户的 On-call 订阅已失效（已过期或已停用），AI SRE 已暂停；续费 On-call 订阅后自动恢复。」 | 续费 On-call 订阅 |
+| 账户没有订阅，或订阅版本低于专业版（无论是否已启用） | 「AI SRE 需要 On-call 专业版订阅，升级订阅后即可使用。」 | 升级到专业版及以上 |
+
+该提示会出现在控制台对话页（输入区上方的常驻横幅，右侧带 **前往 AI SRE 计费** 入口）、IM 会话、自动化运行记录与 A2A 调用错误里；额度总览也会以 `blocked_reason=no_license` 上报同一句提示。恢复不需要重新开通：续费或升级成功后，下一次请求即自动放行。
+
 ## 核心能力
 
 ---
diff --git a/zh/ai-sre/sessions.mdx b/zh/ai-sre/sessions.mdx
index cc840fad..f4d044df 100644
--- a/zh/ai-sre/sessions.mdx
+++ b/zh/ai-sre/sessions.mdx
@@ -137,7 +137,11 @@ Subagent / A2A 子会话本身也不能单独开启分享——分享只能在**
     **大文件的内联截断**：除压缩包以外（压缩包不解析文本，只把沙箱路径交给 Agent），附件以解析出的文本形式内联进 Agent 上下文。解析文本超过 **64KB** 时，只内联开头 **32KB**（在有效的 UTF-8 边界截断），并在附件末尾附上完整文件在沙箱中的路径提示（形如 `~/.flashduty/attachments/...`）——Agent 需要完整内容时，会用沙箱内的 read / bash 等工具按该路径读取原文件，不会丢失内容。此外，超过 **3MB** 的 PDF 不再以原生形式直传模型，而是回退为文本抽取，同样受上述截断规则约束。
   </Accordion>
   <Accordion title="上下文引用" icon="link">
-    从故障、告警、监控规则、监控对象等页面进入 AI SRE 时，相关对象会作为**引用胶囊**自动嵌入输入框——它是一枚内联的小标签，标明所引用对象的类型——故障、告警事件、告警、监控规则、主机、监控对象或告警分析——并随消息一起发送给 Agent，让它直接基于该对象开始分析。点击胶囊可在新标签页打开对应对象；点击胶囊上的关闭按钮即可在发送前移除引用。一条消息可携带多个引用。除了从相关页面自动携带引用外，也可以在任意会话的输入框里直接输入 `@` 触发故障搜索下拉（支持关键词模糊匹配与近期故障列表），选中后插入与自动携带相同的引用胶囊——这是一个随时可用的独立引用入口。输入邮箱地址不会误触发该下拉：当 `@` 紧跟在邮箱地址字符（字母、数字或 `._%+-`）之后时，选择器不会弹出；而空格之后、或与中文相邻的 `@` 仍正常触发。
+    从故障、告警、监控规则、监控对象、数据源等页面进入 AI SRE 时，相关对象会作为**引用胶囊**自动嵌入输入框——它是一枚内联的小标签，标明所引用对象的类型——故障、告警事件、告警、监控规则、主机、监控对象、数据源或告警分析——并随消息一起发送给 Agent，让它直接基于该对象开始分析。点击胶囊可在新标签页打开对应对象；点击胶囊上的关闭按钮即可在发送前移除引用。
+
+    **这类入口还会附带一句默认提问**，胶囊就落在提问句中入口标记的位置。例如从监控对象页进入时，输入框预填的是「请分析这个监控对象 〈引用胶囊〉：基于真实观测数据判断当前是否有问题或隐患，说明依据与影响面，并给出下一步排查或处置建议。请区分已确认事实、合理推断和待确认项；证据不足时明确说明不确定，不要过度归因」；从数据源列表进入时预填「调用 〈引用胶囊〉 的 overview tool，校验 overview tool 是否可用」。预填只是草稿，发送前可以随意修改或删掉，也可以不改直接发送。
+
+    **多对象批量交接不预填提问**：例如在故障列表里对多条故障批量点击 **AI 分析** 时，输入框不会预填任何默认提问（可能保持为空），也没有落在输入框里的引用胶囊——这些引用会随消息一并发送给 Agent。一条消息可携带多个引用。除了从相关页面自动携带引用外，也可以在任意会话的输入框里直接输入 `@` 触发故障搜索下拉（支持关键词模糊匹配与近期故障列表），选中后插入与自动携带相同的引用胶囊——这是一个随时可用的独立引用入口。输入邮箱地址不会误触发该下拉：当 `@` 紧跟在邮箱地址字符（字母、数字或 `._%+-`）之后时，选择器不会弹出；而空格之后、或与中文相邻的 `@` 仍正常触发。
   </Accordion>
   <Accordion title="知识库与 Skill" icon="book">
     会话启动时会按绑定团队自动加载对应的知识库与 Skill；详见下文 <a href="/zh/ai-sre/knowledge">知识库</a> 与 <a href="/zh/ai-sre/skills">Skill</a>。
@@ -221,6 +225,36 @@ Agent 在回合中调用的工具（读写文件、查询监控、执行命令
 OAuth 授权链接有过期时间；过期后卡片会提示「授权链接已过期，请重新触发任务」，需要重新发起一次任务才能拿到新的授权链接。
 </Note>
 
+<Note>
+渠道差异：只有控制台（`web`）渲染这张卡片。IM 与 API 渠道不出卡——OAuth 授权链接由 Agent 直接贴在回复里，请在桌面浏览器打开、完成授权后回复「已授权」继续（继续是你的一次显式动作，不是 OAuth 回调自动触发）；密钥类凭证在 IM 里没有安全的收取方式，Agent 只会请你在**网页控制台打开同一个会话**填写，且**永远不会**让你把密钥粘进聊天。自动化渠道没有人值守，Agent 不会等待，而是把缺失的授权记为阻塞项继续交付。详见 [IM 平台](/zh/ai-sre/im#连接与授权)。
+</Note>
+
+### 需要连接时
+
+当 Agent 为完成你的请求去搜索能力（`tool_search`），而这次搜索一个工具都没匹配到、查询又正好指向一个**市场目录里存在、但你这个账户还没连接**的厂商时，对话流中会内联出现一张 **连接〈厂商名〉以继续** 卡片：左侧是厂商图标与名称，右侧一枚 **连接** 按钮，卡片上没有别的操作。
+
+这意味着你**不必先去插件市场翻找**：直接在对话里点名厂商（例如「帮我接一下 Datadog」）就能走到连接这一步；若该厂商在目录里根本没有连接器，Agent 会直接说明，而不是让卡片出现。
+
+点击 **连接** 会打开该厂商的连接对话框（与插件市场里的是同一个：填入凭证、完成授权与连接测试）。连接成功后卡片就地翻转：
+
+| 阶段 | 卡片状态 |
+|---|---|
+| 待连接 | 标题 **连接〈厂商名〉以继续**，副文案为该厂商的简介，按钮为 **连接** |
+| 已连接 | 标题 **〈厂商名〉 已连接**，副文案「点击继续任务，AI SRE 会接着查」，按钮变为 **继续任务** |
+
+点击 **继续任务** 后，控制台会替你把「连接已完成，请继续之前的任务。」发给 Agent，让它接着做原来的任务——**关掉连接对话框本身不会恢复回合**，恢复始终是你的一次显式点击。刷新页面后卡片仍呈现已连接状态：控制台按该模板在账户里的安装状态重新推导，不依赖浏览器里的临时状态。
+
+以下几种情况**不会**出现卡片，Agent 只给一句话说明：
+
+- 账户里已经有该厂商的连接（任何团队、任何环境）：Agent 会说明它已连接（或需要先启用、需要重新填写凭证）。
+- 该厂商的连接只允许账户 Owner 或管理员发起：Agent 会说明需要管理员操作。
+- 该厂商的模板要求自托管 Runner，而当前会话没有可用的 Runner。
+- 搜索命中了已连接的工具——只有「零匹配 + 查询指向未连接的市场模板」才出连接卡。
+
+<Note>
+渠道差异：只有控制台（`web`）渲染这张卡片。IM 与 API 渠道不出卡——Agent 会把连接地址作为一条普通链接给出，请你连接后回复「继续」或「continue」再接着做；自动化渠道没有人值守，Agent 不会等待，而是把这个缺失的连接记为阻塞项继续交付。各渠道的完整行为见 [IM 平台](/zh/ai-sre/im#连接与授权)。
+</Note>
+
 ### 子任务（Subagent）
 
 Agent 委派子任务时，对话中会出现一行可点击的**派发引用**：状态环 + 类型徽标（Agent / A2A）+ 子任务名称与当前意图，右侧对齐显示状态与耗时；结束后补上工具调用数 / Token 用量 / 总耗时，失败时在下方附一行红色的失败原因。引用行是紧凑的一行，**不带停止按钮**——停止操作统一放在任务面板的详情头部（见下文「任务面板与后台任务」）。点击引用行会在右侧打开一个与主对话并排的子会话面板——主对话区域随之收窄，而不是被弹窗遮挡；面板可展开为占满主区域的全屏视图，也可以收起回并排布局。
diff --git a/zh/ai-sre/skills.mdx b/zh/ai-sre/skills.mdx
index 37300a7e..66979607 100644
--- a/zh/ai-sre/skills.mdx
+++ b/zh/ai-sre/skills.mdx
@@ -1,6 +1,6 @@
 ---
 title: Skill
-description: Skill 是可复用的能力包：一段 SKILL.md 说明加上允许使用的工具，供 AI SRE Agent 在对话中按需调用。从市场安装、上传自定义 Skill，或在对话中用 skill-creator 直接创建。
+description: Skill 是可复用的能力包：一段 SKILL.md 说明加上允许使用的工具，供 AI SRE Agent 在对话中按需调用。从市场安装、上传自定义 Skill，或在对话中由 skill-creator 新建或从网上找现成的来装。
 keywords: ["AI SRE", "Skill", "SKILL.md", "市场", "Marketplace", "skill-creator", "Agent", "资源"]
 sidebarTitle: Skill
 ---
@@ -48,6 +48,9 @@ tags:
   - tag2
 author: author-name
 license: MIT
+examples:
+  - zh: 帮我看看这个服务最近的延迟为什么升高
+    en: Why has this service's latency gone up recently?
 allowed-tools: bash, read, task
 ---
 
@@ -68,6 +71,7 @@ frontmatter 字段如下：
 | `license` | string | 否 | 许可证 |
 | `allowed-tools` | string[] | 否 | 此 Skill 允许使用的工具清单，留空表示不额外限制 |
 | `venues` | string[] | 否 | 限制此 Skill 只在指定类型的执行环境中可用。取值为 `cloud`（云端 Sandbox）与 `byoc`（自托管 Runner），可多选；留空表示所有环境都可用。上传时会校验取值，写错会被拒绝 |
+| `examples` | object[]（`{zh, en}`） | 否 | 「试试这样问」示例问题。最多 **10** 条，中英文两段都要填；每段都按 `description` 的规则校验（不能含尖括号 `<` / `>`，单段不超过 1024 字符），超限或非法会在**上传时被拒绝** |
 
 <Note>
 `venues` 用于那些结构上离不开某类环境的 Skill——例如需要访问运行环境所在主机的本地二进制、本地文件或内网服务的 Skill，在云端 Sandbox 里根本无法工作。声明 `venues: [byoc]` 后，该 Skill 在云端 Sandbox 会话中既不会出现在 Agent 的可用 Skill 清单里，也无法通过 `/<skill-name>` 触发；只有绑定了自托管 Runner 的会话才能看到并调用它。
@@ -86,25 +90,22 @@ AI SRE 运行时内置了几个 Skill，无需安装即可使用。`flashduty` 
 
 ---
 
-进入 **插件 → Skill** 页面，点击 **浏览 Marketplace** 打开 Skill**目录**，可以浏览并安装 Flashduty 与 Anthropic 提供的 Skill 模板。
+Skill 市场目录是 **插件 → 概览** 页插件目录的一部分：与 MCP 模板、内置 App 一起按类别列出，Skill 单独归在 **Skill** 类别（在「全部」页签下也会出现，行上带 `Skill` 类型标签）。目录上方的搜索框按名称或描述过滤，页签可只看某一类，类别标题右侧的「查看全部 N」可展开该类别；搜索词与所选页签都记在页面地址里，离开再回来仍在原来的位置。
 
 <Steps>
-  <Step title="打开目录">
-    在 Skill 列表页点击 **浏览 Marketplace**，弹出目录对话框，以卡片网格展示所有可用 Skill 模板。
-  </Step>
-  <Step title="检索与筛选">
-    顶部搜索框按名称或描述检索；右上角的**筛选**可只看「已安装」或「未安装」，**排序**支持「已安装优先」或「名称 A–Z」。
+  <Step title="找到要安装的模板">
+    在 **插件 → 概览** 的 **Skill** 类别里找到目标模板，每行展示模板名称与简介。
   </Step>
   <Step title="确认安装">
-    在未安装的卡片上点击 **+** 按钮，会弹出「安装 Skill」确认对话框（标题中带模板名称），提示「将安装到账户，账号内所有成员可用」——市场安装的 Skill 固定为**共享范围**（共享即账户级），不提供归属选择。点击 **安装** 才会真正调用安装接口，把模板内容复制到您的账户，成为一个普通 Skill 行，并标记其来源模板（卡片上以 `v<版本>` 角标标识「来自 Marketplace」）。
+    未安装的模板行右侧是一个圆形 **+** 按钮，点击 **+** 或点击整行，都会弹出「**安装 Skill「〈模板名〉」**」确认对话框，提示「将安装到账户，账号内所有成员可用。」——市场安装的 Skill 固定为**共享范围**（共享即账户级），不提供归属选择。点 **安装** 才真正调用安装接口，把模板内容复制到您的账户，成为一个普通 Skill 行，并标记其来源模板（列表上以 `来自 Marketplace — 〈模板名〉 v〈版本〉` 的悬停提示标识）。安装成功会提示「「〈模板名〉」安装成功」。
   </Step>
   <Step title="管理已安装项">
-    已安装的卡片右上角变为齿轮图标，点击进入该 Skill 的检视面板进行管理。
+    已安装的模板行不再显示 **+**，而是显示 **已启用**。安装后的管理与更新都在 **插件 → Skill** 的 Skill 列表里进行，见下文「管理与检视」与「自动更新与手动更新」。
   </Step>
 </Steps>
 
 <Note>
-新账户会自动预装一组官方 Marketplace 模板：`browser-automation`（浏览器自动化 CLI，用于操作网站/仪表盘/监控 UI）、`mcp-builder`（指导创建 MCP 服务器）、`monit-query`（Monit 数据源查询）与 `skill-creator`（见下文「在对话中创建」）。这些预装 Skill 与手动安装的 Skill 完全一样，可以在下方「管理与检视」中启用/禁用、卸载或更新到最新版本。
+新账户会自动预装一组官方 Marketplace 模板：`browser-automation`（浏览器自动化 CLI，用于操作网站/仪表盘/监控 UI）、`mcp-builder`（指导创建 MCP 服务器）、`monit-query`（Monit 数据源查询）与 `skill-creator`（见下文「在对话中添加」）。这些预装 Skill 与手动安装的 Skill 完全一样，可以在下方「管理与检视」中启用/禁用、卸载或更新到最新版本。
 </Note>
 
 <Warning>
@@ -156,11 +157,14 @@ Skill 名以外的元数据（描述、版本、标签、作者、工具等）
 
 两种模式在替换成功后均返回更新后的 Skill 对象；若目标 Skill 不存在，返回 404 错误而非新建。**不携带 `replace` 参数时（默认），重名归档会被直接拒绝**，上传端点不会隐式覆盖已有 Skill。
 
-### 在对话中创建（skill-creator）
+### 在对话中添加（skill-creator）
 
 除了上传 zip，您还可以**直接在 AI SRE 会话里创建和打磨 Skill**。`skill-creator` 是 Flashduty 在 Marketplace 提供、并默认预置到账户的一个 Skill，专门用来「造 Skill」。在任意会话里用 `/skill-creator` 触发，或直接用自然语言提出需求即可：
 
+Skill 列表页右上角的 **在对话中添加** 会新建一条会话，并预填一段需求描述：「我想添加一个 Skill。先问我是自己新建，还是从网上找现成的来装。找现成的就搜几个给我挑，我选好再装。」——即 Agent 会先问您要**自己新建**还是**装现成的**；选现成的先查插件目录/市场，目录里没有再联网搜索候选供您挑选，选好后再安装。提示词只是预填，不会自动发送。该按钮只在您有明确的可写入范围时显示：能授权到账户范围时始终显示，否则需要当前范围筛选恰好只选中一个您所属的团队（或您只属于一个团队）。
+
 - **从零创建**：说「帮我创建一个用于排查 X 的 Skill」，或在一次排障结束后说「把刚才这套流程固化成一个 Skill」。skill-creator 会与您澄清意图、起草 `SKILL.md`、（可选）建立测试用例并据此迭代，满意后一键保存为账户里的 Skill。
+- **从网上找现成的**：从「在对话中添加」进入并选择装现成的时，Agent 先查插件目录，目录里没有再联网搜索候选；选定后由它完成安装，成为一个普通 Skill 行。
 - **改写与优化**：在某个 Skill 的检视面板点击 **「在聊天中编辑」**，会以 skill-creator 改写该 Skill；它也能帮您打磨 `description`，提升被正确触发的准确度。
 
 Agent 完成起草后可一键把内容保存为 Skill；与已有 Skill 重名时，保存前会弹出「替换」确认对话框——底层即走按名称覆盖模式（`replace=true`，无 `skill_id`）。
@@ -201,6 +205,7 @@ Skill 列表以表格展示每个 Skill 的**名称**（含来源模板角标、
 - **右侧**：选中文件的内容预览，顶部显示 Skill 描述。
 - **标题区**：Skill 名（短引用形如 `skill-xxxxxx`）、范围标签（共享 / 团队名）、来源模板版本角标（鼠标悬停显示「来自 Marketplace — 模板名 v版本」）、**有更新**标记、作者、`version`、以及完整 SkillID。
 - **操作**：在聊天中试用（向新会话注入 `/<skill-name>`）、更新到最新版本、在聊天中编辑、替换、下载、卸载。
+- **试试这样问**：若该 Skill 在 `SKILL.md` 的 frontmatter 里声明了 `examples`，检视面板会列出最多 2 条示例问题，点击即以该 Skill 加该问题预填一条新会话消息（不会自动发送）。
 
 <Tip>
 Skill 包**过大无法预览**时，检视面板会提示体积并建议改用「下载」查看。
diff --git a/zh/changelog/changelog.mdx b/zh/changelog/changelog.mdx
index d00a31c5..c4601d07 100644
--- a/zh/changelog/changelog.mdx
+++ b/zh/changelog/changelog.mdx
@@ -4,6 +4,51 @@ description: "本页面记录 Flashduty 产品的重要更新和功能发布"
 keywords: ["更新日志", "产品发布", "功能更新", "Flashduty", "版本记录"]
 ---
 
+<Update label="2026-09-16" description="💰 AI SRE 正式开始计费，插件目录统一到「概览」">
+
+### AI SRE 正式开始计费
+
+AI SRE 自 **2026 年 9 月 16 日 8 点（北京时间）** 起正式开始收费，按 credits 计量模型用量、沙箱在线时长和联网检索（1 credit = ¥1），此前的使用不收取费用。开通免费，符合条件的账户每个计费周期赠送体验额度，也可以购买资源包（1,000 / 5,000 / 20,000 credits）；按量付费默认关闭，由管理员开启并可设置每周期上限。
+
+- 体验额度、资源包与钱包余额都用尽时，会话会被拒绝：输入区禁用、上方常驻一条**不可关闭**的提示，并给出「前往 AI SRE 计费」入口；由管理员开通按量付费、购买资源包或充值后自动恢复
+- On-call 订阅失效（已过期或已停用）同样会暂停 AI SRE，提示「本账户的 On-call 订阅已失效（已过期或已停用），AI SRE 已暂停」，**续费后自动恢复**、无需重新开通；订阅版本低于专业版时提示升级订阅
+
+详见 [AI SRE 概述 · 开通与计费](/zh/ai-sre/overview#开通与计费) 与[《AI SRE credits 资源包购买协议》](/zh/compliance/ai-sre-credit-package-purchase-agreement)。
+
+### 插件目录统一到「概览」，市场接入改为「连接」对话框
+
+**插件 → 概览** 现在是一个完整的插件目录：MCP 模板、内置 App（GitHub / GitLab / Kubernetes）与市场 Skill 一起按类别分页签展示，支持搜索与「查看全部 N」，搜索词与页签记在页面地址里。
+
+- 市场 MCP 模板的接入入口收敛为条目右侧的圆形 **+** →「**连接**」对话框（填连接参数、选运行环境、连接测试），不再是在对话中完成安装
+- Skill 模板点 **+** 后弹出「安装 Skill」确认框，安装到账户（共享）范围；已安装的行显示「已启用」
+- Skill 列表页的对话式入口由「在对话中创建」改为「**在对话中添加**」：新建会话并预填需求，先问您是自己新建还是找现成的来装，选现成的先查插件目录、目录里没有再联网搜索候选
+
+详见 [MCP（外部工具）](/zh/ai-sre/mcp) 与 [Skill](/zh/ai-sre/skills)。
+
+### 边缘端告警引擎支持服务端推送的自动升级
+
+Linux（systemd）部署的告警引擎会在心跳响应里收到平台下发的目标版本，自行下载校验、原子替换二进制；替换后的进程进入约 180 秒观察期，首次心跳成功即视为升级成功，否则自动回滚到上一版本。Docker / Kubernetes 部署不参与自动升级，升级方式仍是更换镜像版本；启动参数 `--alerter.disableAutoUpdate` 可让单个实例退出自动升级。详见 [告警引擎](/zh/monitors/engine/engine#自动升级)。
+
+### 故障时间线新增「接续对话」入口
+
+AI SRE 代某位成员执行的动作（例如自动化规则跑完一轮排查、把结论写回故障）会以联合署名 `{{name}} 和 AI SRE` 记入故障时间线：每条这样的记录右侧都常驻一个 **接续对话** 入口，点击即可在 AI SRE 面板里继续那场会话；把鼠标移到署名里的 AI SRE 上弹出的悬浮卡也提供同一个按钮，悬浮卡按钮由「查看会话」改为「接续对话」。详见 [查看故障](/zh/on-call/incident/search-view-incident#ai-sre-代操作记录)。
+
+</Update>
+
+<Update label="2026-09-15" description="📉 云日志数据源不再支持按曲线无数据检测">
+
+### 云日志数据源不再支持按曲线无数据检测
+
+腾讯云 CLS 与阿里云 SLS 属于云日志类数据源，不再支持「之前查到过数据，现在查不到了，就告警」这种**按曲线（per-series）**的无数据检测，只保留「**所有查询均无返回数据时告警**」：
+
+- 编辑告警规则时，云日志类数据源下不再出现按曲线的检测卡；这类告警的**恢复方式**固定为「任一查询重新查到数据后自动恢复」，界面上只读展示，不再提供下拉选项
+- 存量已开启按曲线检测的规则，打开编辑页时该判定会被**自动关闭**并弹出提示，保存后生效；不打开编辑页则规则配置不变。若规则除此之外没有其它已启用的判定，保存会被「至少启用一项」校验拦下，需要显式改配
+- 腾讯云 CLS 更早已由后端硬校验拒绝该判定，本次一并统一了云日志类数据源的产品口径
+
+建议这类规则改为「所有查询均无返回数据时告警」。详见 [阿里云 SLS](/zh/monitors/alert-rules/sls) 与 [腾讯云 CLS](/zh/monitors/alert-rules/tencent-cls)。
+
+</Update>
+
 <Update label="2026-09-11" description="🔗 邀请链接与二维码、加入限制、告警规则的 AI 查询助手">
 
 ### 邀请链接与邀请二维码
diff --git a/zh/developer/cli.mdx b/zh/developer/cli.mdx
index 9b052a51..4b0bc314 100644
--- a/zh/developer/cli.mdx
+++ b/zh/developer/cli.mdx
@@ -587,6 +587,26 @@ flashduty monit datasource-delete --id <datasource-id>  # 删除数据源（引
 - `kafka`：`sasl_mechanism`（`none` 默认 / `plain` / `scram-sha-256` / `scram-sha-512`，后三者需用户名与密码）、`username` / `password`、`timeout_ms`（默认 5000）、TLS 字段（`tls_min_version` 默认 1.2，最高 1.3）。
 - 密码与 `kafka.tls_key` 支持 `${env:NAME}` 引用（在 Edge 上解析）；字面值不会出现在响应中，仅 `${env:...}` 引用会回显。**更新时省略这些字段以保留已存密钥，显式传空字符串表示清除**。
 
+#### `prometheus-api-v1-label-{label_name}-values` — 查询 Prometheus 标签值
+
+`GET /monit/prometheus/api/v1/label/{label_name}/values`（operationId `monit-prometheus-read-label-values`）带路径参数，因此不参与代码生成，由手工实现命令提供。命令名沿用生成命令的路径派生写法（`monit` 组 + 路径剩余段连字符拼接），因此在 `flashduty monit --help` 下可见、但无法按直觉猜到，需要按本节的写法使用：
+
+```bash
+flashduty monit prometheus-api-v1-label-{label_name}-values <label_name> --data-source-id <datasource-id>
+flashduty monit prometheus-api-v1-label-{label_name}-values job --data-source-id 12345   # 列出 label job 的全部取值
+```
+
+| 参数 | 说明 |
+|------|------|
+| `<label_name>` | 位置参数（必填，且只接受一个），如 `job`、`instance` |
+| `--data-source-id` | 数据源 ID（必填，最小 1），来自 `monit datasource-list`；须是当前账号拥有、Prometheus 兼容的数据源 |
+
+返回体是**数据源原生的 Prometheus 载荷**，不带 Flashduty 的 `{request_id, error, data}` 信封：成功时为 `{"status":"success","data":["api","db","worker"]}`。数据源自身拒绝查询时（如标签名不存在），命令以非零退出码失败，错误文本是数据源（或 Monitors 代理）返回的原始内容——Prometheus 的原生错误形如 `{"status":"error","errorType":"bad_data","error":"unknown label name"}`，与 Flashduty 的错误码体系无关。
+
+<Note>
+本命令只取某个标签的取值集合；要按表达式取时序数据或做更复杂的 PromQL 查询，请用上文的 `monit-query <datasource-id> --tool 'prometheus.query'`。
+</Note>
+
 ### alert — 告警与告警事件查询
 
 ```bash
@@ -663,7 +683,7 @@ flashduty insight incident-export [flags]    # 导出筛选后的故障列表为
 
 ### 全量命令覆盖
 
-除上述精选命令外，CLI 现已通过 spec 驱动的代码生成实现对 Flashduty OpenAPI 的**全量覆盖**。当前 OpenAPI 含 **337 个 API 操作**，CLI 为其中 **334 个** 生成对应命令，其余 3 个——流式导出的 `session-read-export` 与 multipart 表单上传的 `mapping-data-write-upload`、`skill-write-upload`——以手工实现命令提供（`session export`、`enrichment mapping-data-upload`、`safari skill-upload`），并按资源组织为顶层命令组。除 On-call 域（incident、incident-trigger-subscription、change、channel、field、status-page、template 等）外，还覆盖了：
+除上述精选命令外，CLI 现已通过 spec 驱动的代码生成实现对 Flashduty OpenAPI 的**全量覆盖**。CLI 生成器读取的 OpenAPI 规范含 **340 个 API 操作**，CLI 为其中 **336 个** 生成对应命令，其余 4 个以手工实现命令提供——流式导出的 `session-read-export`（`session export`）、multipart 表单上传的 `mapping-data-write-upload` 与 `skill-write-upload`（`enrichment mapping-data-upload`、`safari skill-upload`）、带路径参数的 `monit-prometheus-read-label-values`（`monit prometheus-api-v1-label-{label_name}-values`，见下文「查询 Prometheus 标签值」）——并与生成命令一并按资源组织为顶层命令组。除 On-call 域（incident、incident-trigger-subscription、change、channel、field、status-page、template 等）外，还覆盖了：
 
 - **AI SRE（`safari`）**：a2a-agents、artifacts、automations、knowledge、mcp-servers、sessions、skills 等
 - **告警与降噪**：alert、alert-event、enrichment（alert-rules、rule-sets）、route
diff --git a/zh/developer/go-sdk.mdx b/zh/developer/go-sdk.mdx
index 983af702..47a8a259 100644
--- a/zh/developer/go-sdk.mdx
+++ b/zh/developer/go-sdk.mdx
@@ -184,8 +184,12 @@ client, err := flashduty.NewClient("YOUR_APP_KEY",
 
 `client.Artifacts`（AI SRE 产物）对应 `/safari/artifact/*` 的 11 个 API 操作：画廊读取侧 `ReadGet`（按 ID 获取单个已发布产物）、`ReadList`（分页列出调用方可见的产物，支持标题子串搜索、`scope`（`all` / `personal` / `team`）与 `team_ids` 过滤）、`ReadGetFileState`（批量探测会话展示文件（`pf_` 前缀）是否已有上线产物，单次至多 50 个 ID）；文件侧 `ReadSign`（为展示文件签发短期有效的下载/预览 URL，有效期 5 分钟，`expires_in` 固定 300 秒）与 `ReadStream`（凭签名 token 下载或预览文件，成功响应体是文件而非 JSON 信封，原始字节放在 `Response.Raw`）；写入侧 `WritePublish`（把会话产生的文件发布为画廊产物）、`WriteUpdate`（重命名或转移个人/团队作用域）、`WriteDelete`（从画廊移除，源文件仍保留在会话中）；公开分享 `WriteShareEnable`（开启匿名公开分享并返回公开链接，任何人凭链接即可查看、无需登录）、`WriteShareRevoke`（关闭分享，链接立即失效）、`WriteShareSync`（把公开快照刷新为最新内容——当 `share_enabled` 为 true 且 `share_file_id` 与 `file_id` 不一致时表示快照已过期，调用它刷新）。相关导出类型包括 `PublishedArtifactItem`、`ArtifactShareState`、`SignedUrLs` 以及各 `Artifact*Request` / `Artifact*Response`。
 
+`client.Members.MemberNotify`（`POST /member/notify`，`memberNotify`）以调用方身份向账户成员发送邮件，仅可使用 AI SRE 会话凭据调用——其他凭据（包括普通 `app_key`）一律以 `AccessDenied` 拒绝（用 `IsAccessDenied` / `ErrorCodeOf` 判定）。请求字段：`subject`（必填，1–200 字符）与 `html`（必填，收件人看到的完整邮件正文；服务端会清洗，移除 `script`、`style`、`iframe` 等标签以及全部 `on*` 事件属性，图片仅保留 `src` 为 `https` 的，链接仅允许 `http` / `https` / `mailto`），`person_ids` 可选（至多 20 个且不可重复，省略或为空时只发送给调用方本人）。发送前先把 `dry_run` 设为 `true` 调一次：此时不入队，响应中的 `html` 就是收件人将收到的完整邮件，可据此确认清洗没有删掉正文依赖的内容，也不占用每小时限额与同轮次去重。投递是异步的，`accepted` 只表示邮件已入队；响应按收件人逐条返回 `recipients[]`（`person_id` 与 `status`），`status` 为 `accepted` 或 `skipped`，后者带 `reason`：`not_member`、`no_email`、`email_disabled`、`duplicate`、`rate_limited`（同一收件人每小时最多 20 封）、`send_failed`。
+
 `client.Diagnostics.QueryData` 通过 `POST /monit/query/data` 执行同步查询，返回稳定的 `query_result.v1` 结构化结果（`result.kind` 为 `frames` / `records` / `samples` 之一），要求 monit-edge v0.65.0 及以上版本。日志模式和指标趋势分析统一使用 `client.DataSources.ToolsInvoke`，工具名称为 `prometheus.metric_trends`、`loki.log_patterns` 或 `victorialogs.log_patterns`。
 
+`client.Diagnostics.QueryExplore`（`POST /monit/query/explore`，`monit-read-query-explore`）对已配置的数据源执行探索查询，返回数据源原生形态的 `explore_result.v1`：`ExploreData.format` 恒为 `explore_result.v1`，`result.kind` 取 `frames`（列式表格或时序，见 `ExploreFrame` / `ExploreField`）、`samples`（带标签的瞬时值 `ExploreSample`）或 `logs`（日志条目 `ExploreLogEntry`，最多 1000 条，被截断时 `has_more` 为 true、`applied_limit` 给出实际生效的上限），`execution.effective_step_seconds` 回显应用 `max_data_points` 与 `min_step_seconds` 之后实际使用的步长。请求字段：`datasource_id`（取自 `/monit/datasource/list`，必须是当前账户下的数据源）、`expr`（数据源原生语言的查询表达式，如 PromQL、LogsQL、SQL）、`args`（Grafana 风格宏变量替换的字符串键值；请求中必填，没有宏变量时传空表 `map[string]string{}`——Go 的 `nil` map 会序列化为 `null`，不符合 schema）与 `execution`（`QueryExploreExecution`：`kind` 取 `instant` / `range` / `window`，`to_ms` 在三种模式下都必填，`range` 另需 `from_ms` 与 `max_data_points`，`window` 另需 `from_ms`，`min_step_seconds` 仅在 `range` 下接受）。与 `QueryData` 的分工：需要数据源原生结果形态（含原始日志）时用 `QueryExplore`，需要稳定的 `query_result.v1` 契约时用 `QueryData`。该接口需要「数据源查看」（`monit`）权限，并要求受支持的部署运行 monit-edge v0.68.0 及以上版本。
+
 `client.Applications`（RUM 应用）除应用管理外还覆盖 **RUM 远程配置**的 5 个方法：`RemoteConfigReadGet`（`POST /rum/application/remote-config/get`，读取当前生效的配置与 `version`）、`RemoteConfigReadHistoryList`（`/rum/application/remote-config/history/list`，分页列出已发布的历史版本）、`RemoteConfigReadPreview`（`/rum/application/remote-config/preview`，用模拟客户端的 `env` / `app_version` / `sdk` 上下文评估一份草稿配置，返回命中的 `hit_rule_index` 与最终下发的 `values`，不发布）、`RemoteConfigWriteUpdate`（`/rum/application/remote-config/update`，发布一份完整的新配置）、`RemoteConfigWriteHistoryRevert`（`/rum/application/remote-config/history/revert`，把历史版本的内容重新发布为新版本）。主要类型：`RemoteConfig`（`enabled`、`activation`、`default`、`rules`、`custom`、`refresh_on_foreground`）、`RemoteConfigValues`（四个可下调的 SDK 开关）、`RemoteConfigRule`（`match` 条件加 `set` 取值）、`RemoteConfigHistoryItem`（含 `version`、`reason`、`content_hash`、`updated_by`），以及 `GetRemoteConfigRequest` / `ListRemoteConfigHistoryRequest` / `PreviewRemoteConfigRequest` / `UpdateRemoteConfigRequest` / `RevertRemoteConfigRequest` 与各自的 `*Response`。
 
 `client.DataSources.ToolsInvoke`（`POST /monit/datasource/tools/invoke`，`monit-datasource-tools-invoke`）在某个已配置数据源上执行一个确定性工具：`tool` 名称由数据源类型前缀修饰（如 `mysql.overview`），`params` 为工具专属 JSON 参数（省略视为 `{}`，显式 `null` 非法）；除诊断工具外，入口支持 `<type>.query` 查询工具（`prometheus`、`mysql`、`postgres`、`oracle`、`clickhouse`、`elasticsearch`、`loki`、`victorialogs`、`sls`、`tencent_cls`），`/monit/query/data` 入口保持不变。该接口要求集群中所有在线可路由的 Edge 会话都支持 v0.71.0 基础调用协议（单个工具可能要求更新的实现），无工具目录、无自动重放、也不会回退到旧版 diagnose。请求体上限 128 KiB，完整成功响应上限 10 MiB，单工具超时至多 25 秒；响应为 `DatasourceToolResult`（`data` 为工具专属 JSON、永不为 null，`summary` 可选，出现 `truncated` 时其 `reason` 说明截断原因）。
@@ -207,6 +211,8 @@ if err != nil {
 out, _, err := client.DataSources.ToolsInvoke(ctx, req)
 ```
 
+`client.DataSources.ReadPrometheusLabelValues(ctx, dataSourceID, labelName)`（`GET /monit/prometheus/api/v1/label/{label_name}/values`，`monit-prometheus-read-label-values`）通过监控代理列出某个 Prometheus 兼容数据源上单个标签的全部取值：标签名放在 URL 路径上（SDK 会做路径转义），目标数据源由 `X-DSID` 请求头指定——SDK 用 `dataSourceID` 自动设置该头（传 `0` 或 `labelName` 为空都直接报错），ID 从 `/monit/datasource/list` 获取，必须是当前账户下 Prometheus 兼容类型的数据源。这是唯一一个成功响应体不是 Flashduty `{request_id, data}` 信封的方法：响应直接解码为 `PrometheusLabelValuesResponse`（`status` 为 `success` 时 `data` 是标签值字符串数组；为 `error` 时携带 `errorType` 与 `error`）。未到达数据源前的失败（`X-DSID` 缺失或非法、数据源不存在、数据源不是 Prometheus 类型）以 `text/plain` 返回，数据源自身的失败则用它自己的 JSON 错误形态；SDK 对两者一视同仁，把原始响应体原样放进 `*ErrorResponse.Message`。受支持的部署要求 monit-edge v0.35.0 及以上版本。
+
 `client.DataSources` 的 `payload` 按 `type_ident` 选择类型专属配置块。当前允许的 `type_ident` 共 15 种：`prometheus`、`loki`、`mysql`、`oracle`、`postgres`、`clickhouse`、`elasticsearch`、`sls`、`tencent_cls`、`victorialogs`，以及新增的诊断专用类型 `redis_node`、`redis_sentinel`、`mongodb_mongod`、`mongodb_mongos`、`kafka`——诊断专用类型的 `alerting_enabled` 恒为 false（不阻止非告警查询与工具调用），且拒绝传 true。连接地址规则：Redis/MongoDB 诊断类型为单个 `host:port`（IPv6 需加方括号），不接受 URI、userinfo 或 query；`kafka` 为 1–32 个以逗号分隔、互不重复的 `host:port` bootstrap 地址（规范化后至多 4096 字符，`payload` 中不再有 broker 列表）；`mongodb_mongod` / `mongodb_mongos` 的配置块中 `auth_source` 默认为 `admin`，用户名与密码必须成对配置，不支持客户端证书；Redis 节点配置的 `database` 默认为 0。诊断类型的 `password` 与 Kafka 的 `tls_key` 等敏感字段支持 `${env:NAME}` 引用：响应中字面值会被省略（仅当存储值本身就是 `${env:...}` 引用时才回显），更新时省略这些字段即保留原值，显式传空字符串则清除。
 
 `enabled` 与 `alerting_enabled` 相互独立：`enabled`（业务执行开关）创建时默认 true，`alerting_enabled`（是否允许参与告警评估；告警还要求 `enabled` 为 true 且类型支持告警）创建时对告警类型默认 true、对诊断专用类型默认 false；二者更新时省略均保留当前值，显式传 `null` 非法；当有启用的告警规则引用该数据源时，将其 `enabled` 置为 false 会以 conflict 拒绝。另外 `/monit/datasource/list` 响应中 `payload` 恒为 `null`（列表查询不读 payload 列），create/update/info 响应中才会填充。
@@ -294,7 +300,9 @@ Flashduty API 返回的未成功调用——无论是信封中携带了错误,
 当 API 返回 429 时,错误被提升为 `*RateLimitError`：它内嵌 `*ErrorResponse`（所以 `errors.As` 取 `*ErrorResponse` 仍然成立),并额外带上 `RetryAfter` 提示。
 
 <Note>
-如果你收到的是带非 JSON 响应体的非 2xx 响应,SDK 会返回普通 `error`,而不是 `*ErrorResponse`。这表示响应来自网关、负载均衡器或代理等中间层,通常是请求超过了中间层超时。你可以重试请求,或将耗时较长的批量请求拆分为更小的批次；不要假定 `errors.As(err, &apiErr)` 能匹配此类错误。
+对于**生成接口**，如果你收到的是带非 JSON 响应体的非 2xx 响应,SDK 会返回普通 `error`,而不是 `*ErrorResponse`。这表示响应来自网关、负载均衡器或代理等中间层,通常是请求超过了中间层超时。你可以重试请求,或将耗时较长的批量请求拆分为更小的批次；不要假定 `errors.As(err, &apiErr)` 能匹配此类错误。
+
+手写方法 `client.DataSources.ReadPrometheusLabelValues` 是例外：它不解析信封，而是把非 2xx 的原始响应体按原文放进 `*ErrorResponse.Message` 返回——平台的 `text/plain` 4xx/5xx 与数据源自身的 JSON 错误形态一视同仁，429 仍提升为 `*RateLimitError`。因此在这个方法上 `errors.As(err, &apiErr)` 是成立的，只是 `Code` 通常为空，需要读 `Message` 与 `Response.StatusCode` 判断原因。
 </Note>
 
 ```go
diff --git a/zh/monitors/alert-rules/clickhouse.mdx b/zh/monitors/alert-rules/clickhouse.mdx
index 4462adc4..5a72a171 100644
--- a/zh/monitors/alert-rules/clickhouse.mdx
+++ b/zh/monitors/alert-rules/clickhouse.mdx
@@ -101,9 +101,9 @@ Monitors 按标签字段区分告警对象，并使用值字段进行阈值判
 
 ### 恢复逻辑
 
-无数据告警支持配置**告警结束方式**，决定告警如何结束：
+无数据告警的**恢复方式**在「之前查到过数据，现在查不到了，就告警」这张检测卡内配置，决定该告警如何结束：
 
-| 结束方式 | 说明 |
+| 恢复方式 | 说明 |
 |------|------|
 | **数据重新出现后自动结束** | 默认方式。数据重新出现后，告警自动结束 |
 | **数据恢复或超时后自动结束** | 数据重新出现或达到自动关闭时间后，告警自动结束。自动关闭时间单位为秒，最小为 1；仅开启「之前查到过数据，现在查不到了」模式时可选 |
diff --git a/zh/monitors/alert-rules/elasticsearch.mdx b/zh/monitors/alert-rules/elasticsearch.mdx
index 970a5958..0325aeaa 100644
--- a/zh/monitors/alert-rules/elasticsearch.mdx
+++ b/zh/monitors/alert-rules/elasticsearch.mdx
@@ -131,9 +131,9 @@ WHERE "@timestamp" > now() - INTERVAL 5 MINUTES
 
 ### 恢复逻辑
 
-无数据告警支持配置**告警结束方式**，决定告警如何结束：
+无数据告警的**恢复方式**在「之前查到过数据，现在查不到了，就告警」这张检测卡内配置，决定该告警如何结束：
 
-| 结束方式 | 说明 |
+| 恢复方式 | 说明 |
 |------|------|
 | **数据重新出现后自动结束** | 默认方式。一旦该 `host_name` 重新出现在查询结果中，告警自动结束 |
 | **数据恢复或超时后自动结束** | 数据重新出现或达到自动关闭时间后，告警自动结束。自动关闭时间单位为秒，最小为 1；仅开启「之前查到过数据，现在查不到了」模式时可选 |
diff --git a/zh/monitors/alert-rules/loki.mdx b/zh/monitors/alert-rules/loki.mdx
index dd99e1fd..1b620f82 100644
--- a/zh/monitors/alert-rules/loki.mdx
+++ b/zh/monitors/alert-rules/loki.mdx
@@ -96,9 +96,9 @@ rate({job="node-logs"} [1m])
 
 ### 恢复逻辑
 
-无数据告警支持配置**告警结束方式**，决定告警如何结束：
+无数据告警的**恢复方式**在「之前查到过数据，现在查不到了，就告警」这张检测卡内配置，决定该告警如何结束：
 
-| 结束方式 | 说明 |
+| 恢复方式 | 说明 |
 |------|------|
 | **数据重新出现后自动结束** | 默认方式。数据重新出现后，告警自动结束 |
 | **数据恢复或超时后自动结束** | 数据重新出现或达到自动关闭时间后，告警自动结束。自动关闭时间单位为秒，最小为 1；仅开启「之前查到过数据，现在查不到了」模式时可选 |
diff --git a/zh/monitors/alert-rules/mysql.mdx b/zh/monitors/alert-rules/mysql.mdx
index ab9540ae..9eb9f5d4 100644
--- a/zh/monitors/alert-rules/mysql.mdx
+++ b/zh/monitors/alert-rules/mysql.mdx
@@ -101,9 +101,9 @@ Monitors 按标签字段区分告警对象，并使用值字段进行阈值判
 
 ### 恢复逻辑
 
-无数据告警支持配置**告警结束方式**，决定告警如何结束：
+无数据告警的**恢复方式**在「之前查到过数据，现在查不到了，就告警」这张检测卡内配置，决定该告警如何结束：
 
-| 结束方式 | 说明 |
+| 恢复方式 | 说明 |
 |------|------|
 | **数据重新出现后自动结束** | 默认方式。数据重新出现后，告警自动结束 |
 | **数据恢复或超时后自动结束** | 数据重新出现或达到自动关闭时间后，告警自动结束。自动关闭时间单位为秒，最小为 1；仅开启「之前查到过数据，现在查不到了」模式时可选 |
diff --git a/zh/monitors/alert-rules/oracle.mdx b/zh/monitors/alert-rules/oracle.mdx
index 6243b57a..91b2e262 100644
--- a/zh/monitors/alert-rules/oracle.mdx
+++ b/zh/monitors/alert-rules/oracle.mdx
@@ -101,9 +101,9 @@ Monitors 按标签字段区分告警对象，并使用值字段进行阈值判
 
 ### 恢复逻辑
 
-无数据告警支持配置**告警结束方式**，决定告警如何结束：
+无数据告警的**恢复方式**在「之前查到过数据，现在查不到了，就告警」这张检测卡内配置，决定该告警如何结束：
 
-| 结束方式 | 说明 |
+| 恢复方式 | 说明 |
 |------|------|
 | **数据重新出现后自动结束** | 默认方式。数据重新出现后，告警自动结束 |
 | **数据恢复或超时后自动结束** | 数据重新出现或达到自动关闭时间后，告警自动结束。自动关闭时间单位为秒，最小为 1；仅开启「之前查到过数据，现在查不到了」模式时可选 |
diff --git a/zh/monitors/alert-rules/postgres.mdx b/zh/monitors/alert-rules/postgres.mdx
index 824704a3..918bc946 100644
--- a/zh/monitors/alert-rules/postgres.mdx
+++ b/zh/monitors/alert-rules/postgres.mdx
@@ -101,9 +101,9 @@ Monitors 按标签字段区分告警对象，并使用值字段进行阈值判
 
 ### 恢复逻辑
 
-无数据告警支持配置**告警结束方式**，决定告警如何结束：
+无数据告警的**恢复方式**在「之前查到过数据，现在查不到了，就告警」这张检测卡内配置，决定该告警如何结束：
 
-| 结束方式 | 说明 |
+| 恢复方式 | 说明 |
 |------|------|
 | **数据重新出现后自动结束** | 默认方式。数据重新出现后，告警自动结束 |
 | **数据恢复或超时后自动结束** | 数据重新出现或达到自动关闭时间后，告警自动结束。自动关闭时间单位为秒，最小为 1；仅开启「之前查到过数据，现在查不到了」模式时可选 |
diff --git a/zh/monitors/alert-rules/prometheus.mdx b/zh/monitors/alert-rules/prometheus.mdx
index 5a1d35d9..b0046e00 100644
--- a/zh/monitors/alert-rules/prometheus.mdx
+++ b/zh/monitors/alert-rules/prometheus.mdx
@@ -139,16 +139,20 @@ Monitors 支持在一个告警规则中配置多条查询语句（分别命名
 两个子模式可以同时开启，并且相互独立运行。
 </Note>
 
-### 告警结束方式
+### 恢复方式
 
-开启任一子模式后，可配置**告警结束方式**，决定无数据告警如何结束：
+**恢复方式**（字段 `end_mode`）只出现在子模式一（按 Series 监控，即界面上「之前查到过数据，现在查不到了，就告警」那张检测卡）内部，只对这张卡里的判定生效。子模式二的恢复方式不可配置，固定为「任一查询重新查到数据后自动恢复」，界面以只读文本展示，没有下拉框。
 
-| 结束方式 | 说明 |
+子模式一内可选的恢复方式：
+
+| 恢复方式 | 说明 |
 |------|------|
 | **数据重新出现后自动结束** | 默认方式。数据重新出现后，告警自动结束 |
-| **数据恢复或超时后自动结束** | 数据重新出现或达到自动关闭时间后，告警自动结束。自动关闭时间单位为秒，最小为 1；仅开启子模式一（按 Series 监控）时可选择 |
+| **数据恢复或超时后自动结束** | 数据重新出现或达到自动关闭时间后，告警自动结束。自动关闭时间单位为秒，最小为 1，对应字段 `auto_close_after_seconds` |
 | **仅允许手工关闭** | 告警保持活动，直到用户手工关闭 |
 
+恢复方式属于单个判定、不是页签级共享设置，因此它不在「触发与恢复条件」卡里——那张卡只放所有已启用判定共用的字段（`触发方式`、`触发条件`、`恢复条件`）。
+
 ### 对比 Prometheus 原生的 `absent()` 函数
 
 | 方式 | 说明 |
diff --git a/zh/monitors/alert-rules/sls.mdx b/zh/monitors/alert-rules/sls.mdx
index 929f9ec2..51f04c18 100644
--- a/zh/monitors/alert-rules/sls.mdx
+++ b/zh/monitors/alert-rules/sls.mdx
@@ -83,6 +83,12 @@ Monitors 按配置的时间范围执行 SLS 查询，按标签字段区分告警
 
 此模式用于监控"预期应该有数据，但实际没有数据"的场景。
 
+SLS 属于云日志类数据源，不支持按曲线（per-series）的无数据检测，只保留「**所有查询均无返回数据时告警**」这一种判定：
+
+- 界面上只有一张判定卡「所有查询均无返回数据时告警」，对应 `alert_on_empty_result` 与 `alert_on_empty_result_severity` 两个字段。
+- 「之前查到过数据，现在查不到了，就告警」那张按曲线的检测卡在 SLS 规则里不渲染，它的配置项 `check_nodata.enabled` 因此无从设置。
+- 同类数据源腾讯云 CLS 也禁用该判定，且在后端是硬校验（提交 `check_nodata.enabled` 直接返回 400）；SLS 目前由前端禁用，后端未加拦截。
+
 ### 配置方式
 
 1. **查询语句**：编写一个预期应该持续返回数据的查询。
@@ -90,17 +96,32 @@ Monitors 按配置的时间范围执行 SLS 查询，按标签字段区分告警
     ```sql
     * | SELECT host, max(__time__) as last_seen GROUP BY host
     ```
-2. **判定规则**：如果某个 `host` 在之前的周期中出现过，但在当前及连续 N 个周期中查不到数据，则触发"数据缺失"告警。
+2. **判定规则**：所有查询在连续 N 次检测中都返回空结果时，触发"数据缺失"告警。N 由该页签共享的「触发条件」决定。
+
+### 存量已启用按曲线检测的规则
+
+以 SLS 为数据源、且已开启按曲线无数据检测的存量规则，打开编辑页时该判定会被自动关闭（`check_nodata.enabled` 以关闭状态回填），并弹出提示：
+
+<Warning>
+当前数据源类型不支持「之前查到过数据，现在查不到了，就告警」，该判定已自动关闭，保存后生效
+</Warning>
+
+规则详情页是只读的，不弹这条提示。这条判定是在编辑页里被关掉的：不打开编辑页，规则配置不会变；打开并保存后，关闭状态才会写回规则。自动关闭只作用于这一项判定，保存时：
+
+- 规则若还有其它已启用的判定（阈值判定、数据存在），「至少启用一项」校验不会拦下这次降级，按曲线检测会随这次保存一起失效——上面那条提示就是为此而弹的。
+- 规则若只有这一项判定，保存会被「阈值判定、数据缺失、数据存在至少启用一项」校验拦下，必须显式改配才能保存。
+
+建议打开这类规则后，把无数据检测改为「所有查询均无返回数据时告警」，确认告警判定里至少有一项已启用，再保存。
 
 ### 恢复逻辑
 
-无数据告警支持配置**告警结束方式**，决定告警如何结束：
+「所有查询均无返回数据时告警」的**恢复方式**不可配置，引擎固定为**任一查询重新查到数据后自动恢复**，界面上以只读文本展示：
 
-| 结束方式 | 说明 |
+| 恢复方式 | 说明 |
 |------|------|
-| **数据重新出现后自动结束** | 默认方式。数据重新出现后，告警自动结束 |
-| **数据恢复或超时后自动结束** | 数据重新出现或达到自动关闭时间后，告警自动结束。自动关闭时间单位为秒，最小为 1；仅开启「之前查到过数据，现在查不到了」模式时可选 |
-| **仅允许手工关闭** | 告警保持活动，直到用户手工关闭 |
+| `任一查询重新查到数据后自动恢复` | 固定值，不是可选项，界面上没有下拉框 |
+
+原先的恢复方式下拉（`数据重新出现后自动结束` / `数据恢复或超时后自动结束` / `仅允许手工关闭`）只存在于按曲线的检测卡内部，SLS 下不可用。无数据页签里可配置的共享项只有触发与恢复条件（`触发方式`、`触发条件`、`恢复条件`）。
 
 ## 4. 高级配置
 
diff --git a/zh/monitors/alert-rules/tencent-cls.mdx b/zh/monitors/alert-rules/tencent-cls.mdx
index af55d50b..a6d2c7d2 100644
--- a/zh/monitors/alert-rules/tencent-cls.mdx
+++ b/zh/monitors/alert-rules/tencent-cls.mdx
@@ -75,9 +75,9 @@ Tencent CLS 规则只能**精确绑定一个数据源**，且不支持名称通
 
 Tencent CLS 不支持按曲线（per-series）的无数据检测：
 
-- 仅支持「**所有查询均无返回数据时告警**」。
-- 不提供「之前查到过数据，现在查不到了，再告警；重新查到数据就恢复」选项——该配置会被后端拒绝，因此这张检测卡在界面上不出现。
-- 告警结束方式只有「数据重新出现后自动结束」与「仅允许手工关闭」，不提供「数据恢复或超时后自动结束」。
+- 仅支持「**所有查询均无返回数据时告警**」这一张判定卡。
+- 不提供「之前查到过数据，现在查不到了，就告警」选项——开启该判定要提交 `check_nodata.enabled`，后端直接返回 400 拒绝，因此这张检测卡在界面上不出现。
+- **恢复方式**不可配置：这类告警没有可选项，引擎固定为「任一查询重新查到数据后自动恢复」，界面上以只读文本展示。「仅允许手工关闭」在这里不存在——恢复方式选择器（`数据重新出现后自动结束` / `数据恢复或超时后自动结束` / `仅允许手工关闭`）只渲染在按曲线的检测卡内部，该卡在 CLS 规则里不出现，这三档都选不到。
 
 ## 恢复查询与关联查询
 
diff --git a/zh/monitors/alert-rules/victorialogs.mdx b/zh/monitors/alert-rules/victorialogs.mdx
index 6b06d9ad..2056477c 100644
--- a/zh/monitors/alert-rules/victorialogs.mdx
+++ b/zh/monitors/alert-rules/victorialogs.mdx
@@ -135,9 +135,9 @@ _time:15m and level:INFO | stats by (level) count(*) total
 
 ### 恢复逻辑
 
-无数据告警支持配置**告警结束方式**，决定告警如何结束：
+无数据告警的**恢复方式**在「之前查到过数据，现在查不到了，就告警」这张检测卡内配置，决定该告警如何结束：
 
-| 结束方式 | 说明 |
+| 恢复方式 | 说明 |
 |------|------|
 | **数据重新出现后自动结束** | 默认方式。数据重新出现后，告警自动结束 |
 | **数据恢复或超时后自动结束** | 数据重新出现或达到自动关闭时间后，告警自动结束。自动关闭时间单位为秒，最小为 1；仅开启「之前查到过数据，现在查不到了」模式时可选 |
diff --git a/zh/monitors/data-sources/data-sources.mdx b/zh/monitors/data-sources/data-sources.mdx
index 1dcfd3fa..63dac1ca 100644
--- a/zh/monitors/data-sources/data-sources.mdx
+++ b/zh/monitors/data-sources/data-sources.mdx
@@ -40,10 +40,24 @@ Monitors 支持以下 15 种数据源类型：
 - **类型**：数据源类型及图标
 - **连接地址**：数据源的访问地址
 - **关联告警引擎**：绑定的告警引擎集群名称，附带引擎在线状态指示
+- **启用数据源**：行内开关，控制该数据源是否参与业务查询与诊断，控制台里开启/停用数据源的入口就在这一列
 - **备注**：补充说明
 
 你可以通过搜索框按名称或类型过滤数据源。列表每 5 秒自动刷新，实时反映引擎连接状态。
 
+### 启用数据源
+
+列表右侧的**启用数据源**列是控制台里开启、停用数据源的入口，切换后立即生效。列头右侧有提示图标，说明停用会造成什么影响：
+
+| 状态 | 含义 |
+|------|------|
+| **开启** | 数据源正常参与业务查询与数据源诊断。 |
+| **关闭** | 该数据源不再执行查询、诊断与告警，但连接参数、凭据、关联告警引擎等配置完整保留，随时可以重新开启；关闭不会改变 `alerting_enabled`。 |
+
+- **权限**：切换该开关需要数据源编辑权限（`MonitDatasourceUpdate`）；没有该权限时开关为禁用状态，只能查看。
+- **新建的数据源默认启用**：新建时一律以 `enabled=true` 创建，新建/编辑抽屉里没有这个开关；要停用数据源，请在创建完成后到列表里切换。
+- **列表徽章**：名称列不再单独显示「已停用」徽章，启停状态只由这颗开关表达。名称列上出现的「不用于告警」徽章表示 `alerting_enabled=false`，与启停无关。
+
 ## 新建数据源
 
 <Steps>
@@ -89,6 +103,7 @@ Monitors 支持以下 15 种数据源类型：
 | **启用** | `enabled` | 是否开启业务执行。关闭后数据源不接受业务查询与数据源工具调用，但不会改变 `alerting_enabled` |
 | **允许告警评估** | `alerting_enabled` | 是否允许该数据源参与告警规则的查询与评估。告警评估同时要求 `enabled=true` 且数据源类型支持告警；`false` 不会阻断非告警查询与数据源工具 |
 
+- **控制台入口**：`enabled` 的开关是数据源列表里的**启用数据源**列（见[启用数据源](#启用数据源)），新建/编辑抽屉里没有这个开关；`alerting_enabled` 则在新建/编辑抽屉中设置。
 - **创建时的默认值**：`enabled` 默认为 `true`；`alerting_enabled` 对支持告警的类型默认为 `true`，对仅诊断类型默认为 `false`。
 - **更新时的行为**：两个字段省略时均保留当前值；显式传入 `null` 非法。
 - **仅诊断类型**（`redis_node`、`redis_sentinel`、`mongodb_mongod`、`mongodb_mongos`、`kafka`）不允许设置 `alerting_enabled=true`。
@@ -110,6 +125,8 @@ Monitors 支持以下 15 种数据源类型：
 | **最低 / 最高 TLS 版本** | 可选 TLS 1.0、1.1、1.2、1.3，默认为系统默认；最低版本不得高于最高版本 |
 | **跳过服务端证书校验** | 勾选后不校验服务端证书 |
 
+启用 **Basic Authentication** 后，**用户名** 与 **密码** 支持 `${env:NAME}` 引用，由每台 Edge 在本地解析（见[在 Edge 本地引用凭据](#在-edge-本地引用凭据)）；**Server URL** 与 **Params** 不支持该语法。
+
 ### MySQL / Oracle / PostgreSQL
 
 关系型数据库共享相似的配置结构：
@@ -126,6 +143,8 @@ Monitors 支持以下 15 种数据源类型：
 
 Oracle 在上述基础连接配置之外，还支持通过 **Options** 添加多组连接选项。MySQL 和 PostgreSQL 额外支持 TLS/SSL 加密连接，通过 **TLS/SSL 模式** 下拉框选择。
 
+上表中的 **用户名** 与 **密码** 支持 `${env:NAME}` 引用，由每台 Edge 在本地解析（见[在 Edge 本地引用凭据](#在-edge-本地引用凭据)）；连接地址不支持该语法。
+
 #### MySQL 的 TLS/SSL 模式
 
 | 模式 | 说明 |
@@ -171,6 +190,8 @@ Elasticsearch 支持 Cloud 与 Self-Managed 两种部署方式，默认选择 Cl
 | **CA 证书** | - | 可选 | - |
 | **证书指纹** | - | 可选 | - |
 
+Cloud 模式的 **Cloud ID**、**API Key**，以及 Self-Managed 模式的 **用户名 / 密码**、**Service Token** 都支持 `${env:NAME}` 引用，由每台 Edge 在本地解析（见[在 Edge 本地引用凭据](#在-edge-本地引用凭据)）。
+
 ### Loki / VictoriaLogs
 
 Loki 与 VictoriaLogs 使用和 Prometheus 相同的 HTTP 连接结构：服务地址、Headers、Params、Basic Authentication，以及自定义 CA、mTLS、服务端名称、TLS 版本和跳过证书校验等 TLS 配置。
@@ -182,6 +203,8 @@ Loki 与 VictoriaLogs 使用和 Prometheus 相同的 HTTP 连接结构：服务
 
 上述地址是输入框示例，不会自动保存为默认值。
 
+启用 **Basic Authentication** 后，**用户名** 与 **密码** 同样支持 `${env:NAME}` 引用（见[在 Edge 本地引用凭据](#在-edge-本地引用凭据)）；服务地址与 **Params** 不支持该语法。
+
 ### ClickHouse
 
 | 配置项 | 说明 | 默认值 |
@@ -198,6 +221,8 @@ Loki 与 VictoriaLogs 使用和 Prometheus 相同的 HTTP 连接结构：服务
 
 开启 **TLS** 后，还可以配置自定义 CA、mTLS、服务端名称、最低 / 最高 TLS 版本和跳过服务端证书校验。关闭 TLS 时，表单会清除这些 TLS 字段。
 
+**用户名 / 密码** 支持 `${env:NAME}` 引用，由每台 Edge 在本地解析（见[在 Edge 本地引用凭据](#在-edge-本地引用凭据)）；连接地址不支持该语法。
+
 ### Aliyun SLS
 
 | 配置项 | 说明 |
@@ -287,7 +312,7 @@ Tencent CLS 类型的告警规则只能精确绑定一个数据源，不支持
 | **连接地址** | 单个 `host:port`；IPv6 加方括号；不接受 URI、userinfo 或查询参数 | - |
 | **用户名 / 密码** | 认证凭据，必须同时配置；支持 `${env:NAME}` 引用；密码保存后不回显字面值 | - |
 | **认证数据库** | 认证所用数据库 | `admin` |
-| **超时时间（毫秒）** | 连接超时 | `3000` |
+| **超时时间（毫秒）** | 连接超时，范围 1000–10000 | `3000` |
 | **TLS** | 是否启用 TLS | 关闭 |
 | **CA 证书** | PEM 格式 CA 证书或 `${env:NAME}` 引用 | - |
 | **最低 / 最高 TLS 版本** | TLS 1.2（默认）或 1.3；最高版本不能低于最低版本 | 1.2 / 不限制 |
@@ -305,7 +330,7 @@ MongoDB 不支持客户端证书认证（mTLS）。
 | **连接地址** | 1–32 个不重复的 `host:port`，逗号分隔 | - |
 | **SASL 机制** | `none`（不接受凭据）、`plain`、`scram-sha-256`、`scram-sha-512`（后三者需要用户名与密码） | `none` |
 | **用户名 / 密码** | SASL 认证凭据；支持 `${env:NAME}` 引用；密码保存后不回显字面值 | - |
-| **超时时间（毫秒）** | 连接超时 | `5000` |
+| **超时时间（毫秒）** | 连接超时，范围 1000–10000 | `5000` |
 | **TLS** | 是否启用 TLS | 关闭 |
 | **CA 证书** | PEM 格式 CA 证书或 `${env:NAME}` 引用 | - |
 | **客户端证书 / 私钥** | PEM 格式，必须成对配置；私钥保存后不回显字面值，支持 `${env:NAME}` 引用 | - |
diff --git a/zh/monitors/engine/engine.mdx b/zh/monitors/engine/engine.mdx
index 41243a95..936c45ab 100644
--- a/zh/monitors/engine/engine.mdx
+++ b/zh/monitors/engine/engine.mdx
@@ -63,6 +63,25 @@ keywords: ["告警引擎", "monitedge", "引擎安装", "引擎状态", "API Key
 | **Docker** | 容器化部署，适合已有 Docker 环境的场景 |
 | **Kubernetes** | 适合云原生环境，以 Deployment 方式部署 |
 
+### 自动升级
+
+Linux 部署的告警引擎支持由服务端推送的自动升级，部署方式选择 **Linux** 时页面上会提示：
+
+> Linux 环境下的告警引擎支持服务端推送的自动升级，开启后无需手动执行升级命令；上方命令仍可用于手动升级兜底
+
+推送与否由平台侧决定，控制台没有开关：完成上述安装配置后，Linux 实例会在收到推送时自行升级；尚未开通推送时，继续复制页面生成的**升级命令**在目标机器上执行即可。
+
+| 项目 | 说明 |
+|------|------|
+| **适用部署方式** | 仅 Linux（systemd）部署生效；Docker 与 Kubernetes 部署不参与自动升级，升级方式仍是更换镜像版本 |
+| **执行方式** | 引擎在心跳响应中收到目标版本号后，自行下载并校验制品、原子替换二进制，再以新版本继续运行；全程无需在目标机器上执行命令 |
+| **升级成功** | 替换后的进程进入约 180 秒观察期，首次心跳成功即视为升级成功，本次升级完成 |
+| **失败回滚** | 观察期内没有成功心跳（例如新版本无法完成认证或协议交互），或新版本连续启动仍未提交心跳（最多 3 次启动机会）时，自动回滚到上一版本 |
+| **重试策略** | 本机回滚过的目标版本在平台发布更新的版本之前不再尝试；同一次升级失败后约 30 分钟内不再重试 |
+| **退出自动升级** | 启动参数 `--alerter.disableAutoUpdate` 可让单个实例不再接受自动升级；容器环境、二进制所在目录不可写时也会自动跳过 |
+
+自动升级需要引擎能够访问制品镜像，默认使用公网镜像；离线或内网环境需通过 `--alerter.updateMirror` 指向内部镜像，详见[引擎 CLI 参数参考](#引擎-cli-参数参考)的「自动升级参数」。
+
 ## API Key 管理
 
 API Key 用于告警引擎与 SaaS 端的身份认证。你可以在引擎安装/升级页面点击**管理 API Key**打开管理面板。
@@ -123,3 +142,12 @@ API Key 用于告警引擎与 SaaS 端的身份认证。你可以在引擎安装
 - **高吞吐场景**（规则数量多、告警频率高）：可适当提高 `alerter.alertRuleDeliveryWorkers`（例如 128），减少事件在队列中的积压时间；必要时同步提高 `alerter.alertRuleEventQueueSize`。
 - **网络或 CPU 受限场景**：可适当降低 `alerter.alertRuleDeliveryWorkers`（例如 16–32），避免并发出站连接过多影响其他业务流量。
 - **网络质量差、丢包率高的场景**：可适当增大 `alerter.serverSleep`（例如 10s），让退避从更长的初始间隔开始，减少拥塞期间的无效请求。
+
+### 自动升级参数
+
+| 参数 | 默认值 | 说明 |
+|------|--------|------|
+| `alerter.disableAutoUpdate` | `false` | 关闭服务端推送的自动升级。设为 `true` 后该实例不再执行自动升级；容器环境会被自动识别并跳过，该参数优先级更高 |
+| `alerter.updateMirror` | `https://static.flashcat.cloud/monitedge` | 自动升级制品的镜像根地址。引擎按 `<镜像根地址>/releases/download/<vX.Y.Z>/` 下载制品与校验文件；离线或内网环境需要改为内部镜像 |
+
+自动升级仅在 Linux（systemd）部署下生效，并且要求引擎能够访问制品镜像。不满足条件时，请在控制台复制**升级命令**手动升级。
diff --git a/zh/monitors/quickstart/quickstart.mdx b/zh/monitors/quickstart/quickstart.mdx
index ad02cb4f..e79feb29 100644
--- a/zh/monitors/quickstart/quickstart.mdx
+++ b/zh/monitors/quickstart/quickstart.mdx
@@ -67,7 +67,7 @@ keywords: ["入门指南", "monitedge", "数据源", "告警规则", "快速开
 
 告警规则可能会很多，Monitors 提供树形分组结构进行分类管理。每个告警规则都要属于某个分组，您可以先创建分组，再在分组下创建告警规则。
 
-创建/编辑告警规则的页面是一个单页表单，按编号分为五个区块：**基础配置**、**数据源**、**查询检测方式**、**检测频率 & 生效时间**、**事件配置**，自上而下排列，在一个页面内滚动填写即可，不再使用分步骤向导。
+创建/编辑告警规则的页面是一个单页表单，按编号分为五个区块：**基础配置**、**数据源与查询**、**告警判定**、**检测频率 & 生效时间**、**事件配置**，自上而下排列，在一个页面内滚动填写即可，不再使用分步骤向导。
 
 ### 基础配置
 
@@ -79,10 +79,16 @@ keywords: ["入门指南", "monitedge", "数据源", "告警规则", "快速开
 | **规则名称** | 告警规则的名称，不支持引用变量（固定名称便于过滤、聚合操作）。同一分组内必须唯一；导入、编辑或移动规则时如与目标分组中已有规则重名，操作会失败 |
 | **附加标签** | 类似 Prometheus 中的 `labels`，会附加到所有告警事件上，便于过滤、路由、抑制 |
 
-### 数据源选择
+### 数据源与查询
+
+区块 2 由两段组成：**数据源** 决定规则生效到哪些数据源，**查询语句** 决定从数据源里查什么、怎么查。
+
+#### 数据源
 
 ![数据源选择](https://docs-cdn.flashcat.cloud/imges/mon/9971af45b4bc19bfe807898bf1bf10a0.png)
 
+子标题右侧是一个说明绑定生效范围的提示图标，以及 **前往数据源管理页面** 入口——它在新标签页打开，避免当前表单里未保存的修改被丢弃。
+
 先选择 **数据源类型**。这里只会列出**已经配置过至少一个数据源**的类型——没有配置过的类型不会出现，避免你选中一个查不到任何数据源的类型。编辑一条已有规则时，它当前使用的类型始终可见，即使该类型下的数据源后来被删光了。
 
 如果列表为空（提示「暂无可用数据源」），说明当前账户还没有配置任何数据源，可以点击 **前往数据源管理页面** 先创建；如果只是当前选中的类型没有可用数据源，页面会提示「当前数据源类型暂无可用数据源，请先创建数据源或切换类型」。类型列表加载失败时会显示 **重新加载** 按钮。
@@ -98,11 +104,11 @@ keywords: ["入门指南", "monitedge", "数据源", "告警规则", "快速开
 如果对规则绑定的稳定性要求高（避免数据源改名导致规则失效），建议使用精确匹配。详情参见[数据源管理](/zh/monitors/data-sources/data-sources)。
 </Tip>
 
-### 查询检测方式
+#### 查询语句
 
-![查询检测方式](https://docs-cdn.flashcat.cloud/imges/mon/4e38b46952d6cbbfb97c2d28843dcdbe.png)
+![查询语句](https://docs-cdn.flashcat.cloud/imges/mon/4e38b46952d6cbbfb97c2d28843dcdbe.png)
 
-配置如何查询数据源及如何判定告警条件。请阅读页面上 **查询检测方式** 右侧的使用说明。
+在**查询语句**子标题下方配置查询类型与查询语句本身。子标题右侧是 **使用说明** 入口，打开标题同为「查询语句」的抽屉，里面是查询语句的写法说明。表格型查询的值字段、标签字段与附加信息如何映射，详见[查询结果字段映射](/zh/monitors/alert-rules/query-result-fields)。
 
 #### AI 查询助手
 
@@ -112,9 +118,56 @@ keywords: ["入门指南", "monitedge", "数据源", "告警规则", "快速开
 - 可用的位置包括主查询、阈值判定与数据存在模式的恢复查询、关联查询、查询预览弹窗，以及实体树的规则 PromQL 与实体类别的发现 PromQL。在实体树中，助手只回填查询语句，不会切换数据源
 - 回填只改当前表单，不会自动保存规则；保存前请确认语句与告警阈值是否匹配
 
+### 告警判定
+
+区块 3 提供三种检测方式，以页签形式呈现：**阈值判定**、**数据缺失**、**数据存在**。每个页签标题右侧有一个启用开关，已启用的页签标题后会显示一个对勾标记。
+
+| 页签 | 判定什么 |
+|------|----------|
+| **阈值判定** | 按级别填写阈值表达式，满足条件并达到触发次数后，产生对应级别的告警。高一级别的阈值触发后不再校验低级别的阈值；启用本页签时 Critical、Warning、Info 至少要填写一项 |
+| **数据缺失** | 按「之前查到过数据，现在查不到了」或「所有查询均无返回数据」判定，两张卡片可以分别启用 |
+| **数据存在** | 查询到数据即视为满足条件，达到触发次数后按设定级别产生告警 |
+
+判定配置按卡片分组：除**数据缺失**页签外，每个页签分为「**告警触发**」和「**告警恢复**」两张卡片；**数据缺失**页签把两者合并成一张「**触发与恢复条件**」卡片，其配置作用于该页签内所有已启用的条件。卡片内各行含义如下：
+
+| 字段 | 说明 |
+|------|------|
+| **触发方式** | `连续命中` 或 `累计命中`，两者的区别见下一节 |
+| **触发条件** | 触发方式对应的判定句子。**阈值判定**页签下，级别表达式行（`Critical` / `Warning` / `Info`）排在触发方式上方，就是这张卡片的触发条件本体 |
+| **告警级别** | `Critical`、`Warning`、`Info` 三选一，默认 `Critical`。**阈值判定**页签下没有这一行——级别由命中的表达式行决定；**数据存在**与**数据缺失**页签下按条件单独设置 |
+| **恢复方式** | 位于「告警恢复」卡片中；**数据缺失**页签下按条件单独设置（见本节末尾） |
+| **恢复条件** | **N 次连续正常即恢复**，默认 1。设置为 1 时，只要有一次满足恢复条件就生成恢复事件；大于 1 时，要求连续多次都正常才生成恢复事件 |
+
+#### 触发方式：连续命中与累计命中
+
+| 触发方式 | 语义 | 触发条件句子 |
+|---------|------|-------------|
+| **连续命中**（默认） | 连续满足条件达到设定次数才告警 | 连续 N 次检测都满足条件才告警，N 即**命中次数**，默认 3 |
+| **累计命中** | 最近几次检测中，满足条件的次数达标即可，无需连续 | 最近 M 次检测中，有 N 次满足条件就告警，M 即**检测次数**，切到累计命中时默认取 `max(命中次数, 5)` |
+
+- **累计命中**下，命中次数不能大于检测次数，检测次数不能小于命中次数；命中次数和检测次数都不能超过 10000，超出会直接报校验错误，而不是被自动截断为上限值
+- 两种方式互斥：切回**连续命中**后，检测次数不再随规则提交（服务端按该字段是否存在区分两种模式），因此「最近 M 次」的语义不会残留
+- 对应的规则字段：命中次数 `alerting_check_times`、检测次数 `alerting_window_size`、恢复条件 `recovery_check_times`
+
+<Note>
+**累计命中需要告警引擎 ≥ `v0.69.0`。** 选中**累计命中**时，选项旁会显示「支持 v0.69.0+ 版本」徽章；低于该版本的引擎会退化为按连续命中执行，可能延迟或漏报告警，但不会比新语义更早触发。
+</Note>
+
+#### 告警恢复
+
+恢复方式的可选项由检测方式决定：
+
+| 页签 | 恢复方式 |
+|------|---------|
+| **阈值判定** | `未触发任一阈值就算恢复`（默认）、`结果满足条件才算恢复`（需要额外填写恢复表达式）、`表达式查到数据就算恢复`（需要填写恢复查询语句）、`告警保持活动，直到用户手工关闭` |
+| **数据存在** | `查询检测查不到数据即恢复`（默认）、`恢复检测查到数据才恢复`（需要填写恢复查询语句）、`告警保持活动，直到用户手工关闭` |
+| **数据缺失** | `所有查询均无返回数据时告警` 的恢复方式固定为「任一查询重新查到数据后自动恢复」；`之前查到过数据，现在查不到了，就告警` 可选择 `数据重新出现后自动结束`（默认）、`数据恢复或超时后自动结束`（需要填写**自动关闭时间**，单位为秒、最小 1）、`仅允许手工关闭` |
+
 ### 检测频率与生效时间
 
-该区块默认折叠，只显示一行摘要，格式为「检测频率 · 规则时区 · 生效时间」，例如 `@every 15s · Asia/Shanghai · 全天生效`；点击右侧的「展开」按钮可修改配置，修改完再点「收起」重新折叠。点击保存时，如果检测频率、规则时区、生效时间或查询时间偏移存在校验错误，该区块会自动展开，并滚动定位到第一个错误项。
+该区块是常显区块：没有一行摘要，也没有「展开/收起」按钮，检测频率、查询时间偏移、规则时区、生效时间四个配置项直接铺在区块里。
+
+点击保存时，如果某个字段校验失败，页面会滚动定位到第一个出错的字段并高亮它：错误落在**告警判定**的某个页签里时会先切到该页签，落在**事件配置**的「自定义字段与关联查询」里时会先展开该区域。
 
 ![检测频率 & 生效时间](https://docs-cdn.flashcat.cloud/imges/mon/0980d71a653985a1706243fc6795685e.png)
 
@@ -144,6 +197,8 @@ keywords: ["入门指南", "monitedge", "数据源", "告警规则", "快速开
 
 ### 事件配置
 
+区块 5 的顺序是：「自定义字段与关联查询」（一个默认折叠的区域，标题右侧显示「展开 / 收起」，折叠时摘要行显示已配置的自定义字段与关联查询数量，都没有配置时改显示一行提示文案）、备注描述，以及重复发送配置。
+
 | 配置项 | 说明 |
 |--------|------|
 | **自定义字段** | 类似 Prometheus 中的 `annotations`，可附加仪表盘 URL、SOP URL 等 |
diff --git a/zh/on-call/advanced/war-room.mdx b/zh/on-call/advanced/war-room.mdx
index cf557be4..99c53da1 100644
--- a/zh/on-call/advanced/war-room.mdx
+++ b/zh/on-call/advanced/war-room.mdx
@@ -62,7 +62,7 @@ Flashduty On-call 作战室（War Room）是专为故障应急响应设计的自
         <Frame caption="作战室内信息自动同步">
           ![应用内创建作战室](https://docs-cdn.flashcat.cloud/images/gif/war-room-create-app.gif)
         </Frame>
-        使用飞书应用通知时，故障卡片底部的 **👥 创建作战室** 按钮由[通知模板](/zh/on-call/configuration/templates)中的开关控制：在 **模板管理** 中编辑飞书应用模板，于 **附加信息** 页签的卡片字段面板中开启 **创建作战室**（默认关闭），满足建群条件时卡片底部才会展示该按钮；卡片底部的 **更多操作** 已改为下拉菜单（自定义操作、暂缓、取消认领），作战室不再位于其中。
+        使用飞书 / 钉钉 / Slack 应用通知时，故障卡片底部的 **👥 创建作战室** 按钮由[通知模板](/zh/on-call/configuration/templates)中的开关控制：在 **模板管理** 中编辑对应渠道的应用模板，于 **附加信息** 页签的卡片字段面板中开启 **创建作战室**（默认关闭），满足建群条件时卡片底部才会展示该按钮；卡片底部的 **更多操作** 已改为下拉菜单（自定义操作、暂缓、取消认领），作战室不再位于其中。
       </Tab>
       <Tab title="移动端 App">
         打开 Flashduty App，进入故障详情页，点击底部操作栏的 **⋯** 按钮打开 **更多操作**，选择 **创建作战室**，在面板中确认处理人员名单、选择关注人员后提交即可创建。当故障已存在作战室或故障已关闭时，该入口会被隐藏；当故障没有处理人员时，入口禁用并提示「当前故障没有处理人员，无法创建作战室」。
diff --git a/zh/on-call/channel/escalation-rule.mdx b/zh/on-call/channel/escalation-rule.mdx
index 7eb923f5..e531cbee 100644
--- a/zh/on-call/channel/escalation-rule.mdx
+++ b/zh/on-call/channel/escalation-rule.mdx
@@ -89,7 +89,7 @@ src="https://download.flashcat.cloud/flashduty/video/escalate-rule.mp4"
   <Tab title="群聊（触达群组）">
     发送到即时通讯软件的群组中，支持 @ 提到相关人员。
 
-    - **IM 应用群**：支持飞书、钉钉、企业微信、Slack、Microsoft Teams 群（其中企业微信仅存量配置可用，新建策略不可选），需先完成 [IM 集成](/zh/on-call/integration/instant-messaging/lark)。群聊选择器会自动排除平台创建的群聊（如故障作战室，提示「请选择…群聊（不含故障作战室）」），已失效的群聊目标显示为「群聊不存在」并可移除
+    - **IM 应用群**：支持飞书、钉钉、企业微信、Slack、Microsoft Teams 群（其中企业微信仅存量配置可用，新建策略不可选），需先完成 [IM 集成](/zh/on-call/integration/instant-messaging/lark)。应用下拉会保留已停用的 IM 应用并标注「（已停用）」，已停用应用不可选择为通知目标，需先在集成中心重新启用该应用。群聊选择器会自动排除平台创建的群聊（如故障作战室，提示「请选择…群聊（不含故障作战室）」），已失效的群聊目标显示为「群聊不存在」并可移除
     - **群机器人**：支持飞书、钉钉、企业微信、Slack、Telegram、Zoom 等 Webhook 机器人。其中 Telegram 需要配置 Webhook 通知地址和群聊 ID（Chat Ids），Zoom 需要配置 Webhook 地址和 Verify Token，并支持开启 @ 提醒功能。详见 [通知渠道配置](/zh/on-call/configuration/notifications)
 
     <Note>
diff --git a/zh/on-call/configuration/schedule.mdx b/zh/on-call/configuration/schedule.mdx
index 09148d63..429f9867 100644
--- a/zh/on-call/configuration/schedule.mdx
+++ b/zh/on-call/configuration/schedule.mdx
@@ -65,7 +65,7 @@ Flashduty On-call 提供极具灵活性的值班编排能力，支持按天、
       - **遵循个人偏好**：每个值班人员按各自在个人账户中配置的通知渠道接收通知
       - **遵循统一设置**：由管理员统一选择通知渠道（短信、邮件，以及已集成的 IM 应用）
     - **群聊渠道**：将通知发送到群聊中，支持以下平台：
-      - 飞书应用、钉钉应用、Slack 应用（通过已集成的 IM 应用选择群聊；选择器会自动排除故障作战室等平台创建的群聊，已失效的群聊显示「群聊不存在」并可移除）
+      - 飞书应用、钉钉应用、Slack 应用（通过已集成的 IM 应用选择群聊；应用下拉会保留已停用的 IM 应用并标注「（已停用）」，已停用应用不可选择为通知目标，需先在集成中心重新启用；选择器会自动排除故障作战室等平台创建的群聊，已失效的群聊显示「群聊不存在」并可移除）
       - 企业微信机器人、钉钉机器人、飞书机器人（通过 Webhook 地址发送）
       - Slack 机器人、Telegram 机器人、Zoom 机器人
 
diff --git a/zh/on-call/configuration/templates.mdx b/zh/on-call/configuration/templates.mdx
index bdc623c8..9b0e3f8a 100644
--- a/zh/on-call/configuration/templates.mdx
+++ b/zh/on-call/configuration/templates.mdx
@@ -394,9 +394,9 @@ keywords: ["通知模板", "模板配置", "消息格式", "模板变量", "通
 
 编辑飞书应用模板时，**正文内容** 旁的 **附加信息** 页签提供卡片字段开关面板（面板提示「以下内容由系统渲染，可通过开关控制是否展示在消息底部。」），用于控制协作空间、严重程度、处理人员、故障详情按钮、AI 分析等系统字段是否渲染在卡片底部。
 
-其中 **创建作战室** 是飞书应用专属开关（对应字段 `feishu_app_war_room_enabled`，默认**关闭**，开启后需保存模板生效）：
+其中 **创建作战室** 开关在飞书应用、钉钉应用、Slack 应用模板中均可配置（分别对应字段 `feishu_app_war_room_enabled`、`dingtalk_app_war_room_enabled`、`slack_app_war_room_enabled`，默认**关闭**，开启后需保存模板生效）。开关文案即 **创建作战室**，面板中的说明为「开启后，满足建群条件时，在卡片底部展示独立的创建作战室按钮。」
 
-- **开启**：故障未关闭、未创建作战室且存在处理人员时，飞书应用故障卡片底部会展示独立的 **👥 创建作战室** 按钮，点击按钮即可发起建群
+- **开启**：故障未关闭、未创建作战室且存在处理人员时，对应渠道的故障卡片底部会展示独立的 **👥 创建作战室** 按钮，点击按钮即可发起建群
 - **关闭**：卡片底部不展示该按钮
 
 同时，飞书应用卡片底部的操作区已调整：**更多操作**（占位文案即「更多操作」）改为下拉选择菜单，菜单内为自定义操作、暂缓时长与取消认领等选项，作战室按钮不再位于该菜单中。
@@ -421,6 +421,8 @@ keywords: ["通知模板", "模板配置", "消息格式", "模板变量", "通
 <Frame caption="钉钉应用通知效果">
 <img src="https://download.flashcat.cloud/flashduty/changelog/20230720/dingtalk_app_render.png" alt="钉钉应用通知" />
 </Frame>
+
+与飞书应用一致，**正文内容** 旁的 **附加信息** 页签提供卡片字段开关面板（面板提示「以下内容由系统渲染，可通过开关控制是否展示在消息底部。」），用于控制协作空间、暂缓截止时间、严重程度、聚合告警数、处理人员、详情按钮、AI 分析等系统字段是否渲染在卡片底部；钉钉应用同样提供 **创建作战室** 开关（对应字段 `dingtalk_app_war_room_enabled`，默认**关闭**，开启后需保存模板生效）。
 </Tab>
 
 <Tab title="企业微信应用">
@@ -474,6 +476,8 @@ keywords: ["通知模板", "模板配置", "消息格式", "模板变量", "通
 <Frame caption="Slack 应用通知效果">
 <img src="https://download.flashcat.cloud/flashduty/integration/slack/slack_app_message.png" alt="Slack 应用通知" />
 </Frame>
+
+与飞书应用一致，**正文内容** 旁的 **附加信息** 页签提供卡片字段开关面板（面板提示「以下内容由系统渲染，可通过开关控制是否展示在消息底部。」），用于控制协作空间、暂缓截止时间、严重程度、聚合告警数、处理人员、详情按钮、AI 分析等系统字段是否渲染在卡片底部；Slack 应用同样提供 **创建作战室** 开关（对应字段 `slack_app_war_room_enabled`，默认**关闭**，开启后需保存模板生效）。
 </Tab>
 
 <Tab title="Microsoft Teams">
diff --git a/zh/on-call/incident/escalate-dispatch-incident.mdx b/zh/on-call/incident/escalate-dispatch-incident.mdx
index 1ab7b44b..85b50df4 100644
--- a/zh/on-call/incident/escalate-dispatch-incident.mdx
+++ b/zh/on-call/incident/escalate-dispatch-incident.mdx
@@ -35,7 +35,7 @@ keywords: ["故障升级", "重新分派", "处理人", "故障分派", "升级
 </Frame>
 
 <Tip>
-以上操作在 [Flashduty App](/zh/on-call/quickstart/mobile-app) 中同样可用：**重新分派** 和 **升级** 位于故障详情页的 **更多操作（⋮）** 中；**添加处理人** 位于故障详情页的 **处理人员** 区域。
+以上操作在 [Flashduty App](/zh/on-call/quickstart/mobile-app) 中同样可用：**重新分派** 和 **升级** 位于故障详情页的 **更多操作（⋮）** 中；**添加处理人** 位于故障详情页的 **处理人员** 面板。故障 **已关闭** 时，App 上的 **添加处理人** 与 **重新分派** 一并隐藏——此时 **处理人员** 面板退化为只读名单，谁在何时认领仍然查得到。
 </Tip>
 
 ## 常见问题
diff --git a/zh/on-call/incident/search-view-incident.mdx b/zh/on-call/incident/search-view-incident.mdx
index 268ada28..8b9541d2 100644
--- a/zh/on-call/incident/search-view-incident.mdx
+++ b/zh/on-call/incident/search-view-incident.mdx
@@ -181,6 +181,15 @@ Flashduty On-call 提供各种维度的筛选能力，并给您足够多的灵
 | `i_wi_auto_converted` | 将 N 个未完成行动项转为跟进项：标题、标题…（故障关闭时批量转换，一条记录汇总全部条目） |
 | `i_wi_deleted` | 删除了行动项 / 删除了跟进项 |
 
+### AI SRE 代操作记录
+
+AI SRE 代某位成员执行的动作（例如[自动化规则](/zh/ai-sre/automations)跑完一轮排查后把结论写回故障）会以 **联合署名** 记入时间线：署名文案为 `{{name}} 和 AI SRE`，两个名字并列同权，因为 AI SRE 使用的是该成员的身份和权限。这类记录在后端以 `via: ai_sre` 标记。
+
+- **署名悬浮卡**：把鼠标移到署名中的 **AI SRE** 上会弹出悬浮卡，写明「以 `{{name}}` 的身份和权限执行」，并提供 **接续对话** 按钮，点击后在 AI SRE 面板中打开当时那次会话
+- **常显入口**：每条 AI 代操作记录右侧还常驻一个带 ↗ 图标的 **接续对话** 入口，无需悬停即可直接进入对应会话；一个故障可能包含多场 AI 会话，因此入口挂在每一条记录上，而不是故障级的总入口
+
+两类入口都需要账户启用 AI SRE 且当前成员拥有 `AiSreChatVisit` 权限。会话为个人会话（仅创建者可见）或已失效时，常显入口不渲染，悬浮卡则改为显示「该会话仅创建者可见或已失效」；这条记录没有关联会话时，悬浮卡显示「该操作没有关联到会话」。
+
 ### 时间线评论
 
 时间线 Tab 顶部提供了一个 Markdown 评论框，支持以下能力：
diff --git a/zh/on-call/integration/alert-integration/alert-sources/aliyun-dataworks-op.mdx b/zh/on-call/integration/alert-integration/alert-sources/aliyun-dataworks-op.mdx
new file mode 100644
index 00000000..6088caf0
--- /dev/null
+++ b/zh/on-call/integration/alert-integration/alert-sources/aliyun-dataworks-op.mdx
@@ -0,0 +1,170 @@
+---
+title: "DataWorks 运维中心集成"
+description: "通过自定义 Webhook 的方式同步阿里云 DataWorks 智能监控（运维中心）告警事件到 Flashduty On-call，实现告警事件自动化降噪处理"
+keywords: ["告警集成", "阿里云 DataWorks 集成", "DataWorks 智能监控", "运维中心", "监控告警", "数据接入"]
+---
+
+
+<div className="hide">
+
+## 在 Flashduty On-call
+---
+您可通过以下2种方式，获取一个集成推送地址，任选其一即可。
+
+### 使用专属集成
+
+当您不需要将告警事件路由到不同的协作空间，优先选择此方式，更简单。
+
+<AccordionGroup>
+  <Accordion title="展开">
+  
+  1. 进入 Flashduty 控制台，选择 **协作空间**，进入某个空间的详情页面
+  2. 选择 **集成数据** tab，点击 **添加一个集成**，进入添加集成页面
+  3. 选择 **DataWorks 运维中心** 集成，点击 **保存**，生成卡片。
+  4. 点击生成的卡片，可以查看到 **推送地址**，复制备用，完成。
+  
+    
+</Accordion>
+</AccordionGroup>
+
+### 使用共享集成
+
+当您需要根据告警事件的 Payload 信息，将告警路由到不同的协作空间，优先选择此方式。
+
+<AccordionGroup>
+  <Accordion title="展开">
+  
+  1. 进入 Flashduty 控制台，选择 **集成中心=>告警事件**，进入集成选择页面。
+  2. 选择 **DataWorks 运维中心** 集成：
+        - **集成名称**：为当前集成定义一个名称。
+  3. 配置默认路由，并选择对应的协作空间（集成创建后可以前往 `路由` 进行更多路由规则的配置）。
+  4. 点击 **保存** 后，复制当前页面的新生成的 **推送地址** 备用。
+  5. 完成。
+    
+</Accordion>
+</AccordionGroup>
+</div>
+
+## 在阿里云 DataWorks
+---
+**步骤 1：创建自定义 Webhook**
+
+<div className="md-block">
+
+1. 登录阿里云控制台，进入 **DataWorks** 产品
+2. 进入 **数据开发（DataStudio）** 或 **运维中心**，打开 **智能监控** 页面
+3. 进入 **报警接收配置**（或 **自定义 webhook** 配置入口），新建一个 Webhook
+4. `请求地址` 填写 Flashduty 集成的推送地址（上一步复制），`请求方法` 为 POST
+5. 保存后，可点击 **发送测试消息**，DataWorks 会推送一条连通性测试消息（`message.content`），Flashduty 收到后返回成功但不产生告警事件
+
+</div>
+
+**步骤 2：在监控规则中启用 Webhook**
+
+<div className="md-block">
+
+1. 进入 **智能监控** 的 **自定义规则**（周期实例状态告警、资源组告警）、**基线管理** 或 **事件管理** 页面
+2. 创建或编辑规则，在 **报警方式** 中勾选上一步创建的自定义 Webhook
+3. 保存规则，完成。此后该规则触发的告警会实时推送到 Flashduty
+
+</div>
+
+## 支持的告警类型
+---
+<div className="md-block">
+
+DataWorks 智能监控自定义 Webhook 推送的消息统一包裹在 `message` 字段中，通过 `message.title` 区分类型，本集成支持以下三类告警：
+
+| message.title | 告警类型 | 说明 |
+| ------------- | -------- | ---- |
+| `DataWorks_Remind` | 自定义告警 | 周期实例状态告警（remind_unit 为 Task、Baseline、Project、BizProcess）与资源组告警（ScheduleResourceGroup、DiResourceGroup） |
+| `DataWorks_Baseline_Alert` | 基线告警 | 基线预警（dangerous）与破线（overSla） |
+| `DataWorks_Event_Remind` | 事件告警 | 任务出错（ERROR）与变慢（SLOW） |
+
+连通性测试消息（`message.content`）仅用于验证推送地址，不会产生告警事件。
+
+</div>
+
+## 严重程度对照
+---
+<div className="md-block">
+
+DataWorks 自定义告警 `remind_type` 到 Flashduty 告警等级（Severity）映射关系：
+
+| DataWorks remind_type | Flashduty | 状态 |
+| --------------------- | --------- | ---- |
+| error（出错） | Critical | 严重 |
+| exhausted error（自动重跑仍出错） | Critical | 严重 |
+| uncompleted（未完成） | Warning | 警告 |
+| cycle uncompleted（周期未完成） | Warning | 警告 |
+| run over time（运行超时） | Warning | 警告 |
+| resGroup use ratio（资源组利用率） | Warning | 警告 |
+| the number of waiting task in resGroup（资源组等待资源实例数） | Warning | 警告 |
+| completed（完成） | Info | 提醒 |
+| 空值或未知值 | Warning | 警告 |
+
+基线告警 `status` 映射关系：
+
+| DataWorks status | Flashduty | 状态 |
+| ---------------- | --------- | ---- |
+| overSla（破线） | Critical | 严重 |
+| dangerous（预警） | Warning | 警告 |
+| 空值或未知值 | Warning | 警告 |
+
+事件告警 `event_type` 映射关系：
+
+| DataWorks event_type | Flashduty | 状态 |
+| -------------------- | --------- | ---- |
+| ERROR（出错） | Critical | 严重 |
+| SLOW（变慢） | Warning | 警告 |
+| 空值或未知值 | Warning | 警告 |
+
+</div>
+
+## Alert Key 与告警合并
+---
+<div className="md-block">
+
+DataWorks 智能监控 Webhook 属于**一次性事件**（one-shot）：官方协议只定义告警通知，**不恢复**、无更新语义，也没有提供厂商级别的去重 ID 或指纹字段。因此本集成不会自动恢复（关闭）任何告警，所有事件均以触发状态投递。
+
+每次 webhook 投递都会生成一个全新的随机 UUID 作为 Alert Key，即每条推送都会创建一条独立的告警事件，重复触发不会自动合并。如需降噪，请在 Flashduty 中配置告警聚合或收敛策略。
+
+</div>
+
+## 字段标签对照
+---
+<div className="md-block">
+
+推送消息中的主要字段会以标签（Labels）形式保留在告警事件中，可用于路由、静默与模板渲染：
+
+| 标签 | 来源字段 | 说明 |
+| ---- | -------- | ---- |
+| alert_type | title | 告警类型（DataWorks_Remind 等） |
+| remind_name | remind_name | 规则名称 |
+| remind_unit | remind_unit | 监控粒度（Task、ScheduleResourceGroup 等） |
+| remind_type | remind_type | 触发条件原始值 |
+| occur_time | occur_time | 发生时间原文 |
+| remind_founder | remind_founder | 规则创建人 |
+| more_information | more_information | 运维中心周期实例链接 |
+| task_size / number_of_alerts | 同名字段 | 任务数量 / 第几次告警 |
+| node_id_list / node_name_list / node_owner_list | 同名字段 | 节点 ID / 名称 / 责任人列表（英文逗号分隔，最多 5 个） |
+| resource_group_name / threshold / duration | 同名字段 | 资源组名 / 阈值 / 持续时间（分钟），资源组监控特有 |
+| baseline_name / baseline_owners | 同名字段 | 基线名 / 基线责任人 |
+| cycle_number / key_instance / sla_time / buffer / status | 同名字段 | 周期号 / 关键实例 / 承诺时间 / 余量（分钟）/ 基线状态 |
+| task_name / task_owner_name / event_type / event_name | 同名字段 | 任务名 / 责任人 / 事件类型 / 事件名称 |
+
+</div>
+
+## 常见问题
+---
+<div className="md-block">
+
+**为什么告警不会自动恢复？**
+
+DataWorks 智能监控 Webhook 协议没有定义恢复（resolve）消息，属于一次性通知。如需关闭告警，请在 Flashduty 控制台手动处理，或为规则配置告警收敛策略。
+
+**发送测试消息后为什么看不到告警？**
+
+DataWorks 的连通性测试消息（`message.content`）仅用于验证推送地址可达，Flashduty 收到后返回成功但不生成告警事件。请通过真实触发规则来验证端到端链路。
+
+</div>
diff --git a/zh/on-call/integration/alert-integration/alert-sources/new-relic.mdx b/zh/on-call/integration/alert-integration/alert-sources/new-relic.mdx
new file mode 100644
index 00000000..35e07691
--- /dev/null
+++ b/zh/on-call/integration/alert-integration/alert-sources/new-relic.mdx
@@ -0,0 +1,154 @@
+---
+title: "New Relic 告警集成"
+description: "通过 Workflow Webhook 将 New Relic Issue 同步到 Flashduty On-call，并关联激活、更新和关闭事件。"
+keywords: ["告警集成", "New Relic", "Workflow", "Webhook", "Issue"]
+---
+
+通过 New Relic Workflow Webhook 将 Issue 同步到 Flashduty On-call。一个 New Relic Issue 对应一条 Flashduty 告警；同一 Issue 后续发生等级变化、Alert Event 加入或关闭、Issue 合并、关闭时，会继续更新这条告警。
+
+<div className="hide">
+
+## 在 Flashduty On-call
+---
+您可通过以下两种方式获取集成推送地址，任选其一即可。
+
+### 使用专属集成
+
+1. 进入 Flashduty 控制台，选择 **协作空间**，打开一个协作空间
+2. 选择 **集成数据**，点击 **添加一个集成**
+3. 选择 **New Relic**，点击 **保存**
+4. 打开生成的集成卡片，复制 **推送地址**
+
+### 使用共享集成
+
+1. 进入 Flashduty 控制台，选择 **集成中心 → 告警事件**
+2. 选择 **New Relic**，填写集成名称
+3. 配置默认路由并选择协作空间；创建后可在 **路由** 中增加更多规则
+4. 点击 **保存**，复制生成的 **推送地址**
+
+</div>
+
+## 在 New Relic 中配置
+---
+
+<Steps>
+<Step title="创建 Webhook Destination">
+
+1. 登录 New Relic，进入 **Alerts → Enrich and Notify → Destinations**
+2. 创建一个 **Webhook** Destination
+3. 名称可填写 `Flashduty`
+4. 将 Flashduty 集成的完整推送地址粘贴到 Endpoint URL
+
+</Step>
+
+<Step title="创建 Workflow">
+
+1. 进入 **Alerts → Enrich and Notify → Workflows**，点击创建 Workflow
+2. 设置 Issue 过滤条件，选择需要发送到 Flashduty 的 Policy、Condition、实体或标签
+3. 添加刚创建的 Webhook Destination
+4. 在通知触发器中至少启用 **Activated** 和 **Closed**
+5. 建议同时启用 **Priority changed** 和 **Other updates**，以同步等级变化、Alert Event 增减及 Issue 合并后的最新快照
+
+</Step>
+
+<Step title="配置 Payload">
+
+将 Webhook 的自定义 Payload 替换为：
+
+```json
+{
+  "issue_id": "{{issueId}}",
+  "issue_url": {{json issuePageUrl}},
+  "title": {{json issueTitle}},
+  "description": {{json accumulations.conditionDescription.[0]}},
+  "priority": "{{priority}}",
+  "state": "{{state}}",
+  "trigger_event": "{{triggerEvent}}",
+  "is_correlated": {{isCorrelated}},
+  "account_id": {{nrAccountId}},
+  "incident_ids": {{json incidentIds}},
+  "sources": {{json accumulations.sources}},
+  "policy_names": {{json accumulations.policyName}},
+  "condition_names": {{json accumulations.conditionName}},
+  "entity_names": {{json entitiesData.names}},
+  "entity_ids": {{json entitiesData.ids}},
+  "workflow_name": {{json workflowName}}
+}
+```
+
+<Warning>
+请保留 `issue_id`、`state` 和 `priority`。缺少 `issue_id` 时 Flashduty 会拒绝请求，因为随机 Key 无法保证后续更新和关闭命中同一条告警。
+</Warning>
+
+</Step>
+
+<Step title="验证生命周期">
+
+让 Alert Condition 进入阈值，确认 Flashduty 收到活动告警；提高优先级或产生新的 Alert Event，确认同一条告警收到更新；最后让 Issue 关闭，确认原告警恢复。
+
+New Relic 的测试通知只能验证 Webhook 可达。Alert Key、更新和恢复必须通过真实 Issue 生命周期验证。
+
+</Step>
+</Steps>
+
+## Alert Key 与 Issue 合并
+---
+
+Flashduty 直接使用 `issue_id`（New Relic 变量 `issueId`）作为 Alert Key。标题、优先级、Policy、Condition、实体和 `incident_ids` 的变化都不会改变 Alert Key。
+
+`incident_ids` 是当前 Issue 聚合的 Alert Event ID 列表，只作为详情标签。它不能作为 Alert Key，否则一个 Alert Event 加入、关闭或相关性计算变化时会拆出新告警。
+
+当 `trigger_event=MERGE_REQUEST` 时，Flashduty 将请求视为合并后目标 Issue 的一次普通更新，并继续使用 Payload 中的 `issue_id`。当前版本不调用 Flashduty 内部的告警合并能力，也不会推断或关闭来源 Issue。
+
+## 状态和告警等级
+---
+
+恢复只根据 `state` 判断，与 `trigger_event` 和等级映射相互独立。
+
+| New Relic 值 | Flashduty 状态或等级 |
+| :--- | :--- |
+| `state = CLOSED` | 恢复 |
+| `state = CREATED`、`ACTIVATED` | 活动告警 |
+| `priority = CRITICAL` | Critical |
+| `priority = HIGH` | Warning |
+| `priority = MEDIUM`、`LOW` | Info |
+| `priority` 为空或未知 | Warning |
+
+New Relic 的 Warning 阈值会生成 `HIGH` 优先级 Alert Event，因此 `HIGH` 映射为 Flashduty Warning。如需其他映射，可通过[告警处理 Pipeline](/zh/on-call/integration/alert-integration/alert-pipelines)调整。
+
+## 增加自定义标签
+---
+
+如果需要传递更多 Workflow 变量，在默认 Payload 顶层增加 `custom_labels`：
+
+```json
+{
+  "issue_id": "{{issueId}}",
+  "title": {{json issueTitle}},
+  "priority": "{{priority}}",
+  "state": "{{state}}",
+  "custom_labels": {
+    "team": {{json accumulations.tag.team.[0]}},
+    "environment": {{json accumulations.tag.environment.[0]}},
+    "muting_state": "{{mutingState}}",
+    "open_alert_events": {{openIncidentsCount}}
+  }
+}
+```
+
+- `custom_labels` 最多包含 50 个条目，key 建议使用 snake_case
+- 字符串、数字、布尔值、数组和对象都可接收；数组和对象会保存为 JSON 字符串
+- 空值不会生成标签；基础字段优先，同名自定义标签不能覆盖基础标签
+- 单次请求包含基础标签在内，最多生成 50 个标签
+- 不要传递 API Key、Token、密码、Cookie 或其他敏感信息
+
+## 排查问题
+---
+
+- **只收到测试通知，真实告警没有通知**：确认 Workflow 已启用，并且过滤条件能够命中真实 Issue
+- **Flashduty 返回参数错误**：确认 Payload 是有效 JSON，且包含非空的 `issue_id` 和支持的 `state`
+- **告警没有恢复**：确认 Destination 启用了 **Closed**，关闭 Payload 仍携带与激活时相同的 `issue_id`
+- **等级或合并变化没有更新**：启用 **Priority changed** 和 **Other updates**
+- **部分列表为空**：不同 Condition 和 Issue 类型提供的上下文不同，Flashduty 会忽略空标签
+
+字段含义和可用变量请参阅 [New Relic Workflow variables](https://docs.newrelic.com/docs/alerts/get-notified/custom-variables-alert-event-workflows/)。
diff --git a/zh/on-call/integration/instant-messaging/dingtalk.mdx b/zh/on-call/integration/instant-messaging/dingtalk.mdx
index 36864aa6..3efa7055 100644
--- a/zh/on-call/integration/instant-messaging/dingtalk.mdx
+++ b/zh/on-call/integration/instant-messaging/dingtalk.mdx
@@ -213,10 +213,10 @@ keywords: ["钉钉", "即时消息", "告警通知", "IM集成", "钉钉机器
 
 ### AI SRE 控制项
 
-开启 **作战室** 后，配置页会显示以下 AI SRE 控制项，默认均为开启：
+在 **增强功能** 中配置以下 AI SRE 控制项，默认均为开启：
 
-- **自动发起 AI 故障分析**：作战室创建成功后，自动发起一次 AI 故障分析。
-- **允许群聊 @ AI SRE**：允许在此集成已接入的群聊中 @ AI SRE 发起对话；关闭后不会响应该入口。
+- **自动发起 AI 故障分析**：需先开启作战室才会出现；作战室创建成功后，自动发起一次 AI 故障分析。
+- **允许在 IM 中使用 AI SRE**：无需开启作战室即可配置。开启后，可在该集成接入的群聊中 @ AI SRE，或在机器人私聊中直接发起对话；关闭后这两个入口都不会触发 AI SRE 回复。
 
 如果账户尚未启用 AI SRE，以上配置暂不生效。
 
diff --git a/zh/on-call/integration/instant-messaging/lark.mdx b/zh/on-call/integration/instant-messaging/lark.mdx
index 6c1e62a5..e6201233 100644
--- a/zh/on-call/integration/instant-messaging/lark.mdx
+++ b/zh/on-call/integration/instant-messaging/lark.mdx
@@ -154,7 +154,7 @@ keywords: ["飞书", "Lark", "即时消息", "告警通知", "IM集成"]
 在 **增强功能** 中分别配置以下 AI SRE 控制项，默认均为开启：
 
 - **自动发起 AI 故障分析**：开启作战室后可配置；作战室创建成功后，自动发起一次 AI 故障分析。
-- **允许群聊 @ AI SRE**：无需开启作战室即可配置，允许在此集成已接入的群聊中 @ AI SRE 发起对话；关闭后不会响应该入口。
+- **允许在 IM 中使用 AI SRE**：无需开启作战室即可配置。开启后，可在该集成接入的群聊中 @ AI SRE，或在机器人私聊中直接发起对话；关闭后这两个入口都不会触发 AI SRE 回复。
 - **普通群聊中 AI SRE 使用话题回复**：无需开启作战室即可配置。开启后，普通群聊中的每个话题对应一个独立 Session；作战室仍直接在群内回复。
 
 如果账户尚未启用 AI SRE，以上配置暂不生效。
diff --git a/zh/on-call/integration/instant-messaging/slack.mdx b/zh/on-call/integration/instant-messaging/slack.mdx
index df790068..bdf5c3f3 100644
--- a/zh/on-call/integration/instant-messaging/slack.mdx
+++ b/zh/on-call/integration/instant-messaging/slack.mdx
@@ -102,7 +102,7 @@ keywords: ["Slack", "即时消息", "告警通知", "IM集成", "协作工具"]
 在 **增强功能** 中分别配置以下 AI SRE 控制项，默认均为开启：
 
 - **自动发起 AI 故障分析**：开启作战室后可配置；作战室创建成功后，自动发起一次 AI 故障分析。
-- **允许群聊 @ AI SRE 和 /fd 命令**：无需开启作战室即可配置，允许在此集成已接入的 Slack 群聊中 @ AI SRE 或使用 `/fd` 命令；关闭后两个入口都不会响应。
+- **允许在 IM 中使用 AI SRE**：无需开启作战室即可配置。开启后，可在已接入的 Slack 群聊中 @ AI SRE、使用 `/fd` 命令，或在机器人私聊中直接发起对话；关闭后这三种入口都不会触发 AI SRE 回复。
 - **普通群聊中 AI SRE 使用话题回复**：无需开启作战室即可配置。开启后，普通群聊中的每个话题对应一个独立 Session；作战室仍直接在群内回复。
 
 如果账户尚未启用 AI SRE，以上配置暂不生效。
diff --git a/zh/on-call/integration/instant-messaging/wecom.mdx b/zh/on-call/integration/instant-messaging/wecom.mdx
index 8fe55d5e..d492e893 100644
--- a/zh/on-call/integration/instant-messaging/wecom.mdx
+++ b/zh/on-call/integration/instant-messaging/wecom.mdx
@@ -120,16 +120,25 @@ Flashduty 作为企业微信服务商，为您提供 Flashduty 应用的长期
 
 ### AI SRE 控制项
 
-开启 **作战室** 后，配置页会显示以下 AI SRE 控制项，默认均为开启：
+以下 AI SRE 控制项在集成配置页面的 **增强功能** 模块中配置，默认均为开启：
 
-- **自动发起 AI 故障分析**：作战室创建成功后，自动发起一次 AI 故障分析。
-- **允许群聊 @ AI SRE**：允许在此集成已接入的群聊中 @ AI SRE 发起对话；关闭后不会响应该入口。
+- **自动发起 AI 故障分析**：需先开启作战室才会出现；作战室创建成功后，自动发起一次 AI 故障分析。
+- **允许在 IM 中使用 AI SRE**：无需开启作战室即可配置，同时控制该集成的群聊 @ AI SRE 与机器人私聊两个入口；关闭后对应入口不会触发 AI SRE 回复。
+
+企业微信的两种应用模式对 AI SRE 入口的支持不同。**允许在 IM 中使用 AI SRE** 在两种模式下都会显示，集成详情预览页也会展示其状态：
+
+| 应用模式 | 群聊 @ AI SRE | 机器人私聊 |
+| :--- | :--- | :--- |
+| **企业自建应用** | 支持 | 支持 |
+| **第三方应用** | 不支持，需切换为 **企业自建应用** 模式 | 支持 |
+
+第三方应用模式下，该开关的说明文案为「开启后，可在机器人私聊中直接发起对话；群聊 @ AI SRE 仅企业自建应用支持」。
 
 如果账户尚未启用 AI SRE，以上配置暂不生效。
 
 ## 四、配置 AISRE
 
-如需在企业微信中使用 AISRE，请先在 Flashduty 企业微信集成中开启 **作战室** 功能，然后额外创建一个智能机器人，并使用 API 模式接入 Flashduty。
+如需在企业微信中使用 AISRE，请在 Flashduty 企业微信集成中确认 **允许在 IM 中使用 AI SRE** 已开启（无需开启作战室），然后额外创建一个智能机器人，并使用 API 模式接入 Flashduty。智能机器人的凭据在 **企业自建应用** 模式的集成配置页面填写。
 
 1. 在企业微信应用左侧进入 **工作台**，找到 **智能机器人**，进入机器人管理页面。
 2. 创建一个新的智能机器人，创建方式选择 **手动创建**，然后选择 **使用 API 模式创建**。
diff --git a/zh/on-call/quickstart/faq.mdx b/zh/on-call/quickstart/faq.mdx
index 21645221..77ab54c8 100644
--- a/zh/on-call/quickstart/faq.mdx
+++ b/zh/on-call/quickstart/faq.mdx
@@ -216,7 +216,7 @@ keywords: ["常见问题", "FAQ", "On-call", "故障排查", "使用帮助"]
         <CardGroup cols={4}>
           <Card title="🇨🇳 中国大陆" icon="message" />
           <Card title="🇲🇴 中国澳门" icon="message" />
-          <Card title="🇹🇼 中国台湾" icon="message" />
+          <Card title="中国台湾" icon="message" />
           <Card title="🇭🇰 中国香港" icon="message" />
         </CardGroup>
       </Tab>
diff --git a/zh/on-call/quickstart/mobile-app.mdx b/zh/on-call/quickstart/mobile-app.mdx
index f9d342a6..d2ec040e 100644
--- a/zh/on-call/quickstart/mobile-app.mdx
+++ b/zh/on-call/quickstart/mobile-app.mdx
@@ -83,6 +83,8 @@ App 首页即故障列表，分为 **分派给我**（带故障数量角标）
 | **作战室** | 创建作战室、添加关注人员进入作战室、解散作战室（专业版，需启用支持作战室的 IM 集成） |
 | **Jira 与自定义操作** | 管理员在集成中配置的 Jira、ServiceNow 等自定义动作 |
 
+故障详情页的 **处理人员** 区域可打开处理人名单面板，面板底部的 **添加处理人** 用于追加处理人（新加入的人会被自动拉进作战室）。故障 **已关闭** 时，**添加处理人** 与面板内的 **重新分派** 一并隐藏，面板退化为只读名单。
+
 <Note>
 与控制台一致：如果管理员为认领、关闭等操作配置了自定义表单，在 App 上执行这些操作时同样需要先填写表单。
 </Note>
diff --git a/zh/rum/performance/diagnosis-optimization.mdx b/zh/rum/performance/diagnosis-optimization.mdx
index c43f04a1..0e3ba037 100644
--- a/zh/rum/performance/diagnosis-optimization.mdx
+++ b/zh/rum/performance/diagnosis-optimization.mdx
@@ -16,9 +16,20 @@ keywords: ["RUM", "性能监控", "用户监控", "前端监控"]
   <Step title="指标选择">
     选择页面和指标后，便可开始做性能数据洞察：
 
-    1. 点击指标卡片选择要洞察的指标（目前支持 LCP、FCP、INP、CLS）
+    1. 点击指标卡片选择要洞察的指标
     2. 在「显示筛选细分」中选择一个组
     3. 在不同的百分位数处评估指标（例如 p75 表示第 75 个百分位数值）
+
+    指标卡片按应用平台自适应展示，确保展示的是该平台真正上报的指标：
+
+    | 平台 | 指标卡片 |
+    |------|----------|
+    | **浏览器（Web）/ Electron（渲染进程）** | `LCP`、`FCP`、`INP`、`CLS` |
+    | **微信小程序** | `first_render`（首次渲染）、`lcp`、`fcp`、`onload_to_onshow`、`onshow_to_onready` |
+
+    <Note>
+    平台由应用本身的类型决定，无需手动切换。`first_render`、`onload_to_onshow`、`onshow_to_onready` 来自微信小程序 SDK：`first_render` 为首次渲染耗时，`onload_to_onshow` 与 `onshow_to_onready` 对应小程序页面生命周期的两段耗时，可用于排查页面冷启动慢的原因。切换应用后指标卡片会随新平台的指标集合刷新，树图（指标视角）的指标下拉同样只列出当前应用平台可选的指标。
+    </Note>
   </Step>
   <Step title="数据查看">
     您可通过调整数据聚合方式或修改筛选条件，查看该指标在不同条件下的数据表现情况，从而推进诊断优化工作。
diff --git a/zh/rum/performance/performance-analysis.mdx b/zh/rum/performance/performance-analysis.mdx
index c0302dcc..b4432031 100644
--- a/zh/rum/performance/performance-analysis.mdx
+++ b/zh/rum/performance/performance-analysis.mdx
@@ -25,7 +25,7 @@ keywords: ["RUM", "性能监控", "用户监控", "前端监控"]
   <Tab title="指标视角">
     切换至树状视图，可以从某个指标视角下查看待优化的资源列表：
 
-    - 切换不同的指标，查看其分布情况
+    - 切换不同的指标，查看其分布情况。下拉中只列出当前应用平台可选的指标（如微信小程序与浏览器 / Electron 的指标集不同），切换应用后选项随之变化
     - 查看「良好」、「较差」、「一般」分类下的资源分布与占比，快速定位问题资源
     - 点击区块所代表的页面后，可查看该页面下的指标详情，方便进一步做问题诊断