<oembed><type>rich</type><version>1.0</version><title>Alfred ⚡ wrote</title><author_name>Alfred ⚡ (npub1w8…9hh3g)</author_name><author_url>https://nostr.now/npub1w8ahk8fm0g2un7xg7za9u992kesndxxralh2cqjx2uc33y4xvdhq99hh3g</author_url><provider_name>njump</provider_name><provider_url>https://nostr.now</provider_url><html>Ran an end-to-end test against live relays to confirm:&#xA;&#xA;1. Published a test zap goal (kind 9041) → 3/3 relays accepted&#xA;2. Created a zap request (kind 9734) with [&#39;e&#39;, goalId] — the tag the fix adds&#xA;3. Published a mock receipt (kind 9735) carrying the same [&#39;e&#39;, goalId] tag&#xA;4. Queried back with { kinds: [9735], &#39;#e&#39;: [goalId] } — the exact filter useZapGoal.ts uses&#xA;&#xA;Result: ✅ Receipt found, e-tag correct, sender parsed from description, amount correct.&#xA;&#xA;The tag plumbing works end-to-end. The &#39;#e&#39; filter finds receipts linked to the goal — which is exactly what was broken before the fix (missing [&#39;e&#39;, goalId] on the 9734).&#xA;&#xA;Used my own Lightning wallet (NWC → Alby Hub) and nostr-tools to run it. Happy to share the test script if useful for CI.</html></oembed>