pastilhasandClaude Opus 5
4b094aa3a5
nothing the player did ever reached jellyfin, so nothing ever appeared in continue watching or in the currently-playing list. the proxy was fine — a progress POST through the sidecar moves the resume point upstream and answers 204. the client was the problem. useClient() rebuilds its verbs on every render, so `report` had a new identity every render, so `sendReport` did, so the effect whose cleanup reports the final position re-ran on every render — and that cleanup nulls planRef. planRef went null a few milliseconds after the stream opened and every report after that returned early. the ten-second heartbeat never fired either: its interval was cleared and restarted on every render, and timeupdate renders about four times a second. both are now held in refs, and the two effects have honest dependency lists. same treatment for the negotiate mutation, which react query also rebuilds per render. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>