Exclude StorageBuffer from device.buffers tracking

[slimbuck]

Summary

StorageBuffer registers itself in GraphicsDevice.buffers but does not implement either loseContext() or unlock(), which causes a WebGPU device-lost flow to throw on iteration:

// graphics-device.js: loseContext()
for (const buffer of this.buffers) {
    buffer.loseContext();   // TypeError on StorageBuffer
}
// graphics-device.js: restoreContext()
for (const buffer of this.buffers) {
    buffer.unlock();        // TypeError on StorageBuffer
}

[Copilot]

Pull request overview

This PR addresses a WebGPU device-lost crash caused by StorageBuffer being tracked in GraphicsDevice.buffers without implementing the loseContext() method that GraphicsDevice.loseContext() expects to call for all tracked buffers.

Changes:

• Add StorageBuffer.loseContext() to forward device-lost handling to the underlying implementation.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.