Pull partner token ledgers into a RAM cache so fleet totals are fleet-wide

Deployment/master.conf.template

@@ -380,6 +380,7 @@
         # to 1 day). 30min was true "always fresh" but had no consumer that needed it that often.
         "Arrs_Stack/arr_cache_prefill.sh ARR_PREFILL_WAIT_MINUTES=1"  # keep the shared arr tracked-data cache fresh
         "Arrs_Stack/arrs_failed_stalled_recovery.sh"  # blocklist + re-search failed/stalled arr queue items
+        "AI/ai_token_sync.sh"                         # pull partner AI token ledgers into the tmpfs cache
     )
     # arr_sync.sh runs as a fixed first step in intermediate_sync_maintenance.sh — not listed here.
     # It is controlled by ARR_SYNC_ENABLED (see Arr Sync section above).
@@ -1661,6 +1662,13 @@
     AI_TOKEN_DB="$DATA_DIR/ai_token_history.db"
     AI_TOKEN_RETAIN_ROWS=20000      # oldest rows dropped past this — years of ordinary use
 
+# AI/ai_token_sync.sh pulls each partner's ledger into the tmpfs cache the tab reads, so the
+# fleet total is a fleet total. Same trick conf_sync.sh uses for partner confs, minus the push:
+# nothing here is needed by anyone else, so the reader fetches its own data and controls its
+# own freshness. An unreachable partner is a quiet skip, not a warning — a partner is expected
+# to be down for long stretches, and a four-hourly warn trains you to ignore the script.
+    AI_TOKEN_SYNC_ENABLED=true
+
 # ━━━ AI Feature Toggles ━━━
 # Tier 1 is narration — it cannot change a decision. Tier 2 adds context to a decision a script
 # already made. Tier 3 assists a human. Enable in that order, and give each one weeks.