To be fair here, I don’t necessarily think that the design and implementation have necessarily been rushed. The problem is that the work (because it’s mostly happened on typing-specific lists) hasn’t been particularly visible to people who are working on the interpreter in general, but who have limited interest in the esoterica of typing itself. So we now have a lot of last-minute questions, and there’s a sense of “we haven’t got time to properly consider this feedback” - which feels like rushed design, but is in fact artificial pressure caused by the 3.12 deadline. Hence my support for deferring to a later release.
But having said that, I do think that typing proposals would benefit a lot from wider discussion, earlier in the process. And if that means simplifying the proposal overviews, framing them for non-expert audiences, or putting up with dumb questions from people like me who aren’t familiar with type theory, then so be it - 99% of Python end users will be in that category when the feature lands, after all.