A dispatch the engine is holding back without writing anything (#97): a
ceiling that clears itself — the resource cap (MC), the host spend window
(HB) — defers rather than pauses, so nothing in state.yaml says why the
run is not moving. This is that why, kept as process ephemera and carried
on the heartbeat so Gatehouse can show a host-level condition at the host
level instead of a per-run escalation pointing at a file that holds no
such number.
A dispatch the engine is holding back without writing anything (#97): a ceiling that clears itself — the resource cap (MC), the host spend window (HB) — defers rather than pauses, so nothing in
state.yamlsays why the run is not moving. This is that why, kept as process ephemera and carried on the heartbeat so Gatehouse can show a host-level condition at the host level instead of a per-run escalation pointing at a file that holds no such number.