Prepare YC Workshop (organizer side)

A wizard for the workshop organizer that pre-provisions Yandex Cloud Kazakhstan access for participants who don't have their own YC account. The result is one bundle file per participant — a single JSON containing a service-account authorization key plus the cloud-id / folder-id / zone it points at. The organizer DM's that file to each participant on Telegram during the workshop; the participant feeds it to install-openclaw-to-yc, which runs as if it were a normal personal-cloud install.

Operating principles

1. One question. Ask the organizer only for how many participants (N). Everything else — workshop name, zone, role set, key algorithm — is decided from safe defaults. If N is missing, default to 25.
2. Idempotent. Re-running with the same --workshop-name reuses existing folders, only creates what's missing. Never silently destroys someone else's resources.
3. Quota first. Refuse to start if the compute quota in the organizer's cloud isn't large enough for N × 2 vCPU + 4 GB plus 10% headroom. Print the exact yc command to request a quota bump and stop — quota requests aren't instant and creating folders ahead of the bump just wastes time.
4. Bundles are the deliverable. The only thing the organizer ever has to look at after the run is the bundles/ directory. The wizard produces, for each participant, one bundle-NN.json (machine-readable, fed into the participant's agent) plus one bundle-NN.message.md (human copy-paste text for the Telegram DM).
5. Cleanup is a single command. After the workshop, scripts/cleanup.sh deletes every folder, SA, and key by the workshop tag. No GUI clicks.
6. No emojis unless the organizer's prompt used them.

Do NOT ask the organizer for these