@ia-qa/self-healing 1.7.20 → 1.7.21

package/README.md

@@ -33,9 +33,10 @@ style your suite already uses — CSS stays CSS. The demo adds `--locators`, whi
 `getByRole(…, { exact: true })` where that is provably safe: a locator immune to the *next*
 layout change.
 
-▶ **[The full 49-second version](https://www.ia-qa.com/media/heal-demo.mp4)** also covers what
-deterministic healing *refuses* to guess, the MCP server answering an agent, and the HTML
-report `--report` writes for a PR.
+▶ **[The full 48-second version](https://www.ia-qa.com/media/heal-demo.mp4)** starts one step
+earlier — from a red build, with `explain` telling you which failures are drift and which one is
+**not** — then covers whether the app you mapped is sound at all, the MCP server answering an
+agent, and the HTML report `--report` writes for a PR.
 
 ## Install
 
@@ -483,6 +484,11 @@ monorepo. Every field is documented in full in the tutorial
 
 ## The console — `ia-qa-heal ui`
 
+[![The ia-qa-heal console: a BLOCK verdict, the one element the tool refused to guess, the verbs as plain-language buttons, and the run history as charts](https://www.ia-qa.com/media/heal-ui-poster.png)](https://www.ia-qa.com/media/heal-ui.mp4)
+
+▶ **[Watch the console in 32 seconds](https://www.ia-qa.com/media/heal-ui.mp4)** — buttons pressed,
+results rendered, nothing written.
+
 A local web console for the rows where the tool gave up: highlighted crops of each candidate,
 the `file:line` of every test that breaks, the verbs as plain-language buttons, and the history
 as charts. `--shortcut` writes a desktop launcher.

package/TUTORIAL.md

@@ -581,13 +581,21 @@ wall — and the decision is the one thing the tool cannot take from them.
 ia-qa-heal ui
 ```
 
+[![The ia-qa-heal console: a BLOCK verdict, the one element the tool refused to guess, the verbs as plain-language buttons, and the run history as charts](https://www.ia-qa.com/media/heal-ui-poster.png)](https://www.ia-qa.com/media/heal-ui.mp4)
+
+▶ **[Watch the console in 32 seconds](https://www.ia-qa.com/media/heal-ui.mp4)** — the buttons are
+pressed, not pointed at: *Preview the repairs* answers `would apply 3 rewrites in 1 file · 1 still
+need a human`, and nothing on disk changes. Real state, nothing staged but the drift itself.
+
 A local page opens in your browser with three things a terminal cannot give you:
 
-- **The rows waiting on a human.** Each `ambiguous` / `lost` / `rebound` row, with a **highlighted
-  picture** of each candidate as it looks on the page right now (needs `map --screenshots`), the
-  `file:line` of every test that will break, and — the part that matters — **a sentence saying what
-  to do about it**. When five identical "Copy" buttons exist, `div:nth-of-type(4) > … > button`
-  tells you nothing; the picture tells you which one.
+- **The rows waiting on a human.** Each `ambiguous` / `lost` / `rebound` row, with the `file:line`
+  of every test that will break and — the part that matters — **a sentence saying what to do about
+  it**. `ambiguous` and `rebound` rows also carry a **highlighted picture** of each candidate as it
+  looks on the page right now (needs `map --screenshots`): when five identical "Copy" buttons
+  exist, `div:nth-of-type(4) > … > button` tells you nothing, and the picture tells you which one.
+  A `lost` row has no picture and cannot have one — its element is not on the page any more, so
+  there is nothing left to photograph.
 - **The verbs as buttons**, in plain words: *Look at the app again*, *Check for changes*,
   *Repair my test files ✎*. Every result is a sentence, not an exit code, with the raw output one
   click away.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ia-qa/self-healing",
-  "version": "1.7.20",
+  "version": "1.7.21",
   "description": "Your Playwright, Cypress or Selenium tests break when a selector moves — this finds the element again and rewrites the test. Deterministic: no LLM decides whether your build passes. Runs entirely on your machine, with a local MCP server for agents.",
   "keywords": [
     "self-healing",