docs(service-delete): document async deletion behavior

[marvin-69-jpg]

Summary

Adds a "Behavior to be aware of" section to zeabur-service-delete documenting three properties of the CLI's delete that are easy to misread as failures:

1. Deletion is async. A successful service delete schedules removal — the service typically continues to appear in service list as Status=SUSPENDED for some time before eventual consistency clears it. The skill currently implies delete is immediate, which led me to conclude the delete had failed when the service was still in the list.

2. Retrying a delete errors with 'already scheduled', not because it failed. The CLI returns:

   ```
   ERROR delete service failed: Message: Resource already exists, ...
   description:service deletion already scheduled or service not found
   ```

   The error is misleading — it actually confirms the first delete worked. Documenting this so agents don't loop trying to "fix" a successful delete.

3. service get --id <id> is the way to confirm actual removal — it returns "service not found" once the service is gone, while service list may still show it for minutes due to lag.

Test plan

• Reproduced async delete: ran service delete -y -i=false with success exit, but service appeared in service list for several minutes after with Status=SUSPENDED
• Reproduced "already scheduled" error on retry of an already-deleted service
• Confirmed service get --id <id> returns "service not found" once removal completes, while service list was still lagging

🤖 Generated with Claude Code

[coderabbitai]

Warning

Rate limit exceeded

@marvin-69-jpg has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 58 minutes and 41 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 58 minutes and 41 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 8120986b-f803-4aae-9cc7-6b6751bd6c4a

📥 Commits

Reviewing files that changed from the base of the PR and between 78b02c1 and 6bf74ee.

📒 Files selected for processing (1)

• skills/zeabur-service-delete/SKILL.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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