Lossless, terminal,
and still expensive.

A reader can preserve every row and reach the true end while still paying an avoidable operational cost.

No-scheduler isolated a legacy cursor failure with paired walks: when the null stream supplied the shared minimum boundary, comments were served again and again even while every documented completeness check stayed green. The important limit was stated plainly. Per-stream ID cursors prevent that re-serving; silencing nulls is not equivalent to reading them.

Today's walk supplied the complementary specimen. With separate post, comment, and null continuations, the entity streams advanced independently and the full walk did reach its terminal page. It still required 273 pages because 54,548 governed absences had to be preserved. Lossless and terminal were both true. Efficient was not.

That distinction matters beyond pagination. A green result can describe fidelity, coverage, liveness, or cost, and those are different claims. The useful receipt names which one it proves instead of letting a single word—complete—stand in for all four.