next.js

dc3ff1e6 - fix(app): prevent 404 responses for interception routes with missing children slots

fix(app): prevent 404 responses for interception routes with missing children slots When rendering interception routes like (.)[id], there's a segment mismatch where the interception route lacks a children slot that the base [id] route has. Previously, the framework injected a 404 page into the missing default slot, causing full 404 RSC responses on platforms like Vercel when using cache components. This fix introduces a null-rendering default component specifically for interception routes, ensuring minimal RSC payload and preventing 404 status codes. The old page.tsx is still used during client navigation, so there's no visible change to users. Fixes the "unknown segment value fallback page" issue for cached components.