@wenext/test-toolkit-web v0.3.10
Toolkit 是 WeNext 质量执行、证据冻结和报告导出的唯一质量引擎。Workflow/FLT/E2E Skill 只提供任务范围、业务场景与测试实现,不能复制 Gate、重试、版本或上报规则。
Public CLI
pnpm run wenext-test -- quality instructions --json
pnpm run wenext-test -- quality inspect --task-dir .wenext-spec/tasks/<task> --json
pnpm run wenext-test -- quality run --task-dir .wenext-spec/tasks/<task> --json
pnpm run wenext-test -- quality recover --task-dir .wenext-spec/tasks/<task> --run-id <run-id> --json
pnpm run wenext-test -- quality status --task-dir .wenext-spec/tasks/<task> --json
pnpm run wenext-test -- quality verify --task-dir .wenext-spec/tasks/<task> --json
pnpm run wenext-test -- quality export --task-dir .wenext-spec/tasks/<task> --workflow-context-stdin --json
pnpm run wenext-test -- quality diagnose --task-dir .wenext-spec/tasks/<task> --jsonquality run executes and prepares quality state. quality recover only terminalizes the specified interrupted run after confirming that no process still owns the workspace lock. Registry consumers check and strongly update to the latest Toolkit before any assessment or execution; the transaction is locked, uses an isolated candidate and permits only the Toolkit dependency closure. file:/local tgz consumers never query the registry.
升级在只声明 Toolkit 的专用项目中先完成 frozen 安装与 integrity 校验,再通过受审计 事务更新根 package/lock 和工具入口。其他 workspace importer 与已有共享解析记录保留; 它们的历史依赖漂移不触发全仓安装。已验证的运行时保存在 node_modules/.wenext-toolkit-runtimes/,属于安装内容,不能单独清理。 安装阶段失败不修改根 package/lock;应用事务时中断则保留事务以便显式恢复。 未审核的动态 hook、共享解析冲突和第三方 package/lock 改动继续阻断。
旧升级器迁移
旧版本自身的升级器被 TOOLKIT_UPDATE_DIFF_FORBIDDEN 阻断时,在消费仓库使用已发布 的新版本迁移入口(将 <新版本> 替换为人工发布版本):
pnpm --package=@wenext/test-toolkit-web@<新版本> dlx wenext-toolkit-migrate --task-dir .wenext-spec/tasks/<task>迁移入口校验旧包锁定 integrity、新发布包 integrity、任务范围和安装结果,只写升级收据, 不执行 Gate、不生成质量结论。迁移后通过正常 quality inspect/run/verify/export 重新评估。 已有旧格式未完成事务或 package/lock 人工改动时,需要先审核其准确状态,不能强制覆盖。 仓库有动态 .pnpmfile.cjs 时,使用 quality/request.json 的 preparation.pnpmHook 审核字段绑定代码、引用文件和环境输入;迁移不禁用 hook。
Vue 框架识别
准备阶段优先读取目标包 Vue/catalog 声明;无目标框架声明时,仅继承与 root importer 一致的根共享 Vue。执行前核验实际安装版本;独立 Vue3 包不能因根 Vue2 而被改判。 框架来源、锁定版本及 workspace catalog 纳入 Toolkit 执行指纹与证据。
inspect returns a semantic assessmentFingerprint, an executionFingerprint, and a deterministic managed-config patch preview. A new runtime invalidates old conclusions; the same runtime plus execution fingerprint reuses its historical frozen run, including A→B→A, and unrelated diffs never buy an automatic retry.
export returns quality-report-bundle-v1: the schema-valid quality_run_v3 document (commit_hash: null), Toolkit-produced compatibility events, and waiver events. Workflow persists/transports this bundle verbatim and later emits a separate commit-binding event.
Human-readable artifacts
Toolkit freezes machine evidence under quality/toolkit/runs/<run-id>/. It derives and keeps quality/frontend-logic-test/summary.md, quality/e2e-testing/summary.md, and quality/toolkit/summary.md; scoped Debug checks keep quality/debug-scoped-check/summary.md. Existing Markdown-to-HTML rendering remains unchanged. Markdown is for diagnosis only; verify and export trust only frozen evidence and the report bundle. Re-running quality run for a terminal current run regenerates these derived summaries without re-executing a Gate.
Managed configuration state
.wenext-test/managed.json is a repository-level ownership snapshot, not Check history. It contains only hashes of Toolkit-managed files and managed package.json field values; it never stores run IDs, logs, evidence, or results. Repeated Checks with unchanged configuration leave it byte-for-byte unchanged. Missing files and fields changed by a developer are removed from the snapshot automatically, releasing Toolkit ownership.
Run pnpm test for Toolkit regressions. Publication is always an explicit release action.