golem15/msd-core
4
0
Fork 0
Code Issues 1 Pull Requests Actions 2 Packages Projects Releases Wiki Activity

refactor: hard-fork GSD -> MSD (Make Software Done)

Browse Source 
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.
This commit is contained in:
Jakub Zych
2026-10-06 01:47:40 +02:00
parent fe069b2a56
commit a9a7a328e6
2763 changed files with 78465 additions and 78434 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
docs/how-to/enable-ui-interaction-capture.md
View File

@@ -1,6 +1,6 @@
# How to enable UI interaction capture
Let `/gsd-ui-review`'s auditor capture what a page looks like *after* an interaction — a hover
Let `/msd-ui-review`'s auditor capture what a page looks like *after* an interaction — a hover
state, a focus ring, an open menu, a filled form's validation state — instead of only the first
paint, without configuring an MCP server or widening the agent's tool surface.
@@ -34,17 +34,17 @@ paint, without configuring an MCP server or widening the agent's tool surface.
## Step 1 — Turn the key on
```bash
gsd-tools query config-set workflow.ui_interaction_capture true
msd-tools query config-set workflow.ui_interaction_capture true
```
Verify it took:
```bash
gsd-tools query config-get workflow.ui_interaction_capture
msd-tools query config-get workflow.ui_interaction_capture
# → true
```
`/gsd-ui-review` reads the key and passes `interaction_capture: true` in the auditor's
`/msd-ui-review` reads the key and passes `interaction_capture: true` in the auditor's
`<config>` block — the auditor itself never reads config.
---
@@ -52,7 +52,7 @@ gsd-tools query config-get workflow.ui_interaction_capture
## Step 2 — Run a review and read the report
```bash
/gsd-ui-review 3
/msd-ui-review 3
```
The audit's static captures land where they always did. With the key on and a Chrome
@@ -88,7 +88,7 @@ Experience Design pillar says when its findings are code-derived.
the three viewport shots; it has `--wait-for-selector`, `--device`, `--color-scheme` and
cross-engine `-b firefox|webkit`, none of which the CLI driver offers. Firefox and WebKit needs
stay on Playwright.
- **It does not touch `gsd-dom-verifier` or `workflow.live_dom_uat`.** That capability drives a
- **It does not touch `msd-dom-verifier` or `workflow.live_dom_uat`.** That capability drives a
browser MCP server at execute time; this one drives a CLI from Bash at review time. They are
independent keys.
- **It does not share the `chrome-devtools-mcp` browser profile.** The auditor starts the daemon
@@ -105,7 +105,7 @@ Experience Design pillar says when its findings are code-derived.
## Turning it back off
```bash
gsd-tools query config-set workflow.ui_interaction_capture false
msd-tools query config-set workflow.ui_interaction_capture false
```
The next review runs the Playwright-only path and reports `**Interaction captures:** off`.