[miguel-heygen]

What

The effect scan's loop no longer resolves its option defaults, which brings it back under the complexity limit. No behavior changes.

Why

#7331 split scanCssEffectLiveFrames so that its new end signal fires on every exit, and the inner loop came out at a CRAP score of 31.6 against a limit of 30. #7331 was already in the merge queue when the audit reported, so this follows it.

Related work

Follows #7331.

How

scanCssEffectLiveFrames resolves budgetMs, now and onProgress once and passes them to the loop. The loop no longer reads an options object, and it calls onProgress without the optional check.

Test plan

• Unit tests: riskFrames.test.ts, 19 passed, on the same code before it was rebased onto main.
• tsc --noEmit in packages/engine is clean.
• bunx fallow audit --base origin/main: verdict pass, 0 complexity findings.
• No behavior change, so there's no fails-without-the-fix test.
• Comments follow CONTRIBUTING.md "Comments".

Size

12 added lines and 5 removed in one file. It stands alone because #7331 had already merged.

[heygengenesis]

Approved at 66145876. I found no behavior change.

• The defaults (budgetMs, now, onProgress) still apply only when a value is undefined. Moving them into the outer signature does not change when they take effect. onProgress = () => {} makes the unconditional call in the loop equal to the old onProgress?.().
• onEnd is now read once when the call starts, where before it was read in finally. The only production caller (frameCapture.ts:1362) passes a fresh object literal, so the two behave the same.
• Locally at this head: riskFrames.test.ts 19/19 passed and tsc --noEmit in packages/engine is clean. The branch contains current main.
• This is a refactor, not a fix, so no fails-without-the-fix line is needed.

[github-actions]

Edit accuracy: accurate 267 (base branch 267), smooth 91 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): 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 (1)

• seqab-none-center-r0-root-z100: tracking 0.03, pressJump 0, drop 0, reload 0, render 0.02, renderKey -, undo true, teleport true / tracking 0.03, pressJump 0, drop 0, reload 0, render 0.02, renderKey -, undo true, teleport true / tracking 0.03, pressJump 0, drop 0, reload 0, render 0.02, renderKey -, undo true, teleport true