When an add-on is open in the workspace and the user 1) opens their VS Code settings, and 2) makes a change, VS Code registers this as a file change. This triggers, for one, lints being cleared -- despite the add-on itself not actually having any changes.
Probably a relatively rare edge case and only mildly annoying at most, but still.