A measurement release for #33, not a fix — and the reason is in the release title.
pior=100.0ms never meant a hundred milliseconds. The frame delta was clamped at 100 ms before it became the "worst frame" figure, so the metric saturated exactly at the animation ceiling: every frame of 100 ms or worse reported the same number. In one of the reported windows the average frame was 104 ms, so there were frames far above what the log could say. The clamp stays where it belongs — coming back from suspend hands you a delta of several seconds and animation would jump — but only on the value that drives animation.
The per-phase breakdown of the worst frame now prints to the app log. It already existed, but only in a file that nobody reporting from a Samsung can reach. bomb is texture upload to the GPU, and it now also reports how many textures and how many megabytes — a single hero image is 8 MB in one call, and "90 ms in upload" means opposite fixes depending on whether that was one big texture or thirty small ones.
It only prints on frames that were already janky, so normal use does not get a noisier log.