denokv

I follow the demo deploy on Fly.io and having the error "This machine has exhausted its maximum restart attempts (10).". It's because the access token isn't at minimum 12 chars long. I think in this case it shouldn't restart a lot, and the error log should be clearer, i.e. in red.

Adds KV Connect protocol version 4: a multiplexed watch channel. Today every call opens its own long-lived streaming request, so a client watching many key sets holds many concurrent streams, and every reconnect re-delivers state the client already has. Version 4 multiplexes all watches for a database over one WebSocket connection: Keys are added/removed in-band (), so the watched set changes without new connections. The message carries an optional baseline (last seen versionstamp, or "absent"); the server only sends state that differs from it. Re-adding all keys with their baselines after a reconnect makes resumption lossless and duplicate-free. Server messages are key-tagged and sparse (only changed keys), unlike the positional v3 . gains optional WebSocket support via defaulted methods, so this is semver-compatible: existing transports keep compiling, keep advertising , and keep the per-watch v3 path. Only transports that implement negotiate v4. Nothing changes for any current consumer until its transport opts in. The server gains the endpoint (axum ws) behind the same auth, diffs updates against per-client known state, enforces a per-channel key cap (1024, close code 1008), and pings every 5s. Metadata negotiation now prefers v4. The stream contract is identical under both protocols: first item is a full snapshot, later items mark untouched keys , in request key order — covered by integration tests that exercise the channel path (shared channel across watches, initial snapshots, per-key updates, re-subscription) next to the existing v3 test. Spec for the new endpoint and messages is in ("Watch Channel (version 4)").