import type { ChatModification, WAPatchName } from '../Types/index.js';
import type { SocketContext } from './types.js';
export declare const makeChatActionMethods: (ctx: SocketContext) => {
    pinChat: (jid: string, pin: boolean) => Promise<void>;
    muteChat: (jid: string, muteUntil?: number | null) => Promise<void>;
    archiveChat: (jid: string, archive: boolean) => Promise<void>;
    starMessage: (jid: string, messageId: string, star: boolean) => Promise<void>;
    /**
     * Compatibility wrapper for original Baileys chatModify API.
     * Routes to the appropriate bridge method based on the modification type.
     *
     * Fully supported: archive, pin, mute, star, markRead, delete, deleteForMe, pushNameSetting, contact, clear
     * Not yet in bridge (app-state patches): disableLinkPreviews, labels, quickReply
     */
    chatModify: (mod: ChatModification, jid: string) => Promise<void>;
    /**
     * Force re-sync of app state collections.
     *
     * In the Rust bridge architecture, app state is managed internally by the engine
     * and synced automatically on connect. This method is a no-op provided for API
     * compatibility with upstream Baileys.
     */
    resyncAppState: (_collections?: readonly WAPatchName[], _isInitialSync?: boolean) => Promise<void>;
    /**
     * Fetch disappearing message duration for contacts.
     *
     * Not yet supported — requires USyncQuery which is handled internally by the bridge.
     * Disappearing mode changes are emitted via the 'disappearing_mode_changed' event.
     */
    fetchDisappearingDuration: (..._jids: string[]) => Promise<undefined>;
};
//# sourceMappingURL=chat-actions.d.ts.map