From 0338a193db183b0c9c56b69acd3be817edf3baf0 Mon Sep 17 00:00:00 2001 From: archipelago Date: Wed, 7 Oct 2026 07:22:15 -0400 Subject: [PATCH] Track federated node sync reliability and progress UX --- docs/post-1.9.0-work-backlog.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/post-1.9.0-work-backlog.md b/docs/post-1.9.0-work-backlog.md index d7ef1d93..80a55499 100644 --- a/docs/post-1.9.0-work-backlog.md +++ b/docs/post-1.9.0-work-backlog.md @@ -470,6 +470,12 @@ functional/UX review. These are additions to existing groups, not closed work. - Update relationship, request, availability and operation states automatically across screens without routine manual sync. Handle reconnect, missed events, out-of-order replies and failed refreshes without invented success states. +- Federated Nodes sync is currently reported as unreliable and slow. Diagnose + the actual transport, queue and reconciliation path; prevent indefinite + waits; show a loader with a useful phase/status message and elapsed progress; + provide bounded retry and a truthful success, partial-success or failure + result. Preserve the last known state while a refresh is in flight and make + the next retry safe and idempotent. - When a request changes the 3D map layout, rotate its node to the front, top centre and clearly expose the request action. Cover multiple requests, completion, user camera interaction, reduced motion and mobile viewports.