Not switched on
Useful1 Signal3
Live artifact watches could refresh their connection token in place, but the server never says they can.
Token renewal for live artifact subscriptions is implemented but only runs when the server marks a subscription renewable, which nothing does.
What's wrong with this entry?
Anonymous. No account, no email.
What
A new call renews the token for an artifact's live update channel instead of tearing down and re-establishing the whole subscription. The client only takes that path when the subscribe response marks the subscription renewable, and nothing in the client sets that field, so the code ships inactive until the artifact service starts returning it.
Details
- Renewal posts to
/api/frame/watch-token/<slug>; a failure is reported as a renewal miss and the old re-subscribe path is used.
Evidence
watchTokenRenewEnabled
Strings lifted out of the shipped bundle, so the claim above can be checked against them.