4grayandClaude Opus 5 d3b52cf574 fix(portals): tell a superseded pinned play from an unusable pin ...

Double-clicking Play while a pinned source resolves put both handlers into
`playPinnedSource()`. The second supersedes the first, so the first returned
`false` — which the route read as "no usable pin" and answered by starting the
route source over the playback the second click had just begun.

`playPinnedSource` now reports `played` / `superseded` / `unavailable`, and
only `unavailable` falls through. This is the same distinction `runFailover`
already draws between "keep going" and "stop, something newer owns the screen";
the pinned path simply never had it.

The host crossed the 400-line cap again on the way, so the pinned-play errand
(wait out an in-flight discovery, re-check the session, start the source) moved
into the pin module beside `playPinned`, and the pin-toggle commit went with
it. 388 lines.

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

2026-07-28 23:47:03 +02:00

..

architecture

fix(portals): tell a superseded pinned play from an unusable pin

2026-07-28 23:47:03 +02:00

superpowers

test(performance): add end-to-end Xtream benchmark harness (#1300)

2026-07-28 08:08:07 +02:00