Name the reaper's hard delete in the eventBodyQuery comment (closes #455)

The comment credited the deleted_at predicate with refusing a reaped
event. The retention reaper deletes event rows outright, so a reaped
event is simply gone; nothing soft-deletes an event, so the predicate
excludes nothing today.

Model: opus-5-5

internal/handlers/event_body_test.go

@@ -405,11 +405,10 @@ func TestHandleEventBodyDownload_UnknownEvent404s(t *testing.T) {
 // route. The body is read in one query before any header is
 // written, so a reaped event cannot produce a partial download:
 // it is a clean 404 with no Content-Length and no
-// Content-Disposition. The reaper deletes event rows outright,
-// which is the "hard deleted" case. The "soft deleted" case
-// covers a row no code produces today: it only pins the query's
-// own deleted_at predicate, the soft-delete condition Raw would
-// otherwise skip.
+// Content-Disposition. Both removals the codebase performs are
+// covered — the reaper hard-deletes, and a soft-deleted row is
+// excluded by the query's own deleted_at predicate rather than
+// by GORM's default scope, which Raw bypasses.
 func TestHandleEventBodyDownload_ReapedEvent404s(t *testing.T) {
 	t.Parallel()