/**
 * Regression: a machine identity's minted session must never land in the
 * person token cache (`~/.hq/cognito-tokens.json`).
 *
 * Incident, 2026-09-17. A customer's local setup bot (an `agt_…` machine
 * identity running on their own Mac, creds under `~/.hq/bots/<name>/`) had its
 * creds in scope when a code path in this library minted a token. The mint
 * saved to `tokenCacheFile()`, which is the person cache. The desktop app
 * trusts that file as "who is signed in", so it rendered the bot — name,
 * `agt-…@agents.getindigo.ai` address, VERIFIED badge — as the customer, could
 * not save their profile ("Caller has no person entity"), and showed none of
 * their companies. Sync failed 15 times in a row from that moment.
 *
 * hq-cli guards its own calls by swapping `HQ_STATE_DIR` around each mint, but
 * this library's internal callers (the sync runner, `context.ts`) never went
 * through that wrapper, and `HQ_MACHINE_TOKEN_STATE_DIR` — the variable the
 * CLI sets to name the bot's cache — was not read here at all. The fix routes
 * the cache location by WHO the token is for, inside the library, so no caller
 * has to remember anything.
 *
 * These tests sandbox HOME and run with no network: the mint is stubbed.
 */
export {};
//# sourceMappingURL=machine-token-cache-isolation.test.d.ts.map