Yes. There is some revision going on in the definition of "Work" under the private licensees, but the idea is that if a developer published 1.0.0 to repository

Yes. There is some revision going on in the definition of "Work" under the private licensees, but the idea is that if a developer published 1.0.0 to repository A, you bought a private license, and developer published 2.0.0 there later, your private license covers both 1.0.0 and 2.0.0. If they rewrite and push to C, however, that's a new ballgame. There's no obligation under any L0 form (or any OSS license I'm aware of) to provide any ongoing service. A developer could still offer services---training, support, maintenance, feature adds, etc.---around L0 code. Speaking of perverse incentives, we see exactly that with pure service-based business models. Why write good doc if you're selling training? Why make it easy to deploy if you're selling installation or hosting? And so on. That _is not_ to say those models can't be done well.