The warm-refresh gate (#743) serves the prior complete snapshot when the lock times out or is unavailable, which is correct and fail-closed, but the payload's only time field is the render timestamp, so a stale serve is indistinguishable from a fresh parse. Bounded (self-heals within one refresh cycle) and the served data is real known-good history, so accepted for 0.9.18 per the review's judgment; this tracks surfacing an as-of marker so surfaces can render staleness honestly.
The warm-refresh gate (#743) serves the prior complete snapshot when the lock times out or is unavailable, which is correct and fail-closed, but the payload's only time field is the render timestamp, so a stale serve is indistinguishable from a fresh parse. Bounded (self-heals within one refresh cycle) and the served data is real known-good history, so accepted for 0.9.18 per the review's judgment; this tracks surfacing an as-of marker so surfaces can render staleness honestly.