/**
 * Tests for feature-013: named persistent Chrome profiles.
 *
 * Covers the three pieces of the feature:
 *  - ChromeLauncher: name validation, stable directories, ephemeral: false so
 *    the bug-007 cleanup paths leave them alone, and reset semantics.
 *  - ConfigManager: where the profile root resolves to (global by default,
 *    per-project override via chrome.persistentProfileRoot).
 *  - config tool: the resetProfile / listProfiles actions.
 *
 * No real Chrome is ever spawned - the launch path is exercised through the
 * profile bookkeeping it depends on.
 */
export {};
//# sourceMappingURL=persistent-profiles.test.d.ts.map