3378e528e7
The gateway had exactly one global broadcast (skin.changed) fed by a 0.5s signature loop. Generalize that loop into a table of cheap on-disk signatures so the process broadcasts what it already knows: - pet.changed — active pet slug/sheet-revision/scale moved (/pet, hatch) - cron.changed — cron/jobs.json mtime moved (CRUD + scheduler tick) - sessions.changed — state.db/-wal mtime moved: the cross-process signal for messaging-gateway and cron-run writes (#58671), floored to one broadcast per 2s so a streaming turn's append burst coalesces gateway.ready now carries change_events:true so clients can demote their legacy polls to slow backstops while staying compatible with older backends. Groundwork for #73618.