fix(notifications): keep baselines across degraded usage observations

Three planner defects shared one root cause: a degraded observation was
treated as an authoritative quiet state, dropping threshold baselines.

- processReset skipped a present row whose percentage was unknown, so a
  single unreadable window disarmed an armed reset and the promised
  reset notice could never fire.
- processQuota dropped the row baseline for the same unknown-percentage
  rows, so the next refresh re-announced an unchanged condition.
- an error observation with zero rows still wiped quota/pace/reset state
  when a status incident was present (observationPending only preserved
  it without an incident), so recovery re-announced the ongoing level;
  a failed first observation also primed the scope empty, announcing
  the first healthy level. The observation now carries errorPresent and
  transition leaves threshold state untouched for such passes while
  status keeps processing.

Red/green: the four new QtTests fail on the previous module (433 pass,
4 fail) and pass with the fix (437 pass, 0 fail).
da4a114b2dSimone committed on 9/2/2026, 2:06:26 AMparent70a595b
3 files changedLine totals unavailable