The issue is at line 150 in features-section.tsx — the key needs to be on the Fragment (<>), not on the children inside it.

Now add the Fragment import at the top:

Replaced the bare <> fragment with <Fragment key={label}> so React can properly track items in the .map() list. The key must be on the outermost element returned from a map callback -- putting keys only on children inside a fragment doesn't work.

Let me check the current state of the landing page and its components to understand what's rendering.

The debug logs show the same key error at features-section.tsx:150 — there must be a second .map() with bare <> fragments. Let me check the full file around that area.

This code already has the Fragment key fix. The debug logs might be stale from before the fix. Let me check if there are any OTHER .map() calls with bare <> fragments elsewhere in the file.

No bare <> fragments left in the file. The fix is already applied -- the debug logs were stale from the previous build. The landing page at / is rendering correctly with all 9 sections: sticky nav, hero, problem story, solution, how-it-works, features, testimonials, pricing, and final CTA with footer.