docs(example): one page wiring the whole navigation group together

examples/basic-app/app/pages/navigation.wrn puts all nine navigation
components in a single console shell instead of showing each alone: Navbar
with a nested dropdown, MegaMenu beside it, Breadcrumb, Sidebar as a rail that
becomes a Drawer, Tabs backed by a query parameter, a Stepper wizard,
Pagination, Scrollspy following the article, and Nav in the footer.

Three framework limits shaped the layout and are written into the page rather
than hidden:

  - object props are held in state and bound, because a brace at the start of
    an attribute is read as an interpolation
  - a shared function on a page is compiled standalone and cannot see page
    state by name, so state is passed as arguments
  - component props and slot content render once and do not track page state,
    so anything that has to react lives in page scope; Tabs reports the
    selection and the page owns what is shown

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

examples/basic-app/app/routes.gen.ts

@@ -12,6 +12,7 @@ export interface Routes {
   "/language-tools": Record<string, never>;
   "/login": Record<string, never>;
   "/modal": Record<string, never>;
+  "/navigation": Record<string, never>;
   "/partial-static": Record<string, never>;
   "/platform-showcase": Record<string, never>;
   "/reactive": Record<string, never>;
@@ -32,6 +33,7 @@ export interface RouteNames {
   "language.tools": "/language-tools";
   "login": "/login";
   "modal": "/modal";
+  "navigation": "/navigation";
   "partial.static": "/partial-static";
   "platform.showcase": "/platform-showcase";
   "reactive": "/reactive";
@@ -121,6 +123,7 @@ export function route<N extends RouteName>(
   "language.tools": "/language-tools",
   "login": "/login",
   "modal": "/modal",
+  "navigation": "/navigation",
   "partial.static": "/partial-static",
   "platform.showcase": "/platform-showcase",
   "reactive": "/reactive",