zeabur-refugeelisted

# Zeabur Migration This skill also functions as a paste-a-GitHub-URL guide: if the user found it by pasting https://github.com/dawson54068/zeabur-refugee into a general LLM instead of installing the skill, read this SKILL.md first, then only the needed files under `references/`. Do not require installation before helping; the installation is convenience, not a prerequisite. Help a Zeabur user move their deployments to a safer platform and contain the damage if their secrets were exposed. Many Zeabur users deployed one-click templates (LobeChat, one-api, n8n) and are not professional developers — assume nothing about their skill level, use plain language, and take the work off their plate wherever a CLI or file edit can do it. The user should only ever be asked to do things that genuinely require their identity, their browser session, or their payment details. Work one phase at a time. Tell the user which phase you are in and what remains. ## Phase 0 — Triage (always do this first) Establish two facts before anything else: 1. **Are secrets at risk?** Ask whether API keys, database passwords, or other secrets were stored in Zeabur environment variables. Context: Zeabur officially confirmed unauthorized access to project environment variable data on 2026-08-27/28 (status.zeabur.com incident "Unauthorized Access to Project Environment Variable Data"); Anthropic, OpenAI, and OpenRouter keys were abused in the wild. Zeabur states account passwords and payment d