As I mentioned in my previous reply, that really depends on the perspective of what the users are, which in this case are the stage snap consumers. As stage snaps is a new concept previous conventions will obviously need some adaption to it.
it’s unclear to me how a developer would use this zenity-integration
Should attach it in the first place, apologies:
what happens if the base: requirement for the main snap conflicts with that of the zenity-integration included snap
That isn’t a supported setup in the first place, which is documented in the prerequisite section of the aforementioned forum topic.
we do use tracks to allow a snap to support two different core versions, in such a case the tracks are typically 16 and 18 (not core18 or core16).
I followed the naming fashion of the multipass snap, but that always can be adapted 