/**
 * synap whoami
 *
 * Answers the one question `synap status` can't: WHICH key is this session
 * actually authenticating with, and does the ambient `SYNAP_HUB_API_KEY`
 * silently disagree with the pinned `claude-code` surface key?
 *
 * `synap status` probes via `resolveHubConfig()` and prints a single "Valid"
 * off whichever key wins — which HIDES the case where the env key is revoked
 * but a valid surface key is pinned (or vice-versa). This command:
 *   1. resolves the winning cfg (the key every command uses),
 *   2. independently reads env key + `claude-code` surface key and reproduces
 *      the surface-over-env preference rule from hub-client.ts:394-403,
 *   3. introspects the winner via `/auth/status`, and
 *   4. when env and surface keys diverge, names the winner AND the ignored key,
 *      probing the loser too so the operator sees both states side by side.
 *
 * It never mutates state and never relies on resolveHubConfig's stderr swap
 * warning (hub-client.ts:398-400) — it reads the divergence itself.
 */
export declare function whoami(): Promise<void>;