refactor(usage_reconcile): explicit naming to prevent confusion with storage (backend)

src/infrastructure/scheduler/types.rs

@@ -24,7 +24,7 @@ use serde::{Deserialize, Serialize};
 /// Semantics of `force`, per job:
 /// - `dedup_gc` — skip the orphan grace window (grace = 0).
 /// - `grant_cleanup` — grace = 0.
-/// - Others (trash_cleanup, storage_reconcile, …) — ignored.
+/// - Others (trash_cleanup, usage_reconcile, …) — ignored.
 ///
 /// Semantics of `deep`, per job:
 /// - `consistency_batch` — propagate to sub-jobs; only `storage_consistency`

src/infrastructure/services/drives_consistency_service.rs

@@ -6,7 +6,7 @@
 //! writes never decrement on `move_to_trash`) and the sweep at
 //! `storage_usage_service.rs::update_all_drives_storage_usage`.
 //! **Read-only** — reports drift as findings but does
-//! NOT fix it. The existing `storage_reconcile` job (Part 1) is what
+//! NOT fix it. The existing `usage_reconcile` job (Part 1) is what
 //! corrects the counter; this check surfaces WHEN drift happens so
 //! operators can trace it back to root cause (missed delta call,
 //! delta failed silently, race, etc.).
@@ -145,7 +145,7 @@ impl RecoverableJobHandler for DrivesConsistencyCheck {
 
             // Fetch next batch of drives + their actual SUM in one
             // query. LEFT JOIN via correlated subquery gets us both
-            // sides in one round-trip; the storage_reconcile sweep
+            // sides in one round-trip; the usage_reconcile sweep
             // uses the same shape.
             // Grace window: skip drives created within the last hour.
             // A drive being created RIGHT NOW may still have its first