The page-1/load-more continuity tests compared the filter bags two call sites emitted. Both now call one function, so those comparisons assert that a function equals itself: they cannot fail, and a test that cannot fail is upkeep without signal. Remove them and their shared helper. Nothing they covered goes uncovered. Each query's filters, order, bounds and limit stay pinned in events-load-more.test.ts, which drives every registry entry and asserts the exact params it issues. A route calling the wrong query is still caught by the envelope it emits, since a query mints an envelope naming itself — those assertions are kept where the pairings had them. What remains per route is what a route decides: which query it runs, the scope it derives from url/params, whether an inbound ?cursor= may resume, and its own errors. past-events also keeps the still-running exclusion, which shapes results rather than the query. Frozen clocks stay only there, where fixtures depend on one.