scenescout 3.16.0 → 3.18.0

package/skills/scenescout/SKILL.md

@@ -11,7 +11,7 @@ You are the brain of an exploratory UI tester. The SceneScout MCP server gives y
 
 ## Starting a run: plain questions, or flags
 
-**No flags given** (none of `--url`, `--role`, `--focus`, `--level`, `--observe`, `--read-only`, `--safe-write`, `--allow-destructive`): before setup, ask these four questions in one message, in plain words, and choose the settings from the answers. Skip a question only when the person's request already answers it in words ("test http://localhost:3000" answers the first).
+**No flags given** (none of `--url`, `--role`, `--focus`, `--level`, `--observe`, `--read-only`, `--safe-write`, `--allow-destructive`): before setup, call `scout_intake` (with `url` when the person's request already names the address, so the form starts with it). Where the client can show a form, the person answers the four questions there and it returns the settings: make the calls it lists, in order, and ask nothing more. Where it cannot, or the person declines or closes the form, it returns the questions instead: ask them in one message, in plain words, and choose the settings from the answers by the table below. Skip a question only when the person's request already answers it in words ("test http://localhost:3000" answers the first). With no `scout_intake` tool, ask them yourself.
 
 1. What is the address of the site?
 2. Do you need to sign in to use it? If so, how: Google or Microsoft single sign-on, an email and password, or a one-time code?
@@ -116,7 +116,7 @@ Polite, precise testing misses how real users behave. Once per module's key flow
 - **Wrong-order behaviour:** press Enter mid-form before required fields are filled; go `scout_back` mid-wizard and return; submit, then immediately back-button. State should survive all three without data loss or duplicate records.
 - Keep attribution honest: these are deliberate probes — say so in findings ("under rapid double-click…"), so a developer can reproduce exactly.
 
-The engine is self-healing (orphaned browsers reaped, wedged calls time out with guidance instead of hanging) and observable: `.scenescout/status.json` + `scenescout status <project>` show what every session is doing right now, and there is a live view for the person running you: one card per session with its current tool, how long it has been there, a thumbnail of its page, a feed of the actions it just took, and a stream they can switch on. It works for headless runs too. **`scout_attach` returns its address on a `Live view:` line: pass that address to the user in your next message, once, so they can watch.** On a local desktop session the engine also opens it in the user's browser (an `Opened the live view` line says so), and opens report.html when `scout_report` writes it; pass `open` (`live`, `report`, `both`, `none`) only when the user asks for something else. `scout_session` with no arguments repeats it if they ask again, and `scenescout watch <project>` opens it from a terminal. It is for the person watching: you do not need to open it, and a session shown as stuck there is one to re-attach.
+The engine is self-healing (orphaned browsers reaped, wedged calls time out with guidance instead of hanging) and observable: `.scenescout/status.json` + `scenescout status <project>` show what every session is doing right now, and there is a live view for the person running you: one card per session with its current tool, how long it has been there, a thumbnail of its page, a feed of the actions it just took, and a stream they can switch on. It works for headless runs too. **`scout_attach` returns its address on a `Live view:` line: pass that address to the user in your next message, once, so they can watch.** On a local desktop session the engine also opens it in the user's browser (an `Opened the live view` line says so), and opens report.html when `scout_report` writes it; pass `open` (`live`, `report`, `both`, `none`) only when the user asks for something else. `scout_session` with no arguments repeats it if they ask again, and `scenescout watch <project>` opens it from a terminal. **When the user wants to watch the run, or asks how it is going, call `scout_status`** (no input): a host that renders MCP Apps shows a pane that keeps itself up to date with each session's objective and task, open findings by severity, coverage and a button for the live view; every other host gets the same as text, starting with the `Live view:` address, which you pass on. It is for the person watching: you do not need to open it, and a session shown as stuck there is one to re-attach.
 
 ## Judgment (what the engine can't do)