/**
 * Domain message handler — `event.data.messageId` resolution path.
 *
 * Handles any event whose data carries a `messageId`, regardless of
 * event type (per ADR-097). All stdlib actions use this pattern;
 * story actions emitting `action.success` / `action.blocked` events
 * also flow through here.
 *
 * Public interface: `tryProcessDomainEventMessage`. The pipeline
 * consults this first; on null, it falls through to the type-keyed
 * handlers (room, revealed, generic, etc.).
 *
 * Owner context: `@sharpee/engine` — internal prose pipeline.
 *
 * @see ADR-097 Domain Events with messageId
 * @see ADR-174 §Engine-internal prose pipeline (extracted from
 *   text-service.ts inline)
 */
import type { ITextBlock } from '@sharpee/text-blocks';
import type { ISemanticEvent } from '@sharpee/core';
import type { HandlerContext } from './types';
/**
 * Process domain events that carry messageId directly (ADR-097).
 *
 * @returns Text blocks if event has messageId. Returns null when the
 *   event has no messageId (caller falls through to type-keyed
 *   handlers). Falls back to inline `data.message` / `data.text`
 *   when the messageId fails to resolve.
 */
export declare function tryProcessDomainEventMessage(event: ISemanticEvent, context: HandlerContext): ITextBlock[] | null;
//# sourceMappingURL=domain-message.d.ts.map