# REPORT — 2026-10-09 (afternoon): R-921 pre-check and R-922 `email_cleared` (UNRELEASED)

Not released, not delivered: both ship with the next controller release, **after** the hub release that decodes
`email_cleared` (felhom.eu `d55c590c`). MinAgent unchanged (0.131.0).

- **R-921 — check first, stop second.** Before a window stops apps, the controller asks the agent which tiers have a
  backup job in flight (`GET /backup/status`, per tier). Another tier's job running or snapshotted → no app stops; the
  tier stays due. A refusal after the stop still resumes the apps at once (pinned). Red-proof:
  `TestR921_NoStopWhileAnotherTiersJobIsInFlight` — before: `3 app(s) stopped for a tier the agent refuses`.
  **Not covered:** the agent's host-wide busy lock (night OS step, restore test, fstrim), the case measured on demo-hp
  on 2026-10-08 — no agent endpoint serves it; needs an agent field (felhom.eu R-921, LEFT).
- **R-922 — a household's clear reaches the hub.** Saving an empty address where one was stored marks it cleared
  (`settings.json`); every preferences push while it stays empty carries `"email_cleared": true` (omitted otherwise);
  a never-configured box never sends it; a new address drops it. Red-proof: `TestR922_DeliberateClearSendsEmailCleared`
  — before: `the push after a deliberate clear carries no email_cleared:true`.
- Suite: `go test ./... -count=1` rc 0 (35 packages); `controller_gates.py` rc 0. No docker used.
- Built by a helper session under the brief's fences; reviewed and committed by the main session.