fix: clarify server-project relationship to prevent SSH-based deployment

[yuaanlin]

Summary

• When users ask to deploy to a specific dedicated server (e.g. "deploy to my AWS Tokyo server"), the agent would SSH into the server to check for web servers instead of using the Zeabur CLI deploy flow
• Root cause: no skill explained the server↔project binding (Region.ID = server-<server-id>) or guided the agent away from SSH for deployment
• zeabur-deploy: added "Deploying to a Specific Dedicated Server" section with step-by-step instructions to find the matching project
• zeabur-server-list: added "Servers and Projects" section, marked SSH as debugging-only, added zeabur-deploy to See Also

Test plan

• Ask the agent to "deploy X to my [provider] [location] server" and verify it uses project list --json + Region.ID matching instead of SSH
• Verify SSH-related tasks (e.g. "check kubectl on my server") still work as before

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Enhanced dedicated server deployment instructions with clear guidance on mapping servers to Zeabur projects and establishing the proper deployment workflow.
  • Clarified that production deployments should use automated deployment methods rather than manual SSH-based approaches.
  • Designated SSH access for debugging and troubleshooting purposes only, not for production deployment or service management.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 1487a997-8e50-4576-9ab4-a2df685f0f8f

📥 Commits

Reviewing files that changed from the base of the PR and between 914d0f9 and 7d820a8.

📒 Files selected for processing (2)

• skills/zeabur-deploy/SKILL.md
• skills/zeabur-server-list/SKILL.md

---

Walkthrough

Documentation updates to Zeabur deployment skills clarify the relationship between dedicated servers and projects, establish a server-to-project mapping workflow using ID correlation, and redirect deployment operations from SSH to the zeabur-deploy skill, reserving SSH for debugging only.

Changes

Cohort / File(s)	Summary
Zeabur Deployment Guides skills/zeabur-deploy/SKILL.md, skills/zeabur-server-list/SKILL.md	Updated documentation to introduce dedicated server deployment workflow: establishes server-to-project mapping via server list and project list --json ID correlation, designates zeabur-deploy as the deployment mechanism, and clarifies SSH usage is for debugging only. Added guidance to invoke zeabur-project-create skill when no matching project exists.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'fix: clarify server-project relationship to prevent SSH-based deployment' directly and clearly describes the main change: clarifying the server-project relationship to guide users away from SSH-based deployment, which is exactly what both file changes accomplish.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/server-deploy-guidance

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}