App Router: dynamically imported component renders fallback content instead of its actual content

This issue was created by an agent analysing CI failures from the Next.js Deploy Suite (vinext main vs Next.js v16.2.6, 2026-05-22).

Problem

A dynamically imported component should render its actual content (e.g. submit) but instead renders the loading/fallback text (e.g. Reload). The lazy component never resolves to its target output.

Expected component to render `submit`, rendered `Reload` (loading fallback)

Estimated Impact

~1 test failures across the deploy suite.

Affected Test Suites

• test/e2e/app-dir/dynamic-import/dynamic-import.test.ts

Recommendation

1. Reproduce first in vinext's own test suite. Add a next/dynamic import of a server/client component and assert the actual component text renders, not the loading fallback.

2. Investigate why the lazy import never resolves. Check the dynamic chunk loading path: missing chunk URL, failed module evaluation, or Suspense never resolving.

---

Part of #1328.