@qingflow-tech/qingflow-cli 1.1.50-beta.1 → 1.1.50-beta.2

package/README.md

@@ -7,7 +7,7 @@ Qingflow CLI 是轻流面向开发者和 AI Agent 的命令行工具。它把轻
 ## 安装
 
 ```bash
-npm install @qingflow-tech/qingflow-cli@1.1.50-beta.1
+npm install @qingflow-tech/qingflow-cli@1.1.50-beta.2
 ```
 
 推荐从官网复制这一条一键安装 Qingflow CLI：
@@ -21,7 +21,7 @@ npx qingflow-cli@latest install
 ## 运行
 
 ```bash
-npx -y -p @qingflow-tech/qingflow-cli@1.1.50-beta.1 qingflow
+npx -y -p @qingflow-tech/qingflow-cli@1.1.50-beta.2 qingflow
 ```
 
 全局安装后可以直接运行：
@@ -62,7 +62,7 @@ qingflow-skills install --agent codex --scope user
 如果你通过一次性 `npx -p` 执行 skills 安装，建议加 `--copy`，避免 symlink 指向 npm 临时执行缓存：
 
 ```bash
-npx -y -p @qingflow-tech/qingflow-cli@1.1.50-beta.1 qingflow-skills install --agent codex --scope user --copy
+npx -y -p @qingflow-tech/qingflow-cli@1.1.50-beta.2 qingflow-skills install --agent codex --scope user --copy
 ```
 
 `qingflow-skills install` 默认使用 symlink，且遇到同名 skill 不会覆盖；只有显式传入 `--force` 才会替换。

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@qingflow-tech/qingflow-cli",
-  "version": "1.1.50-beta.1",
+  "version": "1.1.50-beta.2",
   "description": "Human-friendly Qingflow command line interface for auth, record operations, import, tasks, and stable builder flows.",
   "license": "MIT",
   "type": "module",

package/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "qingflow-mcp"
-version = "1.1.50b1"
+version = "1.1.50b2"
 description = "User-authenticated MCP server for Qingflow"
 readme = "README.md"
 license = "MIT"
@@ -40,6 +40,7 @@ dependencies = [
 dev = [
   "pytest>=8.3,<9.0",
   "respx>=0.22,<1.0",
+  "pymysql>=1.2.2",
 ]
 build = [
   "pyinstaller>=6.0,<7.0",

package/skills/qingflow-cli/reference/builder/20-build-complete-system.md

@@ -22,7 +22,7 @@ package apply/get -> AppForm schema/get/apply per app -> app readback -> workflo
 - Do not call the retired `builder schema apply` or `builder layout apply` routes, and do not use their `add_fields`, `apps-file`, or `form-file` payloads as the current path.
 - For relations, create relation-independent apps first, read back their published `appKey`s, then submit complete declarations using the canonical relation shape and known target app keys.
 - One app may contain multiple `relation` fields when the business model needs them.
-- Relation selectors use the AppForm camelCase shape, not bare strings: write `config.displayField: {"name":"产品编码"}` and `config.visibleFields: [{"name":"产品名称"}]`. `config.targetAppKey` must be a target app key confirmed by readback.
+- Relation selectors use the AppForm camelCase shape, not bare strings: write ordered `config.displayFields: [{"field":{"name":"产品编码"},"auth":"visible"}]` (include hidden items) and `config.twoWayBoundField: {"queId":N}` when the binding is two-way (omit for one-way). `config.targetAppKey` must be a target app key confirmed by readback.
 - If AppForm apply times out or returns uncertain write state, perform draft/published form readback before retrying. Do not recreate apps with `V2`, `测试`, or random suffixes.
 - If a same/similar package or app set already exists and the user did not say whether to extend, repair, replace, or create new, stop and ask. Do not start probing with new names.
 - If readback shows part of the requested system already exists, list existing apps/fields/views/charts/portal, identify gaps, and patch only the missing or incorrect slices.
@@ -72,7 +72,7 @@ A complete system is not just several created apps. Before reporting completion,
 
 - Package exists, and its `package_id` is known.
 - Every core business object is a separate app with `app_key`, `app_name`, `icon`, `color`, and exactly one readable data title field.
-- Cross-app relation fields are present where the business model needs them; each relation uses a confirmed `targetAppKey` and object selectors in `config.displayField` / `config.visibleFields`.
+- Cross-app relation fields are present where the business model needs them; each relation uses a confirmed `targetAppKey` and object selectors in `config.displayFields[].field` (+ `twoWayBoundField` for two-way bindings).
 - Core apps were created with complete AppForm declarations, so fields and readable form sections/rows were submitted together.
 - Core operating views exist and their `query_conditions` and `action_buttons` are verified; list-row buttons and detail-page buttons are both configured through the view.
 - Each new app has 5 realistic sample records unless the user explicitly skipped sample data.

package/skills/qingflow-cli/reference/builder/30-schema-fields.md

@@ -185,7 +185,7 @@ current CLI payload.
 | 负责人、审批人、参与人 | `member` | 不要创建“申请人/提交人”等平台系统字段 |
 | 部门、组织 | `department` | 可按需要补 `config.departmentScope` |
 | 图片、文件、附件 | `attachment` | 只有顶层 `attachment` 可被应用级 `dataCoverField` 选择 |
-| 跨应用业务对象关系 | `relation` | 使用已确认的 `targetAppKey`；`displayField` / `visibleFields` 必须写对象选择器 |
+| 跨应用业务对象关系 | `relation` | 使用已确认的 `targetAppKey`；展示字段写有序 `displayFields[]`（含 `auth`），双向绑定写 `twoWayBoundField`；旧 `displayField`/`visibleFields` 兼容窗口内仍可读 |
 
 禁止创建平台系统字段：`数据ID`、`编号`、`申请人`、`申请时间`、`创建人`、`创建时间`、`提交人`、`提交时间`、`更新时间`、`更新人`、`当前流程状态`、`当前处理人`、`当前处理节点`、`流程标题`。需要引用系统字段时，只在工具明确支持的位置引用，例如按钮 `source_field: "数据ID"`。
 
@@ -243,7 +243,7 @@ current CLI payload.
 |--------|----------|-----------------|
 | 标量与选择器 | `name` + `questionType`（+ 业务 `beingRequired` 等） | `questionDescription`、`beingRequired`；数据标题和封面在应用级 `dataTitleField/dataCoverField` 中选择；**`single_select` / `multi_select` 的 `config.options` 是非空字符串数组**，如 `["A", "B"]` |
 | `department` | 同左 | **`config.departmentScope`**：`mode: all \| custom`；`custom` 时 **`departments[]`**（含 `deptId` 等） |
-| `relation` | **`targetAppKey`**；另需 **`displayField`**、**`visibleFields[]`** | **`relationMode`**；目标应用元数据不可读时先读已发布表单，不要猜目标 key |
+| `relation` | **`targetAppKey`**；另需 **`displayFields[]`**（含 `field`+`auth`；可为空列表——空 = 双向绑定未配展示字段的存量形态，round-trip 空↔空稳定；与旧形态不可混用、条目 queId 不可重复） | **`relationMode`**；双向绑定加 **`twoWayBoundField`**（省略 = 单向）；目标应用元数据不可读时先读已发布表单，不要猜目标 key |
 | `subtable` | **`subfields[]` 非空** | 子列递归同父级规则；使用 Schema 返回的 camelCase 子字段配置 |
 | `q_linker` | **`config.qLinkerBinding`**：`inputs`、`request`、**`outputs[]` 每项须含 `targetField`**（能解析到本表单字段） | `request.url` 等须符合**租户/后端远程查询策略**；以字段类型 Schema 返回的配置为准 |
 | `code_block` | **`config.codeBlockBinding`**：`inputs`、`code`、**`outputs[]` + `targetField`**；配置 outputs 时，代码必须显式写 **`qf_output = {...}`**，仅 `return {...}` 不会产生可回写结果，且每个 `outputs[].path` 必须从 `qf_output` 取值 | 以字段类型 Schema 返回的 camelCase 配置为准 |
@@ -265,13 +265,17 @@ current CLI payload.
   "config": {
     "targetAppKey": "PRODUCT_APP_KEY",
     "relationMode": "single",
-    "displayField": {"name": "产品编码"},
-    "visibleFields": [{"name": "产品名称"}, {"name": "产品线"}]
+    "twoWayBoundField": {"name": "产品编码"},
+    "displayFields": [
+      {"field": {"name": "产品编码"}, "auth": "visible"},
+      {"field": {"name": "产品名称"}, "auth": "hidden"},
+      {"field": {"name": "产品线"}, "auth": "visible"}
+    ]
   }
 }
 ```
 
-只在目标应用已经创建并通过 readback 确认后填写 `targetAppKey`。如果返回选择器校验错误，修复 `config.displayField` / `config.visibleFields`，不要重建应用或改 `appKey`。
+只在目标应用已经创建并通过 readback 确认后填写 `targetAppKey`。如果返回选择器校验错误，修复 `config.displayFields[].field` / `config.twoWayBoundField`，不要重建应用或改 `appKey`。旧形态 `displayField`/`visibleFields` 在兼容窗口内仍可读（displayField 同时视为双向绑定目标），新声明一律用 `displayFields`。
 
 引用字段的公式默认值写在 `config.defaultValueFormula`，表达式必须符合固定版本 `relation` 字段详情中的 `FormulaExpression`。不要把后端 `referenceConfig` 字段名或其他 Schema 版本的公式写法直接放进声明。
 

package/skills/qingflow-cli/reference/builder/reference/app-delivery-sop.md

@@ -201,8 +201,8 @@ qingflow builder schema apply \
 - 如果返回 `MULTI_APP_STATIC_VALIDATION_FAILED`，读取 `details.issues[]` 的 `path/error_code/fix_hint` 修 payload；这是写入前失败，通常可以修正后重试，不需要 readback。
 - 多应用 schema apply 不做事务回滚；如果部分失败，只补失败的 `apps[].row_number`，不要整批重复提交。
 - 这个模式只负责应用壳与字段；视图、按钮、关联资源、报表仍拿返回的 `app_key` 继续走各自 apply 工具。
-- `target_app_ref`、`as_data_title`、`display_field` 等只属于旧载荷。迁移时将关系改写为 AppForm `config.targetAppKey`、`config.displayField`、`config.visibleFields`，并使用已确认的真实 app key。
-- 历史 schema adapter 写入后可读 `details.relation_readback_matrix[]`：逐项核对旧 `target_app_key`、`relation_mode`、`display_field`、`visible_fields`。迁移到当前 AppForm 后，改为读取 draft/published form 的 `config.targetAppKey`、`config.relationMode`、`config.displayField`、`config.visibleFields`，不要提交旧 `update_fields` patch。
+- `target_app_ref`、`as_data_title`、`display_field` 等只属于旧载荷。迁移时将关系改写为 AppForm `config.targetAppKey`、`config.displayFields[]`（含 `auth`）、`config.twoWayBoundField`，并使用已确认的真实 app key。
+- 历史 schema adapter 写入后可读 `details.relation_readback_matrix[]`：逐项核对旧 `target_app_key`、`relation_mode`、`display_field`、`visible_fields`。迁移到当前 AppForm 后，改为读取 draft/published form 的 `config.targetAppKey`、`config.relationMode`、`config.twoWayBoundField`、`config.displayFields[]`，不要提交旧 `update_fields` patch。
 - 一个应用可以包含多个 `relation` 字段；不要因为 relation 数量超过 1 就降级成文本。若真实写入失败或 relation readback mismatch，只按实际错误和 `details.relation_repair_plan[]` 做最小修复。
 - 完整系统遇到超时、`partial_success`、`write_executed=true`、`safe_to_retry=false` 或 readback 不完整时，先按 §3.4 读回，不要直接拆成单应用创建。
 
@@ -349,7 +349,7 @@ qingflow builder flow apply \
 | **`address`** | 地址复合字段。 |
 | **`attachment`** | 附件。 |
 | **`boolean`** | 是否。 |
-| **`relation`** | 旧载荷使用 `target_app_key` / `target_app_ref`；当前 AppForm 使用 `config.targetAppKey`、`config.relationMode`、`config.displayField`、`config.visibleFields`。 |
+| **`relation`** | 旧载荷使用 `target_app_key` / `target_app_ref`；当前 AppForm 使用 `config.targetAppKey`、`config.relationMode`、`config.twoWayBoundField`、`config.displayFields[]`。 |
 | **`subtable`** | 当前 AppForm 使用 `subfields[]` 及 Schema 返回的 camelCase 配置；旧 `subfield_updates` 只作迁移线索。 |
 | **`q_linker`** | 当前 AppForm 使用 `config.qLinkerBinding`，其 `outputs[].targetField` 必须按字段 Schema 配置。 |
 | **`code_block`** | 当前 AppForm 使用 `config.codeBlockBinding`，其 `outputs[].targetField` 必须按字段 Schema 配置。 |

package/src/qingflow_mcp/app_form_compat.py

@@ -10,6 +10,9 @@ from .json_types import JSONObject
 TYPE_ALIASES = {
     "multiline": "long_text",
     "textarea": "long_text",
+    "richtext": "rich_text",
+    "rich-text": "rich_text",
+    "rich_text": "rich_text",
     "radio": "single_choice",
     "boolean": "single_choice",
     "select": "single_select",

package/src/qingflow_mcp/app_form_validator.py

@@ -218,8 +218,14 @@ def _static_errors(payload: dict[str, Any]) -> list[tuple[str, str]]:
             widths = ["width" in field for field in fields if isinstance(field, dict)]
             if widths and any(widths) and not all(widths):
                 errors.append((row_path, "width must be present on every field in the row or omitted from all"))
-            if widths and all(widths) and sum(field.get("width", 0) for field in fields if isinstance(field, dict)) != 100:
-                errors.append((row_path, "field widths must total 100"))
+            # 行宽契约(与后端语义对齐):任意 1-100 整数 + 全有或全无。
+            # 后端 html_width 无取值/总和校验,存量存在 33/34 三等分与字段删除后
+            # 留白(如 3×25=75)的行;get 读出的原布局必须能原样过校验
+            # (apply(get(S)) ≡ S 命题的必要条件)。
+            if widths and all(widths):
+                bad = [f.get("width") for f in fields if isinstance(f, dict) and not (isinstance(f.get("width"), int) and 1 <= f["width"] <= 100)]
+                if bad:
+                    errors.append((row_path, "field widths must be an integer between 1 and 100"))
             for field_index, field in enumerate(fields):
                 if isinstance(field, dict):
                     top_fields.append((f"{row_path}/{field_index}", field))
@@ -258,7 +264,14 @@ def _static_errors(payload: dict[str, Any]) -> list[tuple[str, str]]:
     if top_fields:
         if "dataTitleField" not in spec and "appKey" in payload:
             pass
-        elif title_selector is None or resolve_local_selector(title_selector)[0] == "invalid":
+        elif title_selector is None:
+            # dataTitleField=null 仅在带 appKey 的更新/round-trip 场景放行:后端写链
+            # FormSvcImpl.normalizeDataTitleQueId 对 null 自动 fallback 到第一个可用
+            # 字段,get 读面在后端未设置时原样输出 null。创建场景(无 appKey)仍需
+            # 显式 selector。
+            if "appKey" not in payload:
+                errors.append(("/spec/dataTitleField", "dataTitleField must resolve to exactly one top-level field"))
+        elif resolve_local_selector(title_selector)[0] == "invalid":
             errors.append(("/spec/dataTitleField", "dataTitleField must resolve to exactly one top-level field"))
     elif title_selector is not None:
         errors.append(("/spec/dataTitleField", "dataTitleField must be null when body is empty"))