Add InfisicalStaticSecret for telegram-notify in n8n/portfolio/openclaw/polymarket-bot (parallel)

Phase 3a of telegram-notify migration: each syncs TELEGRAM_BOT_TOKEN/
TELEGRAM_CHAT_ID from shared homelab/prod /telegram via read-only
infisical-operator/infisical-auth, into parallel-name telegram-notify-infisical.
Old plaintext secrets + hooks untouched (repoint=3b, removal=3c).
polymarket-bot: standalone secret only; bot-secrets copy is migration #3.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

polymarket-bot/infisical-telegram-notify.yaml

@@ -0,0 +1,24 @@
+apiVersion: secrets.infisical.com/v1beta1
+kind: InfisicalStaticSecret
+metadata:
+  name: telegram-notify
+  namespace: polymarket-bot
+spec:
+  # Shared, read-only machine identity (no write grant, no PushSecret).
+  # NOTE: this migrates only the STANDALONE telegram-notify secret. The same
+  # Telegram token also embedded in bot-secrets is migration #3 — not touched here.
+  infisicalAuthRef:
+    name: infisical-auth
+    namespace: infisical-operator
+  sources:
+    - projectId: 17e98e9d-70f5-43d1-8382-7da818dfcdd0   # project "homelab"
+      environmentSlug: prod
+      secretPath: /telegram                              # shared across all 5 namespaces
+  syncOptions:
+    refreshInterval: 60s
+  targets:
+    - kind: Secret
+      name: telegram-notify-infisical          # parallel name — old telegram-notify stays live until 3c
+      namespace: polymarket-bot
+      creationPolicy: Owner
+      # key passthrough: synced Secret carries TELEGRAM_BOT_TOKEN + TELEGRAM_CHAT_ID verbatim