GTM API / Replay webhook deliveries

Put the deliveries a broken endpoint left behind back on the wire: every webhook_logs row of this webhook created inside [from, to] whose status is in statuses (default failed + cancelled; success re-fires delivered events, opt-in) goes back to pending, oldest first, one row per second, and the normal scheduler delivers it under the same webhook_log_sid. Cancelled rows come back only when the platform cancelled them (webhook_failed / webhook_disabled / webhook_deleted), never an operator's manual cancel; rows in flight are never touched. from is required; the window spans at most 30 days and one call re-arms at most 5000 rows, refused with the cap named beyond either (narrow the window or statuses). Requires status=on: re-enable a failed webhook first (update_webhook status:'on'). Rate-limited to 10 calls/min per webhook. Re-delivers real events; state-changing. Contract: - MCP tool replay_webhook, registry package mcp.orchestration/webhooks, mount orchestration.webhooks. - Operation action, response envelope action. - Flags: dangerous: the MCP layer gates it behind a preview/commit token, and the effect cannot be undone through this API.