Added a note about false negatives to the data race safety FAQ.

Author: daveverwer

Resources/Markdown/docs/builds.md

@@ -95,3 +95,5 @@ The Swift 6.0 compiler can check whether code is safe from data races at compile
 It’s not possible to distinguish between a package that genuinely has no data race safety errors and one where the errors are being suppressed in code. The number we display on the page is the number of data race errors that the compiler reports.
 
 Note that this does not affect package compatibility, as shown in the compatibility matrix. A package can be fully compatible with Swift 6.x without enabling strict concurrency checks, provided it is not running in Swift 6 language mode. For more information on opting into Swift 6 language mode, [read the Swift 6 migration guide for more information](https://www.swift.org/migration/documentation/swift-6-concurrency-migration-guide/completechecking).
+
+**Note:** If see any inconsistencies between the number of data race safety errors reported by the Swift Package Index and the number you see in local testing, we are tracking a [potential issue with false negatives reported by the Swift compiler](https://github.com/SwiftPackageIndex/SwiftPackageIndex-Server/issues/3233#issuecomment-2560966121). Please feel free to note packages that may be affected in that issue thread.