Enable real FTP credentials to flow through to the VPS

deploy/vps/compose.yml hardcoded LVGMC_USER/PASSWORD/URL to inert
placeholder strings directly in the file, unlike POSTGRES_* which
already read from .env.staging — so simply adding real values to
.env.staging would have had no effect. Switched to the same
${VAR} substitution pattern, and enabled ENABLE_LVGMC_FTP_JOBS now
that real credentials exist. HARMONIE stays on placeholders pending
real DMI credentials.

deploy/vps/compose.yml

@@ -32,15 +32,16 @@ services:
       POSTGRES_PASSWORD: ${POSTGRES_PASSWORD}
       POSTGRES_HOST: postgres
       ENABLE_SCHEDULED_JOBS: "true"
-      ENABLE_LVGMC_FTP_JOBS: "false"
+      ENABLE_LVGMC_FTP_JOBS: "true"
       ENABLE_HARMONIE_JOBS: "false"
       DEBUG: "false"
-      # The legacy FTP/HARMONIE provider services are still constructed at
-      # startup even though these flags keep their scheduled jobs off, so
-      # inert values are required until each one's real credentials exist.
-      LVGMC_USER: disabled
-      LVGMC_PASSWORD: disabled
-      LVGMC_URL: https://invalid.local/
+      # LVGMC_* now read real values from .env.staging (real FTP credentials
+      # obtained 2026-08-23). HARMONIE stays on inert placeholders until real
+      # DMI credentials exist — the provider service is still constructed at
+      # startup even with its scheduled job off, so it needs some value.
+      LVGMC_USER: ${LVGMC_USER}
+      LVGMC_PASSWORD: ${LVGMC_PASSWORD}
+      LVGMC_URL: ${LVGMC_URL}
       HARMONIE_EDR_API_KEY: disabled
       HARMONIE_EDR_URL: https://invalid.local/
       HARMONIE_STAC_API_KEY: disabled