CloudNet v4 auto-scaling: dynamic server provisioning

Description

For release, the server fleet needs to scale automatically based on player demand. CloudNet v4 should spin up new game server instances when all existing ones are full and shut them down when idle.

Acceptance Criteria

• CloudNet v4 task is configured with minServiceCount: 1, maxServiceCount: 10
• Auto-start threshold: new instance starts when existing instances are ≥80% full
• Auto-stop: idle instances (0 players for 5 minutes) are stopped
• CloudNet bridge communicates player counts to the load balancer (proxy)
• Proxy (Velocity/Waterfall) routes joining players to least-loaded game server
• Deployment pipeline (ci-deploy.yml) pushes new JAR/Docker image to CloudNet template on release tag
• Documented in docs/ops/cloudnet-scaling.md

Technical Details

• CloudNet v4 REST API or module config for auto-scaling rules
• Game server must send playerCount updates to CloudNet bridge on join/leave
• Requires CloudNet bridge module integration in server

Dependencies

• "Docker Compose + CloudNet v4 deployment config for alpha server" (Alpha) must be the foundation

Estimate

L

Start with the dependent Docker Compose and CloudNet v4 deployment configuration, then inspect the server bridge integration and ci-deploy.yml. Confirm the provisioning thresholds, player-count routing, release deployment, and the documented procedure in docs/ops/cloudnet-scaling.md.