import { SlackMessage } from './types/wire';
/**
 * Slack message-type policy lives on the UI side: the API sends the raw
 * Slack `subtype` and the client decides what to do with it. Today that
 * means hiding the reply affordance for system messages; a future
 * milestone can branch rendering (e.g. a centered "X joined" notice)
 * off the same field.
 *
 * These system subtypes are channel lifecycle events that Slack does NOT
 * allow thread replies on — attempting to reply 500s on their side.
 */
export declare const NON_REPLYABLE_SUBTYPES: ReadonlySet<string>;
/** Ordinary messages (no subtype) are replyable; system subtypes above
 *  are not. Unknown subtypes default to replyable. */
export declare const isReplyable: (message: Pick<SlackMessage, "subtype">) => boolean;
//# sourceMappingURL=messageType.d.ts.map