@qingflow-tech/qingflow-cli 1.1.43-beta.3 → 1.1.43-beta.4

package/src/qingflow_mcp/builder_facade/schemas/app_form/v1alpha1/fields/text.json

@@ -1,15 +1,71 @@
 {
   "$defs": {
     "FieldCommon": {
+      "allOf": [
+        {
+          "if": {
+            "properties": {
+              "defaultType": {
+                "const": 2
+              }
+            },
+            "required": [
+              "defaultType"
+            ]
+          },
+          "then": {
+            "properties": {
+              "defaultValue": {
+                "type": "null"
+              }
+            }
+          }
+        },
+        {
+          "if": {
+            "properties": {
+              "defaultType": {
+                "const": 3
+              }
+            },
+            "required": [
+              "defaultType"
+            ]
+          },
+          "then": {
+            "properties": {
+              "defaultValue": {
+                "minLength": 1,
+                "type": [
+                  "string",
+                  "null"
+                ]
+              }
+            }
+          }
+        }
+      ],
+      "anyOf": [
+        {
+          "required": [
+            "queId"
+          ]
+        },
+        {
+          "required": [
+            "name"
+          ]
+        }
+      ],
       "description": "顶层业务字段的公共属性;字段类型由 TopField 的判别分支定义。",
       "properties": {
-        "dataTitle": {
-          "description": "是否作为数据标题;整个 body 最多且必须按规则存在一个。",
+        "beingRequired": {
+          "description": "该字段是否必填;缺失时保留已有字段当前值。",
           "type": "boolean"
         },
         "defaultType": {
           "default": 1,
-          "description": "默认值类型;1 表示静态值,2 表示关联/绑定值,3 表示公式值。",
+          "description": "默认值类型,与 defaultValue 联动;1 表示静态值,2 表示关联/绑定值且 defaultValue 只能省略或为 null,3 表示公式值且提供 defaultValue 时必须为非空公式文本。省略 defaultType 但提供 defaultValue 时按 1 处理。",
           "enum": [
             1,
             2,
@@ -19,47 +75,46 @@
         },
         "defaultValue": {
           "$ref": "#/$defs/ScalarDefaultValue",
-          "description": "普通字段的标量默认值;表格、地址、附件、引用等结构化默认值必须放在具体字段 config.defaultValues。显式 null 表示清除默认值。"
-        },
-        "description": {
-          "description": "字段说明;null 或空字符串表示清空。",
-          "type": [
-            "string",
-            "null"
-          ]
+          "description": "普通字段的默认值;后端 queDefaultValue 为字符串,因此数字等字面量也必须以字符串传入。defaultType 为 1 时表示静态文本,为 3 时表示公式文本,为 2 时不携带字面量默认值。表格、地址、附件、引用等结构化默认值必须放在具体字段 config.defaultValues。显式 null 表示清除默认值。"
         },
         "name": {
-          "description": "字段展示名称;同一父级内唯一,不单独作为字段身份。",
+          "description": "字段展示名称;新增字段必填,已有字段可在携带 queId 时省略;同一父级内唯一。",
           "minLength": 1,
           "type": "string"
         },
         "queId": {
-          "description": "已有字段的后端 ID;get 返回,新增字段省略。",
+          "description": "已有字段的后端 ID;更新时用于精确定位并复用,新增字段通常省略。",
           "minimum": 1,
           "type": "integer"
         },
-        "required": {
-          "description": "是否必填;缺失时保留已有字段当前值。",
-          "type": "boolean"
+        "questionDescription": {
+          "description": "字段说明;null 或空字符串表示清空。",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "questionType": {
+          "description": "字段类型;具体可用值由当前字段详情 Schema 的判别分支约束。",
+          "type": "string"
         },
         "width": {
-          "description": "字段在所在行的宽度百分比;同一行要么全部提供且合计 100,要么全部省略。",
-          "maximum": 100,
-          "minimum": 1,
+          "description": "字段在所在行的宽度百分比;只能选择 25、50、75 或 100。",
+          "enum": [
+            25,
+            50,
+            75,
+            100
+          ],
           "type": "integer"
         }
       },
-      "required": [
-        "name"
-      ],
       "type": "object"
     },
     "ScalarDefaultValue": {
-      "description": "不包含对象或数组的普通字段默认值。",
+      "description": "后端 queDefaultValue 支持的普通字段默认值;非空值必须是字符串,显式 null 表示清除默认值。数字和布尔值应先转换为字符串,对象和数组必须使用字段专用默认值配置。需要配置结构化默认值时,通过 AppForm Schema 查询能力传入当前 schema_version,并将字段的 questionType 作为 field_type 获取该字段类型的详细 Schema,再按其中的字段专用 config 定义填写。",
       "type": [
         "null",
-        "boolean",
-        "number",
         "string"
       ]
     },
@@ -120,12 +175,12 @@
         "config": {
           "$ref": "#/$defs/TextConfig"
         },
-        "type": {
+        "questionType": {
           "const": "text"
         }
       },
       "required": [
-        "type"
+        "questionType"
       ]
     }
   ],

package/src/qingflow_mcp/builder_facade/schemas/app_form/v1alpha1/summary.json

@@ -2,8 +2,15 @@
   "$defs": {
     "AppFormSpec": {
       "additionalProperties": false,
-      "description": "表单基础配置与字段布局目标态;除 body 外,缺失属性表示保留当前值。",
+      "description": "表单基础配置与字段布局目标态;除 body 外,缺失属性表示保留当前值。应用内所有 q_linker 和 code_block 字段的 outputs[].targetField 必须全局唯一,同一实际字段只能被一个输出映射写入。多个生产方需要回写时,请选择不同目标字段或合并为一个生产方。",
       "properties": {
+        "appDescription": {
+          "description": "应用描述;null 或空字符串表示清空。",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
         "appName": {
           "description": "应用名称;缺失时保留当前名称。",
           "minLength": 1,
@@ -18,46 +25,33 @@
         },
         "body": {
           "$ref": "#/$defs/Body",
-          "description": "业务字段与布局的完整目标态;缺失字段或段落表示删除。"
+          "description": "业务字段与布局的完整目标态;缺失字段或段落表示删除。应用内所有 Q-Linker 和代码块的 outputs[].targetField 不得重复选择同一实际字段。"
         },
-        "color": {
-          "description": "新应用图标颜色;仅创建分支允许,必须来自 workspace icon color catalog。",
-          "minLength": 1,
-          "type": "string"
-        },
-        "description": {
-          "description": "应用描述;null 或空字符串表示清空。",
-          "type": [
-            "string",
-            "null"
+        "dataCoverField": {
+          "description": "数据封面字段选择器;指定每条数据的封面附件来源。仅允许选择顶层 attachment 字段;null 表示清除数据封面。",
+          "oneOf": [
+            {
+              "type": "null"
+            },
+            {
+              "$ref": "#/$defs/FieldSelector"
+            }
           ]
         },
-        "icon": {
-          "description": "新应用图标;仅创建分支允许,必须来自 workspace icon catalog 且不得为 template。",
-          "minLength": 1,
-          "type": "string"
-        },
-        "serialNumber": {
-          "$ref": "#/$defs/SerialNumber",
-          "description": "应用编号规则;支持默认编号或自定义组件编号。"
-        },
-        "style": {
-          "description": "应用样式;对象内缺失属性保留当前值,null 表示清除全部自定义样式。",
+        "dataTitleField": {
+          "description": "数据标题字段选择器;指定每条数据的主显示标题来源。创建非空 body 时必填,更新时省略表示保留当前选择;显式提供时必须唯一定位一个顶层字段,仅 body 为空时允许 null。",
           "oneOf": [
             {
-              "$ref": "#/$defs/Style"
+              "type": "null"
             },
             {
-              "type": "null"
+              "$ref": "#/$defs/FieldSelector"
             }
           ]
         },
-        "theme": {
-          "description": "应用主题 ID;null 表示清除自定义主题。",
-          "type": [
-            "integer",
-            "null"
-          ]
+        "serialNumber": {
+          "$ref": "#/$defs/SerialNumber",
+          "description": "应用编号规则;支持默认编号或自定义组件编号。"
         }
       },
       "required": [
@@ -142,7 +136,7 @@
           ]
         }
       ],
-      "description": "跨字段引用选择器;至少提供 queId 或 name,两者同时提供时必须指向同一字段。",
+      "description": "字段选择器;用于定位应用的数据标题、数据封面、自定义编号取值来源或其他配置引用的字段。至少提供 queId 或 name,两者同时提供时必须指向同一字段。",
       "properties": {
         "name": {
           "description": "字段名称;仅在当前作用域内唯一时可用于解析。",
@@ -159,20 +153,74 @@
     },
     "FieldSummary": {
       "additionalProperties": false,
-      "properties": {
-        "config": {
-          "description": "调用对应 field_type 的详细 Schema 后生成。",
-          "type": "object"
+      "allOf": [
+        {
+          "if": {
+            "properties": {
+              "defaultType": {
+                "const": 2
+              }
+            },
+            "required": [
+              "defaultType"
+            ]
+          },
+          "then": {
+            "properties": {
+              "defaultValue": {
+                "type": "null"
+              }
+            }
+          }
         },
-        "dataCover": {
-          "type": "boolean"
+        {
+          "if": {
+            "properties": {
+              "defaultType": {
+                "const": 3
+              }
+            },
+            "required": [
+              "defaultType"
+            ]
+          },
+          "then": {
+            "properties": {
+              "defaultValue": {
+                "minLength": 1,
+                "type": [
+                  "string",
+                  "null"
+                ]
+              }
+            }
+          }
+        }
+      ],
+      "anyOf": [
+        {
+          "required": [
+            "queId"
+          ]
         },
-        "dataTitle": {
+        {
+          "required": [
+            "name"
+          ]
+        }
+      ],
+      "properties": {
+        "beingRequired": {
+          "description": "该字段是否必填;缺失时更新保留当前值。",
           "type": "boolean"
         },
+        "config": {
+          "description": "调用对应 questionType 的详细 Schema 后生成;q_linker 和 code_block 的 outputs[].targetField 还必须遵守应用级全局唯一规则。",
+          "type": "object"
+        },
         "defaultType": {
           "default": 1,
-          "description": "默认值类型;1 表示静态值,2 表示关联/绑定值,3 表示公式值。",
+          "description": "默认值类型,与 defaultValue 联动;1 表示静态值,2 表示关联/绑定值且 defaultValue 只能省略或为 null,3 表示公式值且提供 defaultValue 时必须为非空公式文本。省略 defaultType 但提供 defaultValue 时按 1 处理。",
           "enum": [
             1,
             2,
@@ -182,42 +230,46 @@
         },
         "defaultValue": {
           "$ref": "#/$defs/ScalarDefaultValue",
-          "description": "普通字段的标量默认值;结构化默认值必须放在具体字段 config.defaultValues。显式 null 表示清除默认值。"
-        },
-        "description": {
-          "type": [
-            "string",
-            "null"
-          ]
+          "description": "普通字段的默认值;后端 queDefaultValue 为字符串,因此数字等字面量也必须以字符串传入。defaultType 为 1 时表示静态文本,为 3 时表示公式文本,为 2 时不携带字面量默认值。结构化默认值必须放在具体字段 config.defaultValues。显式 null 表示清除默认值。"
         },
         "name": {
+          "description": "字段展示名称;新增字段必填,已有字段可在携带 queId 时省略。",
           "minLength": 1,
           "type": "string"
         },
         "queId": {
+          "description": "已有字段的后端 ID;更新时用于精确定位并复用,新增字段通常省略。",
           "minimum": 1,
           "type": "integer"
         },
-        "required": {
-          "type": "boolean"
+        "questionDescription": {
+          "description": "字段说明;null 或空字符串表示清空。",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "questionType": {
+          "description": "字段类型;必须来自 x-qingflow-supported-field-types。",
+          "type": "string"
         },
         "subfields": {
           "description": "仅 subtable 使用;详情见 subtable Schema。",
           "type": "array"
         },
-        "type": {
-          "description": "必须来自 x-qingflow-supported-field-types。",
-          "type": "string"
-        },
         "width": {
-          "maximum": 100,
-          "minimum": 1,
+          "description": "字段在所在行的宽度百分比;只能选择 25、50、75 或 100。",
+          "enum": [
+            25,
+            50,
+            75,
+            100
+          ],
           "type": "integer"
         }
       },
       "required": [
-        "name",
-        "type"
+        "questionType"
       ],
       "type": "object"
     },
@@ -267,11 +319,9 @@
       "type": "object"
     },
     "ScalarDefaultValue": {
-      "description": "不包含对象或数组的普通字段默认值。",
+      "description": "后端 queDefaultValue 支持的普通字段默认值;非空值必须是字符串,显式 null 表示清除默认值。数字和布尔值应先转换为字符串,对象和数组必须使用字段专用默认值配置。需要配置结构化默认值时,通过 AppForm Schema 查询能力传入当前 schema_version,并将字段的 questionType 作为 field_type 获取该字段类型的详细 Schema,再按其中的字段专用 config 定义填写。",
       "type": [
         "null",
-        "boolean",
-        "number",
         "string"
       ]
     },
@@ -450,7 +500,7 @@
             },
             "field": {
               "$ref": "#/$defs/FieldSelector",
-              "description": "取值来源字段。"
+              "description": "自定义编号中参与拼接的取值来源字段。"
             },
             "id": {
               "minimum": 1,
@@ -521,82 +571,15 @@
         }
       ]
     },
-    "Style": {
-      "additionalProperties": false,
-      "description": "表单背景和头部视觉样式;颜色使用 CSS 颜色字符串。",
-      "properties": {
-        "bgColor": {
-          "description": "表单背景色;null 表示清除。",
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "bgImage": {
-          "description": "表单背景图片 URL;null 表示清除。",
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "fontColor": {
-          "description": "表单头部字体颜色;null 表示清除。",
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "headerColor": {
-          "description": "表单头部背景色;null 表示清除。",
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "headerImage": {
-          "description": "表单头图 URL;null 表示清除。",
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "opacity": {
-          "description": "背景透明度,取值 0 到 1;null 表示清除。",
-          "maximum": 1,
-          "minimum": 0,
-          "type": [
-            "number",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    },
-    "TopField": {}
+    "TopField": {
+      "$ref": "#/$defs/FieldSummary"
+    }
   },
   "$id": "https://builder.qingflow.com/schemas/app-form-apply/v1alpha1/summary.json",
   "$schema": "https://json-schema.org/draft/2020-12/schema",
   "additionalProperties": false,
   "oneOf": [
     {
-      "properties": {
-        "spec": {
-          "not": {
-            "anyOf": [
-              {
-                "required": [
-                  "icon"
-                ]
-              },
-              {
-                "required": [
-                  "color"
-                ]
-              }
-            ]
-          }
-        }
-      },
       "required": [
         "appKey"
       ]
@@ -610,9 +593,7 @@
       "properties": {
         "spec": {
           "required": [
-            "appName",
-            "icon",
-            "color"
+            "appName"
           ]
         }
       },
@@ -637,7 +618,15 @@
     },
     "spec": {
       "additionalProperties": false,
+      "description": "应用表单目标态;应用内所有 q_linker 和 code_block 字段的 outputs[].targetField 必须全局唯一,同一实际字段只能被一个输出映射写入。多个生产方需要回写时,请选择不同目标字段或合并为一个生产方。",
       "properties": {
+        "appDescription": {
+          "description": "应用描述;null 或空字符串表示清空。",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
         "appName": {
           "minLength": 1,
           "type": "string"
@@ -650,7 +639,7 @@
           "type": "array"
         },
         "body": {
-          "description": "业务字段与布局完整目标态;缺失业务字段表示删除。",
+          "description": "业务字段与布局完整目标态;缺失业务字段表示删除。应用内所有 Q-Linker 和代码块的 outputs[].targetField 不得重复选择同一实际字段。",
           "items": {
             "oneOf": [
               {
@@ -663,38 +652,31 @@
           },
           "type": "array"
         },
-        "color": {
-          "description": "仅创建时使用;必须来自 workspace icon color catalog。",
-          "minLength": 1,
-          "type": "string"
-        },
-        "description": {
-          "type": [
-            "string",
-            "null"
+        "dataCoverField": {
+          "description": "数据封面字段选择器;指定每条数据的封面附件来源。仅允许选择顶层 attachment 字段;null 表示清除数据封面。",
+          "oneOf": [
+            {
+              "type": "null"
+            },
+            {
+              "$ref": "#/$defs/FieldSelector"
+            }
           ]
         },
-        "icon": {
-          "description": "仅创建时使用;必须来自 workspace icon catalog 且不得为 template。",
-          "minLength": 1,
-          "type": "string"
+        "dataTitleField": {
+          "description": "数据标题字段选择器;指定每条数据的主显示标题来源。创建非空 body 时必填,更新时省略表示保留当前选择;显式提供时必须唯一定位一个顶层字段,仅 body 为空时允许 null。",
+          "oneOf": [
+            {
+              "type": "null"
+            },
+            {
+              "$ref": "#/$defs/FieldSelector"
+            }
+          ]
         },
         "serialNumber": {
           "description": "default 或 custom 编号配置。",
           "type": "object"
-        },
-        "style": {
-          "description": "应用样式;详细属性为 bgImage/bgColor/opacity/headerImage/headerColor/fontColor。",
-          "type": [
-            "object",
-            "null"
-          ]
-        },
-        "theme": {
-          "type": [
-            "integer",
-            "null"
-          ]
         }
       },
       "required": [

package/src/qingflow_mcp/builder_facade/service.py

@@ -22718,6 +22718,7 @@ def _compile_q_linker_binding_fields(
                     "target_field_name": target_field.get("name"),
                     "target_field_ref": target_ref,
                     "alias": output_item.get("alias_name"),
+                    "alias_id": _coerce_positive_int(output_item.get("alias_id")),
                 }
             )
 
@@ -22790,7 +22791,7 @@ def _materialize_q_linker_question_relations(
                     "queId": source_ref,
                     "queTitle": source_field.get("name"),
                     "qlinkerAlias": relation.get("alias"),
-                    "aliasId": None,
+                    "aliasId": _coerce_positive_int(relation.get("alias_id")),
                 },
                 "matchRuleType": 1,
                 "matchRules": [],
@@ -24007,7 +24008,7 @@ def _normalize_formula_defaults_for_save(value: Any) -> None:
         return
     if not isinstance(value, dict):
         return
-    if _coerce_any_int(value.get("queDefaultType")) == DEFAULT_TYPE_FORMULA and value.get("queDefaultValue"):
+    if value.get("queDefaultValue"):
         value["queDefaultValue"] = _encode_formula_for_backend_save(value.get("queDefaultValue"))
     for key in ("subQuestions", "innerQuestions"):
         nested = value.get(key)

package/src/qingflow_mcp/response_trim.py

@@ -85,6 +85,8 @@ def trim_success_response(tool_name: str | None, payload: dict[str, Any]) -> dic
         drop_keys = COMMON_SUCCESS_DROP_TOP - {"output_profile"}
     if tool_name in {"user:record_insert", "user:record_update", "user:record_delete"} and payload.get("ok") is False:
         drop_keys = drop_keys - {"ok"}
+    if tool_name == "builder:app_form_apply" and payload.get("mustReadCurrentStateBeforeRepair") is True:
+        drop_keys = drop_keys - {"suggested_next_call"}
     _drop_top_keys(trimmed, drop_keys)
     transformer = SUCCESS_POLICY_BY_TOOL.get(tool_name or "")
     if transformer is not None:

package/src/qingflow_mcp/server_app_builder.py

@@ -36,7 +36,7 @@ def build_builder_server() -> FastMCP:
             "Use builder_tool_contract when you need a machine-readable contract, aliases, allowed enums, or a minimal valid example for a public builder tool. "
             "Use solution_install when the user explicitly wants to install a packaged solution/template by solution_key, optionally copying bundled demo data. "
             "Use package_list to find visible app packages by keyword and package_get to read package detail before editing; if creating or updating an app package may be appropriate, use package_apply with explicit user intent; otherwise use app_resolve to locate app resources, "
-            "Use workspace_icon_catalog_get before creating app packages, apps, or portals when supported icon/color candidates are needed; new workspace resources require explicit non-template icon + color, and the CLI validates choices without inferring business defaults. "
+            "Use workspace_icon_catalog_get before creating app packages or portals when supported icon/color candidates are needed; those resources require explicit non-template icon + color. AppForm-created apps derive a stable default icon and color from spec.appName. "
             "app_form_schema plus app_form_get for versioned form work, using being_draft=true only for editing and the published default for relation or record consumers; use app_get as the default non-form app map read, then app_get_fields/app_repair_code_blocks/app_get_layout/app_get_views/app_get_flow/app_get_charts/portal_list/portal_get/view_get/chart_get for focused compatibility or non-form reads, "
             "member_search/role_search/role_create when workflow assignees must come from the directory or role catalog, preferring roles over explicit members unless the user explicitly names members, "
             "then app_form_apply for complete app form targets, explicit app_delete for application deletion, and app_flow_apply/app_views_apply/app_associated_resources_apply/app_charts_apply/portal_apply/portal_delete for non-form patches. app_custom_buttons_apply is maintenance-only for explicit standalone button work outside normal view design. These apply/delete tools perform validation, normalization, writes, and readback verification where applicable. AppForm publishes only after a draft change or when the published form lags behind; views noop requests skip publish, app_custom_buttons_apply and app_associated_resources_apply publish after at least one write succeeds and expose no draft-only parameter, charts are immediate-live without publish and resolve targets by chart_id first then exact unique chart name, portal updates use replace semantics only when sections are supplied and edit-mode base-info-only updates may omit sections, portal delete separates DELETE execution from readback verification, portal pc layout is a 24-column grid and mobile is a 6-column grid so omit position or use layout_preset when unsure, publish=false only guarantees draft/base-info updates for tools that still expose that parameter, and flow should use publish=false whenever you only want draft/precheck behavior. "
@@ -44,7 +44,7 @@ def build_builder_server() -> FastMCP:
             "For existing object parameter replacement, prefer patch_views, patch_buttons, patch_resources, and patch_charts with set/unset; the tool reads current config and full-saves internally, while upsert_* is for creation or full target configuration and should not be used as an incomplete partial update. "
             "For builder delete/remove apply results, separate delete execution from readback verification: after DELETE is sent, resources expose delete_executed, readback_status, and safe_to_retry_delete=false. If readback_status is unavailable or still_exists, do not blindly repeat the delete; confirm later with app_get/view_get/chart_get or the relevant apply readback. Views/buttons use single-item readback; associated resources use one app-level resource-pool readback because there is no confirmed single-item GET. "
             "For builder write/apply results, separate write execution from final readback verification: status=partial_success with write_executed=true and safe_to_retry=false means the write was sent or succeeded, while final readback, publish verification, or metadata confirmation is pending or permission-restricted. Report it as written but unverified; do not repeat the same write blindly. "
-            "For app_form_apply, pin the version from app_form_schema, preserve the complete body and existing IDs from a draft get, and use dataTitle/dataCover on canonical fields; App Builder MCP validates the declaration inside app_form_apply, while the CLI route has a separate static validate command. Exactly one top-level dataTitle is required for a non-empty body, while dataCover is optional and must be a top-level attachment field. A root appKey means update and may include packageId; no appKey means create and requires packageId plus spec.appName, spec.icon, and spec.color selected from workspace_icon_catalog_get, with template forbidden. "
+            "For app_form_apply, pin the version from app_form_schema, preserve the complete body and existing IDs from a draft get, and configure data display through app-level spec.dataTitleField/spec.dataCoverField selectors rather than booleans on fields; App Builder MCP validates the declaration inside app_form_apply, while the CLI route has a separate static validate command. dataTitleField must resolve to exactly one top-level field for a non-empty body, while dataCoverField is optional and must resolve to a top-level attachment field. A root appKey means update and may include packageId; no appKey means create and requires packageId plus spec.appName. AppForm does not accept spec.icon or spec.color; creation derives a stable default icon and color from spec.appName. "
             "For app_views_apply, keep fixed saved filters in filters and configure the frontend query panel separately with query_conditions; query_conditions.rows is a matrix of field names compiled to backend queryCondition queIds. New views default associated report/view display to visible with limit_type=all; existing views preserve their current associated display unless associated_resources is explicitly patched. View writes use ViewManagementAuth (beingViewManageStatus), falling back to DataManageAuth when advanced app permissions are not enabled. "
             "For ordinary business buttons, declare them on the target view with app_views_apply.views[].action_buttons; app_views_apply writes the view first, then creates/binds the button. Use app_custom_buttons_apply only when the user explicitly asks to maintain existing standalone buttons outside view design, such as custom style/icon changes, cross-view reuse, deleting button bodies, bulk binding reorder, or exact qRobot/wings config. Button body writes require EditAppAuth; view_configs placement writes require ViewManagementAuth, matching the backend viewConfig route. For addData buttons, prefer action_buttons.target_app_key + field_mappings/default_values on the view path; do not ask agents to write raw que_relation unless maintaining a legacy config. field_mappings.source_field accepts source schema fields and supported system fields: 数据ID/row_record_id/apply_id/_id means current record id (-17), 编号/record_number means visible record number (0). To fill a target relation with the current record, map {'source_field': '数据ID', 'target_field': '目标引用字段'}; default_values is only for static constants. View button bindings merge by default; standalone view_configs are only for explicit maintenance. Builder view_key arguments are raw keys from app_get.views[].view_key and must not be prefixed with custom:. "
             "For BI reports, keep report-body development separate from Qingflow in-app display: use app_charts_apply to create, update, remove, or reorder app-source QingBI chart bodies/configs with dataSourceType=qingflow; chart dimension/metric/filter/query fields must come from app_get_fields.chart_fields, not record schema or form-only fields; dataset BI reports are not created or edited by app_charts_apply yet and should be created in QingBI first, then attached with app_associated_resources_apply using report_source=dataset. "