refactor: remove verification field from responses and update related documentation

SKILL.md

@@ -10,7 +10,6 @@ ScreenJob lets an agent execute tasks that require a real desktop UI plus termin
 - Mouse/keyboard control (`click`, `type`, `press_key`)
 - Terminal execution (`execute_command`, `sleep`)
 - Structured completion payload (`task_complete(return=..., data=...)`)
-- Automatic final verification screen capture on completion
 - Safety gate, auth, history, and live monitoring
 
 ## Important Environment Note
@@ -31,13 +30,19 @@ Agents can use ScreenJob to launch and control GUI workflows, including orchestr
 
 1. Submit job via CLI or API.
 2. Agent performs tool loop.
-3. Read final `response.return`, `response.data`, and `verification` from job status.
+3. Read final `response.return` and `response.data` from job status.
 
 Keyboard combo rule:
 
 - For shortcuts, use one `press_key` call with combo syntax, for example: `win+r`, `ctrl+shift+esc`.
 - Do not split modifier combos into separate calls.
 
+Verification rule:
+
+- Before `task_complete`, verify actual on-screen content matches the expected outcome.
+- Use `see_screen` (and `enhance` if needed) for this check.
+- Include a concise `observed_result` in `data` when completing the task.
+
 ## API Quick Reference
 
 Base URL:
@@ -85,18 +90,10 @@ Result contract in job payload:
   "status": "completed",
   "response": {
     "return": "Task completed successfully",
-    "data": "file1.txt\nfile2.txt",
-    "verification": {
-      "ok": true,
-      "path": "C:/.../screens/screen_final_verification_step_006.png"
-    }
+    "data": "file1.txt\nfile2.txt"
   },
   "return": "Task completed successfully",
-  "data": "file1.txt\nfile2.txt",
-  "verification": {
-    "ok": true,
-    "path": "C:/.../screens/screen_final_verification_step_006.png"
-  }
+  "data": "file1.txt\nfile2.txt"
 }
 ```