pentest-scope

Output the following banner verbatim:

============================================================
[SCOPE DEFINITION]
============================================================

Step 1 — Detect Existing Scope

Try to Read .pentest-scope.json.

If the file exists and is valid JSON, extract these fields and store them:

• existing_target — the saved target value
• existing_engagement — the saved engagement name
• existing_out_of_scope — the saved out-of-scope value
• existing_auth — the saved auth value
• existing_timing — the saved time budget / quota (for backward compatibility: if timing is absent but a legacy window field exists, use window)
• existing_thoroughness — the saved thoroughness level (light, medium, deep, or full)
• existing_output_formats — the saved deliverable formats array (default [] if absent)
• existing_status — either "pending" (not yet launched) or "active" (pentest in progress)

Set has_existing_scope = true.

If the file does not exist or cannot be parsed, set has_existing_scope = false.

Step 2 — Show Existing Scope (if present)

If has_existing_scope = true, output this block with real values substituted in:

============================================================
EXISTING SCOPE FOUND
============================================================
Target:       {existing_target}
Engagement:   {existing_engagement}
Out-of-scope: {existing_out_of_scope}
Auth:         {existing_auth}
Time budget:  {existing_timing}
Thoroughness: {existing_thoroughness}
Deliverables: report.md + pentest-report.json{, plus existing_output_formats if any}
Status:       {existing_status}
============================================================

Then use AskUserQuestion to ask:

"What would you like to do with the existing scope?"

Present exactly these options:

• "Update scope — define a new scope (replaces the existing one)"
• "Cancel — keep the existing scope as-is"

If the user selects "Cancel — keep the existing scope as-is", output: