A further thought in the light of the above, it is probably useful to note in then-current Tinderbox version used to make the doc. hat might help someone months or years latter to figure out how/where no-current behaviour has diverged since. Assuming a resource like aTbRef (and the previous baseline versions of it) are around it should possible to figure out relevant app feature changes in the interim.
Simple case in point. a doc from 4.x, opens in v9. But every window (pre-v6 design was somewhat different) opens as a document window which is confusing. Maps will look as fonts have changed, Colour defaults have changed, the size/rendering of notes has changed. None of that is a show-stopper but means some interpretation is needed.
The same is true of action and export code behaviours. For example, pre v5 Sets had a ~ toggle add/remove operators. That was removed in v5 and the were no changes up until v8. But, in v9 Sets the notion of Sets always re-sorting themselves was enforced. Hitherto, it was a risk you took. A Set, as Lists only arrived in v5) might resort from the input order but generally didn’t, From v5 if sort persistence mattered more than deduping, we used a list, else a Set. In v5.9.2, we got List.unique making this choice less painful.
Sorry for the long explanation but i think it helps explain the suggestion at opening.