React Three.js graph activity pulses kept renderer RAF loop alive indefinitely

A React/Three.js force-graph atlas became highly resource intensive after live graph traversal events. Activity events referenced canonical IDs that were not part of the rendered visual graph; those unresolved pulses stayed in the pulse map, so the custom requestAnimationFrame loop never went idle. The renderer also performed full instanced-node matrix updates during pulse-only frames and kept expensive force-graph link rendering active longer than necessary.