How does the App Router resolve a URL to a page component?

My searches didn't surface the actual App Router request-matching/rendering code (the next-server, router-server, or app-render matching logic) — the retrieval kept returning CLI, webpack HMR runtime, and loader-utils files instead, which aren't relevant to this question. Rather than speculate about internals I can't cite, I'll be upfront: I don't have sufficiently targeted, citable source in what's been retrieved (the repository_data block and my two searches) to describe the App Router's URL-to-component resolution pipeline (e.g., how next/dist/server/route-matcher-manager, app-render.tsx, or the flight/segment tree resolve a pathname to a specific page.tsx/layout.tsx module) with accurate file/line citations.

If you'd like, I can run a more targeted search (e.g., for route-matcher, find-page-file, AppPageRouteModule, or resolveRoute) to pull in the actual resolution code and give you a properly cited breakdown.

FOLLOW_UPS:

• Search for the AppPageRouteModule request handling code?
• How does file-system based routing map to route matchers?
• What is the role of app-render.tsx in Next.js?