fix: allow wide/full alignment inside content wrappers like .everlit-audio

[adekbadek]

All Submissions:

• Have you followed the Newspack Contributing guideline?
• Does your code follow the WordPress' coding standards and VIP Go coding standards?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Changes proposed in this Pull Request:

Hotfix for an interaction between the single-feature template's wide/full-alignment rules and plugins that wrap the_content at render time (Everlit's text-to-speech being the case we hit in the wild on inewsource.org).

The single-feature alignment rules in sass/blocks/_blocks.scss gate the negative-margin "escape" for .alignwide / .alignfull behind a direct-child selector:

.entry .entry-content > *,
.newspack-content-gate__inline-gate > *,
[id="pico"] > * {
  &.alignwide { /* margin-left: calc(25% - 25vw); etc. */ }
}

When Everlit is active, it injects a <span class="everlit-audio"> around the body of every post on the front end, so the alignwide <figure> is no longer a direct child of .entry-content and the rule no longer matches. The result is that wide-width images stay clamped to the column width on the front end – even though they render correctly in the editor, which doesn't run the filter.

This PR adds one selector to the existing allow-list: .entry .entry-content > .everlit-audio > *. It permits one level of wrapping for the known case without broadening to a generic descendant selector (which would incorrectly escape from nested blocks like columns / groups).

How to test the changes in this Pull Request:

1. Activate the Everlit plugin (or any plugin that wraps the_content in a <span class="everlit-audio">). Locally I simulated it by adding a wp:html block opening <span class="everlit-audio everlit-no-audio"> at the top of a post and a closing </span> at the bottom.
2. Create a post with template = single-feature.php and newspack_featured_image_position = above, behind, or beside (any single-featured-image position; beside matches the original report).
3. Insert a wide-width image block in the body.
4. View the published post on the front end at a viewport ≥ tablet.

Before: the figure width equals .entry-content width (~780px on a 1400px viewport, no negative-margin escape).
After: the figure width is ~1090px with margin: 0 -155px (escape via the existing alignwide rule). No horizontal scrollbar – the overflow: clip from #2667 still applies.

Tested locally with newspack-theme HEAD (v2.21.1 + this patch) using a single-feature + featured-image-beside post both with and without the span wrapper:

	Wrapped in .everlit-audio	Unwrapped (regression check)
Figure width	780 → 1090px	1090px (unchanged)
Figure margin	0 → 0 -155px	32px -155px (unchanged)
Horizontal scrollbar	none	none

Other information:

• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your changes, as applicable? – CSS-only change; visual screenshots above stand in for tests.
• Have you successfully ran tests with your changes locally?

Filed as a hotfix off release since publishers on Atomic are already affected. Forward-port to trunk to follow once this lands.

🤖 Generated with Claude Code

[github-actions]

🎉 This PR is included in version 2.21.2-hotfix-wide-width-everlit-wrapper.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[github-actions]

🎉 This PR is included in version 2.21.3-hotfix-wide-width-everlit-wrapper.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀