@rolepod/uiproof 0.5.0 → 0.6.1

package/dist/schemas/tools.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft/2019-09/schema",
-  "rolepod_mcp_version": "0.5.0",
+  "rolepod_mcp_version": "0.6.1",
   "tools": {
     "rolepod_browser_open": {
       "$schema": "https://json-schema.org/draft/2019-09/schema#"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rolepod/uiproof",
-  "version": "0.5.0",
+  "version": "0.6.1",
   "description": "Multi-platform UI/mobile automation for AI agents — MCP server + shipped skills.",
   "keywords": [
     "mcp",

package/skills/audit-a11y/SKILL.md

@@ -43,6 +43,15 @@ MCP server. No fallback (D-024).
 3. Surface counts + critical/serious issues inline; reference the report
    path for the full list.
 
+## Evidence routing
+
+Run artifacts are saved under:
+
+- **Standalone:** `.rolepod-uiproof/artifacts/<prefix>_<ts>_<uuid>/`
+- **With `rolepod` parent** (detected via the marker file `<git-root>/.rolepod/parent-active` written by the parent's SessionStart hook): `<git-root>/.rolepod/evidence/<ts>-rolepod-uiproof-<skill>/`
+
+Either way the run directory contains a `manifest.json` per Extension Protocol v1, so the parent's `check-work` skill can aggregate results into the verify phase report. Standalone users can read the manifest themselves — same shape.
+
 ## If the tool is unavailable
 
 Surface plainly:

package/skills/check-errors/SKILL.md

@@ -107,6 +107,15 @@ User: "Sign in then dashboard — make sure no console errors."
 }
 ```
 
+## Evidence routing
+
+Run artifacts are saved under:
+
+- **Standalone:** `.rolepod-uiproof/artifacts/<prefix>_<ts>_<uuid>/`
+- **With `rolepod` parent** (detected via the marker file `<git-root>/.rolepod/parent-active` written by the parent's SessionStart hook): `<git-root>/.rolepod/evidence/<ts>-rolepod-uiproof-<skill>/`
+
+Either way the run directory contains a `manifest.json` per Extension Protocol v1. Because `/check-errors` wraps `rolepod_verify_ui_flow`, the manifest is written by the underlying composite tool — same shape, same fields.
+
 ## If the tool is unavailable
 
 > The `/check-errors` skill needs the **rolepod-uiproof** MCP server,

package/skills/scaffold-e2e/SKILL.md

@@ -62,6 +62,15 @@ upstream Selenium has no network-capture primitive.
 3. Print the generated file path and the setup steps. Surface
    `dependencies` as an install command.
 
+## Evidence routing
+
+Run artifacts (the generated test file) are saved under:
+
+- **Standalone:** `.rolepod-uiproof/artifacts/<prefix>_<ts>_<uuid>/`
+- **With `rolepod` parent** (detected via the marker file `<git-root>/.rolepod/parent-active` written by the parent's SessionStart hook): `<git-root>/.rolepod/evidence/<ts>-rolepod-uiproof-<skill>/`
+
+Either way the run directory contains a `manifest.json` per Extension Protocol v1 (with `phase: "build"` for this skill).
+
 ## If the tool is unavailable
 
 Surface plainly:

package/skills/verify-ui/SKILL.md

@@ -110,6 +110,15 @@ For ANY user-visible flow, default-include `no_console_errors` and
 `no_failed_requests` in `expect`. Real UI bugs surface as console errors
 or 5xx responses far more often than as wrong text.
 
+## Evidence routing
+
+Run artifacts are saved under:
+
+- **Standalone:** `.rolepod-uiproof/artifacts/<prefix>_<ts>_<uuid>/`
+- **With `rolepod` parent** (detected via the marker file `<git-root>/.rolepod/parent-active` written by the parent's SessionStart hook): `<git-root>/.rolepod/evidence/<ts>-rolepod-uiproof-<skill>/`
+
+Either way the run directory contains a `manifest.json` per Extension Protocol v1, so the parent's `check-work` skill can aggregate results into the verify phase report. Standalone users can read the manifest themselves — same shape.
+
 ## If the tool is unavailable
 
 > The `/verify-ui` skill needs the **rolepod-uiproof** MCP server, which is

package/skills/visual-diff/SKILL.md

@@ -44,6 +44,15 @@ MCP server. No fallback (D-024).
 3. Report `diff_pct`, `passed`, and the three image paths. If the baseline
    was just seeded, say so explicitly.
 
+## Evidence routing
+
+Run artifacts are saved under:
+
+- **Standalone:** `.rolepod-uiproof/artifacts/<prefix>_<ts>_<uuid>/`
+- **With `rolepod` parent** (detected via the marker file `<git-root>/.rolepod/parent-active` written by the parent's SessionStart hook): `<git-root>/.rolepod/evidence/<ts>-rolepod-uiproof-<skill>/`
+
+Baselines under `.rolepod-uiproof/baselines/` are always the same location regardless of mode — they are user-curated config, not per-run evidence. Either way the run directory contains a `manifest.json` per Extension Protocol v1.
+
 ## If the tool is unavailable
 
 Surface plainly: