[DennisSmolek]

Fixes #88.

UpscalerNode._configureUpscaler() rounded the seeded render size (drawingBufferSize / ratio). three's PassNode renders at Math.floor(size * (1 / ratio)). When the quotient's fraction was ≥ .5 (about half of all canvas sizes), the first configure reported a size one texel larger than the real input. Example: 1252×936 at Quality gave 835×624, but three renders 834×624. updateBefore re-synced later, but consumers that validate renderWidth/renderHeight on the first frame saw the mismatch.

Change

• New internal helper getPassRenderResolution (src/math/resolution.ts; not exported from the package) uses three's own arithmetic. For the preset ratios it gives the same result as getRenderResolution at every size up to 8192, which a test pins. For custom ratios it follows three, e.g. 39 * (1 / 1.3) → 29 vs 39 / 1.3 → 30.
• The node seeds _input from that helper, and _configureUpscaler floors instead of rounding.
• TemporalGuidesNode keeps Math.round. It only receives real (integer) texture sizes.

Verification

• New unit tests: the issue's repro case (1252×936 @ 1.5 → 834×624), the custom-ratio divergence, and agreement with getRenderResolution at the preset ratios.
• Lint on the changed files and the build pass locally. No shader or pass changes.

Ship as a patch release (fix: → auto resolves to a patch).

🤖 Generated with Claude Code