v0.27.1

fix(daemon): persist refreshed runtime token to the on-disk JWT cache.

The daemon refreshed its runtime JWT in-memory on a 401 but never wrote it back
to daemon.jwt, so readers of the on-disk token (the per-session credential
resolver and the runner's platform client) kept presenting the stale token —
the platform then 307-redirected credential snapshots to an HTML login page and
401'd status updates. The refresh now persists a complete CachedJWT
(token + expiry + cadence) via SaveCachedJWT after every successful
refresh/reregister, best-effort.

🤖 Generated with Claude Code