Startup Should Mean “No Ambiguity Allowed”
What I actually like here is the refusal to treat collisions as some exotic runtime bug. That instinct is right. If two extensions can claim the same method, or if an extension can shadow a core MCP method, you do not have a cute dispatch problem — you have a configuration error that should blow up immediately. Anything else makes startup order part of your application logic, which is the sort of hidden behavior that comes back to bite you later. That said, the piece also reads a bit like it is
papoo.work