Record real Playwright ledgers, mark 20 audits and 9 remediations done, and leave management-implementation-plan as plan-only.
52 lines
2.6 KiB
Markdown
52 lines
2.6 KiB
Markdown
---
|
||
title: "当前受控文档改写被领域关键词改路由到另一交付物"
|
||
status: done
|
||
created: 2026-09-13
|
||
updated: 2026-09-22
|
||
severity: high
|
||
---
|
||
|
||
# 当前受控文档改写被领域关键词改路由到另一交付物
|
||
|
||
> **W3 UI-rerun 关闭(2026-09-22)**:`status=done`。真实 Playwright 账本 PASS:[`ui-acceptance-results.json`](../test-reports/assets/2026-09-22-docrev-ui-rerun/ui-acceptance-results.json)(main UI-00..16)+ [`ui-acceptance-results-post-restart.json`](../test-reports/assets/2026-09-22-docrev-ui-rerun/ui-acceptance-results-post-restart.json)(UI-15)。任务 tip 已合入本地 `dev`;详见 [short-term](../ops/short-term/2026-09-22-docrev-ui-rerun.md) 与 [测试报告](../test-reports/2026-09-22-docrev-ui-rerun-test-report.md)。
|
||
|
||
|
||
## 现象
|
||
|
||
第二轮真实 UI(schema 30)**UI-05 首个失败**:
|
||
|
||
- 页面打开 `doc_proj6109_intake`(用户初始需求收集表,V2/r0)
|
||
- 用户输入含「当前受控文档」的高风险改写提示(YY/T、GB 9706.1、NMPA 注册法规)
|
||
- 前端按法规关键词路由为 `feasibility_reg`
|
||
- `POST` 启动 `run_1789313290400899325`,生成 `doc_proj6109_feasibility_reg` 并 `completed`
|
||
- 当前 intake **无 pending badge**;E2E 等待 60s 失败
|
||
|
||
## 根因分析
|
||
|
||
| 层 | 问题 |
|
||
|---|---|
|
||
| `resolveTaskKeyFromMessage` | 写动词「改写」通过后,正文「注册」命中 `feasibility_reg`,无视当前打开文档 |
|
||
| `handleSendMessage` | 只把文案+模板池交给 `resolveTaskTemplateForMessage`,未传入 active `doc_proj` |
|
||
| 产品 | 「当前受控文档/本文件/这份文档」是指示语,领域词是改写内容,不是切换交付物 |
|
||
|
||
服务端 `ResolveAndValidateDocID` 已校验 project + task_key 与已注册文档一致,**不得**用客户端 `doc_id` 覆盖 `task_key`。本轮补了 `feasibility_reg` + `doc_proj6109_intake` mismatch 拒绝用例:攻击或误路由不得借 intake 文档改写另一任务键。
|
||
|
||
## 严重度
|
||
|
||
`high`
|
||
|
||
## 关联整改
|
||
|
||
- Short-term: [../ops/short-term/2026-09-13-document-revision-active-doc-routing.md](../archive/ops/2026-09-13-document-revision-active-doc-routing.md)
|
||
- 分支: `fix/document-revision-active-doc-routing`
|
||
|
||
## 证据
|
||
|
||
- Evidence root(勿删、勿提交本轮):`.doc/test-reports/assets/2026-09-13-document-revision-runtime-ui/schema30-ui05-active-doc-routing-failure`
|
||
- E2E:`web/e2e/document-revision-runtime.spec.ts` UI-05(断言不改弱)
|
||
- 审查约束:E2E/用例提示词只留在 test 文件,生产 `templateMatch.ts` 不导出用例编号常量
|
||
|
||
## 开放问题
|
||
|
||
- 占槽后真实 UI-05 重跑;本轮不操作容器
|