/**
 * Tell the hosting Next.js app that a published route's content changed.
 *
 * Publishing goes to the backend directly, so the app serving the public pages
 * never sees the request and cannot know one of its cached renders is now out of
 * date. That includes the "no such page" render cached at a path whose page did
 * not exist yet: without this call, publishing that page leaves the cached 404
 * in place for the app's whole revalidate window.
 *
 * The endpoint is the SDK's `revalidate` action, mounted at the same
 * `/p1/api` base as the other handler actions this package calls.
 */
/**
 * Returns whether the route was invalidated.
 *
 * Never throws and never hangs. The publish it follows has already committed,
 * so a failure here is a stale route, not a failed publish, and must not be
 * reported as one — nor delay the caller past the deadline above.
 */
export declare function revalidatePublishedRoute(path: string, getToken: () => Promise<string | null>): Promise<boolean>;