fix: pin three.js to 0.182.0 for THREE.Clock deprecation (#204)

[Interstellar-code]

Closes #204

What

Pins three from ^0.184.0 to 0.182.0 to eliminate the THREE.Clock deprecation warning in the browser console.

Root Cause

THREE.Clock was deprecated in three.js r183. The project was on 0.184.0, which triggers:

THREE.Clock: This module has been deprecated. Please use THREE.Timer instead.

This warning originates inside @react-three/fiber (v9.6.1, latest stable), which constructs new THREE.Clock() internally in its render loop. The project source code does not use THREE.Clock directly -- it uses R3F's state.clock API (state.clock.elapsedTime, state.clock.getElapsedTime()).

Why pin instead of upgrading R3F?

• R3F 9.6.1 (latest stable): still uses new THREE.Clock() internally -- no fix available
• R3F 10.0.0-alpha.2: drops THREE.Clock (uses performance.now() instead), but is alpha -- not appropriate for production
• R3F issue #3741 tracks this; the fix is targeted for the next major version

Pinning three.js to 0.182.0 (last version before r183 deprecation) is the pragmatic fix that keeps everything on stable releases.

Files Changed

• package.json -- three version pinned from ^0.184.0 to 0.182.0
• pnpm-lock.yaml -- lockfile updated

Compatibility

• @react-three/fiber peer: >=0.156 -- 0.182.0 satisfies
• @react-three/drei peer: >=0.159 -- 0.182.0 satisfies
• @react-three/postprocessing peer: >=0.156 -- 0.182.0 satisfies

Test Output

All three checks produce identical results before (0.184.0) and after (0.182.0) the change:

Check	Result	Pre-existing?
pnpm tsc --noEmit	9 TS7016 errors for three (no bundled types) + other pre-existing errors	Yes -- same on 0.184.0
pnpm lint	20268 pre-existing problems	Yes -- same on 0.184.0
pnpm test	7 failed / 118 passed (34 tests failed, 1199 passed)	Yes -- same on 0.184.0

No new failures, no new errors introduced by this change.