The revert is correct and well-scoped. Here's the summary:

What changed: PR #6902 rendered window.remotion_logLevel unconditionally in the bundle HTML. This caused the inline script to override the value set later by setPropsAndEnv() via evaluateOnNewDocument, because inline scripts execute before evaluateOnNewDocument.

This PR's fix:

1. bundler/src/index-html.ts — only renders window.remotion_logLevel in dev mode (mode === 'dev'), removing it from bundle mode
2. core/src/index.ts — widens the type to LogLevel | undefined to match the new reality
3. All read sites in studio/src/Studio.tsx, studio/src/renderEntry.tsx, core/src/delay-render.ts, and web-renderer/ add ?? 'info' as a safe fallback

Verified: I confirmed all 9 read sites of window.remotion_logLevel across the codebase are covered with the fallback. The web-renderer files already had a triple-chain (options.logLevel ?? window.remotion_logLevel ?? 'info') that correctly handles the undefined case. The set-props-and-env.ts write site in bundle mode remains unchanged — it sets the value before the page loads, which is correct.

In bundle mode, the flow is now: setPropsAndEnv() sets window.remotion_logLevel via evaluateOnNewDocument → page loads → read sites use that value. If somehow neither sets it, 'info' is the fallback. In dev mode, the inline script still sets it as before.

No issues found. This is a clean revert.

  ^{｜ View workflow run ｜ pullfrog.com ｜ 𝕏}