Mechanical rename produced by scripts/msd-rename.cjs: gsd/Gsd/GSD -> msd/Msd/MSD across contents and paths, upstream package/repo coordinates -> @golem15/msd-core and golem15com/msd-core. Deep links into upstream history, sibling upstream packages, the GSD-2 import feature, CHANGELOG.md and .changeset/ are kept as-is. Hand edits on top: MSD block-letter banner and logos, LICENSE copyright line, package/plugin identity, regenerated lockfile, install-tree fixtures, derived registries and benchmark baseline; migration checksum baseline re-locked (MSD keeps its own install state, so no install had applied the old sums); sort-order and regex-escaped expectations in tests adjusted.
53 lines
2.3 KiB
JSON
53 lines
2.3 KiB
JSON
{
|
|
"id": "live-dom-uat",
|
|
"role": "feature",
|
|
"version": "1.14.0",
|
|
"title": "Live-DOM UAT",
|
|
"description": "Default-off live-DOM verification (#2856). Confines browser MCP reach to one purpose-built agent (msd-dom-verifier) that carries the browser globs in its own tools: line, registered as an additive step hook at execute:wave:post. agents/msd-executor.md is deliberately NOT widened: for a first-party agent the static tool list is the only control that exists, no capability can grant tools to one (ADR-1244 D2), no hook kind grants tool permissions (ADR-857 D4), and there is no per-dispatch tool override. Gated by activationKey workflow.live_dom_uat (default false), so with the key off the capability resolves inactive and the hook does not render at all. NOTE on the browser profile lock: chrome-devtools-mcp holds an exclusive lock on $HOME/.cache/chrome-devtools-mcp/chrome-profile, and --isolated is a flag on the user's own MCP-server registration that MSD cannot pass. Concurrent execution waves sharing one profile will therefore collide; the step tolerates and reports that (onError: skip, never blocking) rather than pretending to coordinate a resource it does not own.",
|
|
"tier": "full",
|
|
"requires": [],
|
|
"engines": {
|
|
"msd": ">=1.11.0"
|
|
},
|
|
"runtimeCompat": {
|
|
"supported": [
|
|
"*"
|
|
],
|
|
"unsupported": []
|
|
},
|
|
"skills": [],
|
|
"agents": [
|
|
"msd-dom-verifier"
|
|
],
|
|
"activationKey": "workflow.live_dom_uat",
|
|
"config": {
|
|
"workflow.live_dom_uat": {
|
|
"type": "boolean",
|
|
"default": false,
|
|
"description": "Enable live-DOM verification. Default-off: browser MCP reach is opt-in per project. When on, the orchestrator's automated UI verification may additionally use mcp__chrome-devtools__* / mcp__claude-in-chrome__* when present, and a msd-dom-verifier step runs after each execution wave. When off, neither surface reaches a browser and the pre-existing mcp__playwright__* path is unchanged."
|
|
}
|
|
},
|
|
"hooks": [],
|
|
"steps": [
|
|
{
|
|
"point": "execute:wave:post",
|
|
"ref": {
|
|
"agent": "msd-dom-verifier"
|
|
},
|
|
"fragment": {
|
|
"path": "fragments/execute-wave-post.md"
|
|
},
|
|
"produces": [
|
|
"DOM-VERIFY.md"
|
|
],
|
|
"consumes": [
|
|
"PLAN.md"
|
|
],
|
|
"when": "workflow.live_dom_uat",
|
|
"onError": "skip"
|
|
}
|
|
],
|
|
"contributions": [],
|
|
"gates": []
|
|
}
|