[miguel-heygen]

Problem

When a sub-composition script fails to load, the engine knows where it came from and why ([script_load: cdn/net::ERR_NAME_NOT_RESOLVED]), but it put that closed tag at the END of a warning that also carries the failing URLs and the page's error text. The render's error (RenderQualityError) runs each warning through redactTelemetryString, which cuts long strings, so on any real failure the tag is the part that is cut: the CLI's final error box ends in [script_load: remote/net::ERR_…. A host app reading the CLI's error cannot tell a blocked CDN from a missing local file.

Change

The tag now follows the sentence's head, before the free text: A sub-composition timeline script failed to load [script_load: origin/code] (sources). Same words and same content, different order; nothing else reads the old position (the one test that did is updated).

Verified

• engine frameCapture-scriptLoadCause.test.ts: 8 pass; the changed test fails on main (the tag is not at the head).
• Real check: a 9:16 project whose head GSAP URL is unreachable renders into this error. A 374-character warning in the old order loses the tag through redactTelemetryString; in the new order the tag survives. (Run against the released 0.9.16 CLI for the old order and core's redaction function for the new.)
• Formatted with oxfmt; the repo lint hook was not run (no local install).

fails without the fix: names the closed origin and code of each failed script before the free text, so a cut message keeps them

Why it ships alone: it is the one-line move that lets Desktop name why 65 exports failed this week (36 people); nothing else is queued in the engine to carry it, and each release without it keeps those failures unexplained.

[heygengenesis]

Verdict: APPROVE · 0 blocker · 0 important · 0 nits · head 1d94fd48

Scope

Read the whole diff. scriptLoadCauseSuffix has only the one caller, so no other message carries the tag at the end. With no causes, the suffix is empty and the message reads failed to load (…). I checked the fails-without-fix line: with main's frameCapture.ts, the named test fails and the other 7 pass. At head, all 8 pass. I also ran a probe through redactTelemetryString: a local and a CDN URL, plus a 300-character page error. On main, the cut ends at …gsap.min.js, runtime-error:… and the tag is gone. At head, [script_load: remote/net::ERR_NAME_NOT_RESOLVED, cdn/http-503] survives, and the path redaction leaves the tag alone. CI was still running when I approved, with no failures so far.

— Genesis V2 reviewer

[github-actions]

Edit accuracy: accurate 267 (base branch 267), smooth 109 of those

The gate passes.
Smoothness is reported in the artifact, not gated. A case fails only if it fails 2 of 3 runs.

Quarantined, measured but not gated (8)

• seqplainkeys-none-center-r0-nested-z100 (fixed by studio: undo/redo on a keyframed plain element sometimes leaves the box 230-400px off (edit-accuracy seqplainkeys-none-*) #6989): pass, passes
• seqplainkeys-none-center-r0-root-z100 (fixed by studio: undo/redo on a keyframed plain element sometimes leaves the box 230-400px off (edit-accuracy seqplainkeys-none-*) #6989): fail / pass / pass, passes
• seqplainkeys-none-center-r30-root-z100 (fixed by studio: undo/redo on a keyframed plain element sometimes leaves the box 230-400px off (edit-accuracy seqplainkeys-none-*) #6989): not run
• seqplainkeys-none-pct-r0-root-z100 (fixed by studio: undo/redo on a keyframed plain element sometimes leaves the box 230-400px off (edit-accuracy seqplainkeys-none-*) #6989): fail / pass / pass, passes
• seqplainkeys-none-pct-r30-root-z100 (fixed by studio: undo/redo on a keyframed plain element sometimes leaves the box 230-400px off (edit-accuracy seqplainkeys-none-*) #6989): not run
• seqplainkeys-none-px-r0-nested-z100 (fixed by studio: undo/redo on a keyframed plain element sometimes leaves the box 230-400px off (edit-accuracy seqplainkeys-none-*) #6989): pass, passes
• seqplainkeys-none-px-r30-nested-z100 (fixed by studio: undo/redo on a keyframed plain element sometimes leaves the box 230-400px off (edit-accuracy seqplainkeys-none-*) #6989): not run
• seqplainkeys-none-px-r30-root-z100 (fixed by studio: undo/redo on a keyframed plain element sometimes leaves the box 230-400px off (edit-accuracy seqplainkeys-none-*) #6989): not run

Unstable (2)

• seqrepeat-none-center-r0-nested-z100: tracking 0.05, pressJump 0, drop 0, reload 0, render 0.02, renderKey -, undo true, teleport true / tracking 0.05, pressJump 0, drop 0, reload 0, render 0.02, renderKey -, undo true, teleport true / tracking 0.05, pressJump 0, drop 0, reload 0, render 0.02, renderKey -, undo true, teleport true
• seqfastkeys-none-px-r0-root-z100: tracking 0.07, pressJump 0.05, drop 0, reload 0, render 0.02, renderKey -, undo false, teleport true / tracking 0.06, pressJump 0.05, drop 0, reload 0, render 0.02, renderKey -, undo true, teleport true / tracking 0.06, pressJump 0.05, drop 0, reload 0, render 0.02, renderKey -, undo true, teleport true