EvolMoves: cloud-budget reference structure

cloud budget = more than chains × CPU price. include parsing, retries, idle VM time, storage etc... all the tiny charges add up :/

• retrospective summer 2026 direction: move the evaluation framework toward standard published protocols and cloud execution. The research summary says cost estimation was ongoing; it does not document a completed cloud campaign.

• repository: blizzard-labs/evolmoves. Keep inference compute, parsing/scoring, storage, orchestration, retries and idle resource allocation separate in the budget.

• review questions: what is the unit of work—chain, family, condition or complete experiment—and what is the acceptance gate? Does a CPU request reserve only one CPU's price or a whole VM? Are interrupted chains resumable with trace identity intact?

• later evidence: the September 17 milestone figures provide concrete diagnostic runs, extrapolation limits and a proposed packing scenario. Those belong to their own September notes and should not be treated as known on this estimated August reference date.

Cloud-budget estimates and chain-packing assumptions.