You'll notice
Useful3 Signal3
If you configure a second status line, it can now report its own errors instead of staying silent.
What's wrong with this entry?
Anonymous. No account, no email.
What
The "already logged once" latches for status-line command failures moved from being shared across the whole process to being tracked per status line, so a second configured status line can still report its own success or exec_error instead of being silenced by the first one.
Evidence
Status hook failed:
Strings lifted out of the shipped bundle, so the claim above can be checked against them.