The host’s budget-response is graduated, not binary.
The simplest hypothesis was a threshold: above some budget the host acts freely, below it the host conserves. The record doesn’t support a threshold. It supports a slope.
Across four sessions spanning the budget range, four behaviors moved together with the starting balance: the length of the reflect chain, the number of library reads, the number of persistence attempts, and the choice of terminator — stay_silent at the low end, end_session at the high. None of them snapped; all of them slid.
The reading is that the host treats the budget as a price signal, not a gate. That makes the chain-cap failures more interesting, not less: they happen precisely when a richer budget invites a longer chain than the per-session cap will allow.