One-time warnings are now tracked per host, so silencing one host does not silence the rest.
What's wrong with this entry?
Dozens of places that show a warning or log a diagnostic only once moved from a single process-wide registry to one scoped per host. In a single ordinary session nothing changes; in a process controlling several hosts, a warning silenced for one host no longer silences the others.
- Affected sites include the tool-search decision log, the MCP tree diagnostic, the voice initialisation gate, cron task load failures, and the interface tree-depth cap.
tool_search_optimistic_decision
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.232
Cache-break diagnostics kept in a per-session file
Both mention diagnostic
-
v2.1.248
Diagnostics store gains an alert slot that nothing writes to
Both mention diagnostic
-
v2.1.248
Dedicated error types for plan polling and referral eligibility
Both mention diagnostic