Reports panel: unverified reports say close, not delete (GRYT-1569)

[sivert-io]

What

Server PR Gryt-chat/server#250 made reports:resolve with delete a no-op for an unverified report card — the reported message is the reporter's own copy of an end-to-end-encrypted DM, so the server never had a copy of it to delete, and delete just closes the report. The client still said "permanently delete" and toasted "Message deleted" for both cases.

This changes the copy on an unverified card only:

• Delete button tooltip: "Close this report" instead of "Delete this message"
• Confirm dialog title/body/confirm label: explain that this closes the report and the message stays with the people in that DM because it's end-to-end encrypted
• Success toast: "Report closed" instead of "Message deleted"

The verified path (normal reports, delete_all_and_ban) is untouched.

Least sure about

• The toast fix reads the report's unverified flag through a new reportsRef (mirrors the existing loadingRef pattern), read at the moment reports:resolved comes back, since the effect that handles it only subscribes once and the report is gone from state by the time the toast fires. Worth a look in case there's a cleaner way to carry that flag through the round trip.
• I picked "Close Report" / "Close this report" wording per the task brief. The Vikunja ticket also floated hiding the Delete button entirely for unverified cards; I went with rewording rather than hiding, since Delete still does something useful (closes the report).

Tests

Added yarn test:unverified-report-copy (scripts/check-unverified-report-copy.mjs), following the existing source-check pattern (see test:report-user, test:empty-dm-copy) since this component has no component-level test harness. Wired into .github/workflows/ci.yml next to test:report-user.

Checked

• yarn lint (tsc -b + eslint) — clean
• yarn build — clean
• yarn test:report-user and the new yarn test:unverified-report-copy — pass

🤖 Generated with Claude Code