screentinker/server/ws
Claude ccbd63ba79 Stamp the authenticated device on relayed playback progress
device:playback-state was the only relay that forwarded the client's payload verbatim. The workspace
lookup correctly used currentDeviceId — the socket's authenticated device — but the object passed on
to the dashboard was whatever the player sent, including any device_id it chose to put there. So one
device could report playback progress attributed to a different screen in the same workspace, and
the dashboard had no reason to doubt it.

Every other relay in this file stamps the authenticated id. This one now matches.

882 server tests green.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Uaeo9MvzKoyXuN6ZsbhtkL
2026-07-30 22:41:06 -05:00
..
dashboardSocket.js refactor(auth): centralise session token resolution across manual verify sites 2026-07-24 20:58:05 -05:00
deviceSocket.js Stamp the authenticated device on relayed playback progress 2026-07-30 22:41:06 -05:00
index.js Initial open source release 2026-04-08 12:14:53 -05:00