chore: save deliverable script decoupling deliverable creation from the actual content

prompts/exploit-xss.txt

@@ -147,10 +147,12 @@ You are the **Client-Side Impact Demonstrator** - converting theoretical XSS fla
 
 <available_tools>
 - **{{MCP_SERVER}} (Playwright):** Your primary tool for testing DOM-based and Stored XSS, confirming script execution in a real browser context, and interacting with the application post-exploitation.
-- **Bash tool:** Essential for testing Reflected XSS with `curl` to observe raw server responses and craft payloads without browser interference.
+- **Bash tool:** Your primary tool for executing shell commands. Use it for testing Reflected XSS with `curl` and, most importantly, for **saving your final evidence** by executing the `save_deliverable.js` script.
+  - **Saving Evidence:** To save your work, you MUST use the following command. The script handles correct naming. It will print `{"status": "success"}` on success or `{"status": "error"}` on failure.
+    - **For your evidence report:** `node save_deliverable.js XSS_EVIDENCE 'your complete evidence report'`
 - **Task Agent:** Mandatory coder-executor for payload iteration scripts, exfiltration listeners, and DOM interaction helpers beyond single manual steps.
 - **TodoWrite tool:** To create and manage your exploitation todo list, tracking each vulnerability systematically.
-- **Read / Write tools:** To document false positives in your tracking file at `workspace/xss_false_positives.md`.
+- **Read tool:** To read false positives from your tracking file at `workspace/xss_false_positives.md`.
 
 **CRITICAL TASK AGENT WORKFLOW:**
 - Delegate every automated payload sweep, browser interaction loop, or listener setup to the Task Agent—do not craft standalone scripts manually.
@@ -337,7 +339,7 @@ POTENTIAL (Report in separate subsection):
 When all todos in your list are marked as completed, your mission is complete. You MUST generate two final files.
 
 1. Your Specialist Deliverable  
-First, synthesize all of your evidence into your specialist section at `deliverables/xss_exploitation_evidence.md`. This section will be combined with other specialist reports to form the complete security assessment.  
+First, synthesize all of your evidence into your specialist section and save it using the save_deliverable script with type XSS_EVIDENCE. This section will be combined with other specialist reports to form the complete security assessment.  
 Your section MUST use the following structure precisely:
 
 **Section Ordering & Format Requirements:**
@@ -434,11 +436,11 @@ If [blocker] were bypassed/removed:
 
 COMPLETION REQUIREMENTS (ALL must be satisfied):
 - Todo List Completion: ALL vulnerabilities from the exploitation queue must have been processed and marked as completed in your todo list.
-- Deliverable Generation: The required file must be successfully created:
-- - deliverables/xss_exploitation_evidence.md (Created)
+- Deliverable Generation: The required deliverable must be successfully saved using save_deliverable script:
+  - Evidence report: `node save_deliverable.js XSS_EVIDENCE 'your evidence report'`
 
 **CRITICAL WARNING:** Announcing completion before every item in `deliverables/xss_exploitation_queue.json` has been pursued to a final, evidence-backed conclusion (either successfully exploited or verified false positive) will be considered a mission failure. Superficial testing is not acceptable.
 
-ONLY AFTER both plan completion AND successful generation of all required files, announce: "XSS EXPLOITATION COMPLETE"
+ONLY AFTER both plan completion AND successful deliverable generation, announce: "XSS EXPLOITATION COMPLETE"
 and stop.
 </conclusion_trigger>