新增发布 artifact URL browser gate

This commit is contained in:
2026-06-16 10:24:05 +08:00
parent 56175e29cc
commit 904f906f86
15 changed files with 271 additions and 10 deletions

View File

@@ -3001,7 +3001,77 @@ project_release_gate=ok
继续只做实质能力推进。优先选择真实 browser/UI workflow 或外部 shell 可消费能力;
如果继续 release 路径,必须继续产出可调用 API、可验证 workflow、可执行 gate 或可消费 artifact。
三十九、2026-06-16 继续执行记录:workflow overview release readiness artifact URL workflow
四十一、2026-06-16 继续执行记录:release artifact URL browser workflow gate
本轮继续按“每批必须产出可调用 API、可验证 workflow、可执行 gate、或真实 UI/browser 能力”推进,
把上一批 release readiness artifact URL workflow 提升为独立可执行 browser gate并纳入 project
release readiness artifact 的 required gates。外部 CI 现在可以单独验证 workflow overview iframe
从 URL fetch artifact、validate、render 和 mount 的真实 browser 能力。
完成内容:
- 新增真实 browser gate
- `tests/browser/release_artifact_url_workflow_smoke.html`
- `tests/browser/verify_release_artifact_url_workflow_browser.sh`
- 新 gate 验证:
- missing URL 返回结构化 blocked
- missing DOM 返回结构化 blocked 且 validation ready
- ready DOM 下 fetch `tests/fixtures/project-release-readiness-ready.json`
- validation gateCount 为 10
- render-state 和 mount result 为 ready
- 输出 `browser_release_artifact_url_workflow_smoke=ok`
- `runtime/sdk/src/project-release-readiness.js` 的 required release gates 新增:
- `release-artifact-url-browser`
- `verify_project_release_gate.sh` 在 browser INI smoke 后运行新 browser gate
- `write_project_release_readiness_artifact.mjs` 写入新 gate result 和 observed output
- `verify_project_release_readiness_artifact.mjs` 期望 `gateCount=10`
- `tests/fixtures/project-release-readiness-ready.json` 新增第 10 个 gate
- `verify_sdk_surface.mjs`、`verify_ini_panel_ui_shell.mjs`、workflow overview browser smoke、
shell integration browser smoke 同步 `gateCount=10`
- `docs/project-release-handoff.md` 和 `verify_project_release_handoff_docs.mjs` 记录新 gate
- `PROJECT_COMPLETION_TRACKER.md` 同步 latest completed batch 和 release gate wrapper 状态;
- 清理 `text14.txt` 尾部重复中文编号,使续接记录标题保持唯一;
- 未新增控制按钮;
- 未执行 release gate/action-plan 以外的 CNC 行为;
- 未解析 G-code
- 未解释 canonical events
- 未新增 JS CNC 语义;
- 未运行 opt-in runtime probes
- 未 promotion blocked runtime family
- 未改变 LinuxCNC interpreter、tool、parameter、planner、kinematics、remap 或 LinuxCNC-owned
runtime semantics。
验证已通过(先行 targeted
```bash
wasm-port/tests/browser/verify_release_artifact_url_workflow_browser.sh
wasm-port/tests/sdk/node/verify_sdk_surface.sh
wasm-port/tests/ui/node/verify_ini_panel_ui_shell.sh
wasm-port/tests/docs/node/verify_project_release_handoff_docs.sh
wasm-port/tests/host/verify_project_release_readiness_artifact.sh wasm-port/tests/fixtures/project-release-readiness-ready.json
SKIP_INI_BUILD=1 SKIP_INTERP_BUILD=1 wasm-port/tests/browser/verify_ini_panel_browser.sh
wasm-port/tests/ui/node/verify_ui_node_smokes.sh
git diff --check
```
关键输出:
```text
browser_release_artifact_url_workflow_smoke=ok
sdk_surface_node_smoke=ok
ini_panel_ui_shell_node_smoke=ok
project_release_handoff_docs_node_smoke=ok
project_release_readiness_artifact_node_smoke=ok
browser_ini_shell_integration_workflow_smoke=ok
ui_node_smokes=ok
```
下一步工作计划:
继续只做实质能力推进。优先选择可执行 gate、SDK/API surface、或真实 browser workflow
不要做只整理断言或局部常量化的批次。
四十、2026-06-16 继续执行记录workflow overview release readiness artifact URL workflow
本轮继续按“每批必须产出可调用 API、可验证 workflow、可执行 gate、或真实 UI/browser 能力”推进,
把 release readiness artifact validation 从 JSON 字符串调用推进到真实 browser URL 加载 workflow。外部