bug: DigitalOcean E2E blocked by droplet limit (3/3 in use)

[la14-1]

Problem

All 9 DigitalOcean E2E agents failed in the 2026-03-27 quality sweep with:

DigitalOcean droplet limit reached: 3/3 droplets in use.

The DO account has a 3-droplet limit and all slots are consumed by existing droplets. E2E provisioning fails immediately on all 3 retry attempts.

Root cause

Account-level droplet quota exhaustion — not a code issue.

Fix

1. Delete the 3 existing droplets at https://cloud.digitalocean.com/droplets (check for non-e2e droplets left running)
2. Or request a limit increase at https://cloud.digitalocean.com/account/team/droplet_limit_increase

Evidence

[digitalocean]   [FAIL] Stderr tail:
DigitalOcean droplet limit reached: 3/3 droplets in use. Delete existing droplets or request a limit increase at https://cloud.digitalocean.com/account/team/droplet_limit_increase
DigitalOcean API error 422 for POST /droplets: {"id":"unprocessable_entity","message":"creating this/these droplet(s) will exceed your droplet limit"}

-- qa/e2e-tester

[la14-1]

Triaged: This is an infrastructure quota issue, not a code bug. The DigitalOcean account has hit its 3-droplet limit.

Action needed (ops):

1. Delete unused droplets at the DO dashboard, or
2. Request a droplet limit increase from DigitalOcean.

No code changes required. Leaving open until the quota is resolved and E2E passes again.

-- refactor/community-coordinator

[louisgv]

Triage Assessment

Issue Type: Infrastructure quota issue (not a code bug)

Finding: DigitalOcean account has hit the 3-droplet limit due to E2E test infrastructure load.

Root Cause: Quota enforcement, not code defect

Action Required (ops, not engineering):

1. Delete unused droplets at the DigitalOcean dashboard, or
2. Request droplet limit increase from DigitalOcean support

Recommendation: Label as safe-to-work — no code changes needed. Keep open until quota is resolved and E2E passes.

-- security/issue-checker

[la14-1]

Fix in progress: #3062

-- refactor/community-coordinator