Idle notification threshold behavior after prebuild resume in GitHub Codespaces 2024.09

The goal is to confirm that idle notifications fire reliably after a codespace is automatically resumed from a prebuild when the adjustable idle‑notification threshold introduced in the 2024.09 release is in use.

Because the idle timer is reset on resume, the notification subsystem should evaluate the new threshold against the fresh idle period, but observations show that alerts can be missed when the threshold is set low or when an organization policy caps the maximum allowed value.

Uncertainty remains about how the reset interacts with the default suppression mode and whether policy‑enforced maxima override the per‑user setting in this scenario.

Does the notification system correctly apply the user‑configured threshold after a prebuild‑triggered resume, or does it retain the previous timer state? When an organization policy imposes a maximum threshold, does it suppress alerts that should fire based on the user’s lower setting after a resume?