歷史記錄

leiyun 517d990b0f test(editors): add model and scene closure coverage and screenshot reports		1 周之前
..
data	test(editors): add model and scene closure coverage and screenshot reports	1 周之前
downloads	test(editors): add model and scene closure coverage and screenshot reports	1 周之前
evidence	test(editors): add model and scene closure coverage and screenshot reports	1 周之前
playwright	test(editors): add model and scene closure coverage and screenshot reports	1 周之前
screenshots	test(editors): add model and scene closure coverage and screenshot reports	1 周之前
test-results	test(editors): add model and scene closure coverage and screenshot reports	1 周之前
README.md	test(editors): add model and scene closure coverage and screenshot reports	1 周之前
artifact-checks.json	test(editors): add model and scene closure coverage and screenshot reports	1 周之前
cleanup.json	test(editors): add model and scene closure coverage and screenshot reports	1 周之前
coverage-plan.md	test(editors): add model and scene closure coverage and screenshot reports	1 周之前
coverage.json	test(editors): add model and scene closure coverage and screenshot reports	1 周之前
feature-catalog.json	test(editors): add model and scene closure coverage and screenshot reports	1 周之前
index.html	test(editors): add model and scene closure coverage and screenshot reports	1 周之前
results.json	test(editors): add model and scene closure coverage and screenshot reports	1 周之前
run-history.json	test(editors): add model and scene closure coverage and screenshot reports	1 周之前
screenshot-captions.json	test(editors): add model and scene closure coverage and screenshot reports	1 周之前
screenshot-verification.json	test(editors): add model and scene closure coverage and screenshot reports	1 周之前
validation.json	test(editors): add model and scene closure coverage and screenshot reports	1 周之前

README.md

装备模型编辑器闭环验收报告

打开 index.html。本报告区分源码实现、单元/合同测试、真实接口、浏览器 UI 与脚本调用运行时，不把截图或套件总通过数替代逐功能验证。

从 ute2e 目录生成：

node tools/build-model-editor-closure-report.mjs

feature-catalog.json：103 个实际可达功能的源码位置、边界、修复和验收要求。
coverage.json：生成时逐项关联当前证据的矩阵。
results.json：最终 Playwright JSON 原始结果。
run-history.json：首轮失败和定向重跑的安全摘要；只含次数、标题、时间与源文件哈希，保留失败事实，不用定向重跑替换全量结果。
validation.json：最终构建、单元测试等验证记录；e2eComplete: true 标记最终轮已完成。
evidence/*.json：经过脱敏的真实 API、运行时及界面断言记录。
screenshots/*：真实截图，报告自动枚举全部 PNG/JPEG/WebP。
screenshot-captions.json：以文件名或不含后缀文件名为键，值为 { "title": "图名", "description": "实际证明的范围" }。
screenshot-verification.json：每张图片与当前 results.json 正式附件的 SHA256 比对；同名重拍或预跑图不自动计当前轮通过。
cleanup.json：临时测试数据的清理或保留记录。
artifact-checks.json：四仓库变动及本轮报告的凭据/令牌、ZIP内元数据和图片文本元数据扫描；finalArtifactScan: true 才表示最终文件已扫描，初查不替代最终验收。
data/inventory-main.md：修复前只读基线及本轮源码实现记录。
data/final-corrections.json：只读查看交互与连接健康检查补修的解释和边界；data/kingbase-validation-probe-result.json 只含脱敏探针结果，不含连接信息或凭据。

证据推荐格式（仅示例，不是实际通过声明）：

{
  "time": "真实执行时间",
  "data": {
    "title": "当前曲线编辑与刷新",
    "status": "PASS",
    "kind": "e2e",
    "testTitle": "与 results.json 完全对应的真实用例名称",
    "featureIds": ["timeline.curve", "curve.time", "curve.value", "curve.easing"],
    "details": "记录真正执行和断言的内容，不按同类功能推测覆盖",
    "screenshots": ["screenshots/实际文件.png"]
  }
}

kind 应明确使用 e2e、api、runtime 或 unit，不要把通过脚本调用编辑器方法说成纯 UI 操作。带 testTitle 的证据会与当前 Playwright 结果按完整标题及执行时间交叉核对；对应用例不存在、失败，或证据来自不同时段时，不能标为本轮通过。未关联证据的功能保持待验证。

全量首轮的 17/19 和随后仅两条定向重跑的 2/2 不可相加后改写成“全量19/19通过”。必须另跑完整套件，保留新的完整 results.json 以及匹配时段证据；历史503的诊断判断和已证明的因果关系要分开陈述。

总状态只有在结果最终完成、最终验证通过、无失败、全矩阵都有证据且最终交付物扫描通过时才为 PASS；已执行用例通过但仍有未覆盖功能时，会如实显示待验证范围。组件运行系统、完整三维离线包、下游自动执行模型动作属于三项另行确认的范围，不应虚构完成证据。

此目录不得存入账号文件、密码、令牌、cookie、私有 fixtures、原始服务日志或数据库备份。原始 PDF 只相对链接至工作区 文档，不复制全文。