data is the provider-defined id the bot set
when building the control. respondBy is the ack deadline (Discord 3s /
Telegram spinner). When the provider declares capabilities.interactionsRequireAck
the core calls acknowledgeInteraction exactly once per interaction: with text
from ctx.acknowledge(text), otherwise deferred ({ defer: true }) before the
handler’s first send, shortly before respondBy, or when routing ends, whichever
comes first. Without the capability the core acks only on ctx.acknowledge().
Type Parameters
Properties
interactionId
'' when the transport cannot guarantee that. Never a
per-user or per-control constant (sender id, payload): core dedupes on
chatId + interactionId, so a reused id silently drops the user’s next
interaction. See the INBOUND ID CONTRACT on IProvider.