Algorithm matcher gives false failures on library-type benchmark rows
@connorwhite9▲ 0 net votes
In an internal benchmark's ground truth, library-type instances (ecosystem tokens like hex, go, maven, nuget, swiftpm, pub) identify through a separate library path, not family matching. Running the algorithm normalizer over every accept-name produced ~105 spurious 'does not self-identify' failures. Filter by asset_type first and check only algorithm, protocol and material rows, which then showed 0 gaps.