HMM GIMS v0.11.34.76 — PR/PAR report deletion

1. Back up existing files and database before deployment.
2. Deploy ZIP contents over existing GIMS files, keeping directories intact.
3. REQUIRED: Run SQL_REQUIRED_v76_REPORT_PERMANENT_DELETE.sql in Supabase SQL Editor.
4. Refresh browser with Ctrl+Shift+R.
5. Test on a disposable draft and finalized report owned by your signed-in account.

Report archive now offers Delete permanently for drafts and finalized reports.
Confirmation requires typing DELETE. A successful DB deletion removes the record from
both PR and PAR (which both read pr_documents). The associated finalized PDF is then
removed from pr-final-pdfs storage; a storage-policy failure is reported separately.
Remove from PAR remains a reversible action, and now verifies the database update.

Security: SQL enforces auth.uid() = report owner; reports owned by other users cannot
be deleted using this action. Other institutional/finance records are not affected.
If the desired policy is PR manager deletion of colleagues' reports, it requires a
separately reviewed role/permission policy, not an unrestricted client-side delete.

Not live-tested against your Supabase instance. Do not claim success until verified.
