Correct rendering of childless non-leaf nodes was addressed in T6742, however, there is one corner case where it will still be incorrect: namely, a configtree with //both// leaf and tag set, as can occur during a migration from a leaf (multi) node to a tag node. This only affects rendering, not global validation with `validate_tree`. This was discovered during the course of testing T9460, which exposes the small number of migration scripts missing set_tag in the case above, previously obscured by use of `load_explicit`.
The suggestion would be that `set_tag` unset leaf, as the two are mutually exclusive, and use in migration scripts will easily (past and future) call the former without the latter.