/** * Shared helpers for filesystem-face connectors that delegate to a host-side * fleet supervisor (rclone for sharepoint/webdav/googledrive, git for git). * * When `SKAILE_FLEET_MANAGED_MOUNTS` lists a connector's id, the host has * already prepared the underlying mount (rclone FUSE mountpoint, or a git * worktree bind) and exposed it at the driver's target dir. The driver * short-circuits its own connect path after verifying the bind is live. */ /** * Return `true` when `connectorId` appears in the comma-separated * `SKAILE_FLEET_MANAGED_MOUNTS` env var, indicating the host fleet owns this * mount. */ export declare function isFleetManaged(connectorId: string): boolean; /** * Sanity-check the host bind mount before declaring success. The host * process should have the FUSE mount live before the container starts, so * we verify the directory exists, is readable, and is genuinely a mount * point. Polls briefly to absorb any startup race between container start * and the kernel publishing the mountpoint inside the container. * * `readdir` surfaces FUSE-side errors that `stat` cannot (e.g. transport * endpoint not connected if the host process died after bind). * * The mountpoint assertion is what catches a target mismatch: when the driver * and the host fleet disagree about where the bind lands, the driver's own * target dir exists and reads fine as an empty local directory, and without * this check the session silently runs against container disk instead of the * remote. */ export declare function ensureFleetMounted(dir: string, log: { info: (msg: string, data?: object) => void; }, options?: { timeoutMs?: number; pollIntervalMs?: number; mountinfoPath?: string; }): Promise; /** * Health verdict for a fleet mount target. * * Kept so existing callers can keep typing `ConnectorManager.reportFleetHealth` * while the method is a no-op in the package-side bind-consumer. */ export type FleetHealthVerdict = "healthy" | "degraded" | "error"; //# sourceMappingURL=fleet-utils.d.ts.map