4grayandClaude Fable 5 9799558ad7 fix(stalker): apply the discovered cadence when a repair adopts its session ...

Lazy repair cached `outcome.token` and refreshed the watchdog, but dropped the
cadence its own confirmation profile had just reported. The retried request
then found the cached token, so no authentication path ever applied the
profile outcome and a freshly repaired playlist kept pinging on the default
until the token failed or the app restarted.

`adoptDiscoveredSession()` is the entry point for "another layer already
negotiated this session": it caches the token, applies the cadence and
persists both, keyed to the REPAIRED configuration since the session belongs
to the endpoint it was negotiated against.

Also removes the contradictory watchdog contract from the same document — the
portal-mode summary still said pings run every 25 s with 120 s deferred, while
the lifecycle section below it documents the implemented profile-driven
cadence.

Applying the outcome moved into the session store (it already owns the
persisted half), which keeps the facade under the 400-line limit.

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

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

..

architecture

fix(stalker): apply the discovered cadence when a repair adopts its session

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

superpowers

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

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