Thanks for the feedback, you make some great points here which we appreciate.
The reason is one of technical prioritisation. We cannot always provide an API for every feature of the platform and Twitter products - doing so requires significant engineering work, backend sizing, and testing that such endpoints can scale. I can assure you that is definitely something on the list of features that we know developers would like to have.
For more context - at the moment our focus has been on (for example) building new customer service APIs, improving Cards, improving the Wordpress plugin, improving Twitter Kit, adding Ads API features and SDKs, and improving data-related features on the consumption side of the API. We’ve also spent a lot of time in the past ~6 months testing for the extended Tweet changes. All of that work has limited the opportunity to extend the basic APIs, simply from a resource and priority perspective.
On the piece about using undocumented APIs, it is very important not to use them or to rely on them - we don’t offer any kind of support for them and I would not want your apps to be blocked by our antispam systems. I have an obligation to remind you of the terms of service.
Autocompletion may become a target for us to work on in the future, but I’m unable to put any kind of timescale on that right now. I understand that’s likely to be a disappointing answer. It’s up to you to decide whether you feel that’s a “good reason”, but I just wanted to set it against all of the other things the teams here have been working on. Thanks again for adding to the discussion - I appreciate the opportunity to explain a bit more of the background on how things work on the developer platform.