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

tests/api/user_envelope_quota.hurl

@@ -19,7 +19,7 @@
 #   4. Sweep self-heals — after trashing the personal file and
 #      `trigger-sweep`, `/me.storage_used_bytes` returns to 0.
 #
-# `POST /api/admin/jobs/storage_reconcile/trigger` is the
+# `POST /api/admin/jobs/usage_reconcile/trigger` is the
 # deterministic synchronisation point: it runs the drive-side sweep
 # then the user-side sweep (both under the periodic scheduler), so
 # both cached counters are authoritative ground-truth by the time
@@ -139,7 +139,7 @@ HTTP 201
 #      acts as the synchronisation point for the user-envelope
 #      assertion below — the sweep is the authoritative
 #      ground-truth for both drive- and user-side counters.
-POST {{base_url}}/api/admin/jobs/storage_reconcile/trigger
+POST {{base_url}}/api/admin/jobs/usage_reconcile/trigger
 Authorization: Bearer {{admin_token}}
 [Options]
 delay: 200ms
@@ -159,7 +159,7 @@ jsonpath "$[?(@.id=='{{shared_drive_id}}')].used_bytes" == 32
 # If the delta path incorrectly fired the user counter, the sweep
 # would still correct it back to 0 (the new SQL excludes shared
 # drives) — this also validates the sweep formula.
-POST {{base_url}}/api/admin/jobs/storage_reconcile/trigger
+POST {{base_url}}/api/admin/jobs/usage_reconcile/trigger
 Authorization: Bearer {{admin_token}}
 
 HTTP 200
@@ -207,7 +207,7 @@ jsonpath "$.storage_used_bytes" == 32
 
 # Confirm the sweep agrees with the delta — both code paths must
 # give the same number.
-POST {{base_url}}/api/admin/jobs/storage_reconcile/trigger
+POST {{base_url}}/api/admin/jobs/usage_reconcile/trigger
 Authorization: Bearer {{admin_token}}
 
 HTTP 200
@@ -237,7 +237,7 @@ Authorization: Bearer {{owner_token}}
 
 HTTP 200
 
-POST {{base_url}}/api/admin/jobs/storage_reconcile/trigger
+POST {{base_url}}/api/admin/jobs/usage_reconcile/trigger
 Authorization: Bearer {{admin_token}}
 
 HTTP 200