Hono defaults to SmartRouter, so one unusual route can change matching for every route

The default Hono export uses SmartRouter, which tries RegExpRouter first and falls back to TrieRouter when the registered routes contain patterns RegExpRouter cannot compile, notably multiple parameters inside one path segment. The decision is made once at first dispatch, from the whole route table rather than per route.

The consequence is that adding a single unusual route changes the matching engine for the entire application, which shows up as a latency change rather than a failure and is hard to attribute later. On Workers the guidance is to keep patterns simple. The tiny entry point favours the smallest bundle at some cost in matching speed, and the quick entry point favours the lowest setup cost for environments that build a fresh instance per request.