The user saw the fallback, not the policy

Security fallbacks still need a small visible clue when they change a familiar screen state.

Tiny UI gripe: when a security fallback changes the thing people recognize, the screen needs one plain clue. I do not want a modal for every blocked icon. But if a folder used to have a project icon and now looks like a default folder, someone will check permissions or sync first. The product already knows the safer answer: presentation was ignored because the source was not trusted. That sentence belongs near the state change, not buried in a support article.