@usercase/mcp 0.2.10-next.6 → 0.2.10-next.8

package/agents/research.md

@@ -110,8 +110,11 @@ During the run, do not read the code to look into what visitors ran into, and do
 
 When `results` says the run is complete, tell the user, from the records only:
 - where people came in, how far they got, and why they left (their own words)
-- which survey cards appeared and how people responded (none appearing is normal when the project has no live questions yet — Usercase drafts questions from these visits; do not present it as a fault)
-- any time the site itself was down or showed errors, and which visits it affected
-- what the safety guard blocked, if anything that might have changed the visit
+- which survey cards appeared and how people responded — only if any appeared (none appearing is normal when the project has no live questions yet; then leave cards out)
+- any time the site itself was down or showed errors, and which visits it affected — only if it happened
+- what signed-in visitors changed on each demo account, so the user can check or undo it: name the account and each thing changed (which project or post they followed, saved, commented on or posted, which profile or setting they edited), taken from their steps. Say it as what the visitor did on the site
+- a demo account that could not be used, and that signing in to it again lets the next run use it
+
+**The report is about the user's site and the people who visited it, not about how this tool works.** The `Blocked requests` line in `results` is for you, not for the user: never repeat it or its counts anywhere in the report, not even as a note at the end, and not when they are zero. Also leave out how visits were planned and whether they went to plan, and anything that was normal or did not happen. If the guard stopped something a visitor was trying to do, say it as what that visitor tried on the site and could not finish.
 
 Do not invent findings beyond what the records show, and **do not guess causes** ("the data pipeline must be broken", "the filter is wrong") — report what the visitors saw and said. Findings are built by Usercase once enough answers pile up — point the user to the dashboard for those.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@usercase/mcp",
-  "version": "0.2.10-next.6",
+  "version": "0.2.10-next.8",
   "description": "Virtual users that browse your website and tell you what they thought — an MCP server for Claude Code",
   "license": "UNLICENSED",
   "homepage": "https://usercase.io",