Ability to silence or customize linters

My database has ~30 tables intentionally designed for public access. Each one triggers a warning about permissive RLS policies. These warnings are correct—the policies are permissive—but they're intentional. The issue: warnings can also flag unintentional security gaps. Right now I can't tell the difference at a glance. I have to mentally filter "yeah I know" from "wait, what?" every time I check the advisor. At scale, something will slip through. Some valuable warnings I was oblivious to, as they were at _the bottom_ of the list are: • Postgres Version update (should be at the top in my opinion) • OTP expiry • Leaked Password protection What I'd like: Some way to mark specific warnings as acknowledged/suppressed so only new or unreviewed warnings surface. Options to consider: • Per-table suppression (comment annotation, config file, or UI toggle) • "Acknowledged" state that hides from main vi…