You'll notice
Useful2 Signal1
A bad override warning now shows once per session rather than only in the first session.
What's wrong with this entry?
Anonymous. No account, no email.
What
The warning about a non-boolean override value moved from a process-wide once-flag to per-session tracking, so each session reports it once instead of only the first one doing so.
Evidence
willow_tern: ignoring non-boolean clientData
Strings lifted out of the shipped bundle, so the claim above can be checked against them.