Production: a basic member filing an incident (incl. anonymous) hit an
RLS violation on table incidents. Not reproducible from source; the code
and the 016/017 policy both permit it, so it is a deployed policy/data
divergence.
- scripts/025 idempotently re-asserts incidents_insert verbatim from
017/schema.sql so a drifted deployment converges to the known-good
policy. Access-neutral, no schema change.
- fileIncident maps an RLS rejection to an actionable message and logs
the technical detail server-side instead of raw Postgres.
Minimal hotfix off origin/main: only the two production-affecting files.
If the report persists post-deploy the cause is not policy drift; the
discriminating SQL is tracked in the local stack's HANDOFF.
