pull down to refresh
I've seen something similar-ish once, spotted in a cycle test, where a component didn't have any wear at all, but that turned out to be a test scope error, not a firmware bug.
which should've been disabled in production
That snippet describes exactly what last night's hotfix does.
I also don't understand how they didn't have within their testing a process for ensuring the seed was really being hardware generated, and not relying on the software fallback (which should've been disabled in production in the first place)