[miguel-heygen]

What changed

The doc comment for probeRequiresBrowser now sits directly on that function. A recent change inserted two helpers between the comment and the function, so the long comment described the wrong one. The comment is also cut to its one load-bearing fact.

What I measured

Comment-only diff: 4 lines added, 13 removed in probeStage.ts. oxfmt --check and oxlint are clean on the file. The comment ratchet reports a lower comment share for the file than before.

What I did NOT exercise

No behaviour changes, so I ran no tests or type check locally; CI runs them.

Size

17 lines, comment only. It is a review nit on a change that has already merged, and I have no other open change in this repository to carry it.

[github-actions]

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

[heygengenesis]

Approving at e9ead56d. No blockers.

• The change touches only comments in probeStage.ts. probeRequiresBrowser's doc comment now sits on probeRequiresBrowser again, and checksVariablesInBrowser keeps only its own one-line doc. This resolves the nit I left on #7548.
• This is not a fix PR, so it does not need a fails without the fix: line.
• CI at this head: CI, regression, Windows render, Comments, CodeQL and the captures all pass.

Non-blocking: the shortened comment drops the R4 caveat. A known-duration, media-free composition that builds many nodes in its init script is measured statically and must never reach the band's applied cohort. That is the non-obvious invariant behind this predicate. If a later change wants it back, a short pointer to resolveDeShortBand would keep it findable without raising the file's comment share much.