I haven’t seen the code for how the env stuff works, but… My instinct is that we’re going to want to end up with everything being consistently dirtied, rather than having some things be dirtied and others changing their nodekey. My instinct is also that if we end up with just one, it would probably be the env one, and we would try to treat “file digest” akin to the env var value (possibly through some “mark node as blocked on a filesystem digest notification” mechanism), as that feels more general than going the other way around (trying to shoehorn invalidation into env vars)...