/**
 * Refresh the cached unread count after a command has done its work.
 *
 * Deliberately here and NOT in bin.ts, where the printing lives. bin.ts runs before citty has
 * parsed argv, so it has no resolved environment and no token; by the time a command finishes,
 * CommandContext has both — the same reasoning that puts the telemetry beacon here.
 *
 * Three properties this placement buys, all of them required:
 *  - never fires for a logged-out creator: getAccessToken throws before any network happens,
 *    and nothing is written, because no check took place to back off from.
 *  - never slows a command down: the count is for the NEXT run, the fetch is bounded at two
 *    seconds, and the print side is a pure file read.
 *  - never speaks for the wrong environment: the count is cached against the one that was
 *    actually resolved for this command, flags included.
 *
 * This is NOT telemetry — it is the creator's own inbox — so it is deliberately not gated on
 * DO_NOT_TRACK. It reports nothing about the user; it asks a question on their behalf.
 */
export declare function refreshUnreadMessages(): Promise<void>;