The InstancedMesh feature encountered a graphics rendering issue in the r185 version of webGPU, but it did not have this problem in the r184 version.

### Description Screenshot of the question: webGPU: <img width="910" height="666" alt="Image" src="https://github.com/user-attachments/assets/e4c97889-eeeb-48c5-be24-1e4ef1b674a7" /> Using the 'outline' option to draw the object will make it visible. <img width="562" height="426" alt="Image" src="https://github.com/user-attachments/assets/554557be-deea-44bb-b265-04926f44e797" /> webGL:(It should be emphasized that version r185 works fine in WebGL.） <img width="1886" height="704" alt="Image" src="https://github.com/user-attachments/assets/94a92779-80b0-4444-b88b-5ef9f5dfe06a" /> <img width="1902" height="612" alt="Image" src="https://github.com/user-attachments/assets/ee0bcf53-a553-4e80-a5fc-8b0942d3eca9" /> ### Reproduction steps The source code cannot be posted, but the objects to be used can be informed. const param: WebGPURendererParameters = { alpha: true, depth: true, stencil: true, logarithmicDepthBuffer: true, // reversedDepthBuffer: true, // forceWebGL: true, } new THREE.WebGPURenderer(param) ... material = new THREE.MeshBasicNodeMaterial({ transparent: true }) ... new THREE.InstancedMesh(...) ... iMesh.count = index + 1 ... iMesh.setMatrixAt(index, matrix) ### Code ```js // code goes here ``` ### Live example ..... It is particularly important to note that r184 does not have this issue at all!!! ### Screenshots _No response_ ### Version r185 ### Device Desktop ### Browser Chrome ### OS Windows