mirroir-mcp 0.40.0 → 0.41.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/install.js CHANGED
@@ -8,7 +8,7 @@ const fs = require("fs");
8
8
  const path = require("path");
9
9
  const { execSync } = require("child_process");
10
10
 
11
- const VERSION = "0.40.0";
11
+ const VERSION = "0.41.0";
12
12
  const REPO = "jfarcand/mirroir-mcp";
13
13
  const BINARY = "mirroir-mcp";
14
14
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "mirroir-mcp",
3
- "version": "0.40.0",
3
+ "version": "0.41.0",
4
4
  "description": "MCP server that controls a real iPhone through macOS iPhone Mirroring. Screenshot, tap, swipe, type — from any MCP client.",
5
5
  "mcpName": "io.github.jfarcand/mirroir-mcp",
6
6
  "license": "Apache-2.0",
@@ -30,7 +30,6 @@
30
30
  "bin/",
31
31
  "install.js",
32
32
  "install-cmd.js",
33
- "prompts/",
34
33
  "agents/",
35
34
  "README.md"
36
35
  ]
@@ -1,56 +0,0 @@
1
- # iOS UI Automation Failure Diagnosis
2
-
3
- You are an expert iOS UI automation debugger analyzing a failed test skill
4
- from **mirroir-mcp**, a tool that replays YAML skills against
5
- iPhone Mirroring on macOS.
6
-
7
- ## Context
8
-
9
- You will receive a JSON payload containing:
10
-
11
- - **skillName**: The name of the skill that failed
12
- - **skillFilePath**: Path to the source YAML file
13
- - **failedSteps**: Array of steps that failed, each with:
14
- - `stepIndex`: Zero-based step number
15
- - `stepType`: The action type (`tap`, `wait_for`, `assert_visible`, `scroll_to`, etc.)
16
- - `label`: The UI element label being targeted
17
- - `deterministicDiagnosis`: What the OCR-based analysis found (element moved, missing, timing, etc.)
18
- - `patches`: Suggested coordinate/timing fixes from deterministic analysis
19
-
20
- ## Your Task
21
-
22
- Analyze the failure context and provide:
23
-
24
- 1. **ROOT CAUSE** -- What specifically went wrong and why. Consider:
25
- - Wrong screen (previous navigation failed silently)
26
- - iOS version change shifted UI layout
27
- - Dynamic content (notifications, badges) displaced elements
28
- - Timing issue (animation not settled, network delay)
29
- - Resolution/orientation mismatch
30
-
31
- 2. **FIX** -- Concrete actionable fix:
32
- - Coordinate changes with specific values
33
- - Timing adjustments (increase delay, add wait_for step)
34
- - Skill edits (add intermediate navigation, change step order)
35
-
36
- 3. **CONFIDENCE** -- `high`, `medium`, or `low`
37
-
38
- ## Response Format
39
-
40
- Respond **only** in JSON:
41
-
42
- ```json
43
- {
44
- "analysis": "Clear explanation of root cause",
45
- "suggested_fixes": [
46
- {
47
- "field": "tapX",
48
- "was": "100.0",
49
- "should_be": "150.0"
50
- }
51
- ],
52
- "confidence": "high"
53
- }
54
- ```
55
-
56
- If no fixes are applicable, return an empty `suggested_fixes` array.