@qingflow-tech/qingflow-cli 1.1.61-beta.6 → 1.1.61-beta.7

package/README.md

@@ -7,7 +7,7 @@ Qingflow CLI 是轻流面向开发者和 AI Agent 的命令行工具。它把轻
 ## 安装
 
 ```bash
-npm install @qingflow-tech/qingflow-cli@1.1.61-beta.6
+npm install @qingflow-tech/qingflow-cli@1.1.61-beta.7
 ```
 
 推荐从官网复制这一条一键安装 Qingflow CLI：
@@ -21,7 +21,7 @@ npx qingflow-cli@latest install
 ## 运行
 
 ```bash
-npx -y -p @qingflow-tech/qingflow-cli@1.1.61-beta.6 qingflow
+npx -y -p @qingflow-tech/qingflow-cli@1.1.61-beta.7 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.61-beta.6 qingflow-skills install --agent codex --scope user --copy
+npx -y -p @qingflow-tech/qingflow-cli@1.1.61-beta.7 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.61-beta.6",
+  "version": "1.1.61-beta.7",
   "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.61b6"
+version = "1.1.61b7"
 description = "User-authenticated MCP server for Qingflow"
 readme = "README.md"
 license = "MIT"

package/skills/qingflow-cli/reference/builder/70-portal.md

@@ -47,7 +47,7 @@ Start from the portal job, then choose the section strategy. A portal is an asse
 | Show BI visualizations | Use chart sections | `rows=7`; same-row components share the same `rows` |
 | Show concrete data views | Use view sections | Use business views, not `全部数据` / `我的数据`; `rows=11` |
 | Update one existing portal block | Prefer `patch_sections[]` | Do not replace the whole `sections` list unless intentional |
-| Need a filter bar | Avoid automation by default | `source_type: "filter"` is raw/unstable and not part of the unified filter DSL |
+| Need a filter bar | Use `source_type: "filter"` with non-empty `config.rules` | Empty-rules filters are rejected (backend read face enumerates filter components by their rule groups); see §3.4 |
 
 Short rule: **portal rows are 24-grid layout rows, not form-field rows. Same `y` = same row, same `rows`, `cols` sum 24.**
 
@@ -63,7 +63,7 @@ Before `portal apply`, verify this short list:
 | Standard heights | Metric cards `rows=5`; BI charts `rows=7`; data views `rows=11`. Do not mix different heights in one row. |
 | Standard order | Business entry -> metrics -> BI charts -> data views. Do not put data views before metrics/charts in a dashboard-style portal. |
 | Default/system views | Do not use `全部数据` / `我的数据` as the main business portal views. Use concrete business views. |
-| Filter component | Do not use `source_type: "filter"` as the main automation path; it is raw/unstable and not part of the unified filter DSL. |
+| Filter component | `config.rules` must contain at least one rule group (empty-rules filters are written but invisible in readback; blocked at validation). Rule keys: filterGroupName/filterGroupConfig/filterItemName/que/judge, see §3.4. |
 | Readback | After apply, run `portal get` and compare section count, refs, and positions before claiming frontend visibility. |
 
 Inline QingBI chart creation uses one chart job per section and runs with an internal concurrency limit of 10. If two sections declare the same `app_key + name + chart_type` with identical config, CLI creates/updates once and reuses the chart id. If their config differs, CLI rejects the portal write as a duplicate inline chart conflict.
@@ -90,7 +90,7 @@ Recommended standard workbench skeleton:
 
 搭建侧稳定入口：**`qingflow builder portal`**：`list` / `get` / **`apply`** / **`delete`**（与根命令 **`qingflow portal`** 的「成员可读列表/详情」不同，见 **[QINGFLOW_CLI_EXPLORATION_REPORT.md](../core/QINGFLOW_CLI_EXPLORATION_REPORT.md) §4.6**）。
 
-实现要点来自 CLI 打包内的 `builder_facade/models.py`（`PortalApplyRequest`、`PortalSectionPatch`）、`builder_facade/service.py`（`portal_apply` / `portal_delete`）、`cli/commands/builder.py`。已对 **`package_id=2030703`**、应用 **`ead8ims5i401`** **实跑**：**新建**（`--no-publish`）、**`--publish` 更新**（网关 **503** 恢复后已重试成功）、**五类区块可稳定落库**；**`filter`（`type:6`）经 CLI 直传未落库** 见 **§3.4 / §8**。另已对测试包 **`1414907`** 实跑 **`portal delete`**：临时门户 **`etcivtmv5402`** 删除后回读 **`readback_status=deleted`**。
+实现要点来自 CLI 打包内的 `builder_facade/models.py`（`PortalApplyRequest`、`PortalSectionPatch`）、`builder_facade/service.py`（`portal_apply` / `portal_delete`）、`cli/commands/builder.py`。已对 **`package_id=2030703`**、应用 **`ead8ims5i401`** **实跑**：**新建**（`--no-publish`）、**`--publish` 更新**（网关 **503** 恢复后已重试成功）、**五类区块可稳定落库**；**`filter` 声明式写入受控支持（rules 非空,历史「不落库」实测为空规则读面不可见,见 §3.4）**。另已对测试包 **`1414907`** 实跑 **`portal delete`**：临时门户 **`etcivtmv5402`** 删除后回读 **`readback_status=deleted`**。
 
 > **权限**：**更新**需 **`edit_portal`**；**新建**按后端 `DashCtrl.createDash` 链路只预检目标包 **`add_app`**，不额外要求包 **`edit_app`**。失败时参见主技能与 **ADMIN** 速查。
 
@@ -214,7 +214,7 @@ mobile 固定按 **6 栅格** 从上到下堆叠：通常所有组件 `x=0, cols
 
 **当前工具边界**：
 
-- 声明式（`--file` / complete 档）支持**九类组件**：**`grid` / `chart` / `view` / `text` / `link`**（summary 档稳定面）+ **`carousel` / `task` / `favourite`**（complete 档，配置键见专项 Schema）+ **`filter`**（complete 档受控承载，仍按 **§3.4** raw 边界处理，不作为主路径）。
+- 声明式（`--file` / complete 档）支持**九类组件**：**`grid` / `chart` / `view` / `text` / `link`**（summary 档稳定面）+ **`carousel` / `task` / `favourite`**（complete 档，配置键见专项 Schema）+ **`filter`**（complete 档受控承载：`config.rules` 至少 1 组,空规则读面不可见、模型层阻断,见 **§3.4**）。
 - **`task`（一个门户最多 1 个）与 `favourite`（一个门户最多 1 个）** 已进入 v1alpha1 complete 声明面（`task`/`favourite` 类型化 config 键），不要再按后端 raw 形状（`taskConfig`/`favouriteConfig`）手拼；声明形态见 `qingflow --json builder portal schema --schema-kind task|favourite`。旧文档中的「task/favorite 不在公开合约里」已过时。
 - 推荐门户的可直接 apply 示例见 **[portal_sections_standard_workbench.example.json](../examples/portal/portal_sections_standard_workbench.example.json)**。这是唯一推荐复制的业务工作台布局模板：每一行 `cols_sum=24`，同行 `rows` 一致，下一行 `y` 连续。顶部先用一个业务入口 `grid` 占满 24 栅格；如果工具已支持待办组件，再把顶部拆成 `grid cols=12 + task cols=12`。
 - **[portal_sections_five_types.example.json](../examples/portal/portal_sections_five_types.example.json)** 和 **[portal_sections_all_types.example.json](../examples/portal/portal_sections_all_types.example.json)** 仅用于组件能力探针，不作为业务门户布局模板；搭建正式门户时不要从这些探针推导布局。
@@ -253,7 +253,7 @@ mobile 固定按 **6 栅格** 从上到下堆叠：通常所有组件 `x=0, cols
 | **`grid`** | **2** | 九宫格 | summary |
 | **`text`** | **5** | 富文本说明 | summary |
 | **`link`** | **4** | 外链 | summary |
-| **`filter`** | **6** | 筛选条 | complete（raw/unstable） |
+| **`filter`** | **6** | 筛选条 | complete（rules 必须非空） |
 | **`carousel`** | **3** | 轮播（数据源应用 + 标题/图片/链接字段） | complete |
 | **`task`** | **8** | 待办（一个门户最多 1 个） | complete |
 | **`favourite`** | **7** | 收藏（一个门户最多 1 个） | complete |
@@ -292,14 +292,29 @@ CLI 校验（`PortalSectionPatch`）：**chart** 须 **`chart`** 或 **`chart_re
 }
 ```
 
-### 3.4 **`filter`**：`config` **整包**即接口里的 **`filterConfig`**
+### 3.4 **`filter`**：声明式筛选条（支持,**rules 必须非空**）
 
-实现：组件为 **`{"type": 6, "filterConfig": deepcopy(section.config)}`**。
+声明形态:**`config.graphs`**(受筛选作用的图表引用)+ **`config.rules`**(筛选规则组,至少 1 组),编译为后端 `ComponentFilter`(`graphList` + `filterConfig`)。规则键集:`filterGroupName`(组名)/`filterGroupConfig`(筛选项:`filterItemName` + `que{queId}` + `judge{judgeType,judgeValues}`);代理键 `filterGroupId`/`filterItemId` 为后端自增位移键,声明里不要携带。
 
-- **理论上**与 solution 编译器一致：外层 **`{"filterConfig": [ … ], "graphList": [ … ]}`**；**`graphList`** 常含 **`graphType`**（如 **`CHART`**）、**`graphKey`** 或 **`graphRef`（`entity_id` / `chart_id`）** 等。
-- **本环境 CLI 直写实测（多次 `--publish`）**：在已验证 **chart / view / grid / text / link** 均可落库的前提下，**`source_type: filter` 始终未出现在 `draft_result.components` 中**；尝试过：**空数组**、**仅 `graphList` + QingBI `chart_id`**、**`graphKey` 为门户 `dashChartId`**、**`chart` 排在 **`filter` 前**、**仅 2 块（chart+filter）** 等，回读仍 **只有 chart（`count: 1`）** 或 **五类缺 `type: 6`**。
-  **结论**：当前宜 **在搭建界面创建筛选条**，再 **`builder portal get` 反抓** 原始 `filterConfig` 形状；或向后端确认 **POST `/dash/{dashKey}`** 对 **`type: 6`** 的必填字段。**自动化不要默认认为 `filter` 已写入。**
-- portal `filter` 组件仍按 raw `filterConfig` 处理，不纳入视图 / 报表 / 关联资源的统一筛选 DSL 主链路。
+```json
+{
+  "source_type": "filter",
+  "position": {"pc": {"x": 0, "y": 0, "cols": 24, "rows": 3}},
+  "config": {
+    "graphs": [{"chart_key": "CHART_KEY_1001"}],
+    "rules": [
+      {
+        "filterGroupName": "区域",
+        "filterGroupConfig": [
+          {"filterItemName": "城市", "que": {"queId": 123456}, "judge": {"judgeType": 3, "judgeValues": ["上海"]}}
+        ]
+      }
+    ]
+  }
+}
+```
+
+**关键边界(旧实测记录的真相)**:`rules` 为空的 filter **会被模型层直接拒绝**——后端读面按筛选组(dash_filter_group 行)反查筛选组件,空规则的组件行虽写入但读面枚举不到,表现为「apply 成功、回读缺 type:6」。历史上「filter 不落库」的实测记录(命令式 raw 直传时代、全部空规则组合)即此机制,不是后端拒绝 type:6。存量筛选组件合法无标题(提取产物不带 `title`,不要合成);round-trip 重放已验证(ws40013 基准 337 个 filter 组件一致率 100%)。专项 Schema:`qingflow --json builder portal schema --schema-kind filter`。
 
 ### 3.5 **`grid` / `text` / `link` / `view`**
 
@@ -360,8 +375,8 @@ qingflow --json builder portal delete --dash-key "<DASH_KEY>" > tmp/builder_port
 | 步骤 | 命令要点 | 结果 |
 |------|-----------|------|
 | 新建门户 | `--package-id 2030703`、`--dash-name "CLI门户探针_可删"`、`--no-publish`、单 **view** | **`dash_key`: `ecdcell64s02`** |
-| 503 后重试 | **`--dash-key ecdcell64s02`、`--publish`** + 含 **filter** 的六类 **`sections-file`** | **`published: true`**；**`filter` 仍不落库** → **`partial_success`**，**`components expected 6, got 5`**（与 **§3.4** 一致） |
-| **filter 专项** | 仅 **chart + filter** 两块的多种 **`graphList`/`graphRef`/`dashChartId`/`filterGroupConfig`** 组合 | **回读恒为 1 块（仅 `type: 9`）** |
+| 503 后重试 | **`--dash-key ecdcell64s02`、`--publish`** + 含 **filter** 的六类 **`sections-file`** | **`published: true`**；当时 filter 组合全部**空 rules** → 读面不可见（**§3.4** 机制,非后端拒绝;现空 rules 已被模型层阻断） |
+| **filter 专项** | 仅 **chart + filter** 两块的多种 **`graphList`/`graphRef`/`dashChartId`/`filterGroupConfig`** 组合（历史记录,全部空 rules） | **回读恒为 1 块（仅 `type: 9`）**——空规则读面不可见;含 rules 的声明式写入已由 ws40013 基准验证 |
 | **稳定可复现** | **`--publish`** + **[portal_sections_five_types.example.json](../examples/portal/portal_sections_five_types.example.json)**（**grid / text / link / view / chart**） | **`status: success`**，**`types: [2,4,5,9,10]`**，**`published: true`** |
 | 删除门户 | `builder portal delete --dash-key etcivtmv5402` | **`status: success`**，**`delete_executed: true`**，**`readback_status: deleted`**，**`summary.removed: 1`** |
 
@@ -376,7 +391,7 @@ qingflow --json builder portal delete --dash-key "<DASH_KEY>" > tmp/builder_port
 | 现象 | 处理 |
 |------|------|
 | `portal apply accepts exactly one selector mode` | **`dash-key`** vs **`package-id`** 二选一。 |
-| `PORTAL_READBACK_PENDING` / **`components expected N, got M`** | **`portal get`** 数组件；若多写了 **`filter`** 而回读少一块，见 **§3.4**（**CLI 写 filter 可能整体不生效**）；也可能是 **异步回读**，可再 **`get`** 一次。 |
+| `PORTAL_READBACK_PENDING` / **`components expected N, got M`** | **`portal get`** 数组件；`filter` 回读缺失多为 **空 rules**（模型层已阻断,检查报错）或 **异步回读**（可再 **`get`** 一次）；含规则的 filter 写入正常（见 **§3.4**）。 |
 | **`published: true` 但 `verified: false`** | 读 **§7**；用 **`get` 草稿+线上**对照。 |
 | **503** | 网关/运维；稍后重试。 |
 | 缺 **chart** | 在对应 portal section 写 **`chart`**；或换用已有报表的 **`chart: {"chart_id": "..."}`** / 兼容旧 **`chart_ref`**。 |

package/src/qingflow_mcp/builder_facade/models.py

@@ -2724,6 +2724,18 @@ class PortalSectionPatch(StrictModel):
             raise ValueError("task section requires task")
         if self.source_type == "favourite" and self.favourite is None:
             raise ValueError("favourite section requires favourite")
+        if self.source_type == "filter":
+            # 后端读面(DashSvcImpl#getComponentFilter)按筛选组(dash_filter_group 行)
+            # 反查筛选组件:空规则的 filter 组件行虽会写入,但读面枚举不到——表现为
+            # 「apply 成功但回读缺 type:6」(实测反馈「filter 不落库」的真身)。
+            # 在模型咽喉(apply/validate 共同路径)阻断,不给静默不可见留门。
+            filter_payload = self.config or {}
+            rule_groups = filter_payload.get("rules", filter_payload.get("filterConfig"))
+            if not isinstance(rule_groups, list) or not rule_groups:
+                raise ValueError(
+                    "filter section requires config.rules with at least one rule group; "
+                    "an empty-rules filter is written but invisible in portal get readback"
+                )
         return self
 
 

package/src/qingflow_mcp/builder_facade/schemas/portals/v1alpha1/complete.json

@@ -944,7 +944,7 @@
     "FilterConfig": {
       "type": "object",
       "additionalProperties": false,
-      "filterConfigShapeDescription": "筛选组件配置(受控键集;filter 组件语义 raw/unstable,不建议作为主自动化路径)。graphs 为受影响的图表引用,rules 为筛选规则组(键集以 ws40013 dataset 实测形态定稿)。",
+      "filterConfigShapeDescription": "筛选组件配置(受控键集)。graphs 为受影响的图表引用;rules 为筛选规则组,键集 filterGroupName/filterGroupConfig/filterItemName/que/judge 系(受控透传,dataset 实测形态定稿;代理键 filterGroupId/filterItemId 剔除)。rules 必须至少 1 组——后端读面按筛选组反查筛选组件,空规则的 filter 写入后读面不可见(模型层已阻断)。",
       "properties": {
         "graphs": {
           "type": "array",
@@ -965,7 +965,7 @@
         },
         "rules": {
           "type": "array",
-          "filterRulesDescription": "筛选规则组(受控透传;dataset 校准后开放规范键)。",
+          "filterRulesDescription": "筛选规则组(至少 1 组;空规则组件读面不可见)。组键 filterGroupName(必填)/filterGroupConfig(筛选项:filterItemName/que{queId}/judge{judgeType,judgeValues})。",
           "x-backend": "ComponentFilter.filterConfig(List<FilterConfig>)"
         }
       }

package/src/qingflow_mcp/builder_facade/schemas/portals/v1alpha1/components/filter.json

@@ -57,9 +57,9 @@
       "type": "object",
       "additionalProperties": false,
       "required": [
-        "groups"
+        "rules"
       ],
-      "filterConfigShapeDescription": "筛选组件配置。筛选语义 raw/unstable,不建议作为主自动化路径;条件明细为受控透传(键集以 ws40013 dataset 实测形态定稿)。",
+      "filterConfigShapeDescription": "筛选组件配置。rules 必须非空——后端读面(DashSvcImpl#getComponentFilter)按筛选组(dash_filter_group 行)反查筛选组件,空规则的 filter 组件行虽会写入但读面枚举不到,表现为「apply 成功、回读缺该组件」;规则键集为受控透传(filterGroupName/filterGroupConfig/filterItemName/que/judge 系,以 ws40013 dataset 实测形态定稿)。",
       "properties": {
         "graphs": {
           "type": "array",
@@ -69,12 +69,12 @@
           },
           "x-backend": "ComponentFilter.graphList(GraphVO.graphKey/graphName/graphType)"
         },
-        "groups": {
+        "rules": {
           "type": "array",
           "minItems": 1,
-          "filterGroupsShapeDescription": "筛选规则组。",
+          "filterRulesShapeDescription": "筛选规则组(至少 1 组)。组键:filterGroupName(组名,必填)、filterGroupConfig(组内筛选项列表);项键:filterItemName、que{queId}(绑定字段)、judge{judgeType,judgeValues}(默认条件)。代理键 filterGroupId/filterItemId 为后端自增位移键,读写两侧均剔除,不要携带。",
           "items": {
-            "$ref": "#/$defs/FilterGroup"
+            "$ref": "#/$defs/FilterRuleGroup"
           },
           "x-backend": "ComponentFilter.filterConfig(List<FilterConfig>)"
         }
@@ -109,71 +109,49 @@
         }
       }
     },
-    "FilterGroup": {
+    "FilterRuleGroup": {
       "type": "object",
-      "additionalProperties": false,
       "required": [
-        "items"
+        "filterGroupName"
       ],
-      "filterGroupShapeDescription": "筛选规则组。",
+      "filterRuleGroupShapeDescription": "筛选规则组。组内筛选项走 filterGroupConfig;其余后端键受控透传。",
       "properties": {
-        "group_id": {
-          "type": "integer",
-          "filterGroupIdShapeDescription": "组 id(更新已有组时锚定;缺省新建)。",
-          "x-backend": "FilterConfig.filterGroupId"
-        },
-        "name": {
+        "filterGroupName": {
           "type": "string",
-          "filterGroupNameShapeDescription": "组名称。",
+          "filterRuleGroupNameShapeDescription": "组名称(读面渲染为分组标题)。",
           "x-backend": "FilterConfig.filterGroupName"
         },
-        "items": {
+        "filterGroupConfig": {
           "type": "array",
-          "minItems": 1,
-          "filterGroupItemsShapeDescription": "组内筛选项。",
+          "filterRuleGroupItemsShapeDescription": "组内筛选项(绑定字段与默认条件)。",
           "items": {
-            "$ref": "#/$defs/FilterItem"
-          }
+            "$ref": "#/$defs/FilterRuleItem"
+          },
+          "x-backend": "FilterConfig.filterGroupConfig(List<FilterGroupConfig>)"
         }
       }
     },
-    "FilterItem": {
+    "FilterRuleItem": {
       "type": "object",
-      "additionalProperties": false,
       "required": [
-        "name"
+        "filterItemName"
       ],
-      "filterItemShapeDescription": "单个筛选项(绑定一个字段)。",
+      "filterRuleItemShapeDescription": "单个筛选项(绑定一个字段)。que/judge 为后端受控透传形态;条件表达式(关联图表/字段)键集以 dataset 实测形态为准。",
       "properties": {
-        "item_id": {
-          "type": "integer",
-          "filterItemIdShapeDescription": "筛选项 id(更新锚定)。",
-          "x-backend": "FilterGroupConfig.filterItemId"
-        },
-        "name": {
+        "filterItemName": {
           "type": "string",
-          "filterItemNameShapeDescription": "筛选项名称。",
+          "filterRuleItemNameShapeDescription": "筛选项名称。",
           "x-backend": "FilterGroupConfig.filterItemName"
         },
-        "conditions": {
-          "type": "array",
-          "filterItemConditionsShapeDescription": "筛选条件(受控透传;条件表达式键集以 dataset 实测形态定稿后开放规范键)。",
-          "x-backend": "FilterGroupConfig.filterCondition(List<FilterCondition>)"
-        },
-        "default_judge_type": {
-          "type": "integer",
-          "filterItemDftJudgeTypeShapeDescription": "默认比较符。",
-          "x-backend": "FilterGroupConfig.dftJudgeType"
-        },
-        "default_values": {
-          "type": "array",
-          "filterItemDftValuesShapeDescription": "默认比较值(受控透传)。",
-          "x-backend": "FilterGroupConfig.dftJudgeValue(List<AnswerValue>)"
+        "que": {
+          "type": "object",
+          "filterRuleItemQueShapeDescription": "绑定的字段引用(queId 为字段唯一键)。",
+          "x-backend": "FilterGroupConfig.que(Question)"
         },
-        "filter_type": {
-          "type": "string",
-          "filterItemTypeShapeDescription": "筛选项交互类型(受控枚举,dataset 校准)。",
-          "x-backend": "FilterGroupConfig.filterType"
+        "judge": {
+          "type": "object",
+          "filterRuleItemJudgeShapeDescription": "默认筛选条件:judgeType(比较符)+judgeValues(比较值列表)。",
+          "x-backend": "FilterGroupConfig.dftJudgeType/dftJudgeValue"
         }
       }
     },
@@ -181,16 +159,14 @@
       "type": "object",
       "additionalProperties": false,
       "required": [
-        "title",
         "source_type",
         "config"
       ],
       "properties": {
         "title": {
           "type": "string",
-          "minLength": 1,
-          "sectionTitleShapeDescription": "组件标题(渲染在组件头部)。",
-          "x-backend": "组件标题(DashChartInfo.title / gridConfig.gridTitle 等)"
+          "sectionTitleShapeDescription": "组件标题(可选)。存量筛选组件合法无标题——后端筛选组件无标题存储,提取产物不带 title,不要合成(如「组件 N」)。",
+          "x-backend": "组件标题(筛选组件无标题存储;其余组件见 DashChartInfo.title / gridConfig.gridTitle 等)"
         },
         "source_type": {
           "const": "filter",
@@ -211,7 +187,7 @@
         },
         "config": {
           "$ref": "#/$defs/FilterConfig",
-          "filterConfigPropDescription": "筛选配置(必填,groups 非空)。"
+          "filterConfigPropDescription": "筛选配置(必填,rules 至少 1 组)。"
         }
       }
     }
@@ -230,7 +206,6 @@
   },
   "examples": [
     {
-      "title": "数据筛选",
       "source_type": "filter",
       "position": {
         "pc": {
@@ -249,15 +224,21 @@
             "chart_name": "故障类型分布"
           }
         ],
-        "groups": [
+        "rules": [
           {
-            "name": "默认组",
-            "items": [
+            "filterGroupName": "区域",
+            "filterGroupConfig": [
               {
-                "name": "报修日期",
-                "default_judge_type": 1,
-                "default_values": [],
-                "filter_type": "dateRange"
+                "filterItemName": "城市",
+                "que": {
+                  "queId": 123456
+                },
+                "judge": {
+                  "judgeType": 3,
+                  "judgeValues": [
+                    "上海"
+                  ]
+                }
               }
             ]
           }