The artifact-watch supervisor that keeps a live connection open on a published artifact for auto-reply/reconnect logic can now open either the old websocket transport or a new sync transport, which has its own URL builder, dedicated ping-frame keepalive, and 404/expiry-based reconnect detection. Telemetry marks these connections with sync_transport: true in the artifact_live_subscribe event. The live-subscription bootstrap logic now distinguishes a lease's transport as live or sync, validates sync leases against stored credentials, and returns a new sync_unavailable outcome when sync can't be established.
Artifact live-subscribe gains a second, non-websocket "sync" transport
Live artifact connections can use a new sync transport alongside websockets, with its own keepalive and reconnect logic.
Nothing to try yetTier: how much it should matter to you
4Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
In DevelopmentKind: in v2.1.257,
What probably matters to youSection of the release
Names in the bundlesync_transport