4grayandClaude Fable 5 c248f9a615 fix(stalker): record credentials in the imported session fingerprint ...

The import composed the fingerprint from endpoint and identity only, while the
runtime computes it from the playlist — which carries the credentials too. So
the first `ensureToken()` after importing a login-required portal mismatched
the fingerprint the import had just written, refused the token and repeated
the whole handshake/profile/do_auth flow, silently defeating reuse for exactly
the portals this work exists for.

Also refreshes the mock-server instructions the change invalidated: the README
still described the client `do_auth` path as dormant and HTTP-only, and two
comments still claimed the app sends `auth_second_step=1` on its first profile
request — it now sends 0 first and 1 only on the retry after do_auth.

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

2026-08-03 18:42:11 +02:00

..

electron-backend

feat(stalker): protocol-correct auth lifecycle

2026-08-03 18:41:54 +02:00

electron-backend-e2e

feat(downloads): queue season episode downloads (#1357)

2026-08-03 08:53:44 +02:00

remote-control-web

test(perf): add production renderer benchmark build

2026-07-26 22:37:52 +02:00

stalker-mock-server

fix(stalker): record credentials in the imported session fingerprint

2026-08-03 18:42:11 +02:00

web

feat(stalker): protocol-correct auth lifecycle

2026-08-03 18:41:54 +02:00

web-backend

fix(pwa): bring the Stalker transport to parity with Electron (#1348)

2026-08-02 14:51:36 +02:00

web-e2e

feat(stalker): protocol-correct auth lifecycle

2026-08-03 18:41:54 +02:00

website

docs(website): add unofficial sites post cover

2026-08-02 12:10:02 +02:00

xtream-mock-server

feat(downloads): queue season episode downloads (#1357)

2026-08-03 08:53:44 +02:00