Resolve route admission before opaque data preparation

[KidkArolis]

Cold loads and speculative prefetches could begin resolver and data work before an application applied synchronous admission policy. That unnecessarily warmed protected route data and left authentication boundaries exposed to preparation races.

Routes now support synchronous parent-first guard(route) checks before resolver loading, preparation, prefetching, or rendering. Returning a destination redirects; returning undefined admits the segment and continues through its children. React Space Router depends on space-router@^2.1.0 and reuses its canonical getRouteRedirect() helper, so cold preparation follows the same guard-before-redirect ordering as normal navigation.

Preparation also no longer assumes that every data layer represents work as [definition, args]. Routes declare flat arrays of opaque requests, either statically or through one outer queries(ctx) resolver. The router never invokes values inside that array, including function-valued requests, and forwards each one unchanged to data.prepare(request) or data.prefetch(request). Argument binding and validation stay entirely with the adapter.

Validation: npm test passes all 102 tests against the published space-router@2.1.0 package.