fix(chutes): use force=False to prevent API lag from wiping local usage

The subscription_usage API updates slowly (often sub-cent precision
that truncates to 0). With force=True the background refresh was
overwriting locally-tracked usage with stale zeros. Now uses
force=False so UsageManager keeps max(local, api).

Author: b3nw

src/rotator_library/providers/chutes_provider.py

@@ -295,7 +295,7 @@ async def refresh_single(api_key: str, client: httpx.AsyncClient) -> None:
                             quota_max_requests=four_hour_cap_cents,
                             quota_reset_ts=None,
                             quota_used=four_hour_used_cents,
-                            force=True,  # API values are authoritative
+                            force=False,  # Keep max(local, api) — API lags behind
                         )
 
                         # Push monthly window data (overall budget)
@@ -313,7 +313,7 @@ async def refresh_single(api_key: str, client: httpx.AsyncClient) -> None:
                             quota_reset_ts=None,
                             quota_used=monthly_used_cents,
                             quota_group="monthly($)",
-                            force=True,
+                            force=False,  # Keep max(local, api) — API lags behind
                         )
 
                         monthly = balance_data.get("monthly", {})