pastilhasandClaude Opus 5 cb7ab55cca stop asking what was playing, and say what the socket is doing ...

Two things.

The music now-playing restore is disabled on the web. The music sidecar is not running on
every machine that serves this app, so every page load fired /music/now-playing and logged a
503 in the console of a browser that was not there for music. Restoring a paused track is a
nicety; a permanent error on every load of every screen is not. The player is untouched — it
simply no longer asks what WAS playing.

And the chat socket now logs its own lifecycle: create, open, close with code and whether it
was stale or tearing down, every message received, and every message sent or queued with the
socket readyState. window.__officerWs = false turns it off.

This is instrumentation I should have added two rounds ago. A pane connects and then sits
silent, and I have now reasoned from this hook source three times without explaining it — the
browser says a socket closed and never says who closed it or whether the message left. The
handover doc says instrument before theorising and I did not follow my own note.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-08-10 22:33:56 +01:00

..

src

stop asking what was playing, and say what the socket is doing

2026-08-10 22:33:56 +01:00

package.json

first

2026-02-16 19:34:35 +00:00