/**
 * ecs_launch capability detection.
 *
 * A resident agent should only advertise the `ecs_launch` capability when it
 * can actually perform ECS RunTask/StopTask — i.e. when AWS credentials are
 * resolvable through the default provider chain (env vars, shared
 * config/credentials files, SSO cache, IMDS/ECS metadata, ...). Advertising
 * it unconditionally would let the API's automatic launcher selection pick an
 * agent that cannot launch anything, making ECS dispatch fail unpredictably.
 *
 * Override (checked before detection):
 *   AI_SUPPORT_AGENT_ECS_LAUNCHER=true   force-enable, skip detection
 *   AI_SUPPORT_AGENT_ECS_LAUNCHER=false  force-disable, skip detection
 *
 * The detection result is cached for the process lifetime so the register
 * retry loop does not re-probe the credential chain (IMDS/STS) on every
 * attempt.
 */
/** Reset the positive-detection cache (tests only). */
export declare function resetEcsLauncherCapabilityCache(): void;
/**
 * Decide whether this agent should advertise the `ecs_launch` capability.
 * Returns true when credentials are resolvable or force-enabled via env.
 */
export declare function detectEcsLauncherCapability(env?: NodeJS.ProcessEnv, timeoutMs?: number): Promise<boolean>;
//# sourceMappingURL=launcher-capability.d.ts.map