v5.2.0: trie router, performance pass, executor hardening

[jkyberneees]

Summary

• New trie router (lib/router/trie.js, zero external dependencies): same API, middleware chain, nested routers and error containment as the sequential router, with a segment-trie matcher and a compile-on-demand static table. Case-sensitive by default, literal static segments, null-prototype params, no request-keyed cache. Opt in with require('0http/lib/router/trie')().
• Sequential router performance pass: drop-in find with exact length prefilters, lazy params, top-level lookup fast path, structural query-string fast path, no per-request closure in the setImmediate dispatch.
• Executor hardening (both routers), from an adversarial security/correctness/perf review:
  • mount prefixes are stripped from the path only, so a query string can never become a nested router's path
  • a user errorHandler is skipped once the response has ended (writing would raise an uncatchable stream error)
  • defaultRoute runs under error containment
  • one router mounted at several prefixes keeps every mount; use() normalizes g/y RegExp flags
  • linear query parsing for segment-heavy strings
• Docs and landing page updated; version bumped to 5.2.0.

Benchmarks (ns per lookup, min of 5, Node 22, M2 Pro)

Routes	Router	static	param	2 params	nested	query
5	sequential	153	192	259	325	320
5	trie	81	175	233	339	318
505	sequential	149	1438	7878	334	1615
505	trie	83	180	238	347	323

Verification

• 142 tests passing, lint clean, 97.7% statement coverage; every fix has a regression test
• Differential fuzzing: trie vs sequential (360k lookups), new find vs Trouter#find (millions), query parser vs URLSearchParams (600k strings), all zero diffs
• Repo security tooling (pentest, pollution, type confusion, regex audit) passes with both routers

🤖 Generated with Claude Code