fix: fall back to REQ+EOSE when negentropy retry fails

When negentropy retry makes no progress (relay returns zero events),
this indicates the relay's negentropy implementation is broken. Instead
of marking the batch as failed, we now:

1. Mark the relay as not supporting NIP-77 so future batches skip
   negentropy and use REQ+EOSE directly
2. Fall back to REQ+EOSE using semantic filters (kind/author/tags)
   for the current batch, which may succeed where ID-based queries fail

This addresses the issue where some relays (e.g., azzamo.net, snort.social)
return event IDs during negentropy diff but fail to serve those events
when requested by ID.

0 files changed, 0 insertions, 0 deletions