Move RLS verification into the policy editor, not beside it

Supabase paused the [RLS Tester feature preview]( in April while re-evaluating its direction. This is a concrete proposal for that direction, with a working prototype. The argument in one line: the tester was the right capability in the wrong place. Verification that lives *beside* authoring is a destination people have to remember to visit, and the moment you most need it is the moment you don't know you need it, because a too-strict policy looks exactly like no data. Try it: The prototype there runs a real RLS interpreter over a sample table (grants → role → permissive OR → restrictive AND), so the policy you build is genuinely evaluated rather than mocked. There's a 3½ minute narrated walkthrough if you'd rather watch than click. The research I pulled every discussion in this repo matching "RLS policy" (800), filtered out show-and-tell, and kept the 438 where a policy is the actual subject. Coded each on title and opening post; 27.9% resisted single-t…