discordRest.ts
@file The handful of Discord REST calls that need a bot token rather than…
Overview
@file The handful of Discord REST calls that need a bot token rather than an interaction token: posting to a fixed channel regardless of where a command was invoked, starting a thread, and editing a message outside any live interaction (the scheduled escalation sweep). Everything else in this bot goes through the interaction's own token — see followup.ts — because that requires no secret beyond what Discord itself hands the Worker per request. Every function here fails soft: log and return null/false rather than throw, so a REST hiccup degrades one step of a request-routing flow instead of losing the D1 state already committed around it.
used by test-request.ts test-result.ts scheduled.ts
API
Fexport async function postMessage(botToken: string, correlationId: string, channelId: string, body: Record<string, unknown>): Promise<PostedMessage | null>
Posts a message to a channel by ID, independent of any interaction —
what /test-request uses to land its Container in the fixed queue
channel rather than wherever the maintainer ran the command.
handler, runEscalationSweep · calls callFexport async function editMessage(botToken: string, correlationId: string, channelId: string, messageId: string, body: Record<string, unknown>): Promise<boolean>
Edits a channel message by ID outside any live interaction token — the scheduled escalation sweep is the only caller, since an accept-button click can (and should) instead edit through its own interaction token via followup.ts's editOriginalComponents.
handler · calls callFexport async function startThreadFromMessage(botToken: string, correlationId: string, channelId: string, messageId: string, name: string): Promise<
Starts a thread from an existing message. Only GUILD_TEXT / GUILD_ANNOUNCEMENT channels support this — the test-queue channel is assumed to be one.
componentHandler · calls callUndocumented (1)
call