plan: stability, not gimped — jobs 2, rings all on the box

dami committed Aug 277ecd346

commit: 7ecd3461834e18203091c78776188e699d5abbf1
parent: 4dc8fa938a1f6bc21d0cd71a0cab2926c5900797
author: dami <gazey55@gmail.com>

1 file changed, +4 -4wrap lines

++++----

@@ -652,10 +652,10 @@ with two rings ahead.
652652 ### Decided 2026-08-27: the hosted box is run for stability, not speed653653 654654 Generation moves onto the Fly box now that a chunk is ~250 MB on a655-region-sized board. Rules: one chunk process at a time (`--jobs 1`)656-unless measured RSS and nightly duration both leave wide margin; the657-nightly job has a fixed budget and a ring cap chosen so it finishes658-inside half of it; at rollover there is always a playable field655+region-sized board. Stability does not mean gimped: `--jobs 2` on the656+2-vCPU box (two ~250 MB chunks fit easily), `--rings all` with the657+whole night as budget, no artificial caps; what stability means is that658+at rollover there is always a playable field659659 (prepared, else last pushed, else a small emergency field generated on660660 the spot) — never "no field today"; the generator is a supervised child661661 the daily loop kills on timeout and that can never take the site down;