1 Commits (2099fa65930a1915cb6eff991c347bbdba221d71)

Author	SHA1	Message	Date
Ashley	2099fa6593	Keep a populated home feed when a forced warm publishes nothing ... A forced warm that came up with no publishable candidates deleted the live feed key. For a per-user feed that is destructive in exactly the wrong direction: the warm can come up empty because the viewer's cached following list is stale or because the statuses behind the candidates could not be resolved, and the user who was reading their timeline a moment ago is left with nothing. The scratch key is dropped instead and the live feed is untouched. The instance-wide feeds keep their clear-on-empty behaviour, which now has a comment saying why they differ. warmCache also returns the number of members it published instead of a constant 1, which is what lets a caller tell "rebuilt and ready" from "nothing to show". The unused $returnIds parameter is gone; all four call sites discarded it. Verified standalone off staging: HomeWarmEmptyResultTest 2 passed; HomeChronologicalOrderTest green; tests/Feature/Timeline + HomeFeed 73 passed.	7 days ago