//! Read-only Factory `droid` CLI quota provider.
//!
//! This provider reuses the login the official `droid` CLI already wrote: on
//! Linux the session lives in `~/.factory/auth.v2.keyring`, sealed with a key
//! from the Secret Service keyring. It never logs in, refreshes, or writes
//! credentials itself — near expiry it can ask the CLI to renew its own
//! login (`renew`) — and its HTTP client rejects all redirects so the token
//! is never forwarded through one.
use crateDroidConfig;
use crateResult;
pub use keyring_path;
/// Resolve the CLI's stored login. The config holds no paths: the provider
/// only supports the one place the CLI writes on Linux.