What problem does it solve? Without type safety in @rangojs/router, ctx.reverse() and href() accept any string so typos 404 at runtime instead of failing at compile time, ctx.search and ctx.params fall back to loose Record<string, string>, and untyped ctx.env bindings surface as undefined in production rather than build errors. ## Core Features & Use Cases - Generated route types: Run npx rango generate to produce router.named-routes.gen.ts, which auto-registers GeneratedRouteMap globally for Handler<"name">, ctx.reverse(), href(), and Prerender typing. - Typed params and search: Add search schemas to path() options and use RouteSearchParams/RouteParams utility types for compile-time checked query and URL parameters. - Typed environment and context: Register Rango.Env and Rango.Vars globally, use createVar<T>() for scoped context tokens, and type handles, loaders, and location state. - Use Case: In a monorepo with multiple Rango apps, give each app its own tsconfig and generated route map so Rango.GeneratedRouteMap augmentations do not collide across routers. ## Quick Start Ask the AI to set up end-to-end type safety for my Rango router, including generated route types, typed search params, and typed environment bindings.