Per escalation index, the state commit in which resolved became true — the
record's own answer to "when did the human resolve this", which resolved_at
only claims (#346).
history is newest first, as stateHistory returns it. Escalations are
append-only and their indices are stable, so index i here is index i at
the tip. The commit wanted is the oldest one in the trailing run of being
resolved: keep overwriting while resolved holds, and settle the moment an
older commit shows it false, so a hand un-resolve-and-resolve-again reports
the second resolution rather than the first.
The engine and Gatehouse both read this, from one definition, because the
round-cap card must vanish exactly when rule D4 stands down.
Per escalation index, the state commit in which
resolvedbecame true — the record's own answer to "when did the human resolve this", whichresolved_atonly claims (#346).historyis newest first, asstateHistoryreturns it. Escalations are append-only and their indices are stable, so indexihere is indexiat the tip. The commit wanted is the oldest one in the trailing run of being resolved: keep overwriting whileresolvedholds, and settle the moment an older commit shows it false, so a hand un-resolve-and-resolve-again reports the second resolution rather than the first.The engine and Gatehouse both read this, from one definition, because the round-cap card must vanish exactly when rule D4 stands down.