fix: nested .section fragment bug

[fkakatie]

Problem: Fragment links on pages were getting wrapped in .default-content-wrapper.

Root cause: buildFragmentAutoBlocks was async. It hid the fragment <p> but didn't convert it to a block element before decorateSections ran, so the <p> got wrapped into .default-content-wrapper. By the time the async load resolved, the replacement landed inside that wrapper.

Proposed fix:

• scripts/scripts.js — buildFragmentAutoBlocks now synchronously converts the fragment link <p> into a real fragment block div (same pattern as widget/video auto-blocks) before decorateSections runs.
• blocks/fragment/fragment.js — decorate() now handles two cases:
  • fragment is the only thing in its section: replaces the whole section with the fragment's sections, making them proper siblings in <main>
  • fragment is mixed with other content: strips the fragment's inner section wrappers and flattens the block wrappers directly into the containing section, preserving document order

Headline: No nested .section divs in either case. 🎉

Test URLs:

• Before: https://main--progressrail--aemsites.aem.live/en/company/leadership
• After: https://fragment--progressrail--aemsites.aem.live/en/company/leadership

[aem-code-sync]

Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch and validate page speed.
In case there are problems, just click a checkbox below to rerun the respective action.

• Re-run all PSI checks
• Re-run failed PSI checks
• Re-sync branch

Commits

• 8a2a297 ✅ (latest)
• 84decb5 ✅

[aem-code-sync]

	Page	Scores	Audits	Google
📱	/en/company/leadership
🖥️	/en/company/leadership