pentest-reviewlisted

## User Input ```text $ARGUMENTS ``` You **MUST** consider the user input before proceeding (if not empty). ## Purpose Read existing pentest reports and produce classified findings with actionable triage. ## Workflow ### Phase 1: Locate Report 1. Determine target name from arguments (default: `rockport`) 2. Find the latest report directory: `pentest/reports/<target>/<timestamp>/` 3. If no reports exist, tell the user to run `/pentest <target>` first ### Phase 2: Quick Triage Use jq on `results.json` to extract: - Module summary: status, pass/fail/skip counts, duration per module - Total findings by tag (PASS, FAIL, WARN, LEAK, VULN, SKIP, INFO, FOUND, OK) - Auth bootstrap status - Skipped modules and reasons **Do NOT read entire module output files.** Use jq queries on results.json for the summary view. Also check `auth-bootstrap.log` for auth setup issues — failed auth bootstrap is a common reason for module skips/failures. Fallback: if results.json is missing, grep module output files in `modules/` for tagged lines. ### Phase 3: Deep Read (findings only) For modules that have failures (FAIL, WARN, LEAK, VULN, FOUND): - Read only those module output files from `modules/<module>.txt` - Use a subagent for large files to keep main context clean For modules that passed or were skipped, do NOT read their output files. ### Phase 4: Classification Cross-reference each finding against `pentest/targets/rockport.yaml`: | Classification | Criteria | |---------------|-