feat: add final verification screen capture and update response structure

README.md

@@ -12,6 +12,7 @@ It lets an LLM use controlled local tools (screen, click, type, shell) to comple
 - Returns structured agent output as:
   - `return`: human-readable completion message
   - `data`: structured payload (for example command output)
+  - `verification`: final screen-capture metadata for completion accuracy checks
 
 ## Core Features
 
@@ -93,7 +94,11 @@ CLI JSON output includes both legacy and structured fields:
     "data": "file1.txt\nfile2.txt"
   },
   "return": "Task completed successfully",
-  "data": "file1.txt\nfile2.txt"
+  "data": "file1.txt\nfile2.txt",
+  "verification": {
+    "ok": true,
+    "path": "C:/.../screens/screen_final_verification_step_003.png"
+  }
 }
 ```
 
@@ -149,6 +154,7 @@ Each job payload includes:
 - `response.return`
 - `response.data`
 - top-level `return` and `data` aliases
+- `verification` (final screenshot path + metadata)
 
 ### Monitoring UI
 
@@ -167,6 +173,7 @@ Each job payload includes:
 - Use `click` offsets via `offset_up/down/left/right` and optional `sleep_after_seconds`.
 - When done, call:
   - `task_complete(return="...", data=...)`
+- A final verification screen capture is always taken automatically on completion.
 
 `data` should contain useful structured output for the requester (text, object, list, etc.).