“Fixed” status confusion when code is moved

Moving code to a different line causes the original finding to be marked “fixed,” and the next scan creates a new bug. This creates misleading status churn and extra triage.

Current Behavior
- Finding identity seems tied to line numbers/positions, not code semantics/history.
- Non-semantic moves look “fixed,” then immediately “new.”

We should remove this status or fix the logic.