Codex Security Cloud: fixed findings remain New with no way to resolve them #1561

Problem

Codex Security Cloud is not usable as an ongoing findings tracker if old, fixed findings continue to be displayed as New indefinitely.

A later scan can stop reporting a fixed issue, while the previous finding remains in the open findings list as New. The repository-scan finding UI provides no dismiss, close, or resolve action. This leaves users unable to distinguish current actionable findings from old claims that have already been fixed.

Expected behavior

Provide a supported way to mark a reviewed repository-scan finding as fixed/resolved, preserving its history. Also distinguish findings confirmed in the latest scan from older findings that were not confirmed.

Automatic closure based only on absence from a rescan is not necessary; a manual resolution path is essential.

Impact

The open findings list accumulates stale claims marked New, making prioritization and remediation tracking unreliable.

This report intentionally contains no repository, account, scan, finding, or source-code details.