refactor(dashboard): consolidate Suspense double-comment in tile strip

The trend-card row in src/app/page.tsx carried two adjacent comment
blocks describing the same `<Suspense>` boundary — one from the v1.4.40
W-RSC seed and a second from the v1.4.41 W-FRONTEND-FACTORY fallback
hoist. Collapse into one block keyed to current behaviour with a
one-line history trailer. The sibling chart-row Suspense stayed in
single-block shape so no second consolidation was needed.
This commit is contained in:
Marc-André Bombeck committed 2026-05-21 18:55:14 +02:00
1 parent 1ea0321da7
commit b5ef81a01b
1 file changed
+5 -17
+5 -17
View File
@@ -1400,26 +1400,14 @@ export default function DashboardPage() {
{trendCards.map((entry) => (
<div key={entry.id} className="flex min-w-0">
{/*
* v1.4.40 W-RSC — per-tile `<Suspense>` boundary.
* The tile body is synchronous today (every tile
* reads from the merged `data` memo which already
* gates on the slim/thick analytics queries on the
* parent), so this fallback never paints in the
* current composition. The structural boundary
* matches the chart-row layer below so the entire
* dashboard composition reads as a streaming-ready
* grid of independently suspending cells — and
* future RSC hoists of any tile slot won't need a
* second pass to add the fallback infrastructure.
*/}
{/*
* v1.4.41 W-FRONTEND-FACTORY (UX M1) — swap the
* `null` fallback for a layout-stable placeholder
* that mirrors the trend-card chrome. The body
* stays synchronous today so the fallback rarely
* Per-tile `<Suspense>` boundary with a layout-stable
* placeholder that mirrors the trend-card chrome. Tile
* bodies are synchronous today so the fallback rarely
* paints, but a future RSC hoist of any tile slot
* would otherwise leave the grid track empty and
* trigger CLS as the cell paints in.
*
* v1.4.40 W-RSC — boundary added; v1.4.41 W-FRONTEND-FACTORY — fallback hoisted to layout-stable placeholder.
*/}
<Suspense
fallback={