mirror of
https://github.com/CopilotKit/CopilotKit.git
synced 2026-09-14 16:26:20 +08:00
5c7c82db46
Normalize the migration schema comments to reality: the heartbeat is 45s (not the stale "~30-60s"), retention prunes by stable row id (robust to same-millisecond observed_at ties) rather than a bare timestamp cutoff, and document the null-vs-unavailable convention — the nullable number fields store `null` for the `-1` "unavailable" sentinel so post-wedge queries cleanly separate a measured reading from an unavailable one.