next.js

676b665e - Pass lazy response lifecycle capabilities into App rendering (#100395)

Pass lazy response lifecycle capabilities into App rendering (#100395) ## Summary Continue decoupling App Router rendering from HTTP responses by binding lazy development response capabilities at the route-module boundary. HMR cancellation, validation scheduling, and worker snapshots use these capabilities instead of accessing `originalResponse` in the renderer. Preserves listener registration timing, abort reasons, live completion state, and the response wrapper's preview-cookie synchronization. Adds unit coverage for these behaviors and scoped import restrictions to keep response lifecycle access at the adapter boundary. ## Verification 38 test executions passed: - Lifecycle and existing response-completion unit tests: 11. - `test-dev-turbo`: HMR cancellation, validation scheduling, and worker source maps: 11; 9 snapshots. - `__NEXT_CACHE_COMPONENTS=true test-dev-turbo`: HMR cancellation and static-shell validation: 8; 1 snapshot. - `test-dev-webpack`: HMR cancellation and validation scheduling: 6. - `test-start-webpack`: standalone Node/Edge bundling: 2. <!-- NEXT_JS_LLM -->