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

src/application/services/storage_usage_service.rs

@@ -65,7 +65,7 @@ impl StorageUsageService {
     /// `GET /api/drives` therefore lags by up to the cache TTL (30 s),
     /// which matches the sibling caches' accepted UX phantom for
     /// drive-name staleness. Tests / operators that need immediate
-    /// freshness call `POST /api/admin/jobs/storage_reconcile/trigger`,
+    /// freshness call `POST /api/admin/jobs/usage_reconcile/trigger`,
     /// which runs `update_all_drives_storage_usage` → this method.
     ///
     /// Security posture unaffected: `check_drive_quota` reads
@@ -576,7 +576,7 @@ impl StorageUsageService {
     }
 }
 
-pub const STORAGE_RECONCILE_JOB_NAME: &str = "storage_reconcile";
+pub const USAGE_RECONCILE_JOB_NAME: &str = "usage_reconcile";
 
 use crate::infrastructure::scheduler::{JobHandler, JobOutcome, JobRegistry, JobRunArgs};
 use async_trait::async_trait;
@@ -600,7 +600,7 @@ impl StorageUsageService {
 #[async_trait]
 impl JobHandler for StorageUsageService {
     fn name(&self) -> &str {
-        STORAGE_RECONCILE_JOB_NAME
+        USAGE_RECONCILE_JOB_NAME
     }
 
     /// Runs both reconciliation sweeps — drives first, then users —

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

src/interfaces/api/handlers/admin_handler.rs

@@ -2335,7 +2335,7 @@ pub async fn list_jobs(State(state): State<Arc<AppState>>) -> impl IntoResponse
 /// `force=true` requests acceleration semantics from handlers that
 /// support it (dedup_gc → grace = 0, grant_cleanup → grace = 0).
 /// Silently ignored by handlers that don't (trash_cleanup,
-/// storage_reconcile).
+/// usage_reconcile).
 ///
 /// `deep=true` opts into slow variants — `consistency_batch` fans it
 /// out to sub-jobs; `storage_consistency` (when implemented) will