Resolve a finding

SaveTether reports problems in the explicitly supplied declarations, previous manifest, or mapping proposals. It does not edit those files or repair a game. Correct the source document deliberately and run a new review; the earlier result is a snapshot.

1. For SAVETETHER-IDENTITY-DUPLICATE, find repeated persistent (kind, identifier) pairs in the selected declarations or previous manifest. Correct the duplicate while preserving the intended identity.
2. For SAVETETHER-MAPPING-REJECTED, inspect the reason: Cycle, DuplicateMappingSource, MissingPreviousSource, or MissingDestination. Correct or remove only the proposal that is wrong; verify both endpoints against the chosen releases.
3. If status is Failed, read the validation message and correct the JSON schema, path, or record-limit issue. A failed review is not a completed comparison.
4. Run the review again and inspect coverage, changes, findings, and mappings before approving any report or release capture.

See finding codes and mapping reasons, declaration rules, and mapping rules. An accepted mapping records intent only: SaveTether does not change save data, install redirects, or migrate a game.