fix(seo): include coding solution source in initial HTML

[MuslumYilmaz]

Free coding and debug pages previously omitted structured solution source from their initial HTML until the Solution tab was opened. Render all available JS/TS approaches, HTML/CSS blocks, and framework files as real <pre><code> content while keeping Description selected and preserving the existing language/file visibility rules and lazy desktop Monaco editors.

Framework routes now await the current free solution asset through ASSET_READER and transfer only that normalized snapshot for the first browser render. Premium and pending Pressure Mode solutions stay gated; missing assets retain browser fallback, and existing entitlement/race protections remain in place. Backend APIs, catalog schemas, URLs, and premium SEO policy are unchanged.

Validation:

• All 1,555 frontend unit tests passed, including the 135 focused resolver/component tests for snapshot consumption, asset errors, access revocation, stale requests, pressure isolation, and course warning Cancel/Confirm/analytics.
• All 97 focused production Playwright cases passed across targeted runs; the final source/visual run passed 77/77. Real HTML source was checked against all 75 free coding/debug pages, including every framework file. Interaction coverage includes copying, language/file selection, explicit loading, draft preservation, resizing, navigation, and browser back.
• All 91 critical Chromium E2E tests passed in the pre-push hook. WebKit was unavailable on this macOS version and was skipped using the repository's existing override.
• Compared 57 before/after screenshots at 360, 390, 767, 768, 834, 1366, and 1440px. 47 are pixel-identical; the remaining 10 differ by 4–28 border-antialiasing pixels only, with no layout/content change.
• Production build prerendered 615 routes; the full SEO prerender guard passed. Premium index intent and withheld solution HTML/snapshots passed. Content regressions and the 165-page premium preview audit passed.
• Initial JS grew by 28 bytes; generated HTML grew by 434,905 bytes (about 0.44%).

Existing validation failures reproduced on the baseline: npm run perf:contract -- --strict --no-write exceeds four existing budgets (coding hub, total HTML, Sentry, showcase heavy chunks); the separate premium progress-bar SEO test expects obsolete threshold text. Neither is introduced by this change. Non-Chromium and authenticated premium browser coverage remain outside the focused run.

After production deployment, verify JS coding, React coding, Angular debug, HTML/CSS, and Vue examples using Search Console's live URL test and confirm solution source in Google's rendered HTML without opening the Solution tab.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
frontendatlas	Ready	Preview	Oct 6, 2026 4:38am UTC
frontendatlas-be	Ready	Preview	Oct 6, 2026 4:38am UTC
frontendatlas-fe	Ready	Preview	Oct 6, 2026 4:38am UTC