Two surfaces render zap-receipt messages, each with a different
treatment to suit its constraints.
Engagement-drawer zap row (mini-post)
- Now renders the message through the same `RichContent` pipeline a
regular post body uses. Body text, plain links, hashtags, profile
/ note mentions, and inline images all render the way they would
in a feed post. The row grows vertically rather than truncating —
long zapvertising payloads stay readable.
- Layout: avatar (top-aligned, 30dp) + right-side column (display
name + private icon + bolt + sats on top; RichContent body below).
- `eventRepo` is plumbed from `ReactionDetailsSection` into `ZapRow`
so RichContent can resolve profile mentions.
Top-zap banner above the action bar
- Single-line preview. Image URLs collapse to the literal token
`[image]` (helpers in `ui/util/ZapMessageImage.kt`) so the sats
amount stays visible. Surrounding text is preserved
("nice post [image]"). No image is loaded in the banner — the
drawer handles that.
Cross-platform: `ZAP_IMAGE_PARITY.md` documents the contract — banner
uses URL-collapse, drawer uses the full post-body renderer; iOS port
checklist + visual test included.
