Under the hood
Tool-entry dedup when tracking schema changes now only checks against already-kept entries, not a separate reference set
What
In the internal logic that tracks which tool entries are kept, stripped, or removed when a tool's schema changes, an entry is no longer excluded from the "kept" list just because a tool of the same normalized name exists in a separate reference set. Now, an entry is only blocked from being added if it's already in the kept list itself.
Why
This loosens the deduplication rule, which likely means fewer tool entries get incorrectly dropped from the kept list during schema-change tracking, though the finding doesn't specify the exact downstream effect.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
What visible effect this has for users, since the finding only describes the internal dedup condition, not its downstream consequence.