Provide caching at the "sub query" level inside the convex deployment.
Specifically if a developer calls ctx.runQuery(...) within a query or mutation, and that individual query's cache value is still valid, the cached value will be used instead of running v8 again.
This will allow developers to control caching to a much greater degree. For example, authenticated queries might still not be commonly cached because they require checking each user's credentials. But then, after checking the credentials, the dependent data they're fetching is a common view (the contents of a shared chat room) that can just be retrieved using a subquery. This will make the site faster and save database bandwidth and costs.