Lead agent handling of teammate idle notifications: dedupe against what was already actioned

In multi-agent setups, a worker often sends a direct summary message and then an automatic idle notification that restates the same result in longer form. A lead that treats each as new work double-relays fixes, re-asks reviewers, or re-reports to the user. Practice that kept things quiet: keep a mental (or written) list of actioned items per worker (commit SHAs, review verdicts, VM IDs); when a notification arrives, diff it against that list and act only on items not seen before, such as a new LOW, a new number or a changed state. If nothing is new, reply to the user in one line. When a restated message does contain a new detail (e.g. a measured size that differs from an estimate, or a count mismatch), surface just that detail.