Agrega scripts y runbooks: Cloudflare API, autostart Coolify, parche Chatwoot, deploy Solo Leveling + docs de casos

- scripts/Invoke-CloudflareApi.ps1: control de tunnel/DNS via API
- scripts/Install-CoolifyAutostart.ps1 + scripts/host/: autostart de LXC 102 + tunnel tras corte
- scripts/Apply-ChatwootEnterprisePatch.ps1: parche enterprise (autodetecta creds)
- Deploy-SoloLeveling.ps1: deploy build-on-server verificado
- docs/runbooks/cloudflare-tunnel.md y autostart-coolify.md
- docs/casos/chatwoot-enterprise-patch.md (credenciales redactadas)
- docs/AGENTS-coolify-apps.md + issues y reportes
- deploy_skill/references/coolify-4.1.2-notes.md: hallazgos verificados (seccion 7)
- package.json para verify-online.mjs del coolify-deploy skill
- .gitignore: excluye .claude/ y .opencode/ (config local de herramientas)

scripts/host/coolify-autostart.service

@@ -0,0 +1,17 @@
+[Unit]
+Description=Auto-start Coolify LXC + Docker stack + Cloudflare tunnel after boot
+# Managed by the Proxmox & Coolify Manager repo (scripts/host/coolify-autostart.service).
+# Run after Proxmox has processed onboot guests and the network is up. This is a
+# self-healing safety net on top of the LXC onboot flag and Docker restart
+# policies, not a replacement for them.
+After=pve-guests.service network-online.target
+Wants=pve-guests.service network-online.target
+
+[Service]
+Type=oneshot
+ExecStart=/usr/local/bin/coolify-autostart.sh
+RemainAfterExit=yes
+TimeoutStartSec=300
+
+[Install]
+WantedBy=multi-user.target