/**
 * @file
 *
 * Pure decision for whether unregistering a vault may tear its window down.
 *
 * The desktop CDP transport used to answer this with a single flag. Its
 * readiness guard asks `ownedConfig || isHarnessOwnedInstance` — the two ways
 * "the harness owns this instance" can be true — while its teardown guard asked
 * only `ownedConfig`. A **worker** attached to a harness-owned instance has
 * `isHarnessOwnedInstance: true` and no `ownedConfig` at all (the global setup
 * owns the config; the worker was handed only the port), so it fell straight
 * through the teardown guard and ran `destroyCurrentWindow()` against the vault
 * it was asked to unregister. When that vault is the one the whole run shares,
 * its window is the only one — destroying it quits the app, and every later file
 * fails with `ECONNREFUSED` on a closed CDP port, which reads as a harness
 * outage rather than as a teardown that overreached.
 *
 * Making the two guards identical would fix that and break something else: an
 * attached worker that registers its **own** `TemporaryVault` does need that
 * window closed, and a blanket early-return leaks one stale window per temp
 * vault for the life of the run — each pointing at a directory the disposal has
 * already deleted. Since every worker in a `createSetup` run is an attached one,
 * that is the common path, not an edge case.
 *
 * So the invariant is narrower than either guard expressed: **a worker attached
 * to a harness-owned instance may tear down only a vault it registered itself.**
 * Everything else in that instance belongs to the global setup that launched it.
 *
 * Kept out of the integration-only transport module (excluded from unit tests,
 * `LF:0` in coverage) for the same reason `vault-path-match.ts` is — so the
 * decision is unit-testable while the transport keeps only the plumbing.
 */
/**
 * Parameters for {@link shouldTearDownVaultWindow}.
 */
export interface ShouldTearDownVaultWindowParams {
    /**
    Whether this transport is a worker attached to an instance the harness launched elsewhere.
     */
    readonly isHarnessOwnedInstance: boolean;
    /**
    Whether this transport launched and owns the instance itself.
     */
    readonly isOwnedInstance: boolean;
    /**
    Whether this transport is the one that registered the vault being unregistered.
     */
    readonly isSelfRegistered: boolean;
}
/**
 * Whether unregistering a vault may destroy its window and remove it from the
 * registry, or must leave the instance untouched.
 *
 * @param params - Who owns the instance, and who registered the vault.
 * @returns `true` when the window may be torn down.
 */
export declare function shouldTearDownVaultWindow(params: ShouldTearDownVaultWindowParams): boolean;