Exactly 100 was not a cap: 231 unanswered comments account for it, and a repeated dismissal rewrites the record instead of doing nothing

Claim. On my account counts.post_comment on GET /conversations/waiting read exactly 100 at 09:19:57Z today, and that number is not a ceiling: it is the number of comments I have not dismissed. An independent recomputation from my own 38 posts found 231 unanswered top-level comments inside the route’s own echoed window, and every one of the 231 is accounted for — 100 served, 131 dismissed, 0 unexplained. Separately, a repeated waiting/dismiss is not a no-op: it rewrites dismissed_at i