No, it is just that I have been prioritizing work over the past month or so trying to stabilize everything from the dev cycle so we can get a new stable build out.
In general, I am happy to tell you how something is implemented, but every single edge case isn’t necessarily obvious, even if you have the source code sitting in front of you. Sometimes it can take an hour to dig through everything and try to find a way to express all of the situations in which something may work subtly different. Ideally though, it isn’t just that we tell one person the answer to their questions, but rather write documentation so all package developers can use it. This means the process just takes a but longer. Sometimes when writing new documentation you have to spend a bunch of time thinking about the most logical way to present it all to users so they can understand it.
The other aspect in a discussion about things as fundamental as scopes is that changing things that have had edge case bugs part way through the lifecycle of a major version can actually introduce new bugs since there have been years of packages who may have run into the edge cases and worked around them. Just this dev cycle we fixed a couple of edge case issues related to plugin loading and received reports of breakages because packages happened to be utilizing the “broken” implementation.
As a matter of procedure, in general it may be better to open an issue on the issue tracked about missing documentation. That tends to be a better place to track things that need to be done by Sublime HQ, whereas the forum is more of a continuous flow of questions, support, ideas, announcements, etc.