THREE.JS / FOUNDATIONS 321

One extra import can break a release.

The pinned TSL Graph loader and current-dev loader do not expose the same module libraries. Compare the source contracts, execute only the pinned-safe fixture, and make unsupported code fail before evaluation.

Preparing compatibility fixture—

The pinned loader will evaluate one trusted three/tsl graph; current-dev-only and unknown imports stay source-only.

pinned: —
current-dev: —
fixture: —
storage: —
loader: —
rejections: —
backend: —
frame samples: —
timing: NOT RUN

pinned r185.1waiting

The installed loader exposes three/tsl only.

current-devwaiting

Current source adds three; this route records that as compatibility evidence, not a local runtime claim.

execution gatewaiting

Only the trusted pinned-safe fixture reaches the real loader and material applier.

storage boundarywaiting

The probe restores pre-existing tsl-graph* keys on reset/release.

compatibility event logwaiting

No import probes yet.

The compatibility matrix distinguishes reviewed, executable, and source-only rows; it does not silently upgrade the pinned dependency.

Sources: TSL Graph example · NodeLoader docs · current-dev loader source · WebGPURenderer docs

LAB 321 / TSL GRAPH IMPORT COMPATIBILITY