feat: add --quick flag as shorthand for --level priority

[joshkotrous]

Summary

• Adds a --quick boolean flag to pensar pentest as a convenient shorthand for --level priority
• When passed, only highest-risk endpoints (risk score ≥ 6, HIGH/CRITICAL tier) are tested — matching the "Quick Test" mode in the Pensar console UI (~15 mins vs ~2-4 hours for a full scan)
• --quick takes precedence over --level if both are specified

Usage

# Quick test — highest-risk endpoints only (~15 mins)
pensar pentest --project <id> --quick

# Equivalent to:
pensar pentest --project <id> --level priority

Test plan

• pensar pentest --help shows --quick flag with correct description
• pensar pentest --quick dispatches scan with scanLevel: "priority"
• pensar pentest --quick --level full still uses priority (--quick wins)
• pensar pentest without --quick still defaults to full

Made with Cursor

---

Note

Low Risk
Small CLI argument and documentation change that only affects how the scan level is selected; minimal surface area and no new security-sensitive logic.

Overview
Adds a new --quick flag to pensar pentest that forces scanLevel to "priority", taking precedence over --level while keeping --level defaulting to full.

Updates README.md usage and options docs to describe the full vs quick scan modes and clarify the default --level behavior.

^{Written by Cursor Bugbot for commit 1f47ad7. This will update automatically on new commits. Configure here.}