docs(api): daily audit 2026-09-30 — alert detail_url into the rendered on-call spec, RUM issue-detail team_id semantics

Two changes, both derived from the source repos at origin/main.

B. on-call AlertItem / AlertInfo gain `detail_url`.
   fc-event structs/alert.go:74-78 — `DetailUrl string `json:"detail_url,omitempty"``,
   filled at read time, empty when the deployment has no console base. The
   consolidated specs got the field on 2026-09-29 (4b9015a) but the per-module
   split files — the ones Mintlify renders — never did, so POST /alert/info
   documented no detail_url on the docs site.

A. POST /rum/issue/info documents that `team_id` is the application's current team.
   fc-rum cmd/server/controller/issue/info.go:221 `item.TeamID = application.TeamID`
   (PR #230, merge a190844, 2026-09-29). Issue rows keep the team recorded at
   creation (logic/transfer.go:55), which is what list and export still report.

Author: Flashduty AI-SRE

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

@@ -18334,6 +18334,10 @@
             },
             "description": "Attached images."
           },
+          "detail_url": {
+            "description": "Console URL of this alert (`{console}/alert/detail/{alert_id}`). Empty when the deployment has no console base configured.",
+            "type": "string"
+          },
           "data_source_name": {
             "type": "string",
             "description": "Deprecated. Use `integration_name`."
@@ -18516,6 +18520,10 @@
             },
             "description": "Images attached to the alert."
           },
+          "detail_url": {
+            "description": "Console URL of this alert (`{console}/alert/detail/{alert_id}`). Empty when the deployment has no console base configured.",
+            "type": "string"
+          },
           "data_source_name": {
             "type": "string",
             "description": "Deprecated: use `integration_name` instead.",

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

@@ -18334,6 +18334,10 @@
             },
             "description": "附加图片。"
           },
+          "detail_url": {
+            "description": "这条告警的控制台页面（`{控制台}/alert/detail/{alert_id}`）。部署没有配置控制台地址时为空。",
+            "type": "string"
+          },
           "data_source_name": {
             "type": "string",
             "description": "已废弃，请使用 `integration_name`。"
@@ -18516,6 +18520,10 @@
             },
             "description": "告警附加的图片。"
           },
+          "detail_url": {
+            "description": "这条告警的控制台页面（`{控制台}/alert/detail/{alert_id}`）。部署没有配置控制台地址时为空。",
+            "type": "string"
+          },
           "data_source_name": {
             "type": "string",
             "description": "已废弃：请使用 `integration_name`。",

api-reference/openapi.en.json

@@ -48845,7 +48845,7 @@
           "RUM/Issues"
         ],
         "x-mint": {
-          "content": "## Restrictions\n\n| Aspect | Value |\n| ------ | ----- |\n| Rate limits | **1,000 requests/minute**; **50 requests/second** per account |\n| Permissions | None — any valid `app_key` can call this operation |",
+          "content": "## Restrictions\n\n| Aspect | Value |\n| ------ | ----- |\n| Rate limits | **1,000 requests/minute**; **50 requests/second** per account |\n| Permissions | None — any valid `app_key` can call this operation |\n\n## Usage\n\n- `team_id` is the owning application's **current** team; `POST /rum/issue/list` and `POST /rum/issue/export` report the team recorded when the issue was first seen, which differs once the application moves to another team.",
           "href": "/en/api-reference/rum/issues/rum-issue-read-info",
           "metadata": {
             "sidebarTitle": "Get issue detail"

api-reference/openapi.zh.json

@@ -48845,7 +48845,7 @@
           "RUM/RUM 问题跟踪"
         ],
         "x-mint": {
-          "content": "## 限制说明\n\n| 项目 | 说明 |\n| ---- | ---- |\n| 速率限制 | 每个账户 **1,000 次/分钟**；**50 次/秒** |\n| 权限要求 | 无 —— 持有有效的 `app_key` 即可调用 |",
+          "content": "## 限制说明\n\n| 项目 | 说明 |\n| ---- | ---- |\n| 速率限制 | 每个账户 **1,000 次/分钟**；**50 次/秒** |\n| 权限要求 | 无 —— 持有有效的 `app_key` 即可调用 |\n\n## 使用说明\n\n- `team_id` 为所属应用**当前**的团队；`POST /rum/issue/list` 与 `POST /rum/issue/export` 返回 Issue 首次出现时记录的团队，应用转移到其他团队后两者不同。",
           "href": "/zh/api-reference/rum/issues/rum-issue-read-info",
           "metadata": {
             "sidebarTitle": "查看 Issue 详情"

api-reference/rum.openapi.en.json

@@ -6454,7 +6454,7 @@
           "RUM/Issues"
         ],
         "x-mint": {
-          "content": "## Restrictions\n\n| Aspect | Value |\n| ------ | ----- |\n| Rate limits | **1,000 requests/minute**; **50 requests/second** per account |\n| Permissions | None — any valid `app_key` can call this operation |",
+          "content": "## Restrictions\n\n| Aspect | Value |\n| ------ | ----- |\n| Rate limits | **1,000 requests/minute**; **50 requests/second** per account |\n| Permissions | None — any valid `app_key` can call this operation |\n\n## Usage\n\n- `team_id` is the owning application's **current** team; `POST /rum/issue/list` and `POST /rum/issue/export` report the team recorded when the issue was first seen, which differs once the application moves to another team.",
           "href": "/en/api-reference/rum/issues/rum-issue-read-info",
           "metadata": {
             "sidebarTitle": "Get issue detail"

api-reference/rum.openapi.zh.json

@@ -6454,7 +6454,7 @@
           "RUM/RUM 问题跟踪"
         ],
         "x-mint": {
-          "content": "## 限制说明\n\n| 项目 | 说明 |\n| ---- | ---- |\n| 速率限制 | 每个账户 **1,000 次/分钟**；**50 次/秒** |\n| 权限要求 | 无 —— 持有有效的 `app_key` 即可调用 |",
+          "content": "## 限制说明\n\n| 项目 | 说明 |\n| ---- | ---- |\n| 速率限制 | 每个账户 **1,000 次/分钟**；**50 次/秒** |\n| 权限要求 | 无 —— 持有有效的 `app_key` 即可调用 |\n\n## 使用说明\n\n- `team_id` 为所属应用**当前**的团队；`POST /rum/issue/list` 与 `POST /rum/issue/export` 返回 Issue 首次出现时记录的团队，应用转移到其他团队后两者不同。",
           "href": "/zh/api-reference/rum/issues/rum-issue-read-info",
           "metadata": {
             "sidebarTitle": "查看 Issue 详情"