From e8c8047b9515a3a9a772a0c9ff0498fb7d93410a Mon Sep 17 00:00:00 2001 From: Mimingguang <498526323@qq.com> Date: Thu, 24 Sep 2026 14:39:51 +0800 Subject: [PATCH] =?UTF-8?q?docs(changelog):=20#8330=20=E5=89=8D=E7=AB=AF?= =?UTF-8?q?=E5=B7=B2=E4=BA=A4=E4=BB=98=20verified(ref=3D8785efa8)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- ...ž‹与分组不符原因MEMBER_GROUP_MISMATCH与809125-修改接口-管理后台.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/changelogs-v2/2026-09/24_8330_团期整团确认预检新增车型与分组不符原因MEMBER_GROUP_MISMATCH与809125-修改接口-管理后台.md b/changelogs-v2/2026-09/24_8330_团期整团确认预检新增车型与分组不符原因MEMBER_GROUP_MISMATCH与809125-修改接口-管理后台.md index 778907d5..fa7d3503 100644 --- a/changelogs-v2/2026-09/24_8330_团期整团确认预检新增车型与分组不符原因MEMBER_GROUP_MISMATCH与809125-修改接口-管理后台.md +++ b/changelogs-v2/2026-09/24_8330_团期整团确认预检新增车型与分组不符原因MEMBER_GROUP_MISMATCH与809125-修改接口-管理后台.md @@ -7,12 +7,12 @@ author: "wx(GIT)" change_type: "修改接口" backend_status: "deployed" gateway_status: "verified" -frontend_status: "pending" +frontend_status: "verified" frontend_owner: "mmg" -frontend_ref: "" +frontend_ref: "8785efa8c1ae711648be2016781a1fb63dc6a5c5" target_release: "v2.1" -verified_at: "" -status_note: "PR #8334 squash 合并 dev-v3(39d21cd4f)。部署:hl-order-service-v3 dev-v3 @ 2b4656424(2026-09-24 14:02 滚动部署两实例)。测试服网关实测(groupBatchId=2102981652823302146,生效正式需求 CONFIRMED v4:BUS=[丙]、MPV=[甲,乙];甲已把户级 TRAVEL 需求改成 bus 并放行):GET requirement/confirm-check → ready=false,vehicleMissing 新增一条 reason=MEMBER_GROUP_MISMATCH、orderId=甲、detail=该户报的车型为 bus,但覆盖它的乘车分组(MPV)车型为 mpv,没有车型相符的分组,请重新汇总后保存正式用车需求;同刻 POST requirement/confirm 在原 809109 上先被拒(该团期另有未覆盖户)。改前同一位置 vehicleMissing=[]、ready=true。定向单测 141 绿(CheckVehicleTest 20 / ConfirmVehicleTest 18 / GroupBatchRequirementServiceTest 73 / GroupVehicleRequirementConfirmCheckTest 30)。判据保守 fail-open:户级车型集合为空、分组车型归一失败、无活跃正式需求一律跳过,历史自由文本脏值不会误报。" +verified_at: "2026-09-24" +status_note: "PR #8334 squash 合并 dev-v3(39d21cd4f)。部署:hl-order-service-v3 dev-v3 @ 2b4656424(2026-09-24 14:02 滚动部署两实例)。测试服网关实测(groupBatchId=2102981652823302146,生效正式需求 CONFIRMED v4:BUS=[丙]、MPV=[甲,乙];甲已把户级 TRAVEL 需求改成 bus 并放行):GET requirement/confirm-check → ready=false,vehicleMissing 新增一条 reason=MEMBER_GROUP_MISMATCH、orderId=甲、detail=该户报的车型为 bus,但覆盖它的乘车分组(MPV)车型为 mpv,没有车型相符的分组,请重新汇总后保存正式用车需求;同刻 POST requirement/confirm 在原 809109 上先被拒(该团期另有未覆盖户)。改前同一位置 vehicleMissing=[]、ready=true。定向单测 141 绿(CheckVehicleTest 20 / ConfirmVehicleTest 18 / GroupBatchRequirementServiceTest 73 / GroupVehicleRequirementConfirmCheckTest 30)。判据保守 fail-open:户级车型集合为空、分组车型归一失败、无活跃正式需求一律跳过,历史自由文本脏值不会误报。 | 2026-09-24 mmg 交付:实证 RequirementTab vehicleMissing 链路开箱即用(detail 直显+ready 置灰+orderNo 点击定位)零 UI 改动;orderV2GroupBatch.js JSDoc 补 reason 口径;spec 31 例全绿(新增 1 例回归锁)" updated_at: "2026-09-24" base: "dev-v3" ---