fix: some
All checks were successful
构建并部署前端到生产环境 / build-and-deploy (push) Successful in 2m59s

This commit is contained in:
luo
2026-10-13 14:53:19 +08:00
parent 77b0e25011
commit da95a914e3
31 changed files with 1702 additions and 116 deletions

View File

@@ -0,0 +1,27 @@
## ADDED Requirements
### Requirement: Customer phone changes SHALL leave asset phone associations unchanged
H5 SHALL 按当前 F1 契约调用 `POST /api/c/v1/auth/change-phone`,只更换客户手机号。原/新号码及验证码入参、`change_phone_old` / `change_phone_new` 场景 SHALL 保持不变;H5 SHALL NOT 将客户新号写入资产关联缓存或宣称所有资产关联已迁移。
#### Scenario: Customer changes to a different phone
- **WHEN** 客户换号成功,后端确认新客户手机号
- **THEN** H5 SHALL 更新客户手机号及后续换号的原号来源
- **AND** SHALL 保持资产关联不变,不调用新号写入资产绑定缓存的逻辑
#### Scenario: Asset ownership fact becomes stale
- **WHEN** 客户更换为不同号码,原归属事实为 true,响应未返回最新资产归属
- **THEN** H5 SHALL 失效旧 `asset_phone_is_own` 事实,等真实登录响应确认
- **AND** SHALL NOT 将资产误标为未绑定或要求重新绑定
### Requirement: Customer phone change failures SHALL preserve existing state
H5 SHALL 在换号失败时展示后端错误并留在表单,保留原客户及资产状态;SHALL NOT 套用旧“全部资产事务迁移/回滚”的假设或固定文案。
#### Scenario: Change-phone returns a business error
- **WHEN** 换号请求失败
- **THEN** H5 SHALL 显示实际错误消息并留在页面
- **AND** SHALL NOT 更新客户号码、资产号码或缓存