@guanlin4924/devflow-pi 0.1.86 → 0.1.88

package/plugins/devflow-quality/skills/workflow-gen-test-guide/legacy/references/test-type-slots/api-test.md

@@ -0,0 +1,58 @@
+# API Test Slot
+
+## Applies When
+
+Expanding nodes from:
+- API/服务 section in feature-breakdown
+- Any leaf describing API calls, service triggers, callbacks, idempotency, retry
+
+## Required Fields
+
+- **前置条件**: API path, request parameters, authentication method, mock data setup
+- **测试步骤**: construct request → send → verify response
+- **预期结果**: HTTP status code, response body structure, error code, side effects
+
+## Common Patterns
+
+API trigger:
+```
+- 功能: 每月1日独立任务自动触发
+```
+→ Test case: "每月1日回刷任务自动触发测试"
+- Verify task starts at expected time
+
+API calculation:
+```
+- 逻辑: 回刷后佣金金额 = 原佣金 × (最终分成比例 / 80%)
+  原佣金 100, 新比例 90% → 预期 112.5
+```
+→ Test case: "佣金回刷计算准确性测试"
+
+Idempotency:
+```
+- 功能: 重复执行回刷任务 → 幂等, 不重复累加佣金
+```
+→ Test case: "回刷任务重复执行幂等测试"
+- Execute same batch twice, verify commission unchanged
+
+Retry:
+```
+- 功能: 部分客户回刷失败 → 自动重试, 记录失败原因
+```
+→ Test case: "回刷失败自动重试测试"
+
+Callback:
+```
+- 功能: 回调失败 → 重试机制
+```
+→ Test case: "回调失败重试测试"
+
+## Quality Checklist
+
+- [ ] Normal request/response verified
+- [ ] Parameter validation covered: required, type, range, boundary
+- [ ] Idempotency: repeated request produces no side effects
+- [ ] Retry mechanism verified (if applicable)
+- [ ] Callback handling verified (if applicable)
+- [ ] Error codes and error messages are specific
+- [ ] Authentication/authorization validated at API level

package/plugins/devflow-quality/skills/workflow-gen-test-guide/legacy/references/test-type-slots/boundary-test.md

@@ -0,0 +1,151 @@
+# Boundary Test Slot
+
+## Applies When
+
+Expanding nodes that involve:
+- Numeric constraints: min, max, threshold, step, range (e.g. 分成比例 0-100, 档位数 1-5, 金额上限)
+- Time constraints: effective/expiry switch, grace period end, monthly cutoff, daily deadline
+- State boundary: condition just met / just not met for state transition
+- Capacity constraints: max items, max rows, max file size, max concurrent
+- Order/rank boundary: first position, last position, just promoted, just demoted
+
+Always load before writing boundary test cases. Boundary tests belong in **02-场景类/异常场景** or as a separate **边界场景** subsection.
+
+## Generation Rules
+
+### Rule 1: Numeric Boundary — 界内/界上/界外
+
+For every numeric constraint in the feature-breakdown, generate three test cases:
+
+```
+约束: 分成比例 0-100, 正整数
+→ 界内: 80 (合法值) — "分成比例80正常提交测试"
+→ 界上: 100 (最大值) — "分成比例100允许提交测试"
+→ 界上: 1 (最小值) — "分成比例1允许提交测试"
+→ 界外: 0 — "分成比例0阻断提交测试"
+→ 界外: 101 — "分成比例101阻断提交测试"
+→ 界外: -1 — "分成比例负数阻断提交测试"
+→ 界外: 1.5 — "分成比例小数阻断提交测试"
+```
+
+```
+约束: 档位数 1-5, 第5档后新增置灰
+→ 界内: 3档 — "3个档位正常展示测试"
+→ 界上: 5档 — "5个档位新增按钮置灰测试"
+→ 界外: 尝试新增第6档 — "第6档新增按钮不可点击测试"
+```
+
+```
+约束: 阶梯补贴 < 20 的正整数
+→ 界内: 5 — "阶梯补贴5正常提交测试"
+→ 界上: 19 — "阶梯补贴19正常提交测试"
+→ 界外: 20 — "阶梯补贴20阻断提交测试"
+→ 界外: 0 — "阶梯补贴0阻断提交测试"
+```
+
+```
+约束: 金额不超过云仓 CPA 上限 (5元)
+→ 界内: 3.00 — "金额3元正常提交测试"
+→ 界上: 5.00 — "金额等于上限允许提交测试"
+→ 界外: 5.01 — "金额超过上限0.01阻断提交测试"
+```
+
+### Rule 2: Time Boundary — 生效前/临界点/生效后
+
+For every time constraint in the feature-breakdown, generate:
+
+```
+约束: 配置修改下个自然月生效 (当月15日修改)
+→ 生效前: 当月16日计算 — "当月仍按旧配置计算测试"
+→ 临界点: 当月最后一天 — "当月最后一天仍按旧配置测试"
+→ 生效后: 次月1日0:00 — "次月1日起按新配置计算测试"
+```
+
+```
+约束: 白名单删除次月生效 (5月20日删除)
+→ 删除前: 5月21日回刷 — "当月仍按白名单计算测试"
+→ 临界点: 5月31日 — "月末最后一天仍按白名单测试"
+→ 失效后: 6月1日 — "次月起参与统一爬坡测试"
+```
+
+```
+约束: 回刷1日8:00前完成
+→ 正常: 1日7:30完成 — "8:00前完成回刷任务测试"
+→ 边界: 1日7:59完成 — "临界时间完成测试"
+→ 超时: 1日8:01未完成 — "回刷超时告警测试"
+```
+
+```
+约束: 保档3个自然月 (1月达成第三档, 保档1-3月)
+→ 保档中: 2月考核 — "保档第二月仍按保档阶梯测试"
+→ 临界点: 3月重新考核 — "保档第三月重新考核测试"
+→ 达标续期: 3月达标 — "保档续期3个月测试"
+→ 未达标降档: 3月未达标 — "4月降档到实际订单所属档位测试"
+```
+
+```
+约束: 指定生效日期早于审批日 (指定5-1, 审批5-10)
+→ 审批通过后 — "按指定日期5-1生效测试"
+→ 回刷: 5月1-10日订单 — "允许补算/回刷测试"
+```
+
+### Rule 3: State Boundary — 切换前/切换条件/切换后
+
+For every state transition in the feature-breakdown, generate:
+
+```
+状态: 待审核 → 生效中 / 已拒绝
+→ 切换前: 待审核状态 — "待审核名单操作按钮展示测试"
+→ 切换-通过: 审核通过 — "名单状态变为生效中测试"
+→ 切换-拒绝: 审核拒绝 — "名单状态变为已拒绝测试"
+→ 切换后-生效中: — "生效中名单可修改可删除测试"
+→ 切换后-已拒绝: — "已拒绝名单只读测试"
+```
+
+```
+状态: 升级触发 (保档期内达成更高档)
+→ 切换前: 第二档保档中 — "保档第二档状态展示测试"
+→ 触发条件: 上月订单达第四档 — "达成更高档触发升档测试"
+→ 切换后: 立即升为第四档 — "保档期重置3个月测试"
+→ 回刷: 达成月份按新档回刷 — "达成月份订单回刷测试"
+```
+
+### Rule 4: Capacity Boundary — 空/满/超
+
+For every capacity constraint in the feature-breakdown, generate:
+
+```
+约束: 消息列表最近5条
+→ 空: 0条消息 — "无消息时展示空态测试"
+→ 不满: 3条消息 — "少于5条正常展示测试"
+→ 临界: 5条消息 — "刚好5条正常展示测试"
+→ 超: 6条消息 — "仅展示最近5条测试"
+```
+
+```
+约束: 第5档后新增按钮置灰
+→ 不满: 3档 — "新增按钮可点击测试"
+→ 临界: 5档 — "新增按钮置灰不可点击测试"
+```
+
+```
+约束: 大数据量导出
+→ 正常: 1000条 — "千级数据导出正常测试"
+→ 边界: 阈值条数 — "达到同步导出上限测试"
+→ 超: 超过阈值 — "触发异步导出测试"
+```
+
+## Required Fields
+
+- **前置条件**: the exact constraint value being tested (not "some value" — the exact boundary number)
+- **测试步骤**: set up the boundary condition → trigger the behavior → verify
+- **预期结果**: precise expected behavior at the boundary (允许/阻断/切换/不变)
+
+## Quality Checklist
+
+- [ ] For every numeric constraint field, 界内/界上/界外 cases generated
+- [ ] For every time constraint, 生效前/临界点/生效后 cases generated
+- [ ] For every state transition, 切换前/切换条件/切换后 cases generated
+- [ ] For every capacity constraint, 空/满/超 cases generated
+- [ ] Boundary values are exact numbers (not ranges like "a large number")
+- [ ] Expected results are specific to each boundary case

package/plugins/devflow-quality/skills/workflow-gen-test-guide/legacy/references/test-type-slots/common-test.md

@@ -0,0 +1,49 @@
+# Common Test Type Slot
+
+This slot applies to all checkpoint generation, regardless of type. Always load this slot before type-specific slots.
+
+## Applies When
+
+All checkpoint generation. Always loaded first.
+
+## Generic Constraints（叶子检查点通用约束）
+
+- 叶子是**一句话检查点**,不带任何字段块(无 优先级/关联/前置/步骤/预期)
+- 一个叶子只测一个目的
+- 叶子以动词起头,描述可观察、可验证的行为或结果
+- 叶子内容无模糊词("大概"/"可能"/"或"/"应该")
+- **边界值不合并**(每个边界独立成叶)
+- **FP 编号不进任何节点标题**(标题纯语义名,也不带章节号);FP 仅在文末「覆盖核对」表做追溯(见 writing-guide「FP 编号挂法」)
+
+## Priority Rules（用于决定展开深度,优先级不写进叶子）
+
+- P0 功能点:必须完整展开(正常+边界+异常+权限),不允许跳过
+- P1 功能点:完整展开,缺口需在"待确认测试项(PT-xxx)"注明
+- P2 功能点:主路径覆盖,边界可延迟(注明)
+
+## Output Format
+
+每个叶子只写一句话:
+
+```
+- 输入0或负数时提交阻断并提示
+- 未上传主图时保存阻断并提示必填
+```
+
+**不写**这种用例字段块形态(已废弃):
+
+```
+- xxx测试
+  - 优先级：P1        ❌ 叶子不带字段块
+  - 关联：FP-xxx      ❌
+  - 测试步骤：...      ❌
+  - 预期结果：...      ❌
+```
+
+## Verification Gates
+
+- [ ] 所有叶子是一句话,无字段块
+- [ ] 叶子无模糊词("大概"/"可能"/"或"/"应该")
+- [ ] 边界值是独立叶子,未合并
+- [ ] 标题纯语义名,无 FP 编号、无章节号残留(FP 只在覆盖核对表)
+- [ ] 无残留的用例字段块形态(优先级/关联/测试步骤/预期结果)

package/plugins/devflow-quality/skills/workflow-gen-test-guide/legacy/references/test-type-slots/compatibility-test.md

@@ -0,0 +1,105 @@
+# Compatibility Test Slot
+
+## Applies When
+
+Expanding nodes that involve:
+- Old/new version coexistence (old rules + new rules running in parallel)
+- Data migration / initialization from legacy system
+- Old data read-only after new system launch
+- Cross-version data format compatibility
+- No transition period (硬切换, 无过渡期)
+
+Compatibility test cases belong in **03-专项类/兼容测试**.
+
+## Generation Rules
+
+### Rule 1: For every "下线" / "迁移" / "初始化" node — generate old-to-new transition cases
+
+```
+Pattern: 旧规则下线, 新规则上线
+→ Test case: "旧入口隐藏测试"
+  前置条件: 新系统已上线
+  步骤: 1.查看菜单 2.尝试访问旧URL
+  预期: 旧菜单不展示; 旧URL被拦截或重定向
+
+→ Test case: "旧数据保留只读测试"
+  前置条件: 旧数据存在
+  步骤: 1.查询旧数据 2.尝试编辑/删除
+  预期: 可查询; 不可新建/编辑/删除
+
+→ Test case: "旧规则不再参与计算测试"
+  前置条件: 客户同时有旧规则和新阶梯结果
+  步骤: 1.触发佣金计算 2.查看使用的规则
+  预期: 仅使用新规则; 旧规则不参与计算
+```
+
+### Rule 2: For every "初始化" node — generate data migration cases
+
+```
+Pattern: 历史数据初始化进入新系统
+→ Test case: "初始化数据导入测试"
+  前置条件: 准备初始化名单文件
+  步骤: 1.执行导入 2.查看导入结果
+  预期: 数据正确导入; 状态默认生效通过; 来源标识为"初始化"
+
+→ Test case: "初始化数据与后续新增数据区分测试"
+  前置条件: 初始化数据和后续新增数据共存
+  步骤: 1.查看列表 2.对比来源字段
+  预期: 初始化数据来源可追踪; 与后续新增数据区分
+```
+
+### Rule 3: For every "生效时间" / "切换时间" node — generate cutover cases
+
+```
+Pattern: 新规则 2026-06 生效, 无过渡期
+→ Test case: "2026-05仍按旧规则结算测试"
+  前置条件: 时间 = 2026年5月
+  步骤: 1.触发5月结算
+  预期: 按旧规则结算
+
+→ Test case: "2026-06起按新规则结算测试"
+  前置条件: 时间 = 2026年6月
+  步骤: 1.触发6月结算
+  预期: 按新规则(白名单+新阶梯)结算; 不使用旧规则
+
+→ Test case: "无过渡期直接切换测试"
+  前置条件: 对比5月和6月结算规则
+  步骤: 1.查看5月和6月结算使用的规则
+  预期: 5月使用旧规则; 6月使用新规则; 中间无过渡策略
+```
+
+### Rule 4: For every "权限码" / "权限体系" node — generate old permission compatibility cases
+
+```
+Pattern: 老权限码绑定不应暴露旧入口
+→ Test case: "老权限码绑定不暴露旧入口测试"
+  前置条件: 账号有旧"联盟客户(旧)"权限码
+  步骤: 1.登录后台 2.查看菜单
+  预期: 不展示"联盟客户(旧)"和"分成规则"入口
+```
+
+### Rule 5: For every "文案调整" / "字段变更" node — generate display change cases
+
+```
+Pattern: "饿了么专场" → "淘宝闪购数据"
+→ Test case: "淘宝闪购数据文案替换测试"
+  前置条件: 进入详情页
+  步骤: 1.查看原"饿了么专场"相关内容
+  预期: 文案已调整为"淘宝闪购数据"; 数据查询能力不变
+```
+
+## Required Fields
+
+- **前置条件**: old version state, new version state, cutover time
+- **测试步骤**: operate before cutover → operate at cutover → operate after cutover
+- **预期结果**: behavior difference between old and new system
+
+## Quality Checklist
+
+- [ ] Old entry points hidden (menus, buttons, URLs)
+- [ ] Old data accessible as read-only but not editable
+- [ ] Old rules not participating in new calculations
+- [ ] Cutover date is precise (which month/day the switch happens)
+- [ ] Initialization data is traceable and distinguishable from new data
+- [ ] No transition period means immediate switch (not gradual rollover)
+- [ ] Old permission codes don't leak old entry points

package/plugins/devflow-quality/skills/workflow-gen-test-guide/legacy/references/test-type-slots/data-test.md

@@ -0,0 +1,67 @@
+# Data Test Slot
+
+## Applies When
+
+Expanding nodes from feature-breakdown:
+- `- 逻辑` entries
+- `- 逻辑验证` entries
+- Any leaf describing: calculation formulas, statistics, status transitions, rule priority, data source, data consistency
+
+## Required Fields
+
+- **前置条件**: specific input data values (not "some data" — exact numbers)
+- **测试步骤**: input values → trigger calculation → compare result
+- **预期结果**: precise to decimal places, units, format
+
+## Common Patterns
+
+Calculation formula:
+```
+- 逻辑: 实际到账分成比 = 80% + 阶梯补贴
+  阶梯补贴 = 10% → 预期实际到账比例 = 90%
+```
+→ Test case: "实际到账分成比计算准确性测试"
+- Input: 阶梯补贴 = 10
+- Expected: 实际到账比例 = 90%
+
+Statistics:
+```
+- 逻辑: 日均订单数 = 总订单笔数 / 筛选自然日, 精确到个位数, 非四舍五入
+  总订单 = 100, 自然日 = 30 → 预期 3 (not 3.33)
+```
+→ Test case: "日均订单数精确到个位数非四舍五入测试"
+
+Rule priority:
+```
+- 逻辑: 白名单优先级 > 新阶梯 > 旧规则
+  客户同时有白名单(95%)和新阶梯(85%) → 使用 95%
+```
+→ Test case: "白名单优先级高于新阶梯测试"
+
+Data source:
+```
+- 逻辑: 数据来源为当前登录联盟客户信息
+```
+→ Test case: "客户名称数据来源准确性测试"
+- Compare with account settings
+
+Data consistency:
+```
+- 逻辑: 消息已读状态与消息列表页一致
+```
+→ Test case: "消息已读状态跨页面一致性测试"
+
+Status transition:
+```
+- 逻辑: 审批状态流转: 待审核 → 生效中 / 已拒绝
+```
+→ Test case: "审批状态流转准确性测试"
+
+## Quality Checklist
+
+- [ ] Calculation formula: input / output / precision verified
+- [ ] Data source matches baseline (BR-xxx or FP-xxx)
+- [ ] Rule priority covered (e.g., whitelist > new tier > old rules)
+- [ ] Data consistency across pages verified (same field, same value)
+- [ ] Status transitions mapped and verified
+- [ ] Units and format explicitly stated (元, %, 万, yyyy-MM-dd)

package/plugins/devflow-quality/skills/workflow-gen-test-guide/legacy/references/test-type-slots/exception-test.md

@@ -0,0 +1,109 @@
+# Exception Test Slot
+
+## Applies When
+
+Expanding nodes that involve exception handling:
+- API timeout, network failure, server error
+- Data validation failure (required field empty, format mismatch, duplicate)
+- Business rule violation (insufficient balance, permission denied, status conflict)
+- Concurrency conflicts (two users operating same resource)
+- Partial failure (batch job with some items failing)
+- Bypass scenarios (direct URL access, skipping required steps)
+
+Exception test cases belong in **02-场景类/异常场景**.
+
+Use `references/exception-checklist.md` to identify what exceptions exist, then use this slot to generate the test cases.
+
+## Generation Rules
+
+### Rule 1: For every "接口" or "API" node — generate API failure cases
+
+```
+Pattern: 接口超时/失败 → 用户看到什么, 操作是否保留
+→ Test case: "接口超时时展示错误提示测试"
+  - 前置条件: Mock 接口返回 timeout
+  - 测试步骤: 1.触发操作 2.等待超时
+  - 预期结果: 展示错误提示; 当前页面不崩溃; 用户可重试
+
+→ Test case: "接口返回500时展示错误提示测试"
+  - 前置条件: Mock 接口返回 500
+  - 测试步骤: 1.触发操作
+  - 预期结果: 展示错误提示; 弹窗不关闭 (如为弹窗内操作)
+```
+
+### Rule 2: For every "校验" node — generate validation failure cases
+
+```
+Pattern: 必填校验 / 格式校验 / 唯一性校验
+→ Test case: "XX字段为空时提交阻断测试"
+  前置条件: 打开表单, XX字段为空
+  步骤: 1.点击提交 2.验证阻断
+  预期: 阻断提交; 提示"请输入XX"
+
+→ Test case: "XX字段格式错误时提交阻断测试"
+  前置条件: XX字段输入非法格式
+  步骤: 1.点击提交
+  预期: 阻断提交; 提示具体格式要求
+
+→ Test case: "XX重复时提交阻断测试"
+  前置条件: 已有相同XX的记录
+  步骤: 1.输入重复值 2.提交
+  预期: 阻断提交; 提示"XX已存在"
+```
+
+### Rule 3: For every "权限" node — generate bypass cases
+
+```
+Pattern: 按钮不显示 + 接口层校验
+→ Test case: "绕过前端直接调用接口返回无权限测试"
+  前置条件: 无权限账号已登录
+  步骤: 1.获取接口路径和参数 2.绕过前端直接发送请求
+  预期: 接口返回无权限错误 (非200)
+```
+
+### Rule 4: For every concurrent operation — generate race condition cases
+
+```
+Pattern: 同一资源被两人同时操作
+→ Test case: "并发操作冲突测试"
+  前置条件: 两个账号同时打开同一资源
+  步骤: 1.用户A点击删除 2.用户B同时点击删除
+  预期: 仅一人成功; 另一人收到"资源已被操作"提示
+```
+
+### Rule 5: For every batch/task/job — generate partial failure cases
+
+```
+Pattern: 批量任务部分失败
+→ Test case: "回刷任务部分失败自动重试测试"
+  前置条件: Mock 部分客户回刷失败
+  步骤: 1.触发回刷任务 2.观察失败处理
+  预期: 成功客户正常更新; 失败客户自动重试; 失败原因记录到日志
+```
+
+### Rule 6: For every 幂等 requirement — generate idempotency cases
+
+```
+Pattern: 重复执行不产生副作用
+→ Test case: "回刷任务重复执行幂等测试"
+  前置条件: 同一批次回刷已完成
+  步骤: 1.再次执行同一批次回刷 2.对比结果
+  预期: 佣金金额不变; 不重复累加
+```
+
+## Required Fields
+
+- **前置条件**: mock condition (timeout / error code / empty data / concurrency setup)
+- **测试步骤**: trigger exception → observe error handling → verify recovery
+- **预期结果**: error message displayed; user action preserved or rollback; page not crashed; retry available (if applicable)
+
+## Quality Checklist
+
+- [ ] Every API-dependent operation has: timeout case + server error case
+- [ ] Every validation rule has: empty + invalid format + boundary violation cases
+- [ ] Every permission control has: frontend hide + API bypass rejection
+- [ ] Every concurrent scenario has: two-user race condition
+- [ ] Every batch job has: partial failure + retry cases
+- [ ] Every idempotency requirement has: repeated execution case
+- [ ] Error messages are concrete (not "操作失败" but specific like "该客户在白名单内且已生效")
+- [ ] Error state is recoverable (user can retry or go back)

package/plugins/devflow-quality/skills/workflow-gen-test-guide/legacy/references/test-type-slots/function-test.md

@@ -0,0 +1,65 @@
+# Function Test Slot
+
+## Applies When
+
+Expanding nodes from feature-breakdown:
+- `- 功能` entries
+- `- 功能验证` entries
+- Any leaf describing user interaction, system response, validation, navigation, button behavior
+
+## Required Fields
+
+- **前置条件**: role permissions, data state, current page
+- **测试步骤**: action → observe response → verify result
+- **预期结果**: state change after action, navigation target, data update, error message shown
+
+## Common Patterns
+
+Button click → dialog:
+```
+- 功能: 点击后弹出"新增"弹窗
+```
+→ Test case: "点击按钮弹出新增弹窗测试"
+- Normal scenario: click → dialog opens
+- Exception scenario: rapid double-click → only one dialog
+
+Validation — required field:
+```
+- 功能: 必填校验:为空时阻断并提示"请输入XXX"
+```
+→ Test case: "XXX字段为空时提交阻断测试"
+- Also cover: whitespace-only, extreme length, special characters
+
+Validation — uniqueness:
+```
+- 功能: 唯一性校验:重复时提示"XXX已存在"
+```
+→ Test case: "XXX重复创建阻断测试"
+
+Permission control:
+```
+- 功能: 无操作权限时按钮不显示
+```
+→ Test case: "无权限时操作按钮不显示测试"
+- Must verify: button is NOT displayed (not disabled, not greyed out)
+
+Duplicate submit prevention:
+```
+- 功能: 接口请求中按钮置灰,防止重复提交
+```
+→ Test case: "提交中按钮置灰防重复提交测试"
+
+API error:
+```
+- 功能: 接口异常时提示错误信息
+```
+→ Test case: "接口异常时展示错误提示测试"
+
+## Quality Checklist
+
+- [ ] Validation rules (required / format / length / uniqueness) are covered
+- [ ] Permission control: unauthorized buttons are "not displayed" (not disabled)
+- [ ] Duplicate submit prevention: button disabled during request
+- [ ] API error: error message shown, dialog stays open (if applicable)
+- [ ] Navigation/jump target is correct
+- [ ] Data refresh after successful operation is covered

package/plugins/devflow-quality/skills/workflow-gen-test-guide/legacy/references/test-type-slots/integration-test.md

@@ -0,0 +1,36 @@
+# Integration Test Slot
+
+## Applies When
+
+Expanding nodes involving:
+- Cross-module data flow
+- Cross-system data synchronization
+- Module-to-module data linkage
+- State change propagation across modules
+
+## Required Fields
+
+- **前置条件**: all involved modules/systems in known state
+- **测试步骤**: trigger change in module A → observe impact in module B
+- **预期结果**: data consistency, state synchronization, no orphan data
+
+## Common Patterns
+
+Cross-module data linkage:
+```
+模块A的数据变更 → 模块B展示更新后的数据
+```
+→ Test case: "模块间数据联动测试"
+
+Cross-system sync:
+```
+系统A的回刷结果 → 系统B的账单更新
+```
+→ Test case: "跨系统数据同步测试"
+
+## Quality Checklist
+
+- [ ] Data flows correctly between modules
+- [ ] State changes propagate correctly to related modules
+- [ ] No orphan data after cross-module operations
+- [ ] Data format consistent across system boundaries