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

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

@@ -1,21 +1,26 @@
 {
   "$defs": {
-    "EmptyConfig": {
-      "additionalProperties": false,
-      "description": "该字段类型没有特殊配置。",
-      "type": "object"
-    },
     "FieldCommon": {
       "description": "顶层业务字段的公共属性;字段类型由 TopField 的判别分支定义。",
       "properties": {
-        "dataCover": {
-          "description": "是否作为数据封面;仅顶层附件字段可设为 true。",
-          "type": "boolean"
-        },
         "dataTitle": {
           "description": "是否作为数据标题;整个 body 最多且必须按规则存在一个。",
           "type": "boolean"
         },
+        "defaultType": {
+          "default": 1,
+          "description": "默认值类型;1 表示静态值,2 表示关联/绑定值,3 表示公式值。",
+          "enum": [
+            1,
+            2,
+            3
+          ],
+          "type": "integer"
+        },
+        "defaultValue": {
+          "$ref": "#/$defs/ScalarDefaultValue",
+          "description": "普通字段的标量默认值;表格、地址、附件、引用等结构化默认值必须放在具体字段 config.defaultValues。显式 null 表示清除默认值。"
+        },
         "description": {
           "description": "字段说明;null 或空字符串表示清空。",
           "type": [
@@ -48,6 +53,60 @@
         "name"
       ],
       "type": "object"
+    },
+    "ScalarDefaultValue": {
+      "description": "不包含对象或数组的普通字段默认值。",
+      "type": [
+        "null",
+        "boolean",
+        "number",
+        "string"
+      ]
+    },
+    "TextConfig": {
+      "additionalProperties": false,
+      "description": "文字类字段的长度限制;省略表示保留当前值。",
+      "properties": {
+        "canScan": {
+          "description": "是否允许扫码输入。",
+          "type": [
+            "boolean",
+            "null"
+          ]
+        },
+        "maxWordCount": {
+          "description": "最多字数;null 表示清除限制。",
+          "minimum": 0,
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "minWordCount": {
+          "description": "最少字数;null 表示清除限制。",
+          "minimum": 0,
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "noRepeat": {
+          "description": "是否禁止重复值。",
+          "type": [
+            "boolean",
+            "null"
+          ]
+        },
+        "scanType": {
+          "description": "扫码类型 ID。",
+          "minimum": 0,
+          "type": [
+            "integer",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
     }
   },
   "$id": "https://builder.qingflow.com/schemas/app-form-apply/v1alpha1/fields/text.json",
@@ -59,7 +118,7 @@
     {
       "properties": {
         "config": {
-          "$ref": "#/$defs/EmptyConfig"
+          "$ref": "#/$defs/TextConfig"
         },
         "type": {
           "const": "text"

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

@@ -170,6 +170,20 @@
         "dataTitle": {
           "type": "boolean"
         },
+        "defaultType": {
+          "default": 1,
+          "description": "默认值类型;1 表示静态值,2 表示关联/绑定值,3 表示公式值。",
+          "enum": [
+            1,
+            2,
+            3
+          ],
+          "type": "integer"
+        },
+        "defaultValue": {
+          "$ref": "#/$defs/ScalarDefaultValue",
+          "description": "普通字段的标量默认值;结构化默认值必须放在具体字段 config.defaultValues。显式 null 表示清除默认值。"
+        },
         "description": {
           "type": [
             "string",
@@ -252,6 +266,15 @@
       ],
       "type": "object"
     },
+    "ScalarDefaultValue": {
+      "description": "不包含对象或数组的普通字段默认值。",
+      "type": [
+        "null",
+        "boolean",
+        "number",
+        "string"
+      ]
+    },
     "SectionBlock": {
       "additionalProperties": false,
       "description": "段落布局容器;不是业务字段,必须独占一个根级块。",

package/src/qingflow_mcp/response_trim.py

@@ -55,6 +55,8 @@ SUCCESS_POLICY_BY_TOOL: dict[str, TransformFn] = {}
 def trim_public_response(tool_name: str | None, payload: dict[str, Any]) -> dict[str, Any]:
     if not isinstance(payload, dict):
         return payload
+    if tool_name == "builder:app_form_apply" and str(payload.get("status") or "").lower() == "partial_success":
+        return trim_success_response(tool_name, payload)
     if _looks_like_failure_payload(payload):
         status = str(payload.get("status") or "").lower()
         if _is_executed_nonfatal_payload(payload) or (
@@ -1086,6 +1088,44 @@ def _trim_builder_list_like(payload: JSONObject) -> None:
     _trim_builder_envelope(payload)
 
 
+def _trim_app_form_apply(payload: JSONObject) -> None:
+    details = payload.get("details")
+    details_diff = deepcopy(details.get("diff")) if isinstance(details, dict) and isinstance(details.get("diff"), dict) else None
+    if isinstance(details, dict):
+        _drop_deep_keys(details, {"transportError"})
+    _trim_builder_envelope(payload)
+    _trim_form_diff(payload)
+    if details_diff is not None:
+        payload.setdefault("details", {})["diff"] = _summarize_form_diff(details_diff)
+
+
+def _trim_form_diff(payload: JSONObject) -> None:
+    diff = payload.get("diff")
+    if isinstance(diff, dict):
+        payload["diff"] = _summarize_form_diff(diff)
+
+
+def _summarize_form_diff(diff: dict[str, Any]) -> dict[str, Any]:
+    summary: dict[str, Any] = {}
+    for key in ("added", "updated", "removed"):
+        items = diff.get(key)
+        if not isinstance(items, list):
+            continue
+        names = []
+        for item in items:
+            if isinstance(item, str):
+                names.append(item)
+            elif isinstance(item, dict):
+                name = item.get("name") or item.get("queTitle")
+                if name:
+                    names.append(name)
+        summary[key] = names
+    for key in ("layoutChanged", "configChanged"):
+        if key in diff:
+            summary[key] = bool(diff[key])
+    return summary
+
+
 def _register_policy(domains: tuple[str, ...], names: tuple[str, ...], transform: TransformFn) -> None:
     for domain in domains:
         for name in names:
@@ -1192,7 +1232,6 @@ _register_policy(
         "app_resolve",
         "app_form_schema",
         "app_form_get",
-        "app_form_apply",
         "app_delete",
         "button_style_catalog_get",
         "app_custom_buttons_apply",
@@ -1218,3 +1257,4 @@ _register_policy(
     ),
     _trim_builder_list_like,
 )
+_register_policy((BUILDER_DOMAIN,), ("app_form_apply",), _trim_app_form_apply)

package/src/qingflow_mcp/server.py

@@ -26,12 +26,32 @@ from .tools.workflow_tools import WorkflowTools
 from .tools.workspace_tools import WorkspaceTools
 
 
+def _register_missing_builder_tools(server: FastMCP) -> None:
+    """Add current high-level builder tools to the unified MCP without duplicate names."""
+    from .server_app_builder import build_builder_server
+
+    builder_server = build_builder_server()
+    registered = server._tool_manager._tools
+    for tool in builder_server._tool_manager._tools.values():
+        if tool.name in registered:
+            continue
+        server.add_tool(
+            tool.fn,
+            name=tool.name,
+            title=tool.title,
+            description=tool.description,
+            annotations=tool.annotations,
+            icons=tool.icons,
+            meta=tool.meta,
+        )
+
+
 def build_server() -> FastMCP:
     today = date.today()
     current_year = today.year
     server = FastMCP(
         "Qingflow MCP",
-        instructions=f"""Use this server for Qingflow operational workflows. Current date: `{today.isoformat()}`.
+        instructions=f"""Use this unified server for Qingflow operational and builder workflows. Current date: `{today.isoformat()}`.
 
 ## Authentication
 
@@ -203,9 +223,9 @@ Normalize relative dates before building DSL.
 
 Default to `prod` unless the user explicitly specifies `test`.
 
-## Constraints
+## Builder Path
 
-Avoid builder-side app or schema changes here.
+Use the public builder tools for package, AppForm, workflow, view, chart, portal, and application configuration work. Pin the AppForm Schema version, preserve complete form declarations and existing IDs from draft reads, and use `app_form_apply` for reconciliation. Do not fall back to legacy raw builder write routes.
 
 ## Feedback Path
 
@@ -235,6 +255,7 @@ If the current MCP capability is unsupported, the workflow is awkward, or the us
     WorkflowTools(sessions, backend).register(server)
     ViewTools(sessions, backend).register(server)
     SolutionTools(sessions, backend).register(server)
+    _register_missing_builder_tools(server)
     return server
 
 

package/src/qingflow_mcp/server_app_builder.py

@@ -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, validate the JSON declaration with the qingflow-app-form Skill command, preserve the complete body and existing IDs from a draft get, and use dataTitle/dataCover on canonical fields; 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 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_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. "

package/src/qingflow_mcp/tools/record_tools.py

@@ -11895,7 +11895,7 @@ class RecordTools(ToolBase):
             raise RecordInputError(
                 message=f"field '{field.que_title}' uses unsupported nested subtable writes",
                 error_code="UNSUPPORTED_WRITE_FORMAT",
-                fix_hint="Nested subtable writes are not supported in app-user tools.",
+                fix_hint="Nested subtable writes are not supported by the public record tools.",
                 details={"location": location, "field": _field_ref_payload(field), "expected_format": _write_format_for_field(field), "received_value": item},
             )
         self._raise_if_verify_unsupported_write_field(field, item, location=location)
@@ -11960,7 +11960,7 @@ class RecordTools(ToolBase):
             raise RecordInputError(
                 message=f"field '{field.que_title}' uses unsupported nested subtable writes",
                 error_code="UNSUPPORTED_WRITE_FORMAT",
-                fix_hint="Nested subtable writes are not supported in app-user tools.",
+                fix_hint="Nested subtable writes are not supported by the public record tools.",
                 details={"location": location, "field": _field_ref_payload(field), "expected_format": _write_format_for_field(field), "received_value": raw_value},
             )
         self._raise_if_verify_unsupported_write_field(field, raw_value, location=location)
@@ -21150,7 +21150,7 @@ def _subtable_cell_ref_payload(
 
 def _unsupported_write_reason(que_type: int | None) -> str:
     if que_type == 14:
-        return "time range fields require a backend-specific native payload shape that app-user tools do not build yet"
+        return "time range fields require a backend-specific native payload shape that public record tools do not build yet"
     if que_type == 34:
         return "image recognition fields are runtime AI fields and direct writes are not reliably persisted"
     if que_type == 35:

package/src/qingflow_mcp/version.py

@@ -57,11 +57,9 @@ def _find_package_root() -> Path | None:
         if version and name in {
             "qingflow-mcp-workspace",
             "@qingflow-tech/qingflow-cli",
-            "@qingflow-tech/qingflow-app-user-mcp",
-            "@qingflow-tech/qingflow-app-builder-mcp",
+            "@qingflow-tech/qingflow-mcp",
             "@josephyan/qingflow-cli",
-            "@josephyan/qingflow-app-user-mcp",
-            "@josephyan/qingflow-app-builder-mcp",
+            "@josephyan/qingflow-mcp",
         }:
             return parent
     return None