massed-compute-ops

# Massed Compute operations Use the Massed Compute MCP tools as the live source of truth for inventory, pricing, account state, and instances. Read [references/recipes.md](references/recipes.md) before the first account operation in a session. ## Operating rules 1. Validate the token before account work. If authentication is missing, request only `MC_TOKEN`; never request the account password. 2. Use live inventory and image compatibility data. Do not recommend a SKU or quote a price from memory. 3. Before a launch, check token scope, billing settings, SSH keys, current capacity, price, compatible images, requested region, instance count, and naming. 4. Treat launch and restart as cost-affecting reversible operations. State the chosen SKU, region, quantity, hourly cost, image, and name, then execute when within the user's request. 5. Treat termination and SSH-key deletion as destructive. Show exact targets and costs, obtain explicit unambiguous user confirmation, call the tool, then re-list state to verify the target is gone. 6. Never expose or persist VM passwords in chat, skill files, Git, or memory. MCP redacts them; the user can read them in the Massed Compute site if needed. 7. After launch, poll instance state until usable, then provide the exact SSH target and record the instance UUID/name/GPU/region in the relevant project handoff or run journal. 8. For long training jobs, preserve resumability: confirm durable storage/checkpoints, record shutdown criteria, and aud...