Scene Tagger MD5 Match Shown on Non-Matching Results

[FlashSpazzbo]

Describe the bug
In the Scene Tagger, when a query returns multiple results, the "MD5 Checksum is a match" indicator appears on results whose StashDB fingerprints do not contain the file's MD5 -- apparently propagating from whichever result does match.

To Reproduce

1. Open Scene Tagger for a scene that returns multiple StashDB results.
2. Observe the match indicators on each result.
3. Cross-reference the "MD5 Checksum is a match" indicator against the StashDB fingerprint tables for each result.
4. The indicator appears on results whose fingerprint tables do not contain the file's MD5.

Specific example:
Local scene: Pour Toi Mon Amour 2 (SexArt, 2014-08-08). Scene Tagger returns two results:

• Pour Toi Mon Amour 2 — StashDB ID 8e040478-b66b-4307-ae8b-f431e55054cc
• Pour Toi Mon Amour 3 — StashDB ID e8ec7786-c562-4f97-abe3-4f85fc179f4e

The file's MD5 (7196bb0263ac2feb8ebac8a94a1bbd9f) appears in Pour Toi Mon Amour 2's StashDB fingerprint table and is absent from Pour Toi Mon Amour 3's. Both results nonetheless display "MD5 Checksum is a match."

(Pour Toi Mon Amour 3 appears in the results due to an incorrectly attached OSHASH fingerprint on StashDB -- a separate issue already reported to the fingerprint backlog.)

Expected behavior
The "MD5 Checksum is a match" indicator should only appear on results whose StashDB fingerprint tables contain the file's MD5.

Screenshots

Desktop:

• OS: Windows 11
• Version: v0.31.1 (build hash: 4de2351)

Additional context
The other match indicators (Duration, PHash) appear to evaluate correctly per result, making the MD5 indicator behavior stand out as anomalous.

[InfiniteStash]

Hey, this is a bug on the stash side. Basically the labeling is wrong, it's saying MD5 Checksum is a match, but it's actually matching both MD5 and OSHash. Given that MD5 is going away very soon it should definitely be fixed to show the correct algo.