Shard Versioning Controls

tl;dr - Each shard has a dev copy and a published copy in the "same shard" that allows the author to develop and change and test the shard themselves without interfering with the published copy that subscribers use. When dev is ready, it can be published to become the published copy.

Expanded explanation:

Currently it seems the save and sharing system is very simplistic. The author makes changes and hits save, everyone using the shard gets the changes immediately, assuming they don't have the edit shard option active. This is very useful for actively editing and testing the shard while in development, however...

This causes issues, what if the author makes a mistake while updating or adding features? Everyone using that shard will immediately get the broken shard until the author repairs it.

The author could have a private "Master" copy of the shard, make a copy and publish the copy, a snapshot, but if any updates get made to the Master, a new copy will need to be created and anyone using that shard will need to grab the new version instead.

A version control system would solve this. Allowing publishing of shards, say v1.0, folks can use v1 while the author makes changes, adds features, etc just as now with the instant updating for rapid testing and development. They can then publish that new version (v1.1) only when they've tested it and feel it's ready. The end user now sees the option to switch between v1 and v1.1. The author has the option to delete v1 if they chose, but this doesn't effect the master copy they can still edit and test for themselves (the dev copy they can activate on their own devices for testing) without messing with the published copy that people might be using in their games.