fix: handle broadcast RecvError::Lagged gracefully in maintenance loop

[thepastaclaw]

Addresses review feedback from CodeRabbit on #433:

1. Consistent logging macros
Replaced tracing::error! with log::error! to match the rest of manager.rs which uses the log crate throughout.

2. Handle RecvError::Lagged vs RecvError::Closed separately
Previously, any broadcast::RecvError was treated as fatal (broke the loop). Now:

• RecvError::Lagged(n): Log a warning with the count and continue. Lagged just means we missed some broadcast events — not fatal.
• RecvError::Closed: Log an error and break. The channel is gone, maintenance loop should stop.

---

🤖 This was generated by an automated review bot.
Don't want automated PRs or comments on your code? You can opt out by replying here or messaging @PastaPastaPasta on Slack — we'll make sure the bot skips your PRs/repos going forward.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}