Recover a coherent source snapshot
Economic Calendar now restarts a snapshot read once when the source changes between requests. Partial pages are discarded, and the accepted view is committed only after the coherent read completes. Persistent conflicts retain the previous accepted view and remain visible as errors.
Linked Events adds the same bounded recovery to its map read. A map failure no longer gets overwritten by a success message from the surrounding load. Successfully recovered responses are acknowledged precisely; unrelated successful requests cannot hide unresolved snapshot failures.
Preserve map styling through recovery
The classic geopolitical map's boundary-width expression now conforms to the renderer's zoom-expression rules while preserving selected and unselected widths. The fix was verified across its lenses and forced graphics recovery.
In fullscreen, the source-card panel is now bounded and scrollable so it cannot consume all available map height. Source cards remain accessible. The existing Global Politics missing-layer interaction guard was also exercised directly before its historical report was considered resolved.
Keep retained event data collecting
Linked Events storage admission now uses SQLite allocation and live-page accounting rather than treating file length alone as live data. Existing retention rules run within the update transaction, returning event identities are protected, and the reviewed storage budget is bounded at 2 GiB.
The change was tested on a consistent isolated database copy and checked against production. Unexpired event identities and first-seen dates were preserved; no staged database was restored over production. Worker deadlines are nested within the parent budget, and capacity/deadline failures retain the previous accepted snapshot with clearer diagnostic messages.
Report what the measurement establishes
App Health now distinguishes browser-measured long tasks from event-loop timer gaps, which can also reflect page or device suspension. Genuine long-task reporting remains enabled. Diagnostics also capture the content-addressed loading-runtime version, making future reports easier to associate with the correct deployed code.
Issue status follows verification: a currently successful endpoint does not prove an old network failure was fixed. Unreproduced browser, session and upstream-source cases remain open for investigation. This update is not a claim that every possible browser or provider failure has been eliminated.