mirror of
https://github.com/agentscope-ai/ReMe.git
synced 2026-10-24 05:47:32 +00:00
A reminder's topic_id derives from a stable schedule title, so blocking it
like a discovery item silenced a recurring reminder for the whole cooldown
window after a single delivery. A schedule that is due has to be announced
every time it comes due.
Both layers that apply the cooldown now let kind == "reminder" through:
* the agenda step dropped already-delivered candidates *before* pinning
reminders, so a reported reminder never reached the pinning guarantee;
* the reader's _select_agenda withheld it again on the way out, and
counted it in delivered_ids.
The other three kinds keep the existing behaviour and `failed` deliveries
still never block. Each site gets a regression test that fails without the
exemption.
|
||
|---|---|---|
| .. | ||
| fixtures/config | ||
| integration | ||
| unit | ||