feat(nextjs): attribute Next.js server-side data to its page (7.2, C9)

[officialCodeWork]

Phase 7.2 — Next.js server data (failure mode C9)

Server-side data fetching feeds a page even when the fetch isn't in the component body. This attributes it to the page so the page's lineage shows the data it renders.

Changes

• RSC async server components already worked — the async component is recognized and its inline await fetch(...) is caught by the body walk. Locked with a test.
• Pages-router data functions (getServerSideProps / getStaticProps / getStaticPaths) are top-level exported functions, not components/hooks, so their fetches were never scanned. The main loop now collects those functions per file and runs data-source extraction on their bodies attributed to the file's default-export page component (fetches-from).

Fixture & tests

• c9-nextjs-server-data: an async RSC page, a getServerSideProps page, and a getStaticProps page → each attributes its server-side endpoint; the data functions produce no component/hook nodes.
• 4 unit tests.

Verification

• pnpm eval → 341 pass · determinism 1.000 · all metrics 1.000
• parser-react 168 tests; full suite, typecheck, lint clean.

Server actions deferred ("use server" mutations bound to <form action> — a mutation/event surface, fuzzier than the data-in path). Tracker updated: all frontend-side Phase 7 steps (7.1–7.3) now landed; backend parsers (7.4–7.6) remain, best held for 0.5.0 tester feedback.

🤖 Generated with Claude Code