3.9.0 Beta 22: Event Feed Continuity

Included changes

01Developers can inspect the current bounded feed window or explicitly resume from a locally saved opaque cursor.
02The continuity report identifies observable duplicates, chronological regressions, checkpoint overlap and initial-window truncation.
03Checkpoint import and export uses a strict versioned JSON contract with a bounded history of 100 public event identifiers.
04Request state, local-storage state and progressive event disclosure remain explicit and keyboard operable on compact screens.

01A clean returned window does not prove exhaustive monitoring, network delivery or the absence of events outside the public feed window.
02The lab does not provide endpoint registration, subscriptions, push delivery, server-side replay storage, delivery receipts or an SLA.

01Developers can inspect the current bounded feed window or explicitly resume from a locally saved opaque cursor.
02The continuity report identifies observable duplicates, chronological regressions, checkpoint overlap and initial-window truncation.
03Checkpoint import and export uses a strict versioned JSON contract with a bounded history of 100 public event identifiers.
04Request state, local-storage state and progressive event disclosure remain explicit and keyboard operable on compact screens.

01A clean returned window does not prove exhaustive monitoring, network delivery or the absence of events outside the public feed window.
02The lab does not provide endpoint registration, subscriptions, push delivery, server-side replay storage, delivery receipts or an SLA.