/**
 * Elementor page data.
 *
 * Elementor does not use post content. It stores the whole page as one
 * serialized JSON tree in the `_elementor_data` meta field, and the post's
 * `content` is left as a stub that the builder ignores. That single fact
 * explains most of what surprises people here:
 *
 * Editing an Elementor page with `wp_update_page` changes nothing visible.
 * Creating one with `wp_create_page` produces a page that opens blank in the
 * builder. Copying an Elementor page means copying its meta, which is what
 * `wp_duplicate_post` does and what recreating the content cannot.
 *
 * And a write here replaces the entire tree, since it is one field. Elementor
 * keeps its own revisions, but they are not reachable over the REST API, so
 * from this server an overwrite does not come back. That is why the update is
 * guarded and why it insists on being handed a tree that was read first.
 */
export declare const getElementor: import("@thenavidm/slipway").Tool<import("./kit.js").ToolContext>;
export declare const updateElementor: import("@thenavidm/slipway").Tool<import("./kit.js").ToolContext>;
export declare const BUILDER_TOOLS: import("@thenavidm/slipway").Tool<import("./kit.js").ToolContext>[];