I could be wrong, but the version history (LifeTime) are still environment specific. LifeTime has tables which contains the data of which version is on which environment (I thought based on the eSpace identification guid). So on the environment itself you can delete eSpace versions that could be in a tagged version in OutSystems. LifeTime is the connecting application between the environements.
When you do a deploy OS is building a solution and publish that solution into the next environment. Solutions aren't connected to each other, so a dev eSapce version isn't (physical) connected to a tst eSpace version.
Kind regards,
Evert