That's not entirely true. CFBot never runs on patches that are only in closed commitfests.
Ofcourse the CFBot could be changed to behave differently, but then the question becomes how should it behave then? When do we want to stop running CFBot on patches?
Related: What do we do in general with patches that have been moved? And when do we do that?
It seems clear that if new patches are pushed to a message thread that was registered with commitfest at some point, we'd like CFBot to run on them.
What if we automatically move any patches to the current commitfest if new patch attachments are sent to the corresponding message thread? Heck, perhaps if there are any new messages *at all* in the message thread, and the commitfest entry has not been closed already, we should move it to the current commitfest. We could even have commitfest respond to the message thread to inform when automated actions of this nature have been taken.
