Eight days of silence in #alerts and an eleven-hour queue
One rejected message jammed the whole channel and nothing said so; the seven thousand alerts that piled up were then delivered at one every six seconds.
What I did
Brought the Discord bot back up; it had died with an unexpected machine restart and stayed down because its configuration still held the repository path on the old drive.
Found why #alerts went silent for eight days: one rejected message whose fingerprint ran to 2,224 characters against a 2,048 limit in the footer jammed the whole channel.
Made the parked-task alert name what is parked; until now it sent an empty list.
Went through the piled-up alert queue one at a time and insisted the cause of the slowness be measured rather than guessed; batching came out of it, instead of one card edit per alert.
Extended branch cleanup to every namespace the factory pushes under; only claude/ and codex/ were being swept.
Had the remote branches nobody needs any more deleted.
What the factory did
Stopped one task file from living in two board folders at once.
Promoted nothing and wrote down why: every draft it would have taken sits in one of five open promotion pull requests.