docs: lessons learned from 2026-07-12 session

- gpu-fleet: Corrected architecture (direct GPU, no router in path).
  Updated context values (RTX 3090=256K, not 128K). Added api-key
  standardization requirement.
- gpu-self-heal: Added Lessons Learned section with 5 critical findings:
  L1: API key standardization (RTX 5070 sk-loc...5678 vs not-needed)
  L2: Fallback chain cascading failure loop detection
  L3: Verify running state, not documentation
  L4: Infisical fallback requirement (.env must have uncommented key)
  L5: Zulip event queue can silently die after ~40 reconnects
- litellm-self-heal: Updated status manual-only→deployed, cron schedule
- litellm-api-keys: Added Infisical token expiry warning + .env fallback
- hermes-config-template: Rule 3 updated with .env fallback requirement

hermes-config-template.prose.md

@@ -203,6 +203,13 @@ The following MUST be identical across ALL profiles:
 - Prefer `api_key_env: LITELLM_API_KEY` over hardcoded keys
 - Hardcoded keys in config.yaml become stale after key rotation
 - Infisical vault secrets persist across config updates / reinstalls
+- **NEW (July 2026): Always keep a local `.env` fallback.** Infisical service tokens
+  can expire/404 (tanko incident: token not found, gateway ran without key for hours).
+  The `.env` file should have the key uncommented as a fallback:
+  ```
+  LITELLM_API_KEY=sk-...
+  # [INFISICAL] Also sourced from vault.sysloggh.net
+  ```
 - Restart Hermes after env var updates
 
 ### Rule 4: Sub-Agent Profiles Inherit Auth