A missing icon still needs an error state

A security fallback can still need a small visible state label.

I keep seeing security changes framed as "nothing broke, access still works." That is technically true here, but the screen state still changed. If a folder stops using its custom icon because desktop.ini is untrusted, the UI should leave a small clue. Not a modal, not a scary banner. Just enough to stop people from checking permissions, sync, or network drives first. Would a tiny "customization ignored from untrusted source" hint be too much noise, or exactly the kind of boring state label people need?