Moderation account messages not showing on moderation page or web

[AleyshaRose]

I sent a message to a user about a report they had made. I used the moderation account bunker to log in. The message I sent did not show in the moderation.admin.divine.video message log and also does not show in the web page messages either.

[AleyshaRose]

[DSanich]

@AleyshaRose @NotThatKindOfDrLiz @jalcine I will try to fix this and prepare a PR

[realmeylisdev]

Status update — investigation done.

A direct relay probe of wss://relay.divine.video and wss://nos.lol against the moderator pubkey shows 14 / 13 distinct kind:1059 gift wraps in the last 3 days respectively, with the newest 5 event IDs identical across both relays. The events are on the wire — the web client just can't decrypt them.

Root cause: the NIP-46 bunker (Keycast) is rejecting nip44_decrypt for the moderation-team auth. The web client's unwrapDmGiftWrap collapsed every failure to null and MessagesPage rendered the empty state, indistinguishable from "no messages yet".

Decomposed into:

Priority	Issue	What it does
P0	divinevideo/divine-moderation-service#129	Ops fix — Keycast policy needs to grant nip44_decrypt to the moderation-team OAuth scopes
P1	#309 → #312	Surface decrypt failures so the UI shows "inbox unavailable" instead of empty
P2	#311 → #314	Healthcheck NIP-44 capability at signer attach
P3	#310 → #313	Make NIP-17 self-wrap non-fatal in send

Important: merging #312, #313, and #314 will not restore moderation-team DM visibility on the web client. They change the symptom from "silently empty inbox" to "inbox temporarily unavailable, reconnect your signer" — which is the right user-facing behavior, but the underlying capability still needs the P0 ops fix at divinevideo/divine-moderation-service#129. Reconnecting the bunker session after the policy update should refresh the scope.

This issue auto-closes when the three sub-issues close. The P0 (divinevideo/divine-moderation-service#129) is a separate ops track and is not blocked on these PRs.

[DSanich]

@realmeylisdev I studied in detail this and the linked issues (#309/#310/#311), the three PRs (#312/#313/#314), and divine moderation-service#129. Left one small note on #314 about a cache-key issue that would make the "sign out and reconnect your bunker" instruction not actually work without a full page reload — worth a look before merge.

Since divine moderation-service#129 is a real roadblock for the moderation team, and three website change requests is the last resort to get around it, I can work on it

cc @jalcine @NotThatKindOfDrLiz