Monitoring coding environments without token polling

Developer notifications are scattered across too many surfaces.

You check GitHub. You check Slack. You check CI. You check calendar. Most of the time, nothing needs action, but the context switch still costs attention.

There is a useful inversion here:

do not make the developer visit every surface
bring important signals into the coding environment
do not use model tokens to discover that nothing changed

The model should not be the thing idling in a polling loop. Deterministic workers can watch the boring state. The model should wake when judgment is useful.

That is a small architectural boundary, but it matters. It keeps the coding environment as the command center without turning monitoring into a token tax.